[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSF2P4KYGZB6NRWJSRRHJN":3,"skill-same:01M7CSF2P4KYGZB6NRWJSRRHJN":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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CSF2P4KYGZB6NRWJSRRHJN","scenario-plan-first",null,"Use at the start of every QA round - recording the case matrix with record_test_cases (categories, criterion links, rejected cases) before touching the app, then executing all of it","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fscenario-plan-first\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: scenario-plan-first\ncategory: qa\ndescription: Use at the start of every QA round - recording the case matrix with record_test_cases (categories, criterion links, rejected cases) before touching the app, then executing all of it\n---\n# Case Matrix First\n\nBefore you boot anything or call anything, derive the cases — from the task description and its acceptance criteria, never from the code or the diff (techniques and sources: test-scenario-design) — and write them onto the task with `record_test_cases` (`status=planned`). Never post the plan as a comment; the card is where it lives.\n\nThe criteria are the floor, not the ceiling. They summarise the request in a few lines, so start from them and then ask what the person asking would expect to be true once this is built:\n\n- One or more cases per acceptance criterion (happy path), linked with `criterion_id`.\n- The implied cases nobody wrote down, with `criterion_id` empty (boundary-negative-testing for the data catalogue).\n- Backend: the worker\u002Fasync cases the request implies (worker-job-testing).\n- Frontend: the visual cases at all four widths, empty\u002Floading\u002Ferror states (frontend-manual-testing).\n- UI built from an approved design (your context carries \"## The approved design this task builds\"): the `design:` cases per state and width (design-conformance).\n- A regression case for the adjacent behaviour this change could break (regression-checklist).\n- The cases you considered and REJECTED, as `status=invalid` with the reason in `notes`.\n\nThen execute the matrix in this same run and record every verdict (`set_test_case_result`): `passed`, `failed` with what you actually observed, or `skipped` with what blocked it. A case still `planned` when you try to hand the task on refuses the move.\n\n## Category mapping\n\nThe category enum has no accessibility\u002Fperformance\u002Fsecurity\u002Fcontract value of its own — map them: a11y → `visual` + title prefix `a11y:`; performance → `other` + `perf:`; authz\u002Fsecurity → `auth`; contract\u002Fcompatibility → `negative` or `happy_path` depending on the case; concurrency\u002Fduplicate submission → `negative`; worker\u002Fasync → `async`.\n\n## Title convention\n\n`\u003Csurface>: \u003Caction> -> \u003Cexpected>`, e.g. `settings: rename to 81 chars -> 422`. Titles are the case's identity across rounds — keep them stable so a re-test (retest-after-revision) matches the right history.\n\n## An untestable criterion\n\nIs not a case you invent a proxy for. When there is a concrete choice between two readings, `ask_user` with the readings as options and leave it unapproved meanwhile. When it is unclear with no concrete reading to offer, reject it via `review_criterion` (\"untestable as written: \u003Cwhy> — needs a sharper criterion\") so the move to need_revision puts it in front of the human — a comment asking the PM to sharpen it reaches nobody, since the PM does not subscribe to in_qa.\n","# Case Matrix First\n\nBefore you boot anything or call anything, derive the cases — from the task description and its acceptance criteria, never from the code or the diff (techniques and sources: test-scenario-design) — and write them onto the task with `record_test_cases` (`status=planned`). Never post the plan as a comment; the card is where it lives.\n\nThe criteria are the floor, not the ceiling. They summarise the request in a few lines, so start from them and then ask what the person asking would expect to be true once this is built:\n\n- One or more cases per acceptance criterion (happy path), linked with `criterion_id`.\n- The implied cases nobody wrote down, with `criterion_id` empty (boundary-negative-testing for the data catalogue).\n- Backend: the worker\u002Fasync cases the request implies (worker-job-testing).\n- Frontend: the visual cases at all four widths, empty\u002Floading\u002Ferror states (frontend-manual-testing).\n- UI built from an approved design (your context carries \"## The approved design this task builds\"): the `design:` cases per state and width (design-conformance).\n- A regression case for the adjacent behaviour this change could break (regression-checklist).\n- The cases you considered and REJECTED, as `status=invalid` with the reason in `notes`.\n\nThen execute the matrix in this same run and record every verdict (`set_test_case_result`): `passed`, `failed` with what you actually observed, or `skipped` with what blocked it. A case still `planned` when you try to hand the task on refuses the move.\n\n## Category mapping\n\nThe category enum has no accessibility\u002Fperformance\u002Fsecurity\u002Fcontract value of its own — map them: a11y → `visual` + title prefix `a11y:`; performance → `other` + `perf:`; authz\u002Fsecurity → `auth`; contract\u002Fcompatibility → `negative` or `happy_path` depending on the case; concurrency\u002Fduplicate submission → `negative`; worker\u002Fasync → `async`.\n\n## Title convention\n\n`\u003Csurface>: \u003Caction> -> \u003Cexpected>`, e.g. `settings: rename to 81 chars -> 422`. Titles are the case's identity across rounds — keep them stable so a re-test (retest-after-revision) matches the right history.\n\n## An untestable criterion\n\nIs not a case you invent a proxy for. When there is a concrete choice between two readings, `ask_user` with the readings as options and leave it unapproved meanwhile. When it is unclear with no concrete reading to offer, reject it via `review_criterion` (\"untestable as written: \u003Cwhy> — needs a sharper criterion\") so the move to need_revision puts it in front of the human — a comment asking the PM to sharpen it reaches nobody, since the PM does not subscribe to in_qa.\n",{"name":5,"category":24,"description":7},"qa","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fscenario-plan-first",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill scenario-plan-first",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill scenario-plan-first",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill scenario-plan-first","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fscenario-plan-first\u002FSKILL.md",true,[],[49,55,62,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]