[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77TJB0XV686F3H3M53BFBTY":3,"skill-same:01M77TJB0XV686F3H3M53BFBTY":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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M77TJB0XV686F3H3M53BFBTY","discovery-question-form",null,"Structured clarification form for unresolved material requirements.","hiktan44\u002Fopen-design-app","hiktan44","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140920746?v=4","01M77SNV7J2RH7G3TQVS2FXMW9","hikmet tanriverdi","01M77SNV87GR8D3BJ9WJHFMZ9Y",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fatoms\u002Fdiscovery-question-form\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: discovery-question-form\ndescription: Structured clarification form for unresolved material requirements.\nod:\n  scenario: general\n  mode: discovery\n---\n\n# Discovery question form\n\nThis atom defines the `\u003Cquestion-form>` protocol. It does not decide whether\nclarification is required. Follow the active skill and core prompt's\nrequirements-clarification policy. When they identify unresolved information\nthat would materially change the design direction, content structure, or\ndelivery format, surface the smallest possible set of questions that unblocks\nthe workflow.\n\nThe questions are rendered as a `\u003Cquestion-form>` artifact inline in the\noriginating assistant message. This is assistant text parsed by the host, not a\nplugin GenUI surface or a native tool call. Submitted answers return as the\nnext user message, beginning with `[form answers — \u003Cform-id>]`.\n\n## Activation boundary\n\n- A first turn or new project does not by itself require a form.\n- A `discovery` pipeline stage only makes this protocol available; declaring\n  or entering the stage does not trigger a form.\n- Missing metadata is not automatically a question. First use the request,\n  conversation, plugin inputs, memory, active skill, and design system.\n- If enough information is available to proceed safely, do not emit a form.\n- If a material blocker remains, ask only for that unresolved information.\n\n## Emission shape\n\nEmit the form as a `question-form` block whose body is a JSON object with a\ntop-level `questions` array. Do not emit a bare question object by itself; the\nrenderer only recognizes the wrapped form contract.\n\n```html\n\u003Cquestion-form id=\"discovery\" title=\"Quick brief — 30 seconds\">\n{\n  \"description\": \"I'll lock these in before building. Skip what doesn't apply — I'll fill defaults.\",\n  \"questions\": [\n    {\n      \"id\": \"audience\",\n      \"label\": \"Who's the primary audience?\",\n      \"type\": \"checkbox\",\n      \"options\": [\"VC\", \"Customer\", \"Internal team\"],\n      \"maxSelections\": 2,\n      \"required\": true\n    }\n  ]\n}\n\u003C\u002Fquestion-form>\n```\n\n## Question object shape\n\nEach entry in the top-level `questions` array uses:\n\n- `id`: stable answer key, for example `audience`.\n- `label`: user-facing question copy.\n- `type`: one of `radio`, `checkbox`, `select`, `text`, `textarea`,\n  `number`, `range`, `date`, `time`, `datetime-local`, `color`, `url`,\n  `email`, `tel`, `file`, or `switch`.\n- `options`: required for choice controls; strings are\n  allowed, or objects with localized `label` and stable `value`.\n- At most 6-7 options per question; merge near-duplicates instead of listing more.\n- Choose `radio` vs `select` by option count, not importance: `radio` for a short list, `select` once it runs long (languages, timezones, voices). `checkbox` is always a plain list.\n- `select` options may carry `group` (first group expands, the rest collapse) and `trailingLabel` (a short end-of-row code such as `ZH-CN`). Both optional.\n- Label options in the user's words, not jargon: \"Magazine-style layout\", not \"Editorial\". Reword only `label`; never change a stable `value`.\n- Keep each `label` under ~40 characters; put anything longer in `description`.\n- `allowCustom`: leave unset or set to `true` for finite-choice controls so\n  users can type their own answer instead of accepting only generated options.\n  Set `allowCustom: false` only when the downstream system needs an exact\n  machine id.\n- `customLabel` \u002F `customPlaceholder`: optional localized copy for that custom\n  answer input.\n- `maxSelections`: include this for checkbox controls with a limited selection\n  count.\n- `required`: set to `true` only when the answer is needed before work can\n  continue.\n\n## Convergence\n\nThe discovery atom completes when the next user message contains an answer\nfor every required question. Treat those submitted answers as conversation\ncontext and do not ask the same questions again unless later input invalidates\nan answer.\n","# Discovery question form\n\nThis atom defines the `\u003Cquestion-form>` protocol. It does not decide whether\nclarification is required. Follow the active skill and core prompt's\nrequirements-clarification policy. When they identify unresolved information\nthat would materially change the design direction, content structure, or\ndelivery format, surface the smallest possible set of questions that unblocks\nthe workflow.\n\nThe questions are rendered as a `\u003Cquestion-form>` artifact inline in the\noriginating assistant message. This is assistant text parsed by the host, not a\nplugin GenUI surface or a native tool call. Submitted answers return as the\nnext user message, beginning with `[form answers — \u003Cform-id>]`.\n\n## Activation boundary\n\n- A first turn or new project does not by itself require a form.\n- A `discovery` pipeline stage only makes this protocol available; declaring\n  or entering the stage does not trigger a form.\n- Missing metadata is not automatically a question. First use the request,\n  conversation, plugin inputs, memory, active skill, and design system.\n- If enough information is available to proceed safely, do not emit a form.\n- If a material blocker remains, ask only for that unresolved information.\n\n## Emission shape\n\nEmit the form as a `question-form` block whose body is a JSON object with a\ntop-level `questions` array. Do not emit a bare question object by itself; the\nrenderer only recognizes the wrapped form contract.\n\n```html\n\u003Cquestion-form id=\"discovery\" title=\"Quick brief — 30 seconds\">\n{\n  \"description\": \"I'll lock these in before building. Skip what doesn't apply — I'll fill defaults.\",\n  \"questions\": [\n    {\n      \"id\": \"audience\",\n      \"label\": \"Who's the primary audience?\",\n      \"type\": \"checkbox\",\n      \"options\": [\"VC\", \"Customer\", \"Internal team\"],\n      \"maxSelections\": 2,\n      \"required\": true\n    }\n  ]\n}\n\u003C\u002Fquestion-form>\n```\n\n## Question object shape\n\nEach entry in the top-level `questions` array uses:\n\n- `id`: stable answer key, for example `audience`.\n- `label`: user-facing question copy.\n- `type`: one of `radio`, `checkbox`, `select`, `text`, `textarea`,\n  `number`, `range`, `date`, `time`, `datetime-local`, `color`, `url`,\n  `email`, `tel`, `file`, or `switch`.\n- `options`: required for choice controls; strings are\n  allowed, or objects with localized `label` and stable `value`.\n- At most 6-7 options per question; merge near-duplicates instead of listing more.\n- Choose `radio` vs `select` by option count, not importance: `radio` for a short list, `select` once it runs long (languages, timezones, voices). `checkbox` is always a plain list.\n- `select` options may carry `group` (first group expands, the rest collapse) and `trailingLabel` (a short end-of-row code such as `ZH-CN`). Both optional.\n- Label options in the user's words, not jargon: \"Magazine-style layout\", not \"Editorial\". Reword only `label`; never change a stable `value`.\n- Keep each `label` under ~40 characters; put anything longer in `description`.\n- `allowCustom`: leave unset or set to `true` for finite-choice controls so\n  users can type their own answer instead of accepting only generated options.\n  Set `allowCustom: false` only when the downstream system needs an exact\n  machine id.\n- `customLabel` \u002F `customPlaceholder`: optional localized copy for that custom\n  answer input.\n- `maxSelections`: include this for checkbox controls with a limited selection\n  count.\n- `required`: set to `true` only when the answer is needed before work can\n  continue.\n\n## Convergence\n\nThe discovery atom completes when the next user message contains an answer\nfor every required question. Treat those submitted answers as conversation\ncontext and do not ask the same questions again unless later input invalidates\nan answer.\n",{"od":24,"name":5,"description":7},{"mode":25,"scenario":26},"discovery","general","main","f403d5b733fab92eab16d13e9baf3ac951afed55","plugins\u002F_official\u002Fatoms\u002Fdiscovery-question-form","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app","https:\u002F\u002Fgithub.com\u002Fhiktan44","fasheone.com","Hikmet Tanrıverdi\r\nSTRATEJI DANIŞMANLIK, 2008-2018 İHKİB İSTANBUL HAZIR GİYİM BŞK, İTO MECLİS ÜYESİ, TEXMART DIŞ TİCARET YK STRATEGY CONSULTING, 2008-2018 PRESI","2026-10-11 23:59:08",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add hiktan44\u002Fopen-design-app --skill discovery-question-form",{"tool":41,"command":42},"bunx","bunx skills add hiktan44\u002Fopen-design-app --skill discovery-question-form",{"tool":44,"command":45},"pnpm","pnpm dlx skills add hiktan44\u002Fopen-design-app --skill discovery-question-form","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fatoms\u002Fdiscovery-question-form\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"open-design.json","REFERENCE","参考文档",828,"https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fatoms\u002Fdiscovery-question-form\u002Fopen-design.json",[56,63,70,77,84,93],{"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},"01M77WGV99HNV3Q6JN3H8Z70JE","Beta Skill","Instruction-only fixture skill.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Fbeta\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},"01M77WGRXNRGHT9J1K929BPV5H","Alpha Skill","First fixture skill with a runnable demo.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Falpha\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},"01M77WGQK7F7R1W6RBFZFEZ53M","Deck One","A small deck template fixture.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fdesign-templates\u002Fdeck-one\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},"01M77WGNPEGTDWMKDX659FS5DT","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\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":88,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M77WGJ9KKT6Q4P10GAV3KC48","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","MIT","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M77WGF9P0WT4XBXMM0B9WRGR","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwpds\u002FSKILL.md",[],[]]