Pick a file.
The details will appear here.
Interactive reference
AI Context Files Cheatsheet
The files that tell AI coding tools how to behave on your project. What each one does, when it loads, and what belongs in it.
Keep these files short. Every line should answer one question: would removing this make an AI assistant more likely to make a mistake?
The five files
Click a card to see where that file fits in the stack.
Session flow
Context files matter because load order changes authority and relevance.
- Session opens. Tool-specific instructions such as
CLAUDE.mdor system rules load first. - Project-wide conventions from
AGENTS.mdexplain the stack, commands, and rules every coding agent should follow. - Persistent memory, when configured, carries forward previous decisions and resolved debates.
- Current-session context explains the active branch, known issues, and today's goal.
- Task-specific skills load only when the task matches their description.
What goes where
Most confusion comes from putting temporary notes into permanent files.
Project law
Use AGENTS.md for durable rules
Commands, folder conventions, test expectations, style rules, and non-negotiables that every coding assistant should know.
Tool behavior
Use CLAUDE.md for Claude-specific preferences
Response style, Claude-specific workflow expectations, or tool behavior that should not necessarily apply to every assistant.
History
Use memory for decisions
Architecture choices, completed migrations, and lessons that should carry across sessions without repeating old debates.
Today
Use context for active work
Current branch, blockers, broken local services, and notes that should be replaced or refreshed as the work changes.
Specialist workflow
Use skills for repeatable task playbooks
Migration steps, review checklists, accessibility audits, or deployment workflows that should load only when the task calls for them.
Related references
Other notes that sit near this one.