A Complete Guide To AGENTS.md My agent.md to improve LLM-assisted code quality

numman-ali/openskills- Universal skills loader for AI coding agents evel-Software/Hexis - Git-backed control plane for AI-agent skills, tools, context, permissions, and identity. Self-hosted and MCP-native.


Progressive Disclosure

Writing a concise CLAUDE.md file that covers everything you want Claude to know can be challenging, especially in larger projects.

To address this, we can leverage the principle of Progressive Disclosure to ensure that claude only sees task- or project-specific instructions when it needs them.

Instead of including all your different instructions about building your project, running tests, code conventions, or other important context in your CLAUDE.md file, we recommend keeping task-specific instructions in separate markdown files with self-descriptive names somewhere in your project.

For example:

agent_docs/ |- building_the_project.md |- running_tests.md |- code_conventions.md |- service_architecture.md |- database_schema.md |- service_communication_patterns.md

Then, in your CLAUDE.md file, you can include a list of these files with a brief description of each, and instruct Claude to decide which (if any) are relevant and to read them before it starts working. Or, ask Claude to present you with the files it wants to read for aproval first before reading them.

Prefer pointers to copies. Don’t include code snippets in these files if possible - they will become out-of-date quickly. Instead, include file:line references to point Claude to the authoritative context.

Conceptually, this is very similar to how Claude Skills are intended to work, although skills are more focused on tool use than instructions.

Writing a good CLAUDE.md/AGENTS.md