dev-docs (the in-app product is called Plan Builder) is a Tauri desktop app for vibe-coders — people who know what they want to build but struggle to articulate it technically. You have a plain-English conversation with an LLM; it reads your actual codebase via RAG; and it generates a structured, agent-executable plan in the dev-docs template format. The plan lands on disk ready for an AI coding agent to execute — no manual writing required.
Three screens: Chat (bui, ld a plan), Repos (index a local codebase), Settings (API key + model).
dev-docs/ ← Tauri desktop app (source)
dev/
plans/ ← Active and archived development plans
roadmap/ ← Project-level direction and vision
dev-docs-design-system/ ← Brand & UI design system (source of truth)
package.json ← Root scripts (dev, build, sidecar)
| Layer | Technology |
|---|---|
| Desktop runtime | Tauri 2 (Rust) |
| Frontend | React 19 + TypeScript + Tailwind CSS + Vite + shadcn/ui |
| Icons | lucide-react |
| AI sidecar | FastAPI + Python 3.11+ |
| Vector store | ChromaDB via LlamaIndex |
| LLM provider | OpenRouter (DeepSeek-first) |
| Secrets | macOS Keychain via Tauri |
- Node.js 20+
- Rust (stable toolchain)
- Python 3.11+ with uv
- An OpenRouter API key
# Install frontend dependencies
npm install --prefix dev-docs
# Install Python sidecar dependencies
uv sync --project dev-docs/src-python# Start everything (Tauri dev server + frontend HMR)
npm run dev
# Or start the Python sidecar separately (for backend-only work)
npm run sidecarnpm run buildThis project uses a structured planning workflow. Before starting any work:
- Check
dev/plans/active-plan.mdfor what's currently in progress - Read
dev/roadmap/roadmap.mdfor project direction and constraints - New features are planned in
dev/plans/d-plns/before implementation begins
All plans follow the template in dev/plans/TEMPLATE-x-nnn-plan_name.md/.
See dev/roadmap/roadmap.md for the full feature map and vision.