setup
Configure the songwriting plugin for this repository: inventory or scaffold the project-level prompt-template overrides under songwriting/templates/pat-pattison/, and confirm where craft artifacts land. Use when: 'set up songwriting', 'configure songwriting', 'songwriting setup', 'customize a songwriting template', 'override the co-write prompt', or a craft skill reports a bundled prompt to tune. Actions: check (read-only inventory, default) | apply (scaffold or remove overrides). Re-runnable and safe.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 30
- Forks
- 7
01 前言 Front Matter
- description
- Configure the songwriting plugin for this repository: inventory or scaffold the project-level prompt-template overrides under songwriting/templates/pat-pattison/, and confirm where craft artifacts land. Use when: 'set up songwriting', 'configure songwriting', 'songwriting setup', 'customize a songwriting template', 'override the co-write prompt', or a craft skill reports a bundled prompt to tune. Actions: check (read-only inventory, default) | apply (scaffold or remove overrides). Re-runnable and safe.
- argument-hint
- [check|apply] [scaffold <name>...] [remove <name>...]
- user-invocable
- true
- disable-model-invocation
- true
02 资源文件 1
- 参考文档evals/evals.json7.1 KB
03 SKILL.md 正文
Purpose
Thin check-centric setup per the uniform setup contract (docs/plugin-philosophy.md
"Setup is explicit and repeatable" in the marketplace repository): check inventories the consuming
repo's tracked prompt-template overrides and reports the effective artifact layout; apply scaffolds
an override from a bundled default (or removes a byte-identical one). The override seam and the output
layout are the plugin's only extension points. It carries no userConfig. Both surfaces are described
once in
${CLAUDE_PLUGIN_ROOT}/context/pat-pattison/research/artifact-persistence.md.
Action routing: no argument or check runs the inventory; apply scaffold <name>... copies the named
bundled defaults into overrides; apply remove <name>... deletes the named overrides. apply runs
check first. apply is non-interactive for the safe paths (scaffolding a not-yet-overridden template,
removing a byte-identical one); the single deliberate exception is a destructive-collision guard: overwriting an already-diverged override or removing a customized one would lose the consumer's edits,
so those confirm first rather than clobber.
The two surfaces
- Template overrides (the only thing this skill writes). A file at
${CLAUDE_PROJECT_DIR}/songwriting/templates/pat-pattison/<name>.mdin the consuming repo wins over the bundled default${CLAUDE_PLUGIN_ROOT}/context/pat-pattison/templates/<name>.md(first match). These overrides are tracked, team-shared config. They belong in the consumer's repo, not in machine-local state or the plugin directory. - Artifact layout (read/confirm only, never written by this skill). Craft skills persist work under
${CLAUDE_PROJECT_DIR}/songwriting/by default; if the consuming project's ownCLAUDE.mdor rules declare a different songwriting layout, that layout wins. That declaration is the consumer's own instruction surface. Setup surfaces it and reports the effective layout, but does not edit the consumer'sCLAUDE.md.
The override cost. Scaffold only what you intend to customize
An override freezes that template: once songwriting/templates/pat-pattison/<name>.md exists, the
craft skills load it instead of the bundled default forever, so later plugin improvements to that
template stop reaching this repo. Scaffold an override only for a template the consumer actually
wants to change. Copying every default verbatim is an anti-pattern: a full set of files that opt out
of updates while customizing nothing.
check (read-only)
Inventory without writing anything. Apply the convention-resolution ladder. Override present → it wins; no override → the bundled default stays in force (the safe default).
- Overrides present. List what exists under
${CLAUDE_PROJECT_DIR}/songwriting/templates/pat-pattison/, and list the bundled defaults in${CLAUDE_PLUGIN_ROOT}/context/pat-pattison/templates/(each<name>.mdis loaded by the craft skill that references it, e.g.co-write-session-openerby/songwriting:co-write,metaphor-recipe-promptby/songwriting:metaphor). Report: templates available to override, templates already overridden, and, for each existing override, whether it is byte-identical to the current bundled default (INFO: a byte-identical override customizes nothing and only opts the repo out of future improvements;apply remove <name>clears it). - Artifact layout. Read the consuming project's
CLAUDE.mdand.claude/rulesfor a declared songwriting layout. Report the effective layout, the declared one if present, else the defaultsongwriting/layout from the artifact-persistence contract.
apply (idempotent)
Run check, then act on the named arguments only, never scaffold or remove a template the consumer
did not name.
apply scaffold <name>.... Create the${CLAUDE_PROJECT_DIR}/songwriting/templates/pat-pattison/directory if absent, then copy each named bundled default verbatim to<name>.mdas the starting point for the consumer to edit. If an override already exists, show the difference and do not overwrite it without explicit confirmation in this conversation. Confirm the scaffolded files are tracked, not gitignored, via the pair:git check-ignore -vreports no match (a match is a finding with the pattern) ANDgit ls-files --error-unmatchexits 0 (non-zero right after a fresh scaffold means "written but untracked: commit it to share with the team", never success).apply remove <name>.... Delete the named override(s). Offer this for any overridecheckfound byte-identical to its bundled default; for a diverged override, show what would be lost and confirm first.- Custom artifact layout. If the consumer wants a non-default layout, show them the one-line
convention to add to their own
CLAUDE.mdor rules; do not write it for them (that surface is consumer-owned).
After any change, re-run the check inventory and report the resulting override set. Re-running apply
with no scaffold/remove argument changes nothing and reports the current inventory.
What this skill does NOT do
- Run a craft skill. That is
/songwriting:workflowand the concern skills it routes to. - Write machine-local state. Overrides live in the consumer's tracked repo, never in the plugin directory or the plugin data directory.
- Write the plugin cache, Claude Code user settings, or
pluginConfigs. - Edit the consumer's
CLAUDE.mdor rules, the artifact-layout convention is the consumer's own instruction surface; setup reads and reports it, it does not author it. - Scaffold templates the consumer did not name, a bundled default left in place keeps receiving plugin improvements.
04 同仓库更多 Skills
track
Backlog reads through the bound tracker: search open and closed items, view one item with its comments and state history. Use when another skill searches or reads tracker items.
reviewer-media
Reviewer media for one pull request: decides whether it needs a narrated walkthrough, builds the storyboard from /review:explain-change's digest, has /explainer-video:produce render it and hands the manifest to /source-control:pull-request media. Use when asked for 'reviewer media', 'a walkthrough video for this PR', 'a produced video of this change', or when pull-request ready or monitor hands a PR over.
route
Model and effort per agent role (orchestrator, worker, verifier, retrieval) for a multi-agent run, resolved through the bundled defaults and the user, team and personal override config layers into fenced JSON with single-agent and fan-out variants and the layer behind each value. Use when asked 'which model for the subagents', 'route the roles' or 'model routing', or before a skill passes a role's model on a spawn.
route
Model and effort per agent role (orchestrator, worker, verifier, retrieval) for a multi-agent run, resolved through the bundled defaults and the user, team and personal override config layers into fenced JSON with single-agent and fan-out variants and the layer behind each value. Use when asked 'which model for the subagents', 'route the roles' or 'model routing', or before a skill passes a role's model on a spawn.
principles
Module-design vocabulary for architecture findings, and the checks built on it. Use when: 'what is a deep module', 'what is a seam', 'deep vs shallow module', 'what is the deletion test', 'leverage and locality', 'module design vocabulary', 'which word do we use for X in architecture findings'. Scanning a codebase for friction is /architecture:improve.
write
Structured five-field bug report (title, steps to reproduce, expected vs actual, justified severity, suggested fix location) from an informal description, read-only. Use when the user names a defect they observed, or asks for one written up ('report a bug', 'file a bug', 'write this up as a bug').