prosa-dev-workflowlisted

# Prosa Dev Workflow Use this skill for repository orientation, command selection, and everyday implementation hygiene. ## Module shape Single Go module: `github.com/c3-oss/prosa`. Three binaries built from `cmd/`: - `cmd/prosa` — local CLI. - `cmd/prosa-server` — Connect API server (Postgres + S3-compatible). - `cmd/prosa-panel` — server-rendered web panel (html/template + HTMX). Core paths: - `proto/prosa/v1/` — protobuf source of truth. - `gen/go/prosa/v1/` — Buf-generated Go, committed. - `pkg/importer/` and `pkg/session/` — exportable plugin interface and domain types. - `internal/importers/<agent>/` — Claude Code, Codex, Cursor, Gemini importers. - `internal/store/` — SQLite local store, migrations, FTS5 queries. - `internal/cli/` — Cobra command tree, rendering, sync, search, show. - `internal/server/` — Connect handlers, Postgres + S3 wiring. - `internal/panel/` — html/template + HTMX views. - `internal/paths/` — XDG-aware filesystem layout (the only package that knows where data lives). - `docs/` — operational manual (architecture, source formats, design briefs, distribution). Read `INTENT.md` end-to-end before changing scope or architecture. For the real shape of the code, start at `docs/architecture/README.md`. ## Command surface Standard workflow via `.justfile`. There is no Makefile. ```bash just build # builds prosa, prosa-server, prosa-panel into ./bin just run -- ... # builds, then runs ./bin/prosa with args just test #