[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75Y2FYRG9GEFF8YTH8A6XDN":3,"skill-same:01M75Y2FYRG9GEFF8YTH8A6XDN":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},"01M75Y2FYRG9GEFF8YTH8A6XDN","explore",null,"Explore an idea against the actual codebase without changing files. Investigate whether a change would help, compare alternatives and tradeoffs, and discuss uncertainty before deciding whether to plan anything. Use for \u002Fexplore, considering an idea, or weighing options without writing a spec.","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\u002Fexplore\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: explore\ndescription: Explore an idea against the actual codebase without changing files. Investigate whether a change would help, compare alternatives and tradeoffs, and discuss uncertainty before deciding whether to plan anything. Use for \u002Fexplore, considering an idea, or weighing options without writing a spec.\ndisable-model-invocation: true\n---\n\n# explore - investigate an idea before deciding to build\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\nExplore is a read-only conversation grounded in the actual project. It can help\nwith questions such as whether caching would help a dashboard, whether teams\nbelong in the product, or which upload approach fits existing code.\n\nNo plans or active feature are required. Do not require `\u002Foverview`, invent a\nplan, or treat missing Blueprint context as a blocker to discussing the idea.\nThis command never writes activity state, including `blueprint\u002F.state\u002Frun.json`.\n\n## Start from the question\n\nUse the supplied topic or relevant conversation context. With neither, ask what\nthe user wants to investigate. For a vague idea, state a tentative interpretation\nand ask a focused question only when its answer changes the investigation.\n\nReuse context already loaded in the session. Read relevant project instructions,\ncode, tests as text, manifests, and existing plans when they help answer the\nquestion. Follow the actual implementation far enough to support your claims;\npoint to concrete files or symbols. Avoid scanning unrelated parts of the repo.\nRead-only Git inspection can establish what exists or is already in progress.\n\nAuthoritative documentation lookup is appropriate when technical uncertainty\nneeds it. Distinguish documented facts from what this project actually uses.\nMissing code or evidence is an uncertainty to explain, not permission to execute\nan experiment or to invent current behavior.\n\n## Discuss the options\n\nKeep the conversation proportional to the question. Compare plausible options\nagainst the user's needs and existing project constraints. Include doing nothing\nwhen the current behavior may already be sufficient. Do not invent scale,\nsecurity requirements, or new abstractions to justify a change.\n\nExplain the strongest case against your recommendation and how confident you\nare. Separate observed facts, assumptions, and unanswered questions. Say what\nevidence could change the recommendation without gathering it through execution.\nAn unresolved question or a recommendation to leave the project alone is a valid\noutcome.\n\nUse a small diagram in the response when it makes a relationship or tradeoff\nclearer. Do not create diagram files. There is no mandatory output template,\nreport, question count, or next-step checklist. Follow the user's responses and\nlet the discussion continue as long as useful.\n\n## Keep the boundaries clear\n\n- Never create, edit, or delete files, including specs, plans, notes, generated\n  output, and activity state. Do not save the conversation into the project.\n- Never install dependencies, execute product code, run tests or builds, start\n  servers, perform browser interactions, or call state-changing tools. Read\n  source and existing evidence instead of testing a hypothesis by execution.\n- Never create or switch branches, commit, merge, push, publish, or deploy.\n- Never turn a request to discuss an idea into approval to plan or implement it.\n  If the user asks for changes, explain the appropriate handoff and keep this\n  Explore invocation read-only. Do not invoke another command automatically.\n\n## Neighbors and handoff\n\n- `\u002Fbrief` explains an existing build-plan item, its scope, dependencies, and\n  size. Explore can discuss an unplanned idea or question a planned approach.\n- `\u002Fdiscovery` develops broader product direction and reviewed planning drafts.\n  Explore does not draft either planning file.\n- `\u002Fdebug` reproduces and isolates an actual failure. Explore discusses options\n  without executing code to diagnose or verify them.\n- `\u002Ffeature` writes a buildable spec; `\u002Ffix` specifies a confirmed small change.\n  Suggest the appropriate command only when the user is ready to proceed.\n\nDo not force a handoff at the end of every response. Keep discussing the idea\nwhen that is what the user wants, and leave the project unchanged.\n","# explore - investigate an idea before deciding to build\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\nExplore is a read-only conversation grounded in the actual project. It can help\nwith questions such as whether caching would help a dashboard, whether teams\nbelong in the product, or which upload approach fits existing code.\n\nNo plans or active feature are required. Do not require `\u002Foverview`, invent a\nplan, or treat missing Blueprint context as a blocker to discussing the idea.\nThis command never writes activity state, including `blueprint\u002F.state\u002Frun.json`.\n\n## Start from the question\n\nUse the supplied topic or relevant conversation context. With neither, ask what\nthe user wants to investigate. For a vague idea, state a tentative interpretation\nand ask a focused question only when its answer changes the investigation.\n\nReuse context already loaded in the session. Read relevant project instructions,\ncode, tests as text, manifests, and existing plans when they help answer the\nquestion. Follow the actual implementation far enough to support your claims;\npoint to concrete files or symbols. Avoid scanning unrelated parts of the repo.\nRead-only Git inspection can establish what exists or is already in progress.\n\nAuthoritative documentation lookup is appropriate when technical uncertainty\nneeds it. Distinguish documented facts from what this project actually uses.\nMissing code or evidence is an uncertainty to explain, not permission to execute\nan experiment or to invent current behavior.\n\n## Discuss the options\n\nKeep the conversation proportional to the question. Compare plausible options\nagainst the user's needs and existing project constraints. Include doing nothing\nwhen the current behavior may already be sufficient. Do not invent scale,\nsecurity requirements, or new abstractions to justify a change.\n\nExplain the strongest case against your recommendation and how confident you\nare. Separate observed facts, assumptions, and unanswered questions. Say what\nevidence could change the recommendation without gathering it through execution.\nAn unresolved question or a recommendation to leave the project alone is a valid\noutcome.\n\nUse a small diagram in the response when it makes a relationship or tradeoff\nclearer. Do not create diagram files. There is no mandatory output template,\nreport, question count, or next-step checklist. Follow the user's responses and\nlet the discussion continue as long as useful.\n\n## Keep the boundaries clear\n\n- Never create, edit, or delete files, including specs, plans, notes, generated\n  output, and activity state. Do not save the conversation into the project.\n- Never install dependencies, execute product code, run tests or builds, start\n  servers, perform browser interactions, or call state-changing tools. Read\n  source and existing evidence instead of testing a hypothesis by execution.\n- Never create or switch branches, commit, merge, push, publish, or deploy.\n- Never turn a request to discuss an idea into approval to plan or implement it.\n  If the user asks for changes, explain the appropriate handoff and keep this\n  Explore invocation read-only. Do not invoke another command automatically.\n\n## Neighbors and handoff\n\n- `\u002Fbrief` explains an existing build-plan item, its scope, dependencies, and\n  size. Explore can discuss an unplanned idea or question a planned approach.\n- `\u002Fdiscovery` develops broader product direction and reviewed planning drafts.\n  Explore does not draft either planning file.\n- `\u002Fdebug` reproduces and isolates an actual failure. Explore discusses options\n  without executing code to diagnose or verify them.\n- `\u002Ffeature` writes a buildable spec; `\u002Ffix` specifies a confirmed small change.\n  Suggest the appropriate command only when the user is ready to proceed.\n\nDo not force a handoff at the end of every response. Keep discussing the idea\nwhen that is what the user wants, and leave the project unchanged.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","483eb73dbc58a4b82a5642f864ea7569af947e39",".claude\u002Fskills\u002Fexplore",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 explore",{"tool":38,"command":39},"bunx","bunx skills add aiblueprinthq\u002Fai-blueprint --skill explore",{"tool":41,"command":42},"pnpm","pnpm dlx skills add aiblueprinthq\u002Fai-blueprint --skill explore","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faiblueprinthq\u002Fai-blueprint\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fexplore\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",[],[]]