[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77K2KX6S8Z9CVMTJ27E815C":3,"skill-same:01M77K2KX6S8Z9CVMTJ27E815C":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":50},"01M77K2KX6S8Z9CVMTJ27E815C","produce",null,"Film production from a brief and one or more style packs: boards for the user to approve, then a shot list, rendered frames, a delivered file, and a review against the pack. Use when: 'produce this film', 'animate this brief', 'storyboard then render', 'make a short in this style', 'boards for approval', 'shot list for this film'. Not for copying a reference clip (\u002Fanimation:rotoscope) or measuring a new style (\u002Fanimation:learn-style).","melodic-software\u002Fclaude-code-plugins","melodic-software","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F58273638?v=4","01M77JVQTXNGKCE4MDFY2BC936","Melodic Software","01M77JVQVN9QDWKAH6W03ANP76",30,"MIT","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fanimation\u002Fskills\u002Fproduce\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Film production from a brief and one or more style packs: boards for the user to approve, then a shot list, rendered frames, a delivered file, and a review against the pack. Use when: 'produce this film', 'animate this brief', 'storyboard then render', 'make a short in this style', 'boards for approval', 'shot list for this film'. Not for copying a reference clip (\u002Fanimation:rotoscope) or measuring a new style (\u002Fanimation:learn-style).\"\nargument-hint: \"\u003Cproduction dir>\"\nuser-invocable: true\ndisable-model-invocation: false\nmetadata:\n  workflow-stage: implement\n  summary: Brief, boards, approval gate, shots, render, and pack review\n---\n\n# Produce\n\nTurn a brief and one or more style packs into a film. Nothing past the boards renders until the\nuser approves them. `shots.json` is the only list of shot cuts.\n\nRequirements are the plugin README's. Run each script as\n`python3 ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpydeps.py run --data-dir \"${CLAUDE_PLUGIN_DATA}\" -- \u003Cscript> ...`,\nwhich uses the packages the SessionStart hook installed.\nThe gate script `${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fproduce.py` needs only the standard library.\nRendering is `${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Frender.py`; the pack check is\n`${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Finkstats.py`.\n\n## Production directory\n\nOne directory the user names. `produce.py init \u003Cdir>` creates each missing skeleton file and never\noverwrites one. Paths in these files are relative to the production directory and stay inside it.\n\n| Path | Who writes it | What it holds |\n|---|---|---|\n| `brief.md` | you | `Subject:`, `Length:`, `Audience:`, `Packs:` (comma-separated pack names), `Delivery:` |\n| `boards\u002Fstyle-guide.md` | you | `Pack:` equal to `palette.json` `pack`. Under `Differs from the pack:`, each bullet says `measured` or `judgment` |\n| `boards\u002Fpalette.json` | you | `pack`, `ink` and `paper` as `#rrggbb`, `tones` as `{lv, color}` objects, optional `tolerance` |\n| `boards\u002Fvibe.md` | you | reference images, each with a credit. A film with none still says `Credit:` |\n| `boards\u002Fmodels\u002F\u003Cname>.md` `.js` `.png` | you | at least one character sheet. The `.js` is a scene module (step 2); the `.png` is its turnaround |\n| `boards\u002Felements\u002F\u003Cname>.md` `.js` `.png` | you | the same shape, only for elements you need |\n| `boards\u002Fstoryboard.json` | you | `panels`: `{shot, panel, t, png, action, camera, caption?}`. `png` is a relative path to a real file |\n| `boards\u002Fapproval.json` | `produce.py approve` | `{approved, note, boards_digest}`. Never hand-write it |\n| `shots.json` | you, after approval | `{fps, size:[w,h], shots:[{id, t0, t1, scene, pack, audio?:{path, start}}]}`. The first `t0` is 0, and each `t1` is the next `t0` |\n| `frames\u002Frender.json` | `render.py` | the delivered film. Its `fps`, `size`, and `duration` match the shot list |\n\n## Loop\n\n1. Write `brief.md` from the request. Put unspecified length, audience, or delivery in one defaults\n   line, not a list of questions. `Packs:` names packs that exist (`styles\u002F\u003Cname>\u002F` or a pack the\n   user points at).\n2. Fill the boards. A model or element `.js` is a scene module: it sizes `canvas#c` and defines\n   `window.DURATION`, `window.renderFrame(t)` and `window.renderDrawing(k)`; `--drawings` fails\n   without `renderDrawing`. `skills\u002Frotoscope\u002Ffixtures\u002Fsynthetic.js` is a working per-drawing scene.\n   `render.py` serves the scene's own directory, then the plugin's `scripts\u002F` (`ink.js`), then each\n   `--root`: to share drawing code between board, shot and film modules, pass\n   `--root \u003Cproduction dir>` on every render and import by absolute path from it\n   (`\u002Fboards\u002Felements\u002F\u003Cname>.js`). Load what a scene needs (JSON, other modules) with static imports\n   or top-level `await`: capture starts once the module has finished loading, so `DURATION` must\n   be final by then. Render each sheet with `render.py \u003Cscene.js> \u003Cout> --drawings 0` (or the poses it needs) and copy\n   the PNG into `boards\u002Fmodels\u002F` or `boards\u002Felements\u002F`. These stills are boards, not the film.\n3. `produce.py boards \u003Cdir>` must exit 0. Fix every line it prints.\n4. Stop. Show the boards and ask the user to approve them. Do not write `shots.json`, render a\n   shot, or encode a file in this step.\n5. After the user approves, run `produce.py approve \u003Cdir> --note \"\u003Ctheir words>\"`, with their words\n   as the note. If a board changes later, the digest no longer matches and `shots` exits 2 until\n   they approve again.\n6. Author one shot module per shot and write `shots.json`. A shot module exports\n   `drawShot(ctx, t)`, which draws film time `t` (seconds from the film's start) on the context it\n   is handed, and sets no page hooks. `produce.py shots \u003Cdir>` must exit 0. `produce.py cuts \u003Cdir>`\n   prints the `t0` list.\n7. `render.py` takes one scene: author a film scene that imports `shots.json`, sets `DURATION` to\n   the last `t1`, sizes `canvas#c` to `size`, and in `renderFrame(t)` calls `drawShot` of the shot\n   whose `t0`-`t1` span holds `t`. Render it into `frames\u002F` at `shots.json` `fps` with\n   `--shots \u003Cdir>\u002Fshots.json`, which exits 1 when the film's fps, size, duration or frame count\n   differs from the shot list. `--encode` writes the delivered file beside `frames\u002F`.\n8. `produce.py review \u003Cdir>` prints `inkstats.py \u003Cframes> --cuts \u003Cdir>\u002Fshots.json --pack \u003Cpack>`\n   when every shot uses one pack, and one `--t \u003Ct0>-\u003Ct1> --pack \u003Cpack>` line per shot for mixed\n   packs, since the check judges every frame it reads. A shipped pack resolves to its `styles\u002F` directory. Run each line. Then read frames at\n   1:1 before calling the film done. A passing check whose frames do not read as the pack is a\n   fail; say which mark is wrong.\n   - When a row fails, change the drawing until the frames read as the pack, then check again.\n     Never add or change marks only to move a row into its band (extra specks, rougher strokes,\n     re-timed holds): a row passed that way is still a fail. A change to a board file closes the\n     gate, so the user approves the boards again (step 4) before the next shot render.\n   - When the frames cannot read as the pack without editing its bands, stop and report the\n     failing rows and marks (see Next).\n9. Before delivery, hand the film to a fresh-context reviewer (a subagent that is not a fork) with\n   the brief in [reference\u002Findependent-review.md](reference\u002Findependent-review.md). The builder\n   never decides the film ships: fix what the review finds, render, check and review again with a\n   new reviewer, and deliver only on its SHIP. After three reviews without a SHIP, stop and report\n   the open findings to the user.\n\nPass `--cuts` the `shots.json` path, never a retyped list.\n\n## Next\n\n\u002Fanimation:learn-style \u003Cwork dir> \u003Cpack dir>\n\nWhen the review shows the film is a different style than the pack, that is a new style study. Do\nnot edit the pack's bands to make this film pass.\n\n## Gotchas\n\n- Exit 2 from `shots` or `review` means the gate is closed; exit 1 means a field is wrong. Never\n  edit `shots.json` to get past an exit 2.\n- Model-sheet PNG files are allowed before approval. A shot render is not.\n- `audio.path` is optional; when present it is a file inside the production directory, and\n  `audio.start` is seconds into that file. `render.py --encode` does not mux it: the delivered file\n  is silent until the audio is muxed in with ffmpeg.\n- The approval gate is soft. Only `produce.py shots` and `review` consult the digest; `render.py`\n  and writing `shots.json` are not gated, and `approve --note` carries no proof that the note came\n  from the user. The gate holds only when step 5 is followed.\n- A board set has one `palette.json` and one style-guide `Pack:` line, so in a film with several\n  packs approval covers that one pack's board.\n- A style pack's bands were learned on films of at least about a third of the source. A much\n  shorter film can fail a row the pictures do not deserve; say so, and do not edit the pack.\n  Verified 2026-09-29 against `skills\u002Flearn-style\u002Freference\u002Fstatistics.md` \"Short films\" (at least\n  a third of the source, about 10 s) and the `FLOOR` constant in\n  `skills\u002Flearn-style\u002Fscripts\u002Flearn.py` (`1 \u002F 3`). Recheck when that section or `FLOOR` changes.\n","# Produce\n\nTurn a brief and one or more style packs into a film. Nothing past the boards renders until the\nuser approves them. `shots.json` is the only list of shot cuts.\n\nRequirements are the plugin README's. Run each script as\n`python3 ${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpydeps.py run --data-dir \"${CLAUDE_PLUGIN_DATA}\" -- \u003Cscript> ...`,\nwhich uses the packages the SessionStart hook installed.\nThe gate script `${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fproduce.py` needs only the standard library.\nRendering is `${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Frender.py`; the pack check is\n`${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Finkstats.py`.\n\n## Production directory\n\nOne directory the user names. `produce.py init \u003Cdir>` creates each missing skeleton file and never\noverwrites one. Paths in these files are relative to the production directory and stay inside it.\n\n| Path | Who writes it | What it holds |\n|---|---|---|\n| `brief.md` | you | `Subject:`, `Length:`, `Audience:`, `Packs:` (comma-separated pack names), `Delivery:` |\n| `boards\u002Fstyle-guide.md` | you | `Pack:` equal to `palette.json` `pack`. Under `Differs from the pack:`, each bullet says `measured` or `judgment` |\n| `boards\u002Fpalette.json` | you | `pack`, `ink` and `paper` as `#rrggbb`, `tones` as `{lv, color}` objects, optional `tolerance` |\n| `boards\u002Fvibe.md` | you | reference images, each with a credit. A film with none still says `Credit:` |\n| `boards\u002Fmodels\u002F\u003Cname>.md` `.js` `.png` | you | at least one character sheet. The `.js` is a scene module (step 2); the `.png` is its turnaround |\n| `boards\u002Felements\u002F\u003Cname>.md` `.js` `.png` | you | the same shape, only for elements you need |\n| `boards\u002Fstoryboard.json` | you | `panels`: `{shot, panel, t, png, action, camera, caption?}`. `png` is a relative path to a real file |\n| `boards\u002Fapproval.json` | `produce.py approve` | `{approved, note, boards_digest}`. Never hand-write it |\n| `shots.json` | you, after approval | `{fps, size:[w,h], shots:[{id, t0, t1, scene, pack, audio?:{path, start}}]}`. The first `t0` is 0, and each `t1` is the next `t0` |\n| `frames\u002Frender.json` | `render.py` | the delivered film. Its `fps`, `size`, and `duration` match the shot list |\n\n## Loop\n\n1. Write `brief.md` from the request. Put unspecified length, audience, or delivery in one defaults\n   line, not a list of questions. `Packs:` names packs that exist (`styles\u002F\u003Cname>\u002F` or a pack the\n   user points at).\n2. Fill the boards. A model or element `.js` is a scene module: it sizes `canvas#c` and defines\n   `window.DURATION`, `window.renderFrame(t)` and `window.renderDrawing(k)`; `--drawings` fails\n   without `renderDrawing`. `skills\u002Frotoscope\u002Ffixtures\u002Fsynthetic.js` is a working per-drawing scene.\n   `render.py` serves the scene's own directory, then the plugin's `scripts\u002F` (`ink.js`), then each\n   `--root`: to share drawing code between board, shot and film modules, pass\n   `--root \u003Cproduction dir>` on every render and import by absolute path from it\n   (`\u002Fboards\u002Felements\u002F\u003Cname>.js`). Load what a scene needs (JSON, other modules) with static imports\n   or top-level `await`: capture starts once the module has finished loading, so `DURATION` must\n   be final by then. Render each sheet with `render.py \u003Cscene.js> \u003Cout> --drawings 0` (or the poses it needs) and copy\n   the PNG into `boards\u002Fmodels\u002F` or `boards\u002Felements\u002F`. These stills are boards, not the film.\n3. `produce.py boards \u003Cdir>` must exit 0. Fix every line it prints.\n4. Stop. Show the boards and ask the user to approve them. Do not write `shots.json`, render a\n   shot, or encode a file in this step.\n5. After the user approves, run `produce.py approve \u003Cdir> --note \"\u003Ctheir words>\"`, with their words\n   as the note. If a board changes later, the digest no longer matches and `shots` exits 2 until\n   they approve again.\n6. Author one shot module per shot and write `shots.json`. A shot module exports\n   `drawShot(ctx, t)`, which draws film time `t` (seconds from the film's start) on the context it\n   is handed, and sets no page hooks. `produce.py shots \u003Cdir>` must exit 0. `produce.py cuts \u003Cdir>`\n   prints the `t0` list.\n7. `render.py` takes one scene: author a film scene that imports `shots.json`, sets `DURATION` to\n   the last `t1`, sizes `canvas#c` to `size`, and in `renderFrame(t)` calls `drawShot` of the shot\n   whose `t0`-`t1` span holds `t`. Render it into `frames\u002F` at `shots.json` `fps` with\n   `--shots \u003Cdir>\u002Fshots.json`, which exits 1 when the film's fps, size, duration or frame count\n   differs from the shot list. `--encode` writes the delivered file beside `frames\u002F`.\n8. `produce.py review \u003Cdir>` prints `inkstats.py \u003Cframes> --cuts \u003Cdir>\u002Fshots.json --pack \u003Cpack>`\n   when every shot uses one pack, and one `--t \u003Ct0>-\u003Ct1> --pack \u003Cpack>` line per shot for mixed\n   packs, since the check judges every frame it reads. A shipped pack resolves to its `styles\u002F` directory. Run each line. Then read frames at\n   1:1 before calling the film done. A passing check whose frames do not read as the pack is a\n   fail; say which mark is wrong.\n   - When a row fails, change the drawing until the frames read as the pack, then check again.\n     Never add or change marks only to move a row into its band (extra specks, rougher strokes,\n     re-timed holds): a row passed that way is still a fail. A change to a board file closes the\n     gate, so the user approves the boards again (step 4) before the next shot render.\n   - When the frames cannot read as the pack without editing its bands, stop and report the\n     failing rows and marks (see Next).\n9. Before delivery, hand the film to a fresh-context reviewer (a subagent that is not a fork) with\n   the brief in [reference\u002Findependent-review.md](reference\u002Findependent-review.md). The builder\n   never decides the film ships: fix what the review finds, render, check and review again with a\n   new reviewer, and deliver only on its SHIP. After three reviews without a SHIP, stop and report\n   the open findings to the user.\n\nPass `--cuts` the `shots.json` path, never a retyped list.\n\n## Next\n\n\u002Fanimation:learn-style \u003Cwork dir> \u003Cpack dir>\n\nWhen the review shows the film is a different style than the pack, that is a new style study. Do\nnot edit the pack's bands to make this film pass.\n\n## Gotchas\n\n- Exit 2 from `shots` or `review` means the gate is closed; exit 1 means a field is wrong. Never\n  edit `shots.json` to get past an exit 2.\n- Model-sheet PNG files are allowed before approval. A shot render is not.\n- `audio.path` is optional; when present it is a file inside the production directory, and\n  `audio.start` is seconds into that file. `render.py --encode` does not mux it: the delivered file\n  is silent until the audio is muxed in with ffmpeg.\n- The approval gate is soft. Only `produce.py shots` and `review` consult the digest; `render.py`\n  and writing `shots.json` are not gated, and `approve --note` carries no proof that the note came\n  from the user. The gate holds only when step 5 is followed.\n- A board set has one `palette.json` and one style-guide `Pack:` line, so in a film with several\n  packs approval covers that one pack's board.\n- A style pack's bands were learned on films of at least about a third of the source. A much\n  shorter film can fail a row the pictures do not deserve; say so, and do not edit the pack.\n  Verified 2026-09-29 against `skills\u002Flearn-style\u002Freference\u002Fstatistics.md` \"Short films\" (at least\n  a third of the source, about 10 s) and the `FLOOR` constant in\n  `skills\u002Flearn-style\u002Fscripts\u002Flearn.py` (`1 \u002F 3`). Recheck when that section or `FLOOR` changes.\n",{"metadata":24,"description":7,"argument-hint":27,"user-invocable":28,"disable-model-invocation":20},{"summary":25,"workflow-stage":26},"Brief, boards, approval gate, shots, render, and pack review","implement","\u003Cproduction dir>",true,"main","d0e68c3f36b92a1d6381f0ba0060d7a0b8b886c5","plugins\u002Fanimation\u002Fskills\u002Fproduce",7,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins","https:\u002F\u002Fgithub.com\u002Fmelodic-software","https:\u002F\u002Fmelodicsoftware.com","Independent software studio building developer tools, automation, and application services, with roots in music.","2026-11-15 05:15:06",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":28},[40,43,46],{"tool":41,"command":42},"npx","npx skills add melodic-software\u002Fclaude-code-plugins --skill produce",{"tool":44,"command":45},"bunx","bunx skills add melodic-software\u002Fclaude-code-plugins --skill produce",{"tool":47,"command":48},"pnpm","pnpm dlx skills add melodic-software\u002Fclaude-code-plugins --skill produce","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fanimation\u002Fskills\u002Fproduce\u002FSKILL.md",[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"reference\u002Findependent-review.md","REFERENCE","参考文档",2329,"https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fanimation\u002Fskills\u002Fproduce\u002Freference\u002Findependent-review.md",[58,65,72,79,84,91],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DYYDG31B9YX7N9MB9QW2GW","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.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsession-flow\u002Fevals\u002Frecall-still-reports-reopened-bug\u002Fwork-items-stub\u002Fskills\u002Ftrack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7DYXVBAVG3NV30PA7GKW9Q6","reviewer-media","Reviewer media for one pull request: decides whether it needs a narrated walkthrough, builds the storyboard from \u002Freview:explain-change's digest, has \u002Fexplainer-video:produce render it and hands the manifest to \u002Fsource-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.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freview\u002Fskills\u002Freviewer-media\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DYRZ5YD44AMYH26YR25GZ8","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.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdiscovery\u002Fevals\u002Fex-model-pin-without-override\u002Fmulti-agent-stub\u002Fskills\u002Froute\u002FSKILL.md",[],[],{"skillNo":80,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7DYRTVT4FWTGDJY0HCCFJMZ","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fdiscovery\u002Fevals\u002Fex-model-override-from-route\u002Fmulti-agent-stub\u002Fskills\u002Froute\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7DYNZC8PNW3T27V2ADKECKJ","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 \u002Farchitecture:improve.","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Farchitecture\u002Fskills\u002Fprinciples\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7DYNMCZNEWBFHV9KTSS6H60","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').","https:\u002F\u002Fgithub.com\u002Fmelodic-software\u002Fclaude-code-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Farchitecture\u002Fevals\u002Fdeepening-defect-goes-to-bugs-write\u002Fbugs-stub\u002Fskills\u002Fwrite\u002FSKILL.md",[],[]]