[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75JG5R86XRG8B6EYX3JB06H":3,"skill-same:01M75JG5R86XRG8B6EYX3JB06H":55},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75JG5R86XRG8B6EYX3JB06H","prototype",null,"Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.","colenet-gmbh\u002Fcolenet-claude-code-plugin","colenet-gmbh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F27774717?v=4","01M75JEMA67P2CEDJC0GZCWZDV","Colenet GmbH","01M75JEMASFM02PQP38B77BBN5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fprototype\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: prototype\ndescription: Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.\n---\n\n# Prototype\n\nA prototype is **throwaway code that answers a question**. The question decides the shape.\n\n## Pick a branch\n\nIdentify which question is being answered — from the user's prompt, the surrounding code, or by asking if the user is around:\n\n- **\"Does this logic \u002F state model feel right?\"** → LOGIC.md. Build a tiny interactive terminal app that pushes the state machine through cases that are hard to reason about on paper.\n- **\"What should this look like?\"** → UI.md. Generate several radically different UI variations on a single route, switchable via a URL search param and a floating bottom bar.\n\nThe two branches produce very different artifacts — getting this wrong wastes the whole prototype. If the question is genuinely ambiguous and the user isn't reachable, default to whichever branch better matches the surrounding code (a backend module → logic; a page or component → UI) and state the assumption at the top of the prototype.\n\n## Rules that apply to both\n\n1. **Throwaway from day one, and clearly marked as such.** Locate the prototype code close to where it will actually be used (next to the module or page it's prototyping for) so context is obvious — but name it so a casual reader can see it's a prototype, not production. For throwaway UI routes, obey whatever routing convention the project already uses; don't invent a new top-level structure.\n2. **One command to run.** Whatever the project's existing task runner supports — `pnpm \u003Cname>`, `python \u003Cpath>`, `bun \u003Cpath>`, etc. The user must be able to start it without thinking.\n3. **No persistence by default.** State lives in memory. Persistence is the thing the prototype is _checking_, not something it should depend on. If the question explicitly involves a database, hit a scratch DB or a local file with a clear \"PROTOTYPE — wipe me\" name.\n4. **Skip the polish.** No tests, no error handling beyond what makes the prototype _runnable_, no abstractions. The point is to learn something fast and then delete it.\n5. **Surface the state.** After every action (logic) or on every variant switch (UI), print or render the full relevant state so the user can see what changed.\n6. **Delete or absorb when done.** When the prototype has answered its question, either delete it or fold the validated decision into the real code — don't leave it rotting in the repo.\n\n## When done\n\nThe _answer_ is the only thing worth keeping from a prototype. Capture it somewhere durable (commit message, ADR, issue, or a `NOTES.md` next to the prototype) along with the question it was answering. If the user is around, that capture is a quick conversation; if not, leave the placeholder so they (or you, on the next pass) can fill in the verdict before deleting the prototype.\n","# Prototype\n\nA prototype is **throwaway code that answers a question**. The question decides the shape.\n\n## Pick a branch\n\nIdentify which question is being answered — from the user's prompt, the surrounding code, or by asking if the user is around:\n\n- **\"Does this logic \u002F state model feel right?\"** → LOGIC.md. Build a tiny interactive terminal app that pushes the state machine through cases that are hard to reason about on paper.\n- **\"What should this look like?\"** → UI.md. Generate several radically different UI variations on a single route, switchable via a URL search param and a floating bottom bar.\n\nThe two branches produce very different artifacts — getting this wrong wastes the whole prototype. If the question is genuinely ambiguous and the user isn't reachable, default to whichever branch better matches the surrounding code (a backend module → logic; a page or component → UI) and state the assumption at the top of the prototype.\n\n## Rules that apply to both\n\n1. **Throwaway from day one, and clearly marked as such.** Locate the prototype code close to where it will actually be used (next to the module or page it's prototyping for) so context is obvious — but name it so a casual reader can see it's a prototype, not production. For throwaway UI routes, obey whatever routing convention the project already uses; don't invent a new top-level structure.\n2. **One command to run.** Whatever the project's existing task runner supports — `pnpm \u003Cname>`, `python \u003Cpath>`, `bun \u003Cpath>`, etc. The user must be able to start it without thinking.\n3. **No persistence by default.** State lives in memory. Persistence is the thing the prototype is _checking_, not something it should depend on. If the question explicitly involves a database, hit a scratch DB or a local file with a clear \"PROTOTYPE — wipe me\" name.\n4. **Skip the polish.** No tests, no error handling beyond what makes the prototype _runnable_, no abstractions. The point is to learn something fast and then delete it.\n5. **Surface the state.** After every action (logic) or on every variant switch (UI), print or render the full relevant state so the user can see what changed.\n6. **Delete or absorb when done.** When the prototype has answered its question, either delete it or fold the validated decision into the real code — don't leave it rotting in the repo.\n\n## When done\n\nThe _answer_ is the only thing worth keeping from a prototype. Capture it somewhere durable (commit message, ADR, issue, or a `NOTES.md` next to the prototype) along with the question it was answering. If the user is around, that capture is a quick conversation; if not, leave the placeholder so they (or you, on the next pass) can fill in the verdict before deleting the prototype.\n",{"name":5,"description":7},"main","47dbd725f1dd37f2c0deed3f223249b2cdcbb5a8","skills_source\u002Futility\u002Fprototype","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh","https:\u002F\u002Fwww.colenet.de","2026-10-05 07:40:40",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add colenet-gmbh\u002Fcolenet-claude-code-plugin --skill prototype",{"tool":37,"command":38},"bunx","bunx skills add colenet-gmbh\u002Fcolenet-claude-code-plugin --skill prototype",{"tool":40,"command":41},"pnpm","pnpm dlx skills add colenet-gmbh\u002Fcolenet-claude-code-plugin --skill prototype","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fprototype\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"LOGIC.md","REFERENCE","参考文档",5585,"https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fprototype\u002FLOGIC.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"UI.md",6777,"https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fprototype\u002FUI.md",[56,63,70,77,84,91],{"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},"01M75JGH2BKSPNHEFPK7GGWWX9","triage","Backlog management — move not-yet-worked-up items through triage roles into agent-ready briefs, whatever their origin. Use when the user wants to sort or work up a backlog of bug reports, feature requests, or ideas, mentions \"triage\", \"triagieren\", \"Backlog sichten\", \"Backlog pflegen\", \"sort the backlog\", \"manage the backlog\", or points at an untriaged item in docs\u002Fwork\u002F01-backlog.","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Ftriage\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},"01M75JGDZC06KVV60HW33NKMZV","teach","Teach the user a new skill or concept over multiple sessions, turning the current directory into a stateful teaching workspace grounded in a mission, trusted resources, and beautiful lessons. Use when the user wants to learn or be taught something, or says \"teach me\", \"bring mir bei\", \"lehre mich\", \"ich will X lernen\", \"mach mich fit in\", \"onboard me on\", \"help me learn\".","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fteach\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},"01M75JG9EF7354J71JQRZVQ82X","research","Delegate reading legwork to a background agent — investigate a question against high-trust primary sources (official docs, source code, specs, first-party APIs) and leave the findings as a cited Markdown note in the repo. Use when engineering work needs docs, API, or codebase facts gathered before building, or the user says \"recherchiere das\", \"schau in den Docs nach\", \"lies dich in X ein\", \"research this\", \"gather the facts on\", \"read up on\". For a broad, multi-source web report with adversarial fact-checking, reach for deep-research instead; cape:research is the lighter, repo-bound feeder that leaves a note behind.","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fresearch\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},"01M75JG46T7P54KKF80X22HF4Z","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fhandoff\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},"01M75JG2EM4XSXC32SRRN37VRA","grilling","Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fgrilling\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},"01M75JG06P5EKY5WSJRZAENPQE","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002Fcolenet-gmbh\u002Fcolenet-claude-code-plugin\u002Fblob\u002Fmain\u002Fskills_source\u002Futility\u002Fgrill-me\u002FSKILL.md",[],[]]