# OpenSpec Instructions These instructions are for AI assistants working in this project. Always open `@/openspec/AGENTS.md` when the request: - Mentions planning or proposals (words like proposal, spec, change, plan) - Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work - Sounds ambiguous and you need the authoritative spec before coding Use `@/openspec/AGENTS.md` to learn: - How to create and apply change proposals - Spec format and conventions - Project structure and guidelines Keep this managed block so 'openspec update' can refresh the instructions. # Code Conventions See `CLAUDE.md` for canonical code conventions # Open Code Review Instructions These instructions are for AI assistants handling code review in this project. Always open `.ocr/skills/SKILL.md` when the request: - Asks for code review, PR review, or feedback on changes - Mentions "review my code" or similar phrases - Wants multi-perspective analysis of code quality - Asks to map, organize, or navigate a large changeset Use `.ocr/skills/SKILL.md` to learn: - How to run the 8-phase review workflow - How to generate a Code Review Map for large changesets - Available reviewer personas and their focus areas - Session management and output format Keep this managed block so 'ocr init' can refresh the instructions.