[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSE0CD7V1A8N6F48PAJ3MJ":3,"skill-same:01M7CSE0CD7V1A8N6F48PAJ3MJ":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},"01M7CSE0CD7V1A8N6F48PAJ3MJ","e2e-automation-project",null,"Maintain a dedicated automation test project per repository - separate from the product's unit tests - with API, worker, and UI suites written scenario-first","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\u002Fe2e-automation-project\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: e2e-automation-project\ncategory: testing\ndescription: Maintain a dedicated automation test project per repository - separate from the product's unit tests - with API, worker, and UI suites written scenario-first\nenabled: false\n---\n# E2E Automation Project\n\n## Overview\n\nEvery repository worth testing gets a **dedicated automation test project**: a separate project that exercises the real product through its public surface and can be re-run on every change. It is not the product's unit-test folder and never mixes into it — it has its own dependencies, its own entrypoint, and runs in the repository's own pipeline (automation-pipeline-integration).\n\n**Core principle:** scenarios before code (scenario-plan-first). A suite written without a scenario list tests whatever was easy, not what matters. And automation follows the manual pass: you automate the scenarios you have already executed and understood by hand.\n\n## Structure\n\nOne automation project per repository, following the project's convention — default `qa-automation\u002F` at the repo root (a sibling repo also works):\n\n```\nqa-automation\u002F\n  scenarios\u002F        # the human-readable scenario lists, one file per feature\n  api\u002F              # backend API suite: HTTP client + assertions\n  worker\u002F           # async job suite: trigger → poll → assert side effects\n  ui\u002F               # frontend suite: Playwright against the built app\n  fixtures\u002F         # seed data\n  support\u002F          # helpers, page objects, request builders, stub mappings\n  scripts\u002Fe2e.sh    # single entrypoint: provision, run all suites, teardown\n```\n\n| Surface | Tool (follow the project's existing choice) |\n|---------|---------------------------------------------|\n| REST API | the language's HTTP test client + assertions (Playwright APIRequest, RestAssured, supertest, Go net\u002Fhttp + testify) |\n| Worker \u002F async jobs | same test runner; triggers through the product path, polls for side effects (worker-job-testing) |\n| Web UI | Playwright (preferred) \u002F Cypress — headless Chromium via `executablePath: process.env.CHROME_BIN`, no browser download |\n\nMobile automation is out of scope for now — do not scaffold a mobile suite.\n\n## Determinism\n\n- The app under test boots from the current branch build; the suite never targets stage, prod, or any shared environment.\n- Database and infra are disposable containers seeded per run (test-database-seeding, Testcontainers or the project's equivalent).\n- External services are stubbed and asserted on (test-doubles-wiremock).\n- Each test seeds and cleans its own data; no ordering dependencies; re-running gives the same result.\n\n## The Workflow\n\n1. **Author scenarios first** for the feature: happy path, boundary, negative, auth\u002Fpermission, key regressions — committed under `scenarios\u002F` and posted on the task.\n2. **Stand up the environment** through the entrypoint script, never by hand-managed local state.\n3. **Implement one test per scenario**, named for the behavior (`export_forbidden_for_other_tenant`), reading like the scenario via page objects \u002F request helpers.\n4. **Run the whole suite**, read the output, capture failure artifacts (screenshots, traces, logs) as evidence.\n5. **Wire it into the pipeline** if not already (automation-pipeline-integration) — a suite outside the pipeline enforces nothing.\n\n## Worked Example\n\nFeature: task export to CSV.\n\n- Scenarios: (1) export returns the project's tasks; (2) empty project → header-only CSV; (3) other tenant → 403; (4) export completion event is produced by the worker.\n- Environment: app against a Testcontainers Postgres seeded with a known project; auth provider stubbed with WireMock.\n- Tests: `api\u002Fexport_returns_all_tasks`, `api\u002Fexport_empty_project_header_only`, `api\u002Fexport_forbidden_for_other_tenant`, `worker\u002Fexport_event_emitted`. Each seeds its own rows, asserts, cleans up.\n- `scripts\u002Fe2e.sh` → all green; pipeline runs the same script on the next task.\n\n## Common Mistakes\n\n- Mixing automation into the product's unit-test folders — separate project, separate dependencies.\n- A second automation project forked for the same product — extend the existing one.\n- Suites that hit staging\u002Fshared data → flaky, order-dependent, forbidden.\n- A scenario in the plan with no implementing test, or tests with no scenario.\n\n## Red Flags\n\n- The suite passes locally but fails in a clean environment → hidden shared state.\n- Re-running gives different results → nondeterminism to fix before anything else.\n- UI tests download a browser at run time → use the system Chromium via `CHROME_BIN`.\n","# E2E Automation Project\n\n## Overview\n\nEvery repository worth testing gets a **dedicated automation test project**: a separate project that exercises the real product through its public surface and can be re-run on every change. It is not the product's unit-test folder and never mixes into it — it has its own dependencies, its own entrypoint, and runs in the repository's own pipeline (automation-pipeline-integration).\n\n**Core principle:** scenarios before code (scenario-plan-first). A suite written without a scenario list tests whatever was easy, not what matters. And automation follows the manual pass: you automate the scenarios you have already executed and understood by hand.\n\n## Structure\n\nOne automation project per repository, following the project's convention — default `qa-automation\u002F` at the repo root (a sibling repo also works):\n\n```\nqa-automation\u002F\n  scenarios\u002F        # the human-readable scenario lists, one file per feature\n  api\u002F              # backend API suite: HTTP client + assertions\n  worker\u002F           # async job suite: trigger → poll → assert side effects\n  ui\u002F               # frontend suite: Playwright against the built app\n  fixtures\u002F         # seed data\n  support\u002F          # helpers, page objects, request builders, stub mappings\n  scripts\u002Fe2e.sh    # single entrypoint: provision, run all suites, teardown\n```\n\n| Surface | Tool (follow the project's existing choice) |\n|---------|---------------------------------------------|\n| REST API | the language's HTTP test client + assertions (Playwright APIRequest, RestAssured, supertest, Go net\u002Fhttp + testify) |\n| Worker \u002F async jobs | same test runner; triggers through the product path, polls for side effects (worker-job-testing) |\n| Web UI | Playwright (preferred) \u002F Cypress — headless Chromium via `executablePath: process.env.CHROME_BIN`, no browser download |\n\nMobile automation is out of scope for now — do not scaffold a mobile suite.\n\n## Determinism\n\n- The app under test boots from the current branch build; the suite never targets stage, prod, or any shared environment.\n- Database and infra are disposable containers seeded per run (test-database-seeding, Testcontainers or the project's equivalent).\n- External services are stubbed and asserted on (test-doubles-wiremock).\n- Each test seeds and cleans its own data; no ordering dependencies; re-running gives the same result.\n\n## The Workflow\n\n1. **Author scenarios first** for the feature: happy path, boundary, negative, auth\u002Fpermission, key regressions — committed under `scenarios\u002F` and posted on the task.\n2. **Stand up the environment** through the entrypoint script, never by hand-managed local state.\n3. **Implement one test per scenario**, named for the behavior (`export_forbidden_for_other_tenant`), reading like the scenario via page objects \u002F request helpers.\n4. **Run the whole suite**, read the output, capture failure artifacts (screenshots, traces, logs) as evidence.\n5. **Wire it into the pipeline** if not already (automation-pipeline-integration) — a suite outside the pipeline enforces nothing.\n\n## Worked Example\n\nFeature: task export to CSV.\n\n- Scenarios: (1) export returns the project's tasks; (2) empty project → header-only CSV; (3) other tenant → 403; (4) export completion event is produced by the worker.\n- Environment: app against a Testcontainers Postgres seeded with a known project; auth provider stubbed with WireMock.\n- Tests: `api\u002Fexport_returns_all_tasks`, `api\u002Fexport_empty_project_header_only`, `api\u002Fexport_forbidden_for_other_tenant`, `worker\u002Fexport_event_emitted`. Each seeds its own rows, asserts, cleans up.\n- `scripts\u002Fe2e.sh` → all green; pipeline runs the same script on the next task.\n\n## Common Mistakes\n\n- Mixing automation into the product's unit-test folders — separate project, separate dependencies.\n- A second automation project forked for the same product — extend the existing one.\n- Suites that hit staging\u002Fshared data → flaky, order-dependent, forbidden.\n- A scenario in the plan with no implementing test, or tests with no scenario.\n\n## Red Flags\n\n- The suite passes locally but fails in a clean environment → hidden shared state.\n- Re-running gives different results → nondeterminism to fix before anything else.\n- UI tests download a browser at run time → use the system Chromium via `CHROME_BIN`.\n",{"name":5,"enabled":20,"category":24,"description":7},"testing","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fe2e-automation-project",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 e2e-automation-project",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill e2e-automation-project",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill e2e-automation-project","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Fe2e-automation-project\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",[],[]]