Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From context-files
Apply when the user is working on CLAUDE.md, AGENTS.md, context files, agent memory, or AI coding assistant instructions. Teaches the minimal-context approach backed by empirical research.
npx claudepluginhub maxnoller/claude-code-plugins --plugin context-filesHow this skill is triggered — by the user, by Claude, or both
Slash command
/context-files:claude-md-principlesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Applies to: **CLAUDE.md** (Claude Code), **AGENTS.md** (Jules / other agents), and any equivalent agent instruction file.
Creates minimal, high-signal CLAUDE.md and AGENTS.md context files for repos using empirical best practices. Triggers on /init, create/update requests, or missing context during brainstorming.
Maintains CLAUDE.md and AGENTS.md instruction files by enforcing size limits (<300 lines), progressive disclosure via docs/ references, multi-agent compatibility, and tool-first content. Use for creation, updates, audits.
Optimizes AI agent context setup with rules files (CLAUDE.md), specs, source files, and hierarchy. Use for new sessions, degrading output, task switches, or project configuration.
Share bugs, ideas, or general feedback.
Applies to: CLAUDE.md (Claude Code), AGENTS.md (Jules / other agents), and any equivalent agent instruction file.
Developer-written context files improve task success by only ~4% while increasing compute cost and time by 20%+. LLMs are proficient at exploring codebases independently by reading package.json, source files, and schemas. Bloated context files cause important rules to get buried and ignored.
For every line, ask: "Would removing this cause the agent to make mistakes?"
package.json / Cargo.toml — especially verification steps to run after changes| Content | Why to cut |
|---|---|
| Project description / tech stack | Agent reads package.json |
| Architecture explanations | Belongs in ADRs / docs/ |
| Directory structure | Agent explores the filesystem |
| Key file lists | Agent searches the codebase |
| Environment variable templates | Agent reads .env.example |
| Database schema docs | Agent reads schema files |
| Deployment / CI pipeline info | Irrelevant during coding |
| Anything discoverable by reading code | Agent will find it |
When an agent makes a mistake, prefer fixing the codebase over adding a context file rule:
Context files are a temporary patch. A well-structured codebase with good types and tests needs almost none of it.