agentleFS
sp1esp1e/claude-skills/claude-code-mastery/SKILL.md

claude-code-mastery

Skill1 starsChanged 31 days agoMITView on GitHub

Använd vid arbete med Claude Codes egen konfiguration: skriva eller optimera en CLAUDE.md, skapa en ny skill. Trigga på "CLAUDE.md", "skriv en skill", "skill-frontmatter", "subagent", "allowed-tools", "hook", "settings.json", "kontextbudget", "token-budget", "för många skills", "slash-kommando", "permission mode", "MCP-server", "worktree".

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before scaffolding or optimizing, confirm these inputs.

    line 40
  2. Distinctive:

    Stop rule: ask only the 2-3 that most change the output.

    line 46
  3. Very specific:

    All tools support --json. See references/tool-reference.md for full parameter tables and output formats.

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Claude Code Mastery

Expert skill for Claude Code CLI -- CLAUDE.md optimization, skill authoring, subagent creation, hooks automation, and context engineering.

Keywords: claude-code, claude-cli, CLAUDE.md, skill-authoring, subagents, hooks, context-window, token-budget, MCP-servers, worktrees, permission-modes, prompt-engineering, context-engineering, slash-commands

Core Capabilities

  • CLAUDE.md optimization — audit, restructure, compress, and hierarchize config files for token efficiency.
  • Skill authoring — scaffold and write discoverable skill packages with correct layout and frontmatter.
  • Subagent creation — define scoped agents with allowed-tools and structured custom instructions.
  • Hooks automation — wire PreToolUse/PostToolUse/Stop lifecycle scripts via .claude/settings.json.
  • Context engineering — measure and manage the context-window token budget across a codebase.

When to Use

  • Authoring, structuring, or optimizing a CLAUDE.md file for any project.
  • Scaffolding a new skill package or creating a Claude Code subagent.
  • Configuring hooks for automated quality, security, or workflow steps.
  • Auditing and reducing context-window consumption.

Clarify First

Before scaffolding or optimizing, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Which task — scaffold a new skill, optimize a CLAUDE.md, create a subagent, or analyze context budget (selects skill_scaffolder.py vs claudemd_optimizer.py vs context_analyzer.py)
  • Target identity — for a new skill: its name, domain, and one-line description; for optimization: the file or project path (the inputs the scripts require)
  • Token budget — the target ceiling (sets --token-limit and what counts as over-budget)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Quick Start

# Scaffold a new skill package
python scripts/skill_scaffolder.py my-new-skill --domain engineering --description "Brief description"

# Analyze and optimize an existing CLAUDE.md
python scripts/claudemd_optimizer.py path/to/CLAUDE.md

# Estimate context window usage across a project
python scripts/context_analyzer.py /path/to/project

# All tools support JSON output
python scripts/claudemd_optimizer.py CLAUDE.md --json

Tools

ToolPurposeCommand
skill_scaffolder.pyScaffold a new skill package with correct structure + frontmatterpython scripts/skill_scaffolder.py my-skill -d engineering --description "Does X"
claudemd_optimizer.pyScore a CLAUDE.md for structure, tokens, and redundancy with recommendationspython scripts/claudemd_optimizer.py CLAUDE.md --token-limit 4000
context_analyzer.pyEstimate context-window consumption by file category with a budget breakdownpython scripts/context_analyzer.py /path/to/project --max-depth 4

All tools support --json. See references/tool-reference.md for full parameter tables and output formats.

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/workflows.md — the five numbered playbooks: optimize a CLAUDE.md, author a skill, create a subagent, configure hooks, and manage the context budget. Read when executing any of those tasks step-by-step.
  • references/quick-reference.md — slash commands, permission modes, CLAUDE.md loading order, MCP servers, the troubleshooting table, and success criteria. Read for at-a-glance lookups or when debugging configuration.
  • references/tool-reference.md — full parameter tables and output formats for the three Python tools. Read when scripting the tools or interpreting their JSON output.
  • references/skill-authoring-guide.md — comprehensive reference for writing effective skills, from YAML frontmatter to structure. Read when authoring a skill in depth.
  • references/subagent-patterns.md — guide to creating and using subagents for parallel work and scoped tasks. Read when designing a subagent.
  • references/hooks-cookbook.md — practical hook recipes for code quality, security enforcement, and workflow automation. Read when building hooks.

Templates: assets/skill-template.md, assets/agent-template.md

Scope & Limitations

This skill covers:

  • Authoring, structuring, and optimizing CLAUDE.md files for any project
  • Scaffolding new skill packages with correct directory layout and frontmatter
  • Creating and configuring Claude Code subagents with scoped tool access
  • Analyzing and managing context window token budgets across a codebase

This skill does NOT cover:

  • Writing application source code or implementing business logic (see senior-fullstack, senior-backend)
  • MCP server development or custom transport protocols (see mcp-server-builder)
  • Advanced prompt engineering techniques for LLM applications (see senior-prompt-engineer)
  • CI/CD pipeline configuration or deployment automation (see senior-devops, ci-cd-pipeline-builder)

Integration Points

SkillIntegrationData Flow
senior-architectArchitecture decisions inform CLAUDE.md structure sectionsArchitecture diagrams and patterns feed into the Architecture Overview section of CLAUDE.md
code-reviewerSubagent creation for automated code reviewClaude Code Mastery creates the agent YAML; Code Reviewer provides the review logic
senior-prompt-engineerPrompt optimization for skill descriptions and agent instructionsPrompt engineering techniques improve YAML frontmatter trigger phrases and agent custom-instructions
doc-drift-detectorDetects when CLAUDE.md drifts out of sync with the codebaseContext Analyzer output feeds drift detection; drift findings trigger CLAUDE.md optimization
context-engineAdvanced context management strategiesContext Analyzer provides token budgets; Context Engine applies compression and prioritization
senior-secopsSecurity hooks and permission mode configurationSecOps policies define which tools to deny; Claude Code Mastery configures the permission allowlists

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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.