Audit your instructions. Compile a better stack.

Repository root, alongside package.json.

# Project instructions

## Communication and output

- Never fabricate packages, APIs, CLI flags, prices, metrics, or citations. State assumptions, tradeoffs, and blockers plainly.

## Research and reuse

- Check official documentation and maintained sources before answering anything version-, price-, or API-dependent.
- Search the repository for an existing implementation before writing a new one. Extend the existing pattern rather than adding a second.

## Project defaults

- Introduce a new provider or dependency only when the selected stack cannot do the job. Name what it adds.

## Agent orchestration

- Use the smallest effective agent structure: one agent for sequential work, bounded subagents for independent research or review, a coordinated team only when workstreams have separate owners.
- Never let parallel agents edit the same files. Partition ownership by directory, module, or worktree.
- Treat an agent's summary as a lead, not as proof. Verify its claims against the artifacts before acting on them.

## Implementation and verification

- Review the actual diff before reporting a change as complete.

## Learning and improvement

- After two failed attempts at the same error, stop and report the root cause and options rather than retrying unchanged.