[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75Y2MV6YJYRH4TWNQJ57KA7":3,"skill-same:01M75Y2MV6YJYRH4TWNQJ57KA7":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M75Y2MV6YJYRH4TWNQJ57KA7","fix",null,"Write a current-feature.md spec for an ad-hoc bug fix or small unplanned change, then stop before implementation. Use for \u002Ffix, confirmed bugs, or small changes that do not belong in the build plan.","aiblueprinthq\u002Fai-blueprint","aiblueprinthq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F317905365?v=4","01M75XZGKSB8GPVXQ69BA57VA7","01M75XZGME4HNZG9CDB8K3TQ8X",510,"MIT","https:\u002F\u002Fgithub.com\u002Faiblueprinthq\u002Fai-blueprint\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffix\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: fix\ndescription: Write a current-feature.md spec for an ad-hoc bug fix or small unplanned change, then stop before implementation. Use for \u002Ffix, confirmed bugs, or small changes that do not belong in the build plan.\ndisable-model-invocation: true\n---\n\n# fix - document an ad-hoc fix, then build it like anything else\n\n**Context reuse:** Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.\n\n**First action:** Before project inspection, preflight, or any other tool call,\npublish `running` to `blueprint\u002F.state\u002Frun.json` when `blueprint\u002F.state\u002F`\nexists. From the project root, run the first helper that exists,\n`node .agents\u002Fskills\u002Fblueprint-doctor\u002Fscripts\u002Frun-state.mjs` or\n`node .claude\u002Fskills\u002Fblueprint-doctor\u002Fscripts\u002Frun-state.mjs`, with `start --command\n\u003Cskill> --summary \"\u003Ctruthful summary>\" --boundary\n\u003Cread-only|reviewed|local-only>`. Use `update` at milestones, with `--status\nblocked --resume \u003Ccommand>` for a blocker, and `finish --status ready|completed`\nat the end; `--help` lists every option and `blueprint\u002Fworkflow.md` has the full\nactivity contract. A missing or failing helper is a warning, not a blocker.\n\nWhere this sits in the workflow:\n\n    \u002Ffix  ->  \u002Fimplement  ->  \u002Fcomplete  ->  back to your features\n    (spec     (build it,      (log to blueprint\u002Fhistory\u002Ffixes\u002F\n     the fix)  reviewed)       + merge)\n\nA fix is a bug or small change that isn't a planned build-plan feature. It runs\nthrough the same loop as a feature (build with review gates, iterate, then merge);\nit just starts here instead of `\u002Ffeature`, and is logged separately.\n\n## Input\n\nA description of the bug or change, for example `\u002Ffix \"password reset email never\nsends\"`. If the user just reported the problem in chat, use that.\n\nThe input may also be a finding ID from `blueprint\u002Fcontext\u002Ffindings.md`, alone\nor with a description, for example `\u002Ffix F-03`. Pull the problem statement from\nthat ledger entry. Use this form only between work items, when\n`current-feature.md` is the reset stub: this skill overwrites that file, so\nwhile a spec is active, repair its findings through `\u002Fimplement` instead.\nNever replace another worker's active spec. Parallel work uses one clone or Git\nworktree per work item, with a separate branch in each checkout.\n\n## Step 1 - write the fix spec\n\nPull context from `blueprint\u002Fcontext\u002Fproject-overview.md` and `blueprint\u002Fcontext\u002Fcoding-standards.md`,\nthen write a short spec to `blueprint\u002Fcontext\u002Fcurrent-feature.md` (this file holds whatever\nis being built now, feature or fix). Its first heading must be exactly\n`# Fix: \u003Ctitle>`, and it must retain the `**Type:** Fix` contract below. Keep it\nlighter than a feature spec:\n\n- **Title** - the bug or change in a few words.\n- **Type:** Fix  (so `\u002Fcomplete` logs it to `blueprint\u002Fhistory\u002Ffixes\u002F`, not `blueprint\u002Fhistory\u002Ffeatures\u002F`).\n- **Status:** not started - `\u002Fimplement` updates this durable workflow state as\n  work and verification progress.\n- **Branch:** the full fix branch from the configured prefix plus the fix title\n  in lowercase kebab-case.\n- **Fixes:** `\u003Cfinding id>` - only when the fix targets a ledger finding. The\n  stamp makes the repair traceable: `\u002Fimplement` marks that finding `fixed`\n  when the repairing step lands, and `\u002Faudit` re-reviews it before it closes.\n- **The problem** - what's wrong or what needs to change, and where.\n- **The fix** - the root-cause repair, and anything it must not break. Do not add\n  an abstraction, dependency, service, configuration surface, compatibility\n  layer, or security mechanism unless the defect is in that layer or an\n  established repository requirement needs it now. Adding a missing\n  authorization, ownership, validation, escaping, or redaction check is a\n  root-cause repair, not new machinery.\n- **Build steps** - usually one small step; split only if the diff would be too\n  big to read. Each ends with an observable \"done when\".\n- **Verify** - how to confirm it's fixed (what to click or test).\n\nThen stop. Tell the user to review the fix spec, then run `\u002Fimplement` to build it.\n\n## Rules\n\n- A fix is not a build-plan item; don't add it to `build-plan.md`.\n- Removing a completed feature is a fix. Keep its original feature archive. The\n  plans stay user-owned: to build it again later, the user unchecks its item; if\n  it is abandoned, they edit the plans and rerun `\u002Foverview`.\n- Keep it small. If it's really a new feature, use `\u002Ffeature` and the build plan\n  instead.\n- Same conventions as everything else (`blueprint\u002Fcontext\u002Fcoding-standards.md`).\n\n## Formatting\n\nFormat the output to match the project's conventions in\n`blueprint\u002Fcontext\u002Fai-interaction.md`: concise, scannable markdown, with lists for\nenumerations and tables for matrices rather than dense paragraphs.\n","# fix - document an ad-hoc fix, then build it like anything else\n\n**Context reuse:** Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.\n\n**First action:** Before project inspection, preflight, or any other tool call,\npublish `running` to `blueprint\u002F.state\u002Frun.json` when `blueprint\u002F.state\u002F`\nexists. From the project root, run the first helper that exists,\n`node .agents\u002Fskills\u002Fblueprint-doctor\u002Fscripts\u002Frun-state.mjs` or\n`node .claude\u002Fskills\u002Fblueprint-doctor\u002Fscripts\u002Frun-state.mjs`, with `start --command\n\u003Cskill> --summary \"\u003Ctruthful summary>\" --boundary\n\u003Cread-only|reviewed|local-only>`. Use `update` at milestones, with `--status\nblocked --resume \u003Ccommand>` for a blocker, and `finish --status ready|completed`\nat the end; `--help` lists every option and `blueprint\u002Fworkflow.md` has the full\nactivity contract. A missing or failing helper is a warning, not a blocker.\n\nWhere this sits in the workflow:\n\n    \u002Ffix  ->  \u002Fimplement  ->  \u002Fcomplete  ->  back to your features\n    (spec     (build it,      (log to blueprint\u002Fhistory\u002Ffixes\u002F\n     the fix)  reviewed)       + merge)\n\nA fix is a bug or small change that isn't a planned build-plan feature. It runs\nthrough the same loop as a feature (build with review gates, iterate, then merge);\nit just starts here instead of `\u002Ffeature`, and is logged separately.\n\n## Input\n\nA description of the bug or change, for example `\u002Ffix \"password reset email never\nsends\"`. If the user just reported the problem in chat, use that.\n\nThe input may also be a finding ID from `blueprint\u002Fcontext\u002Ffindings.md`, alone\nor with a description, for example `\u002Ffix F-03`. Pull the problem statement from\nthat ledger entry. Use this form only between work items, when\n`current-feature.md` is the reset stub: this skill overwrites that file, so\nwhile a spec is active, repair its findings through `\u002Fimplement` instead.\nNever replace another worker's active spec. Parallel work uses one clone or Git\nworktree per work item, with a separate branch in each checkout.\n\n## Step 1 - write the fix spec\n\nPull context from `blueprint\u002Fcontext\u002Fproject-overview.md` and `blueprint\u002Fcontext\u002Fcoding-standards.md`,\nthen write a short spec to `blueprint\u002Fcontext\u002Fcurrent-feature.md` (this file holds whatever\nis being built now, feature or fix). Its first heading must be exactly\n`# Fix: \u003Ctitle>`, and it must retain the `**Type:** Fix` contract below. Keep it\nlighter than a feature spec:\n\n- **Title** - the bug or change in a few words.\n- **Type:** Fix  (so `\u002Fcomplete` logs it to `blueprint\u002Fhistory\u002Ffixes\u002F`, not `blueprint\u002Fhistory\u002Ffeatures\u002F`).\n- **Status:** not started - `\u002Fimplement` updates this durable workflow state as\n  work and verification progress.\n- **Branch:** the full fix branch from the configured prefix plus the fix title\n  in lowercase kebab-case.\n- **Fixes:** `\u003Cfinding id>` - only when the fix targets a ledger finding. The\n  stamp makes the repair traceable: `\u002Fimplement` marks that finding `fixed`\n  when the repairing step lands, and `\u002Faudit` re-reviews it before it closes.\n- **The problem** - what's wrong or what needs to change, and where.\n- **The fix** - the root-cause repair, and anything it must not break. Do not add\n  an abstraction, dependency, service, configuration surface, compatibility\n  layer, or security mechanism unless the defect is in that layer or an\n  established repository requirement needs it now. Adding a missing\n  authorization, ownership, validation, escaping, or redaction check is a\n  root-cause repair, not new machinery.\n- **Build steps** - usually one small step; split only if the diff would be too\n  big to read. Each ends with an observable \"done when\".\n- **Verify** - how to confirm it's fixed (what to click or test).\n\nThen stop. Tell the user to review the fix spec, then run `\u002Fimplement` to build it.\n\n## Rules\n\n- A fix is not a build-plan item; don't add it to `build-plan.md`.\n- Removing a completed feature is a fix. Keep its original feature archive. The\n  plans stay user-owned: to build it again later, the user unchecks its item; if\n  it is abandoned, they edit the plans and rerun `\u002Foverview`.\n- Keep it small. If it's really a new feature, use `\u002Ffeature` and the build plan\n  instead.\n- Same conventions as everything else (`blueprint\u002Fcontext\u002Fcoding-standards.md`).\n\n## Formatting\n\nFormat the output to match the project's conventions in\n`blueprint\u002Fcontext\u002Fai-interaction.md`: concise, scannable markdown, with lists for\nenumerations and tables for matrices rather than dense paragraphs.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","483eb73dbc58a4b82a5642f864ea7569af947e39",".claude\u002Fskills\u002Ffix",132,"https:\u002F\u002Fgithub.com\u002Faiblueprinthq\u002Fai-blueprint","https:\u002F\u002Fai-blueprint.dev","https:\u002F\u002Fgithub.com\u002Faiblueprinthq","2026-11-14 19:46:05",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":23},[34,37,40],{"tool":35,"command":36},"npx","npx skills add aiblueprinthq\u002Fai-blueprint --skill fix",{"tool":38,"command":39},"bunx","bunx skills add aiblueprinthq\u002Fai-blueprint --skill fix",{"tool":41,"command":42},"pnpm","pnpm dlx skills add aiblueprinthq\u002Fai-blueprint --skill fix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faiblueprinthq\u002Fai-blueprint\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffix\u002FSKILL.md",[],[46,52,57,64,71,78],{"skillNo":47,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M75Y34X26C74A66RYE49W8JY","status","https:\u002F\u002Fgithub.com\u002Faiblueprinthq\u002Fai-blueprint\u002Fblob\u002Fmain\u002Fpackages\u002Fcreate-ai-blueprint\u002Ftest\u002Ffixtures\u002Fhealthy-blueprint\u002F.claude\u002Fskills\u002Fstatus\u002FSKILL.md",[],[],{"skillNo":53,"name":48,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M75Y3456H4WZZ25634QY9KRA","https:\u002F\u002Fgithub.com\u002Faiblueprinthq\u002Fai-blueprint\u002Fblob\u002Fmain\u002Fpackages\u002Fcreate-ai-blueprint\u002Ftest\u002Ffixtures\u002Fhealthy-blueprint\u002F.agents\u002Fskills\u002Fstatus\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M75Y31WCYVFM5M4NH7D9MRMW","tests","Set up unit testing with \u002Ftests or \u002Ftests unit, or explicitly set up browser and end-to-end testing with \u002Ftests browser. Reuse or install a suitable test runner, add one example or smoke test, document commands, and verify. Use check for one-time live verification.","https:\u002F\u002Fgithub.com\u002Faiblueprinthq\u002Fai-blueprint\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftests\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75Y2ZETQZEHN2V19HWZBB1R","prototype","Plan and create throwaway static HTML and CSS mockups with shared design tokens before feature implementation. Use for \u002Fprototype, screen mockups, layout exploration, themes, or deciding a project's look and feel.","https:\u002F\u002Fgithub.com\u002Faiblueprinthq\u002Fai-blueprint\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fprototype\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75Y2WY81F9N40G2RADX2FKH","overview","Validate and normalize project-plan.md and build-plan.md, then generate the durable project-overview.md used by agents. Use for \u002Foverview, plan cleanup, generating the first overview, or refreshing context after either plan changes.","https:\u002F\u002Fgithub.com\u002Faiblueprinthq\u002Fai-blueprint\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Foverview\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75Y2SNF3FZJP3NHRT0B5MQE","onboard","Onboard a fresh or early scaffold after Blueprint is overlaid by tuning commands, standards, adapters, visibility, and context loading. Use for \u002Fonboard, fresh installation setup, or what to do after installing Blueprint. Use adopt for an established app.","https:\u002F\u002Fgithub.com\u002Faiblueprinthq\u002Fai-blueprint\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fonboard\u002FSKILL.md",[],[]]