agentleFS
TironFoxTironFox/everything-claude-code/CLAUDE.md

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
  1. Distinctive:

    rules/: - Always-follow guidelines (security, coding style, testing requirements)

    line 29
  2. Distinctive:

    tests/: - Test suite for scripts and utilities

    line 32
  3. Distinctive:

    Follow the formats in CONTRIBUTING.md:

    line 55
  4. Distinctive:

    Use the following skills when working on related files:

    line 65
  5. Distinctive:

    When spawning subagents, always pass conventions from the respective skill into the agent's prompt.

    line 72

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

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.js

Architecture

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_MANAGER env 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.

Download now (ZIP)

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.