1 File Map en
zelenij edited this page 2026-07-11 22:25:03 +03:00

Русский

File Map

This page mirrors the router table in CLAUDE.md §0 — it is navigation, not a copy of the rules. Each row says which file to open before doing a given kind of action; the actual rule text lives only in the linked file.

A task can match more than one row — open all of them, not just the first.

Action Rule file(s)
Any meaningful repository change (code/tests/config/CI/specs/build, commit/branch/push/worktree) git-discipline.md, issue-tracker.md
Issue/task in the tracker (even without a repository change) issue-tracker.md
Launching a subagent / choosing a model subagents-and-models.md
Routing a task (inline / skill / agent) task-routing.md
Editing code in an existing project code-style.md
Refactoring / tests / verifying a result testing-and-verification.md
Session failure / lost context incident-recovery.md
Release / version bump versioning.md
Editing documentation documentation.md
Working with a project spec (maintaining/splitting/tracing) spec-discipline.md
Secrets / sensitive output to chat/log secrets.md
End of session / pause / handoff / model switch / compaction risk / architectural decision session-memory.md

Not in the router table, but referenced from it

  • skills.md — how to use skills, checked before classifying a nontrivial task by the table above (see task-routing.md).

Core file

  • CLAUDE.md — the router table itself, plus the rules that apply to every task regardless of topic (plan → consent → work → verification, language, commits/push, persistent memory, secrets). Core wins over any single .ai-workflow/*.md in a conflict; a conflict between two topic files is not resolved by Claude on its own — ask the user.

Repository metadata