project-e5a5d1e7

byShivhari Lokhande

# Job Pilot v2 — Build Prompt (paste into a fresh Cowork session) First connect the folder `JobPilot-v2` from your home directory, then paste everything below: --- Build the Job Pilot v2 application from scratch. The complete, binding specification already exists in the folder I've connected (`~/JobPilot-v2`) — do not redesign or re-scope anything, implement exactly what the documents say. **Read in this order before writing any code:** 1. `docs/00-context.md` — vision + hard constraints (local-only, Claude Code CLI with subscription login and the mandatory Ollama env-override, BrowserClaw MCP at http://127.0.0.1:9000/mcp, human submit gate, zero npm dependencies) 2. `docs/02-prd.md` — features and acceptance criteria (P0 first, then P1) 3. `docs/05-architecture-hld.md` + `docs/06-lld.md` — architecture, module tree, data model, REST + SSE contracts, prompt catalog. Follow the LLD literally. 4. `docs/07-trd.md` — CLI invocation contracts, MOCK_AGENT=1 test mode, safety invariants with named tests 5. `docs/03-ux-spec.md` + `design/prototype.html` — the UI must visually match the prototype (same design tokens, layout, components). Open the prototype and reuse its CSS as the starting point. 6. `docs/04-delivery-plan.md` — build in its phases with its definition-of-done gates: Phase 0 scaffold/store/adapters → Phase 1 P0 modules in dependency order (Profile → Discovery → Evaluation → Tracker → Tailoring → Apply → Auto-Pilot) → Phase 2 P1 (Interviews, Resume templates) → Phase 3 hardening + QA checklist 7. `docs/01-brd.md` and `docs/08-cloudhire-research.md` — background reference only **Execution rules:** - Create the app in a `app/` subfolder of this same connected folder; deploy/run on port 7878; do NOT touch the existing v1 at ~/JobPilot - Zero npm dependencies (Node 26 built-ins only), per ADR-02 storage is JSON-file collections with atomic writes + JSONL event logs — no SQLite - After each phase: run syntax checks, endpoint smoke tests with MOCK_AGENT=1, and confirm the UI loads before proceeding - The 10 safety invariants in the TRD are non-negotiable: the agent never clicks submit, never stores credentials, stops on CAPTCHA/2FA - At the end: start the server, verify http://localhost:7878 serves the app, run the QA checklist from the delivery plan, and give me a short acceptance report Track progress with a task list per phase. If a document is ambiguous, resolve it in favor of the LLD, and log the decision in `docs/09-build-decisions.md` rather than asking me.

ContextTRDPRD
Context

Comments (0)

No comments yet. Be the first!

Architecture

No Services Diagrams Yet

Architecture diagrams will be automatically generated when the Project Manager creates tasks for your project.

Context design preview
Context: Read Constraints
PRD: Review Features
Architecture: Study HLD
Architecture: Study LLD
TRD: Review Contracts
TRD: Check Invariants
UXSpec: Match Prototype
DeliveryPlan: Follow Phases
DeliveryPlan: Run Tests
BuildDecisions: Log Decisions
Context design preview
Context: Read Constraints
PRD: Review Features
Architecture: Study HLD
Architecture: Study LLD
TRD: Review Contracts
TRD: Check Invariants
UXSpec: Match Prototype
DeliveryPlan: Follow Phases
DeliveryPlan: Run Tests
BuildDecisions: Log Decisions