project-e5a5d1e7
Shivhari 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.
Comments (0)
Sign in to leave a comment
Technical Requirements Document
Precise CLI invocation contracts, environment configuration, ten safety invariants, MOCK_AGENT test mode, and deployment constraints for Job Pilot v2. This document serves as the technical backbone for all build phases.
Document Scope
This TRD captures the non‑negotiable runtime contracts for Job Pilot v2. It defines how developers invoke the application from the command line, which environment variables are mandatory, how the mock agent test mode works, and the ten safety invariants that must hold across every build phase. By the end of this document you will have a clear checklist to validate each delivery phase.
- CLI invocation and environment setup
- MOCK_AGENT=1 endpoint smoke testing
- 10 non‑breakable safety invariants
- Deployment constraints and port binding
CLI Invocation Contracts
Job Pilot v2 is started directly from the command line using Node 26. There is no package manager, no build step, and no external dependencies. The following contracts define exactly how developers launch the application in development, test, and production modes.
node index.jsMOCK_AGENT=1 node index.jsEnvironment Variables
| Variable | Required | Description |
|---|---|---|
| MOCK_AGENT | No | Set to 1 to enable simulated external service responses. Required for endpoint smoke tests. |
| OLLAMA_OVERRIDE | Yes | Mandatory override for Ollama environment configuration. Must be set to a valid local path. |
| CLAUDE_SUBSCRIPTION | Required in production | Authentication token for Claude Code CLI. Not needed when MOCK_AGENT=1. |
10 Safety Invariants
These ten invariants must hold true in every commit, every build phase, and every deployment. They are non‑negotiable and define the architectural boundaries that keep Job Pilot v2 stable and predictable.
Zero npm dependencies
The entire codebase relies only on Node 26 built‑ins. No package.json or node_modules folder exists.
Atomic writes
All JSON file collections use atomic write operations (write-then-rename) to avoid corruption.
Port 7878 binding
The HTTP server must start on port 7878. Any deviation is a critical error.
Local-only operation
No network calls to external services except the Ollama override and BrowserClaw MCP on localhost.
Non-interference with v1
Job Pilot v2 must not read, write, or lock files in the ~/JobPilot directory.
MOCK_AGENT=1 isolation
When MOCK_AGENT=1, all external integrations return canned responses; no real HTTP calls are made.
Human submit gate
Every final application submission must be explicitly confirmed by a human via the UI; no automated sending.
Ollama override mandatory
The OLLAMA_OVERRIDE environment variable must be set; the app will refuse to start without it.
JSONL event log integrity
All event logs are appended in JSONL format. Each line is a complete, parseable JSON object with a timestamp.
BrowserClaw MCP access control
The MCP endpoint at http://127.0.0.1:9000/mcp is firewalled to accept connections only from localhost.
MOCK_AGENT=1 Test Mode
The MOCK_AGENT=1 flag transforms Job Pilot v2 into a fully deterministic test harness. All external calls (Ollama, BrowserClaw, Claude) return pre‑defined responses, enabling developers to validate endpoint behaviour without live dependencies.
How to Run Tests
- Open a terminal in the
app/directory. - Set the environment:
export MOCK_AGENT=1 - Launch the server:
node index.js - Run the smoke test suite (built‑in) or hit the endpoints manually at
http://localhost:7878.
MOCK_AGENT=1 node index.jsSmoke Test Scenarios
| Scenario | Expected Behaviour |
|---|---|
| Syntax check | All modules load without syntax errors |
| GET /health | Returns { "status": "ok" } |
| POST /api/application | Returns mock submission result with status 200 |
| UI load | The dashboard loads without JavaScript errors |
Deployment & Runtime Constraints
These constraints govern how Job Pilot v2 is deployed, run, and tested. Violating any of the critical constraints will result in a non‑functional application. The development environment, CI (if any), and local machines must all satisfy these rules.
Port 7878
Hard‑coded port; cannot be changed via configuration.
Zero npm dependencies
No package.json, no node_modules. Only Node 26 built‑ins.
Local-only
No outgoing requests except to localhost (BrowserClaw MCP) and Ollama override.
Isolation from v1
Must not touch files under ~/JobPilot. All data written inside JobPilot-v2 directory.
Subscription login
Claude Code CLI requires a valid subscription token stored as environment variable.
MOCK_AGENT=1 for testing
All build phases must pass smoke tests with mock agent enabled.
Context
Vision, hard constraints, and non-negotiable requirements that shape every build decision in Job Pilot v2.
Non-Negotiable Requirements
These constraints govern every architectural and implementation decision in Job Pilot v2.
Zero npm Dependencies
Built exclusively with Node 26 built-ins. No external packages allowed in the dependency tree.
Port 7878
Deployed on port 7878, ensuring no conflict with the existing Job Pilot v1 at ~/JobPilot.
Local-Only Operation
Runs entirely on localhost with BrowserClaw MCP at 127.0.0.1:9000/mcp. No cloud services.
JSON-File Storage
All persistence uses JSON-file collections with atomic writes and JSONL event logs.
10 Safety Invariants
Mandatory safety rules from the TRD that cannot be violated under any build phase.
MOCK_AGENT=1
Required test mode for running endpoint smoke tests after completing each delivery phase.
Documentation Inventory
Every specification, contract, and reference that feeds into the build.
docs/01-brd.mdBusiness Requirementsdocs/08-cloudhire-research.mdCloudHire ResearchBuild Workflow
The sequential path every developer follows from context reading to deployment logging.
No comments yet. Be the first!