claude-code-tool-kit
CLAUDE.md7 starsChanged 6 months agoMITView on GitHub
Universal Claude Code configuration — stack-agnostic, upgradable, shared across all projects. Detailed rules are in .claude/rules/ and auto-load into context. Current directory: !pwd Project files: !ls -1 2>/dev/null | head -20 Git branch: !git branch --show-current 2>/dev/null || echo "not a git repo" Language hints: !ls package.json requirements.txt Pipfile pyproject.toml go.mod Cargo.toml *.csproj *.sln Gemfile build.gradle pom.xml composer.json mix.exs deno.json 2>/dev/null Customize this section per project, or create CLAUDE.local.md for personal notes.
- Reads credentials
In this repository45 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- api-designSkill
- architecture-reviewSkill
- business-blueprintSkill
- business-logic-auditSkill
- changelogSkill
- ci-pipelineSkill
- code-coverageSkill
- competitive-analysisSkill
- convert-codeSkill
- create-componentSkill
- db-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- design-flowSkill
- docker-setupSkill
- env-setupSkill
- error-monitorSkill
- estimateSkill
- explain-codeSkill
- fix-issueSkill
- generate-docsSkill
- git-cleanupSkill
- grill-meSkill
- handoffSkill
- legal-pagesSkill
- memory-importSkill
- memorySkill
- microcopySkill
- migrate-frameworkSkill
- onboardSkill
- optimizeSkill
- pr-summarySkill
- refactorSkill
- reference-appSkill
- review-prSkill
- security-scanSkill
- seo-scaffoldSkill
- tddSkill
- web-launch-checkSkill
- wireframeSkill
- write-skillSkill
- write-testsSkill
The file
We split this CLAUDE.md into the rules it gives an agent
12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 17
Follow the existing patterns and conventions already present in THIS project
- Distinctive: line 19
When rules conflict with project conventions, project conventions win
- Distinctive: line 22
Verify directories exist before creating files
- Distinctive: line 23
Prefer editing specific sections over rewriting entire files
- Distinctive: line 25
Follow existing naming conventions in the project
- Distinctive: line 30
Ask clarifying questions rather than assuming
- Distinctive: line 33
Do not refactor files outside the current task scope
- Distinctive: line 34
Do not install new packages without confirming with the user
- Distinctive: line 35
Do not modify lock files manually
- Distinctive: line 36
Do not overwrite .env files or secrets
- Distinctive: line 37
Do not make architectural changes without discussion
- Distinctive: line 38
Do not delete tests, even if currently failing
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Instructions
Universal Claude Code configuration — stack-agnostic, upgradable, shared across all projects. Detailed rules are in
.claude/rules/and auto-load into context.
Environment Detection
Current directory: !pwd
Project files: !ls -1 2>/dev/null | head -20
Git branch: !git branch --show-current 2>/dev/null || echo "not a git repo"
Language hints: !ls package.json requirements.txt Pipfile pyproject.toml go.mod Cargo.toml *.csproj *.sln Gemfile build.gradle pom.xml composer.json mix.exs deno.json 2>/dev/null
Core Principles
- Follow the existing patterns and conventions already present in THIS project
- Detailed standards are in
.claude/rules/— they auto-load per session - When rules conflict with project conventions, project conventions win
File Operations
- Verify directories exist before creating files
- Prefer editing specific sections over rewriting entire files
- Respect .gitignore — never modify ignored file categories
- Follow existing naming conventions in the project
Communication
- Be concise but thorough — explain "why" not just "what"
- Flag potential issues and trade-offs proactively
- Ask clarifying questions rather than assuming
Boundaries
- Do not refactor files outside the current task scope
- Do not install new packages without confirming with the user
- Do not modify lock files manually
- Do not overwrite .env files or secrets
- Do not make architectural changes without discussion
- Do not delete tests, even if currently failing
Project-Specific Configuration
Customize this section per project, or create
CLAUDE.local.mdfor personal notes.
Stack
<!-- Language, framework, database, test runner, package manager -->Build & Dev Commands
<!-- dev server, build, test, lint, type check -->Architecture Notes
<!-- Key directories, patterns, data flow -->Key Conventions
<!-- Project-specific conventions beyond the universal rules -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.