project-instructions-policylisted

# Project Instructions Policy ## Purpose Keep durable project instructions useful for future Claude Code sessions without turning them into chat history or generic advice. ## Rules - Create or update `AGENTS.md` when durable root-level project rules, setup commands, quality gates, architecture constraints, deploy contracts, or workflow guidance change. `AGENTS.md` is the cross-tool standard root project-instruction file (see https://agents.md/). - Keep `AGENTS.md` concise; it is loaded as a high-signal entry point and instruction size matters. - Create or update `.claude/CLAUDE.md` for fullrepo-managed projects so Claude Code has first-class project memory. - Keep `.claude/CLAUDE.md` optimized for Claude Code, not as a thin `@AGENTS.md` import. Reference Claude-specific locations when relevant: `.claude/settings.json`, `.claude/skills/`, `.claude-plugin/`, `/memory`, `/context`, `/hooks`, `/mcp`, `/permissions`, `/doctor`, `/status`. - Do not create root `CLAUDE.md` by default; `.claude/CLAUDE.md` is the rldyour project memory path. - Create or update `REVIEW.md` when review-specific rules are durable and materially help future review agents. - Create ADRs (MADR 4.0.0 format) for important architecture, technology, dependency, deployment, security, or irreversible design decisions. - Repository docs, instructions, ADRs, memories, plans, comments, and commits are English. User-facing conversation with the user is Russian. - Do not store secrets, personal tokens, local-only