everything-claude-code
CLAUDE.md1 starsChanged 7 months agoMITView on GitHub
This is a Claude Code plugin - a collection of production-ready agents, skills, hooks, commands, rules, and MCP configurations. The project provides battle-tested workflows for software development using Claude Code. The project is organized into several core components: Follow the formats in CONTRIBUTING.md: - Agents: Markdown with frontmatter (name, description, tools, model) - Skills: Clear sections (When to Use, How It Works, Examples) - Commands: Markdown with description frontmatter - Hooks: JSON with matcher and hooks array File naming: lowercase…
We split this CLAUDE.md into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 29
rules/: - Always-follow guidelines (security, coding style, testing requirements)
- Distinctive: line 32
tests/: - Test suite for scripts and utilities
- Distinctive: line 55
Follow the formats in CONTRIBUTING.md:
- Distinctive: line 65
Use the following skills when working on related files:
- Distinctive: line 72
When spawning subagents, always pass conventions from the respective skill into the agent's prompt.
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 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
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a Claude Code plugin - a collection of production-ready agents, skills, hooks, commands, rules, and MCP configurations. The project provides battle-tested workflows for software development using Claude Code.
Running Tests
# Run all tests
node tests/run-all.js
# Run individual test files
node tests/lib/utils.test.js
node tests/lib/package-manager.test.js
node tests/hooks/hooks.test.jsArchitecture
The project is organized into several core components:
- agents/ - Specialized subagents for delegation (planner, code-reviewer, tdd-guide, etc.)
- skills/ - Workflow definitions and domain knowledge (coding standards, patterns, testing)
- commands/ - Slash commands invoked by users (/tdd, /plan, /e2e, etc.)
- hooks/ - Trigger-based automations (session persistence, pre/post-tool hooks)
- rules/ - Always-follow guidelines (security, coding style, testing requirements)
- mcp-configs/ - MCP server configurations for external integrations
- scripts/ - Cross-platform Node.js utilities for hooks and setup
- tests/ - Test suite for scripts and utilities
Key Commands
/tdd- Test-driven development workflow/plan- Implementation planning/e2e- Generate and run E2E tests/code-review- Quality review/build-fix- Fix build errors/learn- Extract patterns from sessions/skill-create- Generate skills from git history
Development Notes
- Package manager detection: npm, pnpm, yarn, bun (configurable via
CLAUDE_PACKAGE_MANAGERenv var or project config) - Cross-platform: Windows, macOS, Linux support via Node.js scripts
- Agent format: Markdown with YAML frontmatter (name, description, tools, model)
- Skill format: Markdown with clear sections for when to use, how it works, examples
- Skill placement: Curated in skills/; generated/imported under ~/.claude/skills/. See docs/SKILL-PLACEMENT-POLICY.md
- Hook format: JSON with matcher conditions and command/notification hooks
Contributing
Follow the formats in CONTRIBUTING.md:
- Agents: Markdown with frontmatter (name, description, tools, model)
- Skills: Clear sections (When to Use, How It Works, Examples)
- Commands: Markdown with description frontmatter
- Hooks: JSON with matcher and hooks array
File naming: lowercase with hyphens (e.g., python-reviewer.md, tdd-workflow.md)
Skills
Use the following skills when working on related files:
| File(s) | Skill |
README.md | /readme |
.github/workflows/*.yml | /ci-workflow |
When spawning subagents, always pass conventions from the respective skill into the agent's prompt.
Other versions5 projects use a version of this.
Word for word · 5
- mit-network/everything-claude-code★ 76100% same
- ArogyaReddy/https-github.com-affaan-m-everything-claude-code1★ 2100% same
- Najeebullah3124/awesome-claude-universe★ 2100% same
- divenhuang88/everything-claude-code★ 1100% same
- pcoulbourne/everything-claude-code★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository224 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- examples/CLAUDE.mdCLAUDE.md
- .cursor/rules/common-agents.mdCursor rule
- .cursor/rules/common-coding-style.mdCursor rule
- .cursor/rules/common-development-workflow.mdCursor rule
- .cursor/rules/common-git-workflow.mdCursor rule
- .cursor/rules/common-hooks.mdCursor rule
- .cursor/rules/common-patterns.mdCursor rule
- .cursor/rules/common-performance.mdCursor rule
- .cursor/rules/common-security.mdCursor rule
- .cursor/rules/common-testing.mdCursor rule
- .cursor/rules/golang-coding-style.mdCursor rule
- .cursor/rules/golang-hooks.mdCursor rule
- .cursor/rules/golang-patterns.mdCursor rule
- .cursor/rules/golang-security.mdCursor rule
- .cursor/rules/golang-testing.mdCursor rule
- .cursor/rules/kotlin-coding-style.mdCursor rule
- .cursor/rules/kotlin-hooks.mdCursor rule
- .cursor/rules/kotlin-patterns.mdCursor rule
- .cursor/rules/kotlin-security.mdCursor rule
- .cursor/rules/kotlin-testing.mdCursor rule
- .cursor/rules/php-coding-style.mdCursor rule
- .cursor/rules/php-hooks.mdCursor rule
- .cursor/rules/php-patterns.mdCursor rule
- .cursor/rules/php-security.mdCursor rule
- .cursor/rules/php-testing.mdCursor rule
- .cursor/rules/python-coding-style.mdCursor rule
- .cursor/rules/python-hooks.mdCursor rule
- .cursor/rules/python-patterns.mdCursor rule
- .cursor/rules/python-security.mdCursor rule
- .cursor/rules/python-testing.mdCursor rule
- .cursor/rules/swift-coding-style.mdCursor rule
- .cursor/rules/swift-hooks.mdCursor rule
- .cursor/rules/swift-patterns.mdCursor rule
- .cursor/rules/swift-security.mdCursor rule
- .cursor/rules/swift-testing.mdCursor rule
- .cursor/rules/typescript-coding-style.mdCursor rule
- .cursor/rules/typescript-hooks.mdCursor rule
- .cursor/rules/typescript-patterns.mdCursor rule
- .cursor/rules/typescript-security.mdCursor rule
- .cursor/rules/typescript-testing.mdCursor rule
- api-designSkill
- article-writingSkill
- backend-patternsSkill
- bun-runtimeSkill
- claude-apiSkill
- coding-standardsSkill
- content-engineSkill
- crosspostSkill
- deep-researchSkill
- dmux-workflowsSkill
- documentation-lookupSkill
- e2e-testingSkill
- eval-harnessSkill
- everything-claude-code-conventionsSkill
- exa-searchSkill
- fal-ai-mediaSkill
- frontend-patternsSkill
- frontend-slidesSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

