[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZJ10VTSPE5TE3YX2MH8WR":3,"skill-same:01M72ZJ10VTSPE5TE3YX2MH8WR":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M72ZJ10VTSPE5TE3YX2MH8WR","playwright-expert",null,"Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.","andrewthomastaylor\u002FSkills","andrewthomastaylor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249856925?v=4","01M72Z00NZWQPWA1TVXZPKXXWJ","01M72Z00PJ210Z6DAD1N93P2HG",0,"MIT","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fplaywright-expert\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: playwright-expert\ndescription: \"Use when writing E2E tests with Playwright, setting up test infrastructure, or debugging flaky browser tests. Invoke to write test scripts, create page objects, configure test fixtures, set up reporters, add CI integration, implement API mocking, or perform visual regression testing. Trigger terms: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing, Page Object Model, test flakiness.\"\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: quality\n  triggers: Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing\n  role: specialist\n  scope: testing\n  output-format: code\n  related-skills: test-master, react-expert, devops-engineer\n---\n\n# Playwright Expert\n\nE2E testing specialist with deep expertise in Playwright for robust, maintainable browser automation.\n\n## Core Workflow\n\n1. **Analyze requirements** - Identify user flows to test\n2. **Setup** - Configure Playwright with proper settings\n3. **Write tests** - Use POM pattern, proper selectors, auto-waiting\n4. **Debug** - Run test → check trace → identify issue → fix → verify fix\n5. **Integrate** - Add to CI\u002FCD pipeline\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Selectors | `references\u002Fselectors-locators.md` | Writing selectors, locator priority |\n| Page Objects | `references\u002Fpage-object-model.md` | POM patterns, fixtures |\n| API Mocking | `references\u002Fapi-mocking.md` | Route interception, mocking |\n| Configuration | `references\u002Fconfiguration.md` | playwright.config.ts setup |\n| Debugging | `references\u002Fdebugging-flaky.md` | Flaky tests, trace viewer |\n\n## Constraints\n\n### MUST DO\n- Use role-based selectors when possible\n- Leverage auto-waiting (don't add arbitrary timeouts)\n- Keep tests independent (no shared state)\n- Use Page Object Model for maintainability\n- Enable traces\u002Fscreenshots for debugging\n- Run tests in parallel\n\n### MUST NOT DO\n- Use `waitForTimeout()` (use proper waits)\n- Rely on CSS class selectors (brittle)\n- Share state between tests\n- Ignore flaky tests\n- Use `first()`, `nth()` without good reason\n\n## Code Examples\n\n### Selector: Role-based (correct) vs CSS class (brittle)\n\n```typescript\n\u002F\u002F ✅ Role-based selector — resilient to styling changes\nawait page.getByRole('button', { name: 'Submit' }).click();\nawait page.getByLabel('Email address').fill('user@example.com');\n\n\u002F\u002F ❌ CSS class selector — breaks on refactor\nawait page.locator('.btn-primary.submit-btn').click();\nawait page.locator('.email-input').fill('user@example.com');\n```\n\n### Page Object Model + Test File\n\n```typescript\n\u002F\u002F pages\u002FLoginPage.ts\nimport { type Page, type Locator } from '@playwright\u002Ftest';\n\nexport class LoginPage {\n  readonly page: Page;\n  readonly emailInput: Locator;\n  readonly passwordInput: Locator;\n  readonly submitButton: Locator;\n  readonly errorMessage: Locator;\n\n  constructor(page: Page) {\n    this.page = page;\n    this.emailInput = page.getByLabel('Email address');\n    this.passwordInput = page.getByLabel('Password');\n    this.submitButton = page.getByRole('button', { name: 'Sign in' });\n    this.errorMessage = page.getByRole('alert');\n  }\n\n  async goto() {\n    await this.page.goto('\u002Flogin');\n  }\n\n  async login(email: string, password: string) {\n    await this.emailInput.fill(email);\n    await this.passwordInput.fill(password);\n    await this.submitButton.click();\n  }\n}\n```\n\n```typescript\n\u002F\u002F tests\u002Flogin.spec.ts\nimport { test, expect } from '@playwright\u002Ftest';\nimport { LoginPage } from '..\u002Fpages\u002FLoginPage';\n\ntest.describe('Login', () => {\n  let loginPage: LoginPage;\n\n  test.beforeEach(async ({ page }) => {\n    loginPage = new LoginPage(page);\n    await loginPage.goto();\n  });\n\n  test('successful login redirects to dashboard', async ({ page }) => {\n    await loginPage.login('user@example.com', 'correct-password');\n    await expect(page).toHaveURL('\u002Fdashboard');\n  });\n\n  test('invalid credentials shows error', async () => {\n    await loginPage.login('user@example.com', 'wrong-password');\n    await expect(loginPage.errorMessage).toBeVisible();\n    await expect(loginPage.errorMessage).toContainText('Invalid credentials');\n  });\n});\n```\n\n### Debugging Workflow for Flaky Tests\n\n```typescript\n\u002F\u002F 1. Run failing test with trace enabled\n\u002F\u002F playwright.config.ts\nuse: {\n  trace: 'on-first-retry',\n  screenshot: 'only-on-failure',\n}\n\n\u002F\u002F 2. Re-run with retries to capture trace\n\u002F\u002F npx playwright test --retries=2\n\n\u002F\u002F 3. Open trace viewer to inspect timeline\n\u002F\u002F npx playwright show-trace test-results\u002F...\u002Ftrace.zip\n\n\u002F\u002F 4. Common fix — replace arbitrary timeout with proper wait\n\u002F\u002F ❌ Flaky\nawait page.waitForTimeout(2000);\nawait page.getByRole('button', { name: 'Save' }).click();\n\n\u002F\u002F ✅ Reliable — waits for element state\nawait page.getByRole('button', { name: 'Save' }).waitFor({ state: 'visible' });\nawait page.getByRole('button', { name: 'Save' }).click();\n\n\u002F\u002F 5. Verify fix — run test 10x to confirm stability\n\u002F\u002F npx playwright test --repeat-each=10\n```\n\n## Output Templates\n\nWhen implementing Playwright tests, provide:\n1. Page Object classes\n2. Test files with proper assertions\n3. Fixture setup if needed\n4. Configuration recommendations\n\n## Knowledge Reference\n\nPlaywright, Page Object Model, auto-waiting, locators, fixtures, API mocking, trace viewer, visual comparisons, parallel execution, CI\u002FCD integration\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fquality\u002Fplaywright-expert\u002F)\n","# Playwright Expert\n\nE2E testing specialist with deep expertise in Playwright for robust, maintainable browser automation.\n\n## Core Workflow\n\n1. **Analyze requirements** - Identify user flows to test\n2. **Setup** - Configure Playwright with proper settings\n3. **Write tests** - Use POM pattern, proper selectors, auto-waiting\n4. **Debug** - Run test → check trace → identify issue → fix → verify fix\n5. **Integrate** - Add to CI\u002FCD pipeline\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Selectors | `references\u002Fselectors-locators.md` | Writing selectors, locator priority |\n| Page Objects | `references\u002Fpage-object-model.md` | POM patterns, fixtures |\n| API Mocking | `references\u002Fapi-mocking.md` | Route interception, mocking |\n| Configuration | `references\u002Fconfiguration.md` | playwright.config.ts setup |\n| Debugging | `references\u002Fdebugging-flaky.md` | Flaky tests, trace viewer |\n\n## Constraints\n\n### MUST DO\n- Use role-based selectors when possible\n- Leverage auto-waiting (don't add arbitrary timeouts)\n- Keep tests independent (no shared state)\n- Use Page Object Model for maintainability\n- Enable traces\u002Fscreenshots for debugging\n- Run tests in parallel\n\n### MUST NOT DO\n- Use `waitForTimeout()` (use proper waits)\n- Rely on CSS class selectors (brittle)\n- Share state between tests\n- Ignore flaky tests\n- Use `first()`, `nth()` without good reason\n\n## Code Examples\n\n### Selector: Role-based (correct) vs CSS class (brittle)\n\n```typescript\n\u002F\u002F ✅ Role-based selector — resilient to styling changes\nawait page.getByRole('button', { name: 'Submit' }).click();\nawait page.getByLabel('Email address').fill('user@example.com');\n\n\u002F\u002F ❌ CSS class selector — breaks on refactor\nawait page.locator('.btn-primary.submit-btn').click();\nawait page.locator('.email-input').fill('user@example.com');\n```\n\n### Page Object Model + Test File\n\n```typescript\n\u002F\u002F pages\u002FLoginPage.ts\nimport { type Page, type Locator } from '@playwright\u002Ftest';\n\nexport class LoginPage {\n  readonly page: Page;\n  readonly emailInput: Locator;\n  readonly passwordInput: Locator;\n  readonly submitButton: Locator;\n  readonly errorMessage: Locator;\n\n  constructor(page: Page) {\n    this.page = page;\n    this.emailInput = page.getByLabel('Email address');\n    this.passwordInput = page.getByLabel('Password');\n    this.submitButton = page.getByRole('button', { name: 'Sign in' });\n    this.errorMessage = page.getByRole('alert');\n  }\n\n  async goto() {\n    await this.page.goto('\u002Flogin');\n  }\n\n  async login(email: string, password: string) {\n    await this.emailInput.fill(email);\n    await this.passwordInput.fill(password);\n    await this.submitButton.click();\n  }\n}\n```\n\n```typescript\n\u002F\u002F tests\u002Flogin.spec.ts\nimport { test, expect } from '@playwright\u002Ftest';\nimport { LoginPage } from '..\u002Fpages\u002FLoginPage';\n\ntest.describe('Login', () => {\n  let loginPage: LoginPage;\n\n  test.beforeEach(async ({ page }) => {\n    loginPage = new LoginPage(page);\n    await loginPage.goto();\n  });\n\n  test('successful login redirects to dashboard', async ({ page }) => {\n    await loginPage.login('user@example.com', 'correct-password');\n    await expect(page).toHaveURL('\u002Fdashboard');\n  });\n\n  test('invalid credentials shows error', async () => {\n    await loginPage.login('user@example.com', 'wrong-password');\n    await expect(loginPage.errorMessage).toBeVisible();\n    await expect(loginPage.errorMessage).toContainText('Invalid credentials');\n  });\n});\n```\n\n### Debugging Workflow for Flaky Tests\n\n```typescript\n\u002F\u002F 1. Run failing test with trace enabled\n\u002F\u002F playwright.config.ts\nuse: {\n  trace: 'on-first-retry',\n  screenshot: 'only-on-failure',\n}\n\n\u002F\u002F 2. Re-run with retries to capture trace\n\u002F\u002F npx playwright test --retries=2\n\n\u002F\u002F 3. Open trace viewer to inspect timeline\n\u002F\u002F npx playwright show-trace test-results\u002F...\u002Ftrace.zip\n\n\u002F\u002F 4. Common fix — replace arbitrary timeout with proper wait\n\u002F\u002F ❌ Flaky\nawait page.waitForTimeout(2000);\nawait page.getByRole('button', { name: 'Save' }).click();\n\n\u002F\u002F ✅ Reliable — waits for element state\nawait page.getByRole('button', { name: 'Save' }).waitFor({ state: 'visible' });\nawait page.getByRole('button', { name: 'Save' }).click();\n\n\u002F\u002F 5. Verify fix — run test 10x to confirm stability\n\u002F\u002F npx playwright test --repeat-each=10\n```\n\n## Output Templates\n\nWhen implementing Playwright tests, provide:\n1. Page Object classes\n2. Test files with proper assertions\n3. Fixture setup if needed\n4. Configuration recommendations\n\n## Knowledge Reference\n\nPlaywright, Page Object Model, auto-waiting, locators, fixtures, API mocking, trace viewer, visual comparisons, parallel execution, CI\u002FCD integration\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fquality\u002Fplaywright-expert\u002F)\n",{"name":5,"license":14,"metadata":23,"description":7},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"specialist","testing","https:\u002F\u002Fgithub.com\u002FJeffallan","quality","1.1.0","Playwright, E2E test, end-to-end, browser testing, automation, UI testing, visual testing","code","test-master, react-expert, devops-engineer","main","cb7b4065bacb4b06224de86d509ccef568f68b79","claude-skills\u002Fskills\u002Fplaywright-expert","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor","2026-05-29 06:53:07",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add andrewthomastaylor\u002FSkills --skill playwright-expert",{"tool":44,"command":45},"bunx","bunx skills add andrewthomastaylor\u002FSkills --skill playwright-expert",{"tool":47,"command":48},"pnpm","pnpm dlx skills add andrewthomastaylor\u002FSkills --skill playwright-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fplaywright-expert\u002FSKILL.md",true,[52,58,62,66,70],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fapi-mocking.md","REFERENCE","参考文档",3145,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fplaywright-expert\u002Freferences\u002Fapi-mocking.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fconfiguration.md",3286,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fplaywright-expert\u002Freferences\u002Fconfiguration.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fdebugging-flaky.md",3207,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fplaywright-expert\u002Freferences\u002Fdebugging-flaky.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fpage-object-model.md",3684,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fplaywright-expert\u002Freferences\u002Fpage-object-model.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fselectors-locators.md",2798,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fplaywright-expert\u002Freferences\u002Fselectors-locators.md",[75,84,92,99,106,113],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M732GDQJ0CWHBAW4D7ENMA3N","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M731QVEE2QCT389Z3X1JWFVQ","humanizer-zh","去除文本中的 AI 生成痕迹。适用于编辑或审阅文本，使其听起来更自然、更像人类书写。\n基于维基百科的\"AI 写作特征\"综合指南。检测并修复以下模式：夸大的象征意义、\n宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、\nAI 词汇、否定式排比、过多的连接性短语。","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M731AMWEC72GFFNFS55F0TTC","returns-reverse-logistics","Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Freturns-reverse-logistics\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M7319BJFM3CBX39C85QWSMD1","quality-nonconformance","Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fquality-nonconformance\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M7318DPHWK6CEVCVT7PHNKDZ","production-scheduling","Codified expertise for production scheduling, job sequencing, line balancing, changeover optimization, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC\u002Fdrum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP\u002FMES interaction patterns. Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fproduction-scheduling\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":18},"01M7315ZE0J0AB6KTQAFGCYF5V","logistics-exception-management","Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Flogistics-exception-management\u002FSKILL.md",[],[]]