context-engineering

# Context Engineering Feed the agent the right information at the right time. Too little context causes invented APIs; too much context hides the relevant pattern. ## Context Order 1. **Rules:** root `AGENTS.md`, scoped `AGENTS.md`, and any invoked skills. 2. **Spec/plan/ADR:** relevant `docs/specs/<slug>/spec.md`, `docs/plans/<slug>/plan.md`, needed `docs/plans/<slug>/task-*.md`, and `docs/decisions/`. 3. **Source:** exact files to modify, related tests, and one similar implementation. 4. **Evidence:** focused error output, failing test name, CI summary, screenshots, or logs. 5. **Conversation:** current user request and any confirmed decisions. ## Kandev Loading Checklist Before changing code: - Read the scoped `AGENTS.md` for the subtree you will touch, e.g. `apps/backend/AGENTS.md`, `apps/web/AGENTS.md`, or integration-specific guidance. - Use `rg` to find existing patterns before inventing one. - Read the file you will edit and nearby tests. - For product features, read the relevant spec and decision index. When implementing from a plan, read `docs/plans/<slug>/plan.md` for orientation and only the task file(s) needed for the current work. - For frontend/UI, include `/mobile-parity` and `/e2e` guidance when applicable. - For OpenAI/API docs or other fast-moving dependencies, use official docs or primary sources. ## Selective Context Patterns For a focused task, gather: ```text TASK: Add validation to the workspace import endpoint. RULES: apps/backend/AGENTS.md FI...