plugin-authoring

# /plugin-authoring The authoring procedures for this marketplace: how to create a skill, how to create a plugin, what to update when either changes, and how to delete one without leaving dangling metadata. Promoted out of `CLAUDE.md` (issue #2140) because all four are **procedures with a clear trigger** — they do not need to be resident when the user is debugging a hook. `CLAUDE.md` keeps only the repo blurb, the rules index, and the gotchas. Detailed patterns live in the rules this skill names; it is the sequence, not a second copy of them. ## Creating New Skills See `.claude/rules/skill-development.md` for detailed patterns. > **Note (Claude Code 2.1.157):** plugins placed in `.claude/skills` are now auto-loaded without a marketplace entry — handy for local or quick one-off plugins. This repo's *published* plugins still use the full marketplace + release-please lifecycle described in Plugin Lifecycle below. ### Quick Start 1. Create skill directory: `mkdir -p <plugin>/skills/<skill-name>` 2. Create `skill.md` with YAML frontmatter: ```yaml --- name: <Skill Name> description: <1-2 sentence description> allowed-tools: Bash, Read, Grep, Glob, TodoWrite created: YYYY-MM-DD modified: YYYY-MM-DD reviewed: YYYY-MM-DD --- ``` 3. Follow content structure: Core Expertise → Commands → Patterns → Quick Reference 4. Include agentic optimizations table 5. Update all metadata files (see Plugin Lifecycle section) ### Skill Granularity Decision | Cho...