AI Coding Assistant
The main operating system for this vault is SPEC → MAP → BUILD → PROVE → LEARN. The developer's role is not merely code writer; it is system designer, direction giver, boundary setter, and verification designer.
Best working loop
- Give the assistant the goal, users, constraints, repository context, and definition of done.
- Ask it to inspect before editing and to state important assumptions.
- Request the smallest coherent implementation.
- Require proportional verification: tests, build, lint, typecheck, or manual checks.
- Review the diff and ask for risks, missing cases, and rollback notes.
- Save reusable lessons here; keep transient chat out of durable notes.
Task brief
Goal:
Why it matters:
Current behavior:
Desired behavior:
In scope:
Out of scope:
Constraints:
Relevant files/commands:
Acceptance criteria:
Verification required:Give context in this order
- Objective and definition of done
- Relevant source files and observed behavior
- Constraints and conventions
- Failed attempts and exact errors
- Permission boundaries
Warning signs
- A solution appears before repository inspection.
- The assistant invents APIs, files, test results, or citations.
- A refactor grows beyond the requested outcome.
- Tests only confirm implementation details, not behavior.
- Destructive or external actions occur without explicit scope.
See Prompt Library, Context Pack, and Agent Rules.