[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CTJACB782WA71PWWAYPBVX":3,"skill-same:01M7CTJACB782WA71PWWAYPBVX":67},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CTJACB782WA71PWWAYPBVX","e2e",null,"End-to-end testing methodology using Playwright — test structure, Page Object Model, flaky test management, artifact capture, and CI integration. Use when writing, reviewing, or debugging E2E tests, or when working with Playwright test suites.","xiaden\u002FSkyScow","xiaden","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3605480?v=4","01M7CTGKNTD1XNQE710J977HVD","Lucian Hardy","01M7CTGKPVQ3XRNXNRJ3A6E31F",1,"MIT","https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: e2e\ndescription: End-to-end testing methodology using Playwright — test structure, Page Object Model, flaky test management, artifact capture, and CI integration. Use when writing, reviewing, or debugging E2E tests, or when working with Playwright test suites.\n---\n\n# E2E Testing\n\n**Purpose:** End-to-end testing methodology for Playwright. Covers the full lifecycle: planning, authoring, debugging flaky tests, and CI integration.\n\n---\n\n## When to Use\n\n**Trigger conditions:**\n\n- Writing or reviewing E2E tests\n- Debugging flaky or failing Playwright tests\n- Setting up Playwright or CI pipelines for E2E\n\n**Do NOT use when:**\n\n- Writing unit or integration tests\n- Working with non-Playwright tools (Cypress, Selenium)\n- Testing business logic without UI\n\n---\n\n## Navigation\n\nUse this table to find the right reference for your task:\n\n| Task | Reference |\n|------|-----------|\n| Writing a test, choosing selectors, setting up isolation | [`references\u002Fcore-patterns.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fcore-patterns.md) |\n| Designing page objects, fixtures, composition | [`references\u002Fpom-patterns.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fpom-patterns.md) |\n| Debugging flaky tests, quarantining, prevention | [`references\u002Fflaky-test-management.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fflaky-test-management.md) |\n| Configuring CI pipelines, sharding, artifacts | [`references\u002Fci-integration.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fci-integration.md) |\n| Running tests, debugging, code generation, reports | [`references\u002Fcli-commands.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fcli-commands.md) |\n\n---\n\n## E2E Testing Workflow\n\n### 1. Plan Phase\n- Identify critical user journeys (auth, core features, payments, data integrity)\n- Define test scenarios (happy path, edge cases, error cases)\n- Prioritize by risk:\n  - **HIGH**: Financial transactions, authentication flows\n  - **MEDIUM**: Search\u002Ffilter, form submissions\n  - **LOW**: UI polish, cosmetic changes\n\n### 2. Create Phase\n- Write tests following Page Object Model (POM) pattern\n- Use meaningful test descriptions: `test('should [expected behavior] when [condition]')`\n- Include assertions at key steps\n- Capture screenshots at critical interaction points, on failure, and for full-page verification\n\n### 3. Run Phase\n- Run across browsers (Chromium, Firefox, WebKit) and mobile viewports\n- Capture artifacts — screenshots, videos, and traces (see [`references\u002Fcore-patterns.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fcore-patterns.md) for wait strategies)\n- Handle flaky tests through quarantine (see [`references\u002Fflaky-test-management.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fflaky-test-management.md))\n- Use CLI commands for headed debugging, retries, and repeat runs (see [`references\u002Fcli-commands.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fcli-commands.md))\n\n### 4. Report Phase\n- Generate HTML reports, JUnit XML, and JSON output\n- Summarize pass rates, flaky rates, failures with screenshots and error details\n- See [`references\u002Fci-integration.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fci-integration.md) for CI reporting and artifact upload\n\n---\n\n## Core Patterns\n\nFor detailed code examples, see [`references\u002Fcore-patterns.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fcore-patterns.md).\n\n### Test Structure\nFollow AAA (Arrange, Act, Assert) within `test.describe` blocks. Set up state in `beforeEach`, capture screenshots on failure in `afterEach`.\n\n### Selector Strategy\nPriority order: `data-testid` → semantic selectors (`getByRole`, `getByLabel`, `getByText`) → avoid CSS classes. `data-testid` is most stable because your team controls it.\n\n### Wait Strategy\nUse Playwright's auto-waiting: `expect().toBeVisible()` and locator actions retry until the element is ready. Prefer `page.waitForResponse()` for network-dependent checks. Avoid `page.waitForTimeout()` — it masks real timing issues.\n\n### Test Isolation\nEach test must be independently runnable. Use unique test data per test, clear state in `beforeEach`, and close the page in `afterEach`. No shared state, no ordering dependencies.\n\n---\n\n## Validation Checklist\n\nBefore declaring E2E work complete:\n\n### Test Quality\n- [ ] Test descriptions follow `'should [expected behavior] when [condition]'` format\n- [ ] All critical user journeys have test coverage\n- [ ] Selectors use `data-testid` or semantic APIs, not CSS classes\n- [ ] No `page.waitForTimeout()` calls — use auto-waiting or `waitForResponse`\n\n### Stability\n- [ ] Each test is independently runnable (no shared state)\n- [ ] Unique test data per test (no hardcoded values that collide)\n- [ ] Tests pass consistently when run 3+ times locally\n\n### CI Readiness\n- [ ] `playwright.config.ts` configured with CI retries and artifact capture\n- [ ] CI pipeline runs tests on relevant branches\n- [ ] Test duration is under the CI timeout limit\n\n---\n\n## Success Metrics\n\n- All critical journeys passing (100%)\n- Pass rate > 95%\n- Flaky rate \u003C 5%\n- No failed tests blocking deployment\n- Test duration \u003C 10 minutes\n","# E2E Testing\n\n**Purpose:** End-to-end testing methodology for Playwright. Covers the full lifecycle: planning, authoring, debugging flaky tests, and CI integration.\n\n---\n\n## When to Use\n\n**Trigger conditions:**\n\n- Writing or reviewing E2E tests\n- Debugging flaky or failing Playwright tests\n- Setting up Playwright or CI pipelines for E2E\n\n**Do NOT use when:**\n\n- Writing unit or integration tests\n- Working with non-Playwright tools (Cypress, Selenium)\n- Testing business logic without UI\n\n---\n\n## Navigation\n\nUse this table to find the right reference for your task:\n\n| Task | Reference |\n|------|-----------|\n| Writing a test, choosing selectors, setting up isolation | [`references\u002Fcore-patterns.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fcore-patterns.md) |\n| Designing page objects, fixtures, composition | [`references\u002Fpom-patterns.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fpom-patterns.md) |\n| Debugging flaky tests, quarantining, prevention | [`references\u002Fflaky-test-management.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fflaky-test-management.md) |\n| Configuring CI pipelines, sharding, artifacts | [`references\u002Fci-integration.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fci-integration.md) |\n| Running tests, debugging, code generation, reports | [`references\u002Fcli-commands.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fcli-commands.md) |\n\n---\n\n## E2E Testing Workflow\n\n### 1. Plan Phase\n- Identify critical user journeys (auth, core features, payments, data integrity)\n- Define test scenarios (happy path, edge cases, error cases)\n- Prioritize by risk:\n  - **HIGH**: Financial transactions, authentication flows\n  - **MEDIUM**: Search\u002Ffilter, form submissions\n  - **LOW**: UI polish, cosmetic changes\n\n### 2. Create Phase\n- Write tests following Page Object Model (POM) pattern\n- Use meaningful test descriptions: `test('should [expected behavior] when [condition]')`\n- Include assertions at key steps\n- Capture screenshots at critical interaction points, on failure, and for full-page verification\n\n### 3. Run Phase\n- Run across browsers (Chromium, Firefox, WebKit) and mobile viewports\n- Capture artifacts — screenshots, videos, and traces (see [`references\u002Fcore-patterns.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fcore-patterns.md) for wait strategies)\n- Handle flaky tests through quarantine (see [`references\u002Fflaky-test-management.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fflaky-test-management.md))\n- Use CLI commands for headed debugging, retries, and repeat runs (see [`references\u002Fcli-commands.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fcli-commands.md))\n\n### 4. Report Phase\n- Generate HTML reports, JUnit XML, and JSON output\n- Summarize pass rates, flaky rates, failures with screenshots and error details\n- See [`references\u002Fci-integration.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fci-integration.md) for CI reporting and artifact upload\n\n---\n\n## Core Patterns\n\nFor detailed code examples, see [`references\u002Fcore-patterns.md`](file:\u002F\u002F\u002Fhome\u002Fopencode\u002F.config\u002Fopencode\u002Fskills\u002Fe2e\u002Freferences\u002Fcore-patterns.md).\n\n### Test Structure\nFollow AAA (Arrange, Act, Assert) within `test.describe` blocks. Set up state in `beforeEach`, capture screenshots on failure in `afterEach`.\n\n### Selector Strategy\nPriority order: `data-testid` → semantic selectors (`getByRole`, `getByLabel`, `getByText`) → avoid CSS classes. `data-testid` is most stable because your team controls it.\n\n### Wait Strategy\nUse Playwright's auto-waiting: `expect().toBeVisible()` and locator actions retry until the element is ready. Prefer `page.waitForResponse()` for network-dependent checks. Avoid `page.waitForTimeout()` — it masks real timing issues.\n\n### Test Isolation\nEach test must be independently runnable. Use unique test data per test, clear state in `beforeEach`, and close the page in `afterEach`. No shared state, no ordering dependencies.\n\n---\n\n## Validation Checklist\n\nBefore declaring E2E work complete:\n\n### Test Quality\n- [ ] Test descriptions follow `'should [expected behavior] when [condition]'` format\n- [ ] All critical user journeys have test coverage\n- [ ] Selectors use `data-testid` or semantic APIs, not CSS classes\n- [ ] No `page.waitForTimeout()` calls — use auto-waiting or `waitForResponse`\n\n### Stability\n- [ ] Each test is independently runnable (no shared state)\n- [ ] Unique test data per test (no hardcoded values that collide)\n- [ ] Tests pass consistently when run 3+ times locally\n\n### CI Readiness\n- [ ] `playwright.config.ts` configured with CI retries and artifact capture\n- [ ] CI pipeline runs tests on relevant branches\n- [ ] Test duration is under the CI timeout limit\n\n---\n\n## Success Metrics\n\n- All critical journeys passing (100%)\n- Pass rate > 95%\n- Flaky rate \u003C 5%\n- No failed tests blocking deployment\n- Test duration \u003C 10 minutes\n",{"name":5,"description":7},"main","8f95d6b7cbf4ec39161b4e6c8bc5e1493e58003c","config\u002Fskills\u002Fe2e",0,"https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow","https:\u002F\u002Fgithub.com\u002Fxiaden","2026-09-30 22:33:49",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add xiaden\u002FSkyScow --skill e2e",{"tool":37,"command":38},"bunx","bunx skills add xiaden\u002FSkyScow --skill e2e",{"tool":40,"command":41},"pnpm","pnpm dlx skills add xiaden\u002FSkyScow --skill e2e","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Fskills\u002Fe2e\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fci-integration.md","REFERENCE","参考文档",5906,"https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Fskills\u002Fe2e\u002Freferences\u002Fci-integration.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcli-commands.md",2377,"https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Fskills\u002Fe2e\u002Freferences\u002Fcli-commands.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fcore-patterns.md",3166,"https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Fskills\u002Fe2e\u002Freferences\u002Fcore-patterns.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fflaky-test-management.md",5012,"https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Fskills\u002Fe2e\u002Freferences\u002Fflaky-test-management.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fpom-patterns.md",5081,"https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Fskills\u002Fe2e\u002Freferences\u002Fpom-patterns.md",[68,74,81,87,94,101],{"skillNo":69,"name":70,"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":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CTNJ49PJ794TEFBCNYYKQM","unquoted-colon","https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Ftools\u002Ftests\u002Ffixtures\u002Fskills\u002Funquoted-colon\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CTNENFBZPEX63HNSRBCW4T","quoted-description","Use when a plain scalar contains a colon: like this one.","https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Ftools\u002Ftests\u002Ffixtures\u002Fskills\u002Fquoted-description\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CTNBBPKA6GMCVEM3GPB59F","block-description","https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Ftools\u002Ftests\u002Ffixtures\u002Fskills\u002Fblock-description\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7CTN4M0SR4Z4TPJMHWC3A3B","work-routing","Canonical authority for who owns the next unit of work — direct work versus delegation, task tiers, bounded localization, the Change DAG size threshold, R&D evaluation routing, progressive research escalation, researcher scope signals, and QA\u002Fsupport owner selection. Use before choosing execution, investigation, design, or QA ownership; do not use to construct dispatch prompts, handoff schemas, or Change DAG\u002FDD tool operation.","https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Fskills\u002Fwork-routing\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7CTMY5AY3NSNHGQJA0M7VP9","update-docs","Update project documentation to match code changes — generate codemaps, refresh READMEs, detect doc\u002Fcode drift using AST analysis. Use when updating documentation after code changes, generating codemaps, verifying doc accuracy, or detecting stale documentation. Do NOT use for writing API reference docs from scratch (use doc-coauthoring) or for creating new skill files (use making-editing-skills).","https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Fskills\u002Fupdate-docs\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7CTMSQD82CPD53C6F07J0R9","skill-loading-system","Explain or troubleshoot OpenCode skill discovery, loading, permissions, availability, or prompt injection.","https:\u002F\u002Fgithub.com\u002Fxiaden\u002FSkyScow\u002Fblob\u002Fmain\u002Fconfig\u002Fskills\u002Fskill-loading-system\u002FSKILL.md",[],[]]