[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KB1M3P5673B8P42TMV5TH2":3,"skill-same:01M6KB1M3P5673B8P42TMV5TH2":68},{"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":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6KB1M3P5673B8P42TMV5TH2","init",null,"Set up Playwright in a project. Use when user says \"set up playwright\", \"add e2e tests\", \"configure playwright\", \"testing setup\", \"init playwright\", or \"add test infrastructure\".","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Finit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"e2e","test infrastructure","add","tests","project","up","use","user","configure","testing","SET","infrastructure","e2e tests","add test","setup","test","playwright","2026-11-10 10:12:30",false,"---\nname: \"init\"\ndescription: >-\n  Set up Playwright in a project. Use when user says \"set up playwright\",\n  \"add e2e tests\", \"configure playwright\", \"testing setup\", \"init playwright\",\n  or \"add test infrastructure\".\n---\n\n# Initialize Playwright Project\n\nSet up a production-ready Playwright testing environment. Detect the framework, generate config, folder structure, example test, and CI workflow.\n\n## Steps\n\n### 1. Analyze the Project\n\nUse the `Explore` subagent to scan the project:\n\n- Check `package.json` for framework (React, Next.js, Vue, Angular, Svelte)\n- Check for `tsconfig.json` → use TypeScript; otherwise JavaScript\n- Check if Playwright is already installed (`@playwright\u002Ftest` in dependencies)\n- Check for existing test directories (`tests\u002F`, `e2e\u002F`, `__tests__\u002F`)\n- Check for existing CI config (`.github\u002Fworkflows\u002F`, `.gitlab-ci.yml`)\n\n### 2. Install Playwright\n\nIf not already installed:\n\n```bash\nnpm init playwright@latest -- --quiet\n```\n\nOr if the user prefers manual setup:\n\n```bash\nnpm install -D @playwright\u002Ftest\nnpx playwright install --with-deps chromium\n```\n\n### 3. Generate `playwright.config.ts`\n\nAdapt to the detected framework:\n\n**Next.js:**\n```typescript\nimport { defineConfig, devices } from '@playwright\u002Ftest';\n\nexport default defineConfig({\n  testDir: '.\u002Fe2e',\n  fullyParallel: true,\n  forbidOnly: !!process.env.CI,\n  retries: process.env.CI ? 2 : 0,\n  workers: process.env.CI ? 1 : undefined,\n  reporter: [\n    ['html', { open: 'never' }],\n    ['list'],\n  ],\n  use: {\n    baseURL: 'http:\u002F\u002Flocalhost:3000',\n    trace: 'on-first-retry',\n    screenshot: 'only-on-failure',\n  },\n  projects: [\n    { name: \"chromium\", use: { ...devices['Desktop Chrome'] } },\n    { name: \"firefox\", use: { ...devices['Desktop Firefox'] } },\n    { name: \"webkit\", use: { ...devices['Desktop Safari'] } },\n  ],\n  webServer: {\n    command: 'npm run dev',\n    url: 'http:\u002F\u002Flocalhost:3000',\n    reuseExistingServer: !process.env.CI,\n  },\n});\n```\n\n**React (Vite):**\n- Change `baseURL` to `http:\u002F\u002Flocalhost:5173`\n- Change `webServer.command` to `npm run dev`\n\n**Vue\u002FNuxt:**\n- Change `baseURL` to `http:\u002F\u002Flocalhost:3000`\n- Change `webServer.command` to `npm run dev`\n\n**Angular:**\n- Change `baseURL` to `http:\u002F\u002Flocalhost:4200`\n- Change `webServer.command` to `npm run start`\n\n**No framework detected:**\n- Omit `webServer` block\n- Set `baseURL` from user input or leave as placeholder\n\n### 4. Create Folder Structure\n\n```\ne2e\u002F\n├── fixtures\u002F\n│   └── index.ts          # Custom fixtures\n├── pages\u002F\n│   └── .gitkeep          # Page object models\n├── test-data\u002F\n│   └── .gitkeep          # Test data files\n└── example.spec.ts       # First example test\n```\n\n### 5. Generate Example Test\n\n```typescript\nimport { test, expect } from '@playwright\u002Ftest';\n\ntest.describe('Homepage', () => {\n  test('should load successfully', async ({ page }) => {\n    await page.goto('\u002F');\n    await expect(page).toHaveTitle(\u002F.+\u002F);\n  });\n\n  test('should have visible navigation', async ({ page }) => {\n    await page.goto('\u002F');\n    await expect(page.getByRole('navigation')).toBeVisible();\n  });\n});\n```\n\n### 6. Generate CI Workflow\n\nIf `.github\u002Fworkflows\u002F` exists, create `playwright.yml`:\n\n```yaml\nname: \"playwright-tests\"\n\non:\n  push:\n    branches: [main, dev]\n  pull_request:\n    branches: [main, dev]\n\njobs:\n  test:\n    timeout-minutes: 60\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: lts\u002F*\n      - name: \"install-dependencies\"\n        run: npm ci\n      - name: \"install-playwright-browsers\"\n        run: npx playwright install --with-deps\n      - name: \"run-playwright-tests\"\n        run: npx playwright test\n      - uses: actions\u002Fupload-artifact@v4\n        if: ${{ !cancelled() }}\n        with:\n          name: \"playwright-report\"\n          path: playwright-report\u002F\n          retention-days: 30\n```\n\nIf `.gitlab-ci.yml` exists, add a Playwright stage instead.\n\n### 7. Update `.gitignore`\n\nAppend if not already present:\n\n```\n\u002Ftest-results\u002F\n\u002Fplaywright-report\u002F\n\u002Fblob-report\u002F\n\u002Fplaywright\u002F.cache\u002F\n```\n\n### 8. Add npm Scripts\n\nAdd to `package.json` scripts:\n\n```json\n{\n  \"test:e2e\": \"playwright test\",\n  \"test:e2e:ui\": \"playwright test --ui\",\n  \"test:e2e:debug\": \"playwright test --debug\"\n}\n```\n\n### 9. Verify Setup\n\nRun the example test:\n\n```bash\nnpx playwright test\n```\n\nReport the result. If it fails, diagnose and fix before completing.\n\n## Output\n\nConfirm what was created:\n- Config file path and key settings\n- Test directory and example test\n- CI workflow (if applicable)\n- npm scripts added\n- How to run: `npx playwright test` or `npm run test:e2e`\n","# Initialize Playwright Project\n\nSet up a production-ready Playwright testing environment. Detect the framework, generate config, folder structure, example test, and CI workflow.\n\n## Steps\n\n### 1. Analyze the Project\n\nUse the `Explore` subagent to scan the project:\n\n- Check `package.json` for framework (React, Next.js, Vue, Angular, Svelte)\n- Check for `tsconfig.json` → use TypeScript; otherwise JavaScript\n- Check if Playwright is already installed (`@playwright\u002Ftest` in dependencies)\n- Check for existing test directories (`tests\u002F`, `e2e\u002F`, `__tests__\u002F`)\n- Check for existing CI config (`.github\u002Fworkflows\u002F`, `.gitlab-ci.yml`)\n\n### 2. Install Playwright\n\nIf not already installed:\n\n```bash\nnpm init playwright@latest -- --quiet\n```\n\nOr if the user prefers manual setup:\n\n```bash\nnpm install -D @playwright\u002Ftest\nnpx playwright install --with-deps chromium\n```\n\n### 3. Generate `playwright.config.ts`\n\nAdapt to the detected framework:\n\n**Next.js:**\n```typescript\nimport { defineConfig, devices } from '@playwright\u002Ftest';\n\nexport default defineConfig({\n  testDir: '.\u002Fe2e',\n  fullyParallel: true,\n  forbidOnly: !!process.env.CI,\n  retries: process.env.CI ? 2 : 0,\n  workers: process.env.CI ? 1 : undefined,\n  reporter: [\n    ['html', { open: 'never' }],\n    ['list'],\n  ],\n  use: {\n    baseURL: 'http:\u002F\u002Flocalhost:3000',\n    trace: 'on-first-retry',\n    screenshot: 'only-on-failure',\n  },\n  projects: [\n    { name: \"chromium\", use: { ...devices['Desktop Chrome'] } },\n    { name: \"firefox\", use: { ...devices['Desktop Firefox'] } },\n    { name: \"webkit\", use: { ...devices['Desktop Safari'] } },\n  ],\n  webServer: {\n    command: 'npm run dev',\n    url: 'http:\u002F\u002Flocalhost:3000',\n    reuseExistingServer: !process.env.CI,\n  },\n});\n```\n\n**React (Vite):**\n- Change `baseURL` to `http:\u002F\u002Flocalhost:5173`\n- Change `webServer.command` to `npm run dev`\n\n**Vue\u002FNuxt:**\n- Change `baseURL` to `http:\u002F\u002Flocalhost:3000`\n- Change `webServer.command` to `npm run dev`\n\n**Angular:**\n- Change `baseURL` to `http:\u002F\u002Flocalhost:4200`\n- Change `webServer.command` to `npm run start`\n\n**No framework detected:**\n- Omit `webServer` block\n- Set `baseURL` from user input or leave as placeholder\n\n### 4. Create Folder Structure\n\n```\ne2e\u002F\n├── fixtures\u002F\n│   └── index.ts          # Custom fixtures\n├── pages\u002F\n│   └── .gitkeep          # Page object models\n├── test-data\u002F\n│   └── .gitkeep          # Test data files\n└── example.spec.ts       # First example test\n```\n\n### 5. Generate Example Test\n\n```typescript\nimport { test, expect } from '@playwright\u002Ftest';\n\ntest.describe('Homepage', () => {\n  test('should load successfully', async ({ page }) => {\n    await page.goto('\u002F');\n    await expect(page).toHaveTitle(\u002F.+\u002F);\n  });\n\n  test('should have visible navigation', async ({ page }) => {\n    await page.goto('\u002F');\n    await expect(page.getByRole('navigation')).toBeVisible();\n  });\n});\n```\n\n### 6. Generate CI Workflow\n\nIf `.github\u002Fworkflows\u002F` exists, create `playwright.yml`:\n\n```yaml\nname: \"playwright-tests\"\n\non:\n  push:\n    branches: [main, dev]\n  pull_request:\n    branches: [main, dev]\n\njobs:\n  test:\n    timeout-minutes: 60\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with:\n          node-version: lts\u002F*\n      - name: \"install-dependencies\"\n        run: npm ci\n      - name: \"install-playwright-browsers\"\n        run: npx playwright install --with-deps\n      - name: \"run-playwright-tests\"\n        run: npx playwright test\n      - uses: actions\u002Fupload-artifact@v4\n        if: ${{ !cancelled() }}\n        with:\n          name: \"playwright-report\"\n          path: playwright-report\u002F\n          retention-days: 30\n```\n\nIf `.gitlab-ci.yml` exists, add a Playwright stage instead.\n\n### 7. Update `.gitignore`\n\nAppend if not already present:\n\n```\n\u002Ftest-results\u002F\n\u002Fplaywright-report\u002F\n\u002Fblob-report\u002F\n\u002Fplaywright\u002F.cache\u002F\n```\n\n### 8. Add npm Scripts\n\nAdd to `package.json` scripts:\n\n```json\n{\n  \"test:e2e\": \"playwright test\",\n  \"test:e2e:ui\": \"playwright test --ui\",\n  \"test:e2e:debug\": \"playwright test --debug\"\n}\n```\n\n### 9. Verify Setup\n\nRun the example test:\n\n```bash\nnpx playwright test\n```\n\nReport the result. If it fails, diagnose and fix before completing.\n\n## Output\n\nConfirm what was created:\n- Config file path and key settings\n- Test directory and example test\n- CI workflow (if applicable)\n- npm scripts added\n- How to run: `npx playwright test` or `npm run test:e2e`\n",{"name":5,"description":7},"main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering-team\u002Fplaywright-pro\u002Fskills\u002Finit",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill init",{"tool":60,"command":61},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill init",{"tool":63,"command":64},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering-team\u002Fplaywright-pro\u002Fskills\u002Finit\u002FSKILL.md",true,[],[69,100,125,150,180,200],{"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":80,"publishedAt":41},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[75],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[81,82,83,84,85,86,87,88,30,89,90,91,92,93,94,95,96,97,98,99],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":41},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[107,108,109,110,111,112,113,114,88,30,115,116,117,118,119,120,121,122,123,124],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":41},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[132,133,134,135,136,137,138,139,140,30,141,142,143,144,145,146,147,148,149,99],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":162,"publishedAt":41},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[156,159],{"categoryNo":157,"categoryName":158,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":160,"categoryName":161,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000032","设计师",[163,164,149,165,166,167,168,169,170,30,171,172,173,174,175,176,177,178,99,179],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":187,"publishedAt":41},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[186],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[188,164,149,189,190,191,192,193,81,194,170,195,133,196,197,198,116,175,99,199],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":213,"publishedAt":41},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[206,209,212],{"categoryNo":207,"categoryName":208,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":210,"categoryName":211,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},[214,215,164,149,189,216,217,85,170,218,219,220,221,222,117,223,224,225,226,99],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]