[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79HHRYW9KK6ZD0D8FSKA006":3,"skill-same:01M79HHRYW9KK6ZD0D8FSKA006":48},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79HHRYW9KK6ZD0D8FSKA006","blueprint-authoring",null,"Draft, refine, and tidy a multi-file project blueprint under blueprint\u002F as the exploratory pre-foundation draft, before any docs or specification work.","1naichii\u002Fai-engineering-starter","1naichii","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F152734670?v=4","01M79HHQD0PPGMD6EHPGN1YEDP",".mochaa","01M79HHQE5KHHHXYVYXSDX6RSX",0,"MIT","https:\u002F\u002Fgithub.com\u002F1naichii\u002Fai-engineering-starter\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fblueprint-authoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: blueprint-authoring\ndescription: Draft, refine, and tidy a multi-file project blueprint under blueprint\u002F as the exploratory pre-foundation draft, before any docs or specification work.\ncompatibility: Codex and OpenCode\nmetadata:\n  version: \"1.0.0\"\n---\n\n# Blueprint Authoring\n\nCreate and maintain the project blueprint under `blueprint\u002F`: the earliest,\nexploratory draft that captures product intent, technical direction, scope, and\nopen questions before they are promoted into the `docs\u002F` foundation or into\n`specs\u002F`. This is the draft stage. It is allowed to be tentative and to propose\noptions, but every open decision must be marked as open, not silently resolved.\n\nThe blueprint is upstream of everything: `docs-author` later transcribes the\napproved blueprint into `docs\u002F`, and `spec-writer` turns its buildable features\ninto `specs\u002F`.\n\n## Inputs\n\n- The operator's product idea, notes, or an existing blueprint to refine.\n- The current `blueprint\u002F` files, if any, and `blueprint\u002FREADME.md` for the format.\n- Do not read or depend on `docs\u002F` or `specs\u002F`; the blueprint precedes them.\n\n## Blueprint format\n\nFollow the multi-file convention documented in `blueprint\u002FREADME.md`:\n\n- `blueprint\u002FREADME.md` is the index: metadata blockquote (working title, tagline, type, stack, architecture summary, estimate, status), reading order, a file-list table with section numbers, a one-paragraph summary, and an explicit status marker.\n- Each section file starts with a `# §n — Title` heading and a navigation line linking the previous and next sections, then cross-references other sections as `[§n](file)`.\n- Code blocks that state a binding contract or algorithm are marked as binding; illustrative snippets are marked as illustration.\n- Version history is accumulative: append a new version row, never rewrite past decisions. A newer version may supersede conflicting detail, but the record of the older decision stays.\n\n## Procedure\n\n1. If starting fresh, scaffold from the template files under `blueprint\u002F`, filling bracketed placeholders. If refining, read the existing blueprint in full first.\n2. Capture, in the right section files: pitch, mental model, feature scope (MVP \u002F stretch \u002F later \u002F out of scope), tech stack, architecture, data model, technical deep dives, access control, folder structure, roadmap, notable challenges, positioning, and — for anything with a user interface — UX and design intent in §16.\n3. Keep the `README.md` index, reading order, and file-list table in sync with the files that actually exist.\n4. Record every unresolved product or technical decision explicitly as an open question rather than inventing an answer. Tentative choices must be labelled tentative.\n5. When tidying, preserve exact numbers, version pins, thresholds, and binding contracts the source already states; do not paraphrase a precise value.\n6. Update the version history and the status marker to reflect the current state.\n\n## Stop conditions\n\nStop and ask the operator when: the product goal itself is undefined, two sources conflict on a decision that changes scope, or the request would require promoting the draft into `docs\u002F` or `specs\u002F` (that is downstream work for `docs-author` and `spec-writer`).\n\n## Scope limits\n\n- Modify only files under `blueprint\u002F`.\n- Never create or edit `docs\u002F`, `specs\u002F`, application code, tests, agent configuration, policies, scripts, or CI.\n- Never present a tentative or invented decision as settled; open questions stay visible.\n- Never rewrite version history to erase a past decision.\n\n## Output\n\nReport the exact `blueprint\u002F` files changed, the current status marker, and the list of open questions the operator must resolve before the blueprint is promoted to `docs\u002F` and `specs\u002F`.\n","# Blueprint Authoring\n\nCreate and maintain the project blueprint under `blueprint\u002F`: the earliest,\nexploratory draft that captures product intent, technical direction, scope, and\nopen questions before they are promoted into the `docs\u002F` foundation or into\n`specs\u002F`. This is the draft stage. It is allowed to be tentative and to propose\noptions, but every open decision must be marked as open, not silently resolved.\n\nThe blueprint is upstream of everything: `docs-author` later transcribes the\napproved blueprint into `docs\u002F`, and `spec-writer` turns its buildable features\ninto `specs\u002F`.\n\n## Inputs\n\n- The operator's product idea, notes, or an existing blueprint to refine.\n- The current `blueprint\u002F` files, if any, and `blueprint\u002FREADME.md` for the format.\n- Do not read or depend on `docs\u002F` or `specs\u002F`; the blueprint precedes them.\n\n## Blueprint format\n\nFollow the multi-file convention documented in `blueprint\u002FREADME.md`:\n\n- `blueprint\u002FREADME.md` is the index: metadata blockquote (working title, tagline, type, stack, architecture summary, estimate, status), reading order, a file-list table with section numbers, a one-paragraph summary, and an explicit status marker.\n- Each section file starts with a `# §n — Title` heading and a navigation line linking the previous and next sections, then cross-references other sections as `[§n](file)`.\n- Code blocks that state a binding contract or algorithm are marked as binding; illustrative snippets are marked as illustration.\n- Version history is accumulative: append a new version row, never rewrite past decisions. A newer version may supersede conflicting detail, but the record of the older decision stays.\n\n## Procedure\n\n1. If starting fresh, scaffold from the template files under `blueprint\u002F`, filling bracketed placeholders. If refining, read the existing blueprint in full first.\n2. Capture, in the right section files: pitch, mental model, feature scope (MVP \u002F stretch \u002F later \u002F out of scope), tech stack, architecture, data model, technical deep dives, access control, folder structure, roadmap, notable challenges, positioning, and — for anything with a user interface — UX and design intent in §16.\n3. Keep the `README.md` index, reading order, and file-list table in sync with the files that actually exist.\n4. Record every unresolved product or technical decision explicitly as an open question rather than inventing an answer. Tentative choices must be labelled tentative.\n5. When tidying, preserve exact numbers, version pins, thresholds, and binding contracts the source already states; do not paraphrase a precise value.\n6. Update the version history and the status marker to reflect the current state.\n\n## Stop conditions\n\nStop and ask the operator when: the product goal itself is undefined, two sources conflict on a decision that changes scope, or the request would require promoting the draft into `docs\u002F` or `specs\u002F` (that is downstream work for `docs-author` and `spec-writer`).\n\n## Scope limits\n\n- Modify only files under `blueprint\u002F`.\n- Never create or edit `docs\u002F`, `specs\u002F`, application code, tests, agent configuration, policies, scripts, or CI.\n- Never present a tentative or invented decision as settled; open questions stay visible.\n- Never rewrite version history to erase a past decision.\n\n## Output\n\nReport the exact `blueprint\u002F` files changed, the current status marker, and the list of open questions the operator must resolve before the blueprint is promoted to `docs\u002F` and `specs\u002F`.\n",{"name":5,"metadata":24,"description":7,"compatibility":26},{"version":25},"1.0.0","Codex and OpenCode","main","5f3ca0700214ee19e51249f736b8048bcfaf6064",".agents\u002Fskills\u002Fblueprint-authoring","https:\u002F\u002Fgithub.com\u002F1naichii\u002Fai-engineering-starter","https:\u002F\u002Fgithub.com\u002F1naichii","just a person who is addicted to anime :b","2026-07-29 14:58:57",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add 1naichii\u002Fai-engineering-starter --skill blueprint-authoring",{"tool":40,"command":41},"bunx","bunx skills add 1naichii\u002Fai-engineering-starter --skill blueprint-authoring",{"tool":43,"command":44},"pnpm","pnpm dlx skills add 1naichii\u002Fai-engineering-starter --skill blueprint-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F1naichii\u002Fai-engineering-starter\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fblueprint-authoring\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M79HNKF6ZB9J69QC524HXTME","workflow-retrospective","Improve the durable workflow when the same agent, review, test, scope, or validation failure pattern recurs; use after incidents or repeated verifier returns.","https:\u002F\u002Fgithub.com\u002F1naichii\u002Fai-engineering-starter\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworkflow-retrospective\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M79HNHD4K5N9PMN793F40KQ1","verification","Perform final independent read-only verification of acceptance criteria, review remediation, test integrity, scope, and quality-gate evidence.","https:\u002F\u002Fgithub.com\u002F1naichii\u002Fai-engineering-starter\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79HNEKSJS296CJDEBJVSZG6","ticket-authoring","Turn a reported or observed defect into one reviewable ticket under tickets\u002F with reproduction, evidence, impact, and closure criteria, bound to a fix version — without fixing it or rewriting it into a specification.","https:\u002F\u002Fgithub.com\u002F1naichii\u002Fai-engineering-starter\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fticket-authoring\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79HNC6V7YRQNEB3R7A5SC31","technical-planning","Create a read-only implementation plan from an approved specification before code changes; use for non-trivial features, bugs, migrations, and cross-module work.","https:\u002F\u002Fgithub.com\u002F1naichii\u002Fai-engineering-starter\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftechnical-planning\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"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},"01M79HN9F2JKZS82EHS9A40WNW","skill-governance","Audit newly installed or updated agent skills as untrusted content and propose required, optional, or denied assignments to existing agent roles. Use after staging a skills.sh installation and before promoting the skill or changing agent permissions.","https:\u002F\u002Fgithub.com\u002F1naichii\u002Fai-engineering-starter\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fskill-governance\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},"01M79HN799GY36V3SYVASG69YB","security-review","Adversarially review authentication, authorization, tenant isolation, sensitive data, abuse resistance, and production reliability for a completed implementation.","https:\u002F\u002Fgithub.com\u002F1naichii\u002Fai-engineering-starter\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]