[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSDBBTCTNAAEJKHH9WAV6M":3,"skill-same:01M7CSDBBTCTNAAEJKHH9WAV6M":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},"01M7CSDBBTCTNAAEJKHH9WAV6M","backend-manual-testing",null,"Use when the task touches a backend API, database or worker - booting it from the task branch, driving real requests and verifying side effects (DB rows, outbound calls, logs) as evidence","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\u002Fbackend-manual-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: backend-manual-testing\ncategory: qa\ndescription: Use when the task touches a backend API, database or worker - booting it from the task branch, driving real requests and verifying side effects (DB rows, outbound calls, logs) as evidence\n---\n# Backend Manual Testing\n\n## Overview\n\nManual verification of a backend task means booting the real service (and its worker, if the repo has one) from the task branch and executing your scenario plan against it. The scenario plan comes first and comes from the task description and acceptance criteria alone (scenario-plan-first) — you never derive cases from the diff or the source.\n\n**Preconditions:** case matrix recorded with `record_test_cases` (scenario-plan-first); environment chosen per test-environment-selection (local by default — side effects are only observable there — else the repository's stage deploy target; never prod).\n\n## Booting in the workspace\n\n1. **Learn how the project runs** — in this order: `search_memory` (scope=project) for a boot recipe from an earlier round, `get_project_brief` for the components\u002Fcommands\u002Fports, the repository's `build_command`\u002F`test_command`\u002F`verify_command` settings, README \u002F Makefile \u002F docker-compose \u002F example env files, and any comment the developer left (a clean run leaves none). `list_links` shows what this component talks to — the side effects you'll need to verify and the dependencies to stub. Do not guess ports, flags, or env vars when the project declares them.\n2. **Provision dependencies.** Database and other infrastructure run as disposable containers when a container runtime (podman\u002Fdocker) is available; run the project's real migrations and a minimal seed. External third-party services are stubbed so failure scenarios are drivable (test-data-and-stubs).\n3. **Start the processes**: the API server, and every worker\u002Fconsumer process the repo defines (see worker-job-testing). Keep their logs streaming to a per-task scratch file: `QA=${TMPDIR:-\u002Ftmp}\u002Ftt-\u003Ctask-key>\u002Fqa; mkdir -p \"$QA\"; ... > \"$QA\u002Fapi.log\" 2>&1 &`.\n4. **Smoke check** before scenarios: health endpoint answers, migrations applied, worker connected. A failed boot is itself a finding — capture the exact error output.\n\n## Executing scenarios\n\nFor each scenario in the plan, in order:\n\n- **Drive the real surface**: `curl`\u002Fhttpie against the running API (api-contract-testing). Record the exact request and the exact response — status, body, headers that matter.\n- **Verify side effects, not just responses**: the DB row that should exist (`psql -c \"select ...\"`), the outbound call that should have been made (the stub's received-requests log), the file\u002Fevent that should have been produced. A 200 with the wrong side effect is a FAIL.\n- **Watch the logs during every scenario.** Stack traces, ERROR\u002FWARN lines, or panics count as findings even when the HTTP response looks correct.\n- Cover the implied cases too: invalid input, missing\u002Fwrong auth, empty state, duplicate submission (boundary-negative-testing).\n\n## Evidence and wrap-up\n\n- Every scenario gets PASS\u002FFAIL with the executed command and observed output (qa-verify-before-verdict).\n- After targeted scenarios, run the regression sweep (regression-checklist).\n- Stop the processes you started; the workspace must not keep orphan servers running.\n- Automation is out of scope this iteration (manual-only-testing): the same scenarios are not added to a suite. A red existing pipeline (`get_pipeline_status`) is a finding; green is not a substitute for this round.\n- Once booting took real effort, save the recipe to project memory (`save_memory`, scope=project) so the next round on this repo starts faster.\n\n## Red Flags\n\n- You are about to form a verdict without having booted anything → that is code review, not QA.\n- The response is right but you never checked the DB\u002Flog\u002Fstub side → half-tested.\n- Boot instructions missing and you improvised a config → post what is missing instead; untestable is not done (test-environment-selection).\n","# Backend Manual Testing\n\n## Overview\n\nManual verification of a backend task means booting the real service (and its worker, if the repo has one) from the task branch and executing your scenario plan against it. The scenario plan comes first and comes from the task description and acceptance criteria alone (scenario-plan-first) — you never derive cases from the diff or the source.\n\n**Preconditions:** case matrix recorded with `record_test_cases` (scenario-plan-first); environment chosen per test-environment-selection (local by default — side effects are only observable there — else the repository's stage deploy target; never prod).\n\n## Booting in the workspace\n\n1. **Learn how the project runs** — in this order: `search_memory` (scope=project) for a boot recipe from an earlier round, `get_project_brief` for the components\u002Fcommands\u002Fports, the repository's `build_command`\u002F`test_command`\u002F`verify_command` settings, README \u002F Makefile \u002F docker-compose \u002F example env files, and any comment the developer left (a clean run leaves none). `list_links` shows what this component talks to — the side effects you'll need to verify and the dependencies to stub. Do not guess ports, flags, or env vars when the project declares them.\n2. **Provision dependencies.** Database and other infrastructure run as disposable containers when a container runtime (podman\u002Fdocker) is available; run the project's real migrations and a minimal seed. External third-party services are stubbed so failure scenarios are drivable (test-data-and-stubs).\n3. **Start the processes**: the API server, and every worker\u002Fconsumer process the repo defines (see worker-job-testing). Keep their logs streaming to a per-task scratch file: `QA=${TMPDIR:-\u002Ftmp}\u002Ftt-\u003Ctask-key>\u002Fqa; mkdir -p \"$QA\"; ... > \"$QA\u002Fapi.log\" 2>&1 &`.\n4. **Smoke check** before scenarios: health endpoint answers, migrations applied, worker connected. A failed boot is itself a finding — capture the exact error output.\n\n## Executing scenarios\n\nFor each scenario in the plan, in order:\n\n- **Drive the real surface**: `curl`\u002Fhttpie against the running API (api-contract-testing). Record the exact request and the exact response — status, body, headers that matter.\n- **Verify side effects, not just responses**: the DB row that should exist (`psql -c \"select ...\"`), the outbound call that should have been made (the stub's received-requests log), the file\u002Fevent that should have been produced. A 200 with the wrong side effect is a FAIL.\n- **Watch the logs during every scenario.** Stack traces, ERROR\u002FWARN lines, or panics count as findings even when the HTTP response looks correct.\n- Cover the implied cases too: invalid input, missing\u002Fwrong auth, empty state, duplicate submission (boundary-negative-testing).\n\n## Evidence and wrap-up\n\n- Every scenario gets PASS\u002FFAIL with the executed command and observed output (qa-verify-before-verdict).\n- After targeted scenarios, run the regression sweep (regression-checklist).\n- Stop the processes you started; the workspace must not keep orphan servers running.\n- Automation is out of scope this iteration (manual-only-testing): the same scenarios are not added to a suite. A red existing pipeline (`get_pipeline_status`) is a finding; green is not a substitute for this round.\n- Once booting took real effort, save the recipe to project memory (`save_memory`, scope=project) so the next round on this repo starts faster.\n\n## Red Flags\n\n- You are about to form a verdict without having booted anything → that is code review, not QA.\n- The response is right but you never checked the DB\u002Flog\u002Fstub side → half-tested.\n- Boot instructions missing and you improvised a config → post what is missing instead; untestable is not done (test-environment-selection).\n",{"name":5,"category":24,"description":7},"qa","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fbackend-manual-testing",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 backend-manual-testing",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill backend-manual-testing",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill backend-manual-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fbackend-manual-testing\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",[],[]]