--- title: "anthropics/claude-code" description: "Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands." source: https://github.com/anthropics/claude-code ref: main license: null licenseName: "No licence detected" canonical: https://skillsdocs.com/anthropics/claude-code base: https://github.com/anthropics/claude-code/blob/main/ chapters: 10 inlined: 1 withheld: 9 words: 10604 updated: 2026-08-11T19:50:58Z generator: "Skills Docs" --- > **anthropics/claude-code** — every Agent Skill in this repository, inlined verbatim. > > Canonical HTML: https://skillsdocs.com/anthropics/claude-code > Per-chapter Markdown: https://skillsdocs.com/anthropics/claude-code/.md > Machine manifest: https://skillsdocs.com/anthropics/claude-code/.well-known/agent-skills/index.json > JSON: https://skillsdocs.com/api/v1/books/anthropics/claude-code > Install: `npx skills add anthropics/claude-code` > Upstream: https://github.com/anthropics/claude-code @ `main` > Licence: No licence detected — all rights reserved by its authors > > Content is mirrored from GitHub and © its authors, served unmodified. Takedown: https://github.com/DreambaseAI/skillsdocs/issues/new?labels=takedown&title=Takedown+request # anthropics/claude-code Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands. - **Chapters:** 10 - **Inlined:** 1 (licence detected) - **Words:** 10,604 - **Reading time:** 49 min - **Stars:** 141,104 ## Table of contents 1. [claude-opus-4-5-migration](https://skillsdocs.com/anthropics/claude-code/claude-opus-4-5-migration.md) — Not licensed for republication — link only. 2. [frontend-design](https://skillsdocs.com/anthropics/claude-code/frontend-design.md) — Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making c… 3. [Writing Hookify Rules](https://skillsdocs.com/anthropics/claude-code/writing-rules.md) — Not licensed for republication — link only. 4. [Agent Development](https://skillsdocs.com/anthropics/claude-code/agent-development.md) — Not licensed for republication — link only. 5. [Command Development](https://skillsdocs.com/anthropics/claude-code/command-development.md) — Not licensed for republication — link only. 6. [Hook Development](https://skillsdocs.com/anthropics/claude-code/hook-development.md) — Not licensed for republication — link only. 7. [MCP Integration](https://skillsdocs.com/anthropics/claude-code/mcp-integration.md) — Not licensed for republication — link only. 8. [Plugin Settings](https://skillsdocs.com/anthropics/claude-code/plugin-settings.md) — Not licensed for republication — link only. 9. [Plugin Structure](https://skillsdocs.com/anthropics/claude-code/plugin-structure.md) — Not licensed for republication — link only. 10. [Skill Development](https://skillsdocs.com/anthropics/claude-code/skill-development.md) — Not licensed for republication — link only. ## Licence notice 9 of 10 chapters in this book have no licence that we could detect, at either the repository or the skill level. Their bodies are **not** reproduced here and they are **not** listed in the Agent Skills manifest. Read them upstream: - claude-opus-4-5-migration — https://github.com/anthropics/claude-code/blob/main/plugins/claude-opus-4-5-migration/skills/claude-opus-4-5-migration/SKILL.md - Writing Hookify Rules — https://github.com/anthropics/claude-code/blob/main/plugins/hookify/skills/writing-rules/SKILL.md - Agent Development — https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/agent-development/SKILL.md - Command Development — https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/command-development/SKILL.md - Hook Development — https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/hook-development/SKILL.md - MCP Integration — https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/mcp-integration/SKILL.md - Plugin Settings — https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/plugin-settings/SKILL.md - Plugin Structure — https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/plugin-structure/SKILL.md - Skill Development — https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/skill-development/SKILL.md ## Front matter _The repository README, verbatim except that relative links are resolved against https://github.com/anthropics/claude-code/blob/main/._ # Claude Code ![](https://img.shields.io/badge/Node.js-18%2B-brightgreen?style=flat-square) [![npm]](https://www.npmjs.com/package/@anthropic-ai/claude-code) [npm]: https://img.shields.io/npm/v/@anthropic-ai/claude-code.svg?style=flat-square Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language commands. Use it in your terminal, IDE, or tag @claude on Github. **Learn more in the [official documentation](https://code.claude.com/docs/en/overview)**. ## Get started > [!NOTE] > Installation via npm is deprecated. Use one of the recommended methods below. For more installation options, uninstall steps, and troubleshooting, see the [setup documentation](https://code.claude.com/docs/en/setup). 1. Install Claude Code: **MacOS/Linux (Recommended):** ```bash curl -fsSL https://claude.ai/install.sh | bash ``` **Homebrew (MacOS/Linux):** ```bash brew install --cask claude-code ``` **Windows (Recommended):** ```powershell irm https://claude.ai/install.ps1 | iex ``` **WinGet (Windows):** ```powershell winget install Anthropic.ClaudeCode ``` **NPM (Deprecated):** ```bash npm install -g @anthropic-ai/claude-code ``` 2. Navigate to your project directory and run `claude`. ## Plugins This repository includes several Claude Code plugins that extend functionality with custom commands and agents. See the [plugins directory](https://github.com/anthropics/claude-code/blob/main/plugins/README.md) for detailed documentation on available plugins. ## Reporting Bugs We welcome your feedback. Use the `/bug` command to report issues directly within Claude Code, or file a [GitHub issue](https://github.com/anthropics/claude-code/issues). ## Connect on Discord Join the [Claude Developers Discord](https://anthropic.com/discord) to connect with other developers using Claude Code. Get help, share feedback, and discuss your projects with the community. ## Data collection, usage, and retention When you use Claude Code, we collect feedback, which includes usage data (such as code acceptance or rejections), associated conversation data, and user feedback submitted via the `/bug` command. ### How we use your data See our [data usage policies](https://code.claude.com/docs/en/data-usage). ### Privacy safeguards We have implemented several safeguards to protect your data, including limited retention periods for sensitive information, restricted access to user session data, and clear policies against using feedback for model training. For full details, please review our [Commercial Terms of Service](https://www.anthropic.com/legal/commercial-terms) and [Privacy Policy](https://www.anthropic.com/legal/privacy). --- ## Part: Claude Opus 4 5 Migration --- ## 1. claude-opus-4-5-migration Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5. - **Source:** https://github.com/anthropics/claude-code/blob/main/plugins/claude-opus-4-5-migration/skills/claude-opus-4-5-migration/SKILL.md - **Raw:** https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/claude-opus-4-5-migration/skills/claude-opus-4-5-migration/SKILL.md - **Markdown:** https://skillsdocs.com/anthropics/claude-code/claude-opus-4-5-migration.md - **Licence:** No licence detected — all rights reserved by its authors Bundled files (2), referenced from this skill's directory: - `references/effort.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/claude-opus-4-5-migration/skills/claude-opus-4-5-migration/references/effort.md - `references/prompt-snippets.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/claude-opus-4-5-migration/skills/claude-opus-4-5-migration/references/prompt-snippets.md _Body withheld: no licence could be detected for this skill. Read it upstream._ --- ## Part: Frontend Design --- ## 2. frontend-design - **Source:** https://github.com/anthropics/claude-code/blob/main/plugins/frontend-design/skills/frontend-design/SKILL.md - **Raw:** https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/frontend-design/skills/frontend-design/SKILL.md - **Markdown:** https://skillsdocs.com/anthropics/claude-code/frontend-design.md - **Licence:** Complete terms in LICENSE.txt — https://github.com/anthropics/claude-code/blob/main/plugins/frontend-design/skills/frontend-design/SKILL.md --- name: frontend-design description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. license: Complete terms in LICENSE.txt --- # Frontend Design Approach this as the design lead at a small studio known for giving every client a visual identity that could not be mistaken for anyone else's. This client has already rejected proposals that felt templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take one real aesthetic risk you can justify. ## Ground it in the subject If the brief does not pin down what the product or subject is, pin it yourself before designing: name one concrete subject, its audience, and the page's single job, and state your choice. If there's any information in your memory about the human's preferences, context about what they're building, or designs you've made before – use that as a hint. The subject's own world, its materials, instruments, artifacts, and vernacular, is where distinctive choices come from. Build with the brief's real content and subject matter throughout. ## Design principles For web designs, the hero is a thesis. Open with the most characteristic thing in the subject's world, in whatever form makes sense for it: a headline, an image, an animation, a live demo, an interactive moment. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the template answer, only use if that's truly the best option. Typography carries the personality of the page. Pair the display and body faces deliberately, not the same families you would reach for on any other project, and set a clear type scale with intentional weights, widths, and spacing. Make the type treatment itself a memorable part of the design, not a neutral delivery vehicle for the content. Structure is information. Structural devices, numbering, eyebrows, dividers, labels, should encode something true about the content, not decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence - like a real process or a typed timeline where order carries information the reader needs. Question if choices like numbered markers actually make sense before incorporating them. Leverage motion deliberately. Think about where and if animation can serve the subject: a page-load sequence, a scroll-triggered reveal, hover micro-interactions, ambient atmosphere. An orchestrated moment usually lands harder than scattered effects; choose what the direction calls for. However, sometimes less is more, and extra animation contributes to the feeling that the design is AI-generated. Match complexity to the vision. Maximalist directions need elaborate execution; minimal directions need precision in spacing, type, and detail. Elegance is executing the chosen vision well. Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance. ## Process: brainstorm, explore, plan, critique, build, critique again For calibration: AI-generated design right now clusters around three looks: (1) a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta accent; (2) a near-black background with a single bright acid-green or vermilion accent; (3) a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns. All three are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. Just like a human designer who's hired, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn. Work in two passes. First, brainstorm a short design plan based on the human's design brief: create a compact token system with color, type, layout, and signature. Color: describe the palette as 4–6 named hex values. Type: the typefaces for 2+ roles (a characterful display face that's used with restraint, a complementary body face, and a utility face for captions or data if needed). Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Signature: the single unique element this page will be remembered by that embodies the brief in an appropriate way. Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan exactly and deriving every color and type decision from it. When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and a element-based selector like .cta). This can happen often with paddings/margins between sections. Try to do a lot of this planning and iteration in your thinking, and only show ideas to the user when you have higher confidence it'll delight them. ## Restraint and self-critique Spend your boldness in one place. Let the signature element be the one memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Not taking a risk can be a risk itself! Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected. Critique your own work as you build, taking screenshots if your environment supports it – a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creators have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes. ## More on writing in design Words appear in a design for one reason: to make it easier to understand, and therefore easier to use. They are design material, not decoration. Bring the same intentionality to copy that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience. Write from the end user's side of the screen. Name things by what people control and recognize, never by how the system is built. A person manages notifications, not webhook config. Describe what something does in plain terms rather than selling it. Being specific is always better than being clever. Use active voice as default. A control should say exactly what happens when it's used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around. Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act. Keep the register conversational and tuned: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each element do exactly one job. A label labels, an example demonstrates, and nothing quietly does double duty. --- ## Part: Hookify --- ## 3. Writing Hookify Rules This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns. - **Source:** https://github.com/anthropics/claude-code/blob/main/plugins/hookify/skills/writing-rules/SKILL.md - **Raw:** https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/hookify/skills/writing-rules/SKILL.md - **Markdown:** https://skillsdocs.com/anthropics/claude-code/writing-rules.md - **Licence:** No licence detected — all rights reserved by its authors _Body withheld: no licence could be detected for this skill. Read it upstream._ --- ## Part: Plugin Dev --- ## 4. Agent Development This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins. - **Source:** https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/agent-development/SKILL.md - **Raw:** https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/agent-development/SKILL.md - **Markdown:** https://skillsdocs.com/anthropics/claude-code/agent-development.md - **Licence:** No licence detected — all rights reserved by its authors Bundled files (6), referenced from this skill's directory: - `examples/agent-creation-prompt.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/agent-development/examples/agent-creation-prompt.md - `examples/complete-agent-examples.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/agent-development/examples/complete-agent-examples.md - `references/agent-creation-system-prompt.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/agent-development/references/agent-creation-system-prompt.md - `references/system-prompt-design.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/agent-development/references/system-prompt-design.md - `references/triggering-examples.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/agent-development/references/triggering-examples.md - `scripts/validate-agent.sh` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/agent-development/scripts/validate-agent.sh _Body withheld: no licence could be detected for this skill. Read it upstream._ --- ## 5. Command Development This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code. - **Source:** https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/command-development/SKILL.md - **Raw:** https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/command-development/SKILL.md - **Markdown:** https://skillsdocs.com/anthropics/claude-code/command-development.md - **Licence:** No licence detected — all rights reserved by its authors Bundled files (10), referenced from this skill's directory: - `examples/plugin-commands.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/command-development/examples/plugin-commands.md - `examples/simple-commands.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/command-development/examples/simple-commands.md - `README.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/command-development/README.md - `references/advanced-workflows.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/command-development/references/advanced-workflows.md - `references/documentation-patterns.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/command-development/references/documentation-patterns.md - `references/frontmatter-reference.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/command-development/references/frontmatter-reference.md - `references/interactive-commands.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/command-development/references/interactive-commands.md - `references/marketplace-considerations.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/command-development/references/marketplace-considerations.md - `references/plugin-features-reference.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/command-development/references/plugin-features-reference.md - `references/testing-strategies.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/command-development/references/testing-strategies.md _Body withheld: no licence could be detected for this skill. Read it upstream._ --- ## 6. Hook Development This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API. - **Source:** https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/hook-development/SKILL.md - **Raw:** https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/hook-development/SKILL.md - **Markdown:** https://skillsdocs.com/anthropics/claude-code/hook-development.md - **Licence:** No licence detected — all rights reserved by its authors Bundled files (10), referenced from this skill's directory: - `examples/load-context.sh` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/hook-development/examples/load-context.sh - `examples/validate-bash.sh` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/hook-development/examples/validate-bash.sh - `examples/validate-write.sh` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/hook-development/examples/validate-write.sh - `references/advanced.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/hook-development/references/advanced.md - `references/migration.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/hook-development/references/migration.md - `references/patterns.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/hook-development/references/patterns.md - `scripts/hook-linter.sh` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/hook-development/scripts/hook-linter.sh - `scripts/README.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/hook-development/scripts/README.md - `scripts/test-hook.sh` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/hook-development/scripts/test-hook.sh - `scripts/validate-hook-schema.sh` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/hook-development/scripts/validate-hook-schema.sh _Body withheld: no licence could be detected for this skill. Read it upstream._ --- ## 7. MCP Integration This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration. - **Source:** https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/mcp-integration/SKILL.md - **Raw:** https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/mcp-integration/SKILL.md - **Markdown:** https://skillsdocs.com/anthropics/claude-code/mcp-integration.md - **Licence:** No licence detected — all rights reserved by its authors Bundled files (6), referenced from this skill's directory: - `examples/http-server.json` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/mcp-integration/examples/http-server.json - `examples/sse-server.json` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/mcp-integration/examples/sse-server.json - `examples/stdio-server.json` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/mcp-integration/examples/stdio-server.json - `references/authentication.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/mcp-integration/references/authentication.md - `references/server-types.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/mcp-integration/references/server-types.md - `references/tool-usage.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/mcp-integration/references/tool-usage.md _Body withheld: no licence could be detected for this skill. Read it upstream._ --- ## 8. Plugin Settings This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content. - **Source:** https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/plugin-settings/SKILL.md - **Raw:** https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-settings/SKILL.md - **Markdown:** https://skillsdocs.com/anthropics/claude-code/plugin-settings.md - **Licence:** No licence detected — all rights reserved by its authors Bundled files (7), referenced from this skill's directory: - `examples/create-settings-command.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-settings/examples/create-settings-command.md - `examples/example-settings.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-settings/examples/example-settings.md - `examples/read-settings-hook.sh` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-settings/examples/read-settings-hook.sh - `references/parsing-techniques.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-settings/references/parsing-techniques.md - `references/real-world-examples.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-settings/references/real-world-examples.md - `scripts/parse-frontmatter.sh` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-settings/scripts/parse-frontmatter.sh - `scripts/validate-settings.sh` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-settings/scripts/validate-settings.sh _Body withheld: no licence could be detected for this skill. Read it upstream._ --- ## 9. Plugin Structure This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices. - **Source:** https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/plugin-structure/SKILL.md - **Raw:** https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-structure/SKILL.md - **Markdown:** https://skillsdocs.com/anthropics/claude-code/plugin-structure.md - **Licence:** No licence detected — all rights reserved by its authors Bundled files (6), referenced from this skill's directory: - `examples/advanced-plugin.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-structure/examples/advanced-plugin.md - `examples/minimal-plugin.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-structure/examples/minimal-plugin.md - `examples/standard-plugin.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-structure/examples/standard-plugin.md - `README.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-structure/README.md - `references/component-patterns.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-structure/references/component-patterns.md - `references/manifest-reference.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/plugin-structure/references/manifest-reference.md _Body withheld: no licence could be detected for this skill. Read it upstream._ --- ## 10. Skill Development This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins. - **Source:** https://github.com/anthropics/claude-code/blob/main/plugins/plugin-dev/skills/skill-development/SKILL.md - **Raw:** https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/skill-development/SKILL.md - **Markdown:** https://skillsdocs.com/anthropics/claude-code/skill-development.md - **Licence:** No licence detected — all rights reserved by its authors Bundled files (1), referenced from this skill's directory: - `references/skill-creator-original.md` — https://raw.githubusercontent.com/anthropics/claude-code/main/plugins/plugin-dev/skills/skill-development/references/skill-creator-original.md _Body withheld: no licence could be detected for this skill. Read it upstream._