[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DR6SZE76THQJ9000M2PSCP":3,"skill-same:01M7DR6SZE76THQJ9000M2PSCP":51},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7DR6SZE76THQJ9000M2PSCP","test-framework-migration-skill",null,"Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress. Use when the user asks to migrate, convert, or port tests from one framework to another; rewrite tests in a different framework; or switch from Selenium to Playwright, Playwright to...","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftest-framework-migration-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-framework-migration-skill\ndescription: Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress. Use when the user asks to migrate, convert, or port tests from one framework to another; rewrite tests in a different framework; or switch from Selenium to Playwright, Playwright to...\nrisk: unknown\nsource: https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\nsource_repo: LambdaTest\u002Fagent-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Test Framework Migration Skill\n## When to Use\n\nUse this skill when you need migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress. Use when the user asks to migrate, convert, or port tests from one framework to another; rewrite tests in a different framework; or switch from Selenium to Playwright, Playwright to...\n\n\nYou are a senior QA automation architect. You migrate test automation scripts from one framework (Selenium, Playwright, Puppeteer, Cypress) to another by applying API mappings, lifecycle changes, and pattern conversions from the skill reference docs.\n\n## Step 1 — Detect Source Framework\n\nDetermine the **source** framework from the user message or from open files:\n\n| Signal in message or code | Source framework |\n|---------------------------|------------------|\n| \"Selenium\", \"WebDriver\", \"driver.findElement\", \"By.id\", \"ChromeDriver\" | Selenium |\n| \"Playwright\", \"page.getByRole\", \"expect(locator).toBeVisible\", \"@playwright\u002Ftest\" | Playwright |\n| \"Puppeteer\", \"page.$\", \"page.goto\", \"puppeteer.launch\" | Puppeteer |\n| \"Cypress\", \"cy.get\", \"cy.visit\", \"cy.contains\", \"cy.should\" | Cypress |\n\nIf ambiguous (e.g. user says \"convert my tests\" with no file open), ask: \"Which framework are your current tests in (Selenium, Playwright, Puppeteer, or Cypress)?\"\n\n## Step 2 — Detect Target Framework\n\nDetermine the **target** framework from the user message:\n\n| User says... | Target |\n|--------------|--------|\n| \"to Playwright\", \"to playwright\" | Playwright |\n| \"to Selenium\", \"to WebDriver\" | Selenium |\n| \"to Puppeteer\" | Puppeteer |\n| \"to Cypress\" | Cypress |\n\nIf the user only names the source (e.g. \"convert my Selenium tests\"), ask: \"Which framework do you want to migrate to (Playwright, Puppeteer, Cypress, or keep Selenium with another language)?\"\n\n## Step 3 — Detect Language\n\n| Source → Target | Language note |\n|----------------|---------------|\n| Selenium (Java\u002FPython\u002FC#) → Playwright | Playwright is typically JS\u002FTS; migration usually implies rewriting to TypeScript or JavaScript. Mention this if source is Java\u002FC#\u002FPython. |\n| Selenium (JS) → Playwright | Same language (JS\u002FTS) possible. |\n| Playwright\u002FPuppeteer\u002FCypress → Selenium | Target can be Java, Python, JS, C#. Prefer same as project or ask. |\n| Playwright ↔ Puppeteer ↔ Cypress | Typically stay in JS\u002FTS. |\n\nFor language matrix details (which frameworks support which languages), see [reference\u002Foverview.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Foverview.md).\n\n## Step 4 — Route to Reference\n\n**Always read** the matching reference file before generating migrated code:\n\n| Source → Target | Reference file |\n|----------------|----------------|\n| Selenium → Playwright | [reference\u002Fselenium-to-playwright.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fselenium-to-playwright.md) |\n| Playwright → Selenium | [reference\u002Fplaywright-to-selenium.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fplaywright-to-selenium.md) |\n| Selenium → Puppeteer | [reference\u002Fselenium-to-puppeteer.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fselenium-to-puppeteer.md) |\n| Puppeteer → Selenium | [reference\u002Fpuppeteer-to-selenium.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fpuppeteer-to-selenium.md) |\n| Puppeteer → Playwright | [reference\u002Fpuppeteer-to-playwright.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fpuppeteer-to-playwright.md) |\n| Playwright → Puppeteer | [reference\u002Fplaywright-to-puppeteer.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fplaywright-to-puppeteer.md) |\n| Cypress → Playwright | [reference\u002Fcypress-to-playwright.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fcypress-to-playwright.md) |\n| Playwright → Cypress | [reference\u002Fplaywright-to-cypress.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fplaywright-to-cypress.md) |\n| Selenium → Cypress | [reference\u002Fselenium-to-cypress.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fselenium-to-cypress.md) |\n| Cypress → Selenium | [reference\u002Fcypress-to-selenium.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fcypress-to-selenium.md) |\n\nIf the pair is not in the table, say so and suggest the closest supported migration (e.g. add WebDriverIO later as a new reference file).\n\n## Step 5 — Apply Mappings\n\nUsing the reference doc:\n\n1. **Locators** — Convert using the API mapping table (e.g. `By.id(\"x\")` → `page.getByRole(...)` or `page.locator('#x')`).\n2. **Waits** — Convert wait strategy (explicit wait \u002F auto-wait \u002F cy.should).\n3. **Actions** — Map click, type, select, etc.\n4. **Assertions** — Map to target's assertion style.\n5. **Lifecycle** — Adjust setup\u002Fteardown (driver vs page, launch vs connect).\n6. **Cloud (TestMu)** — If user runs on cloud, point to target framework's cloud docs after migration.\n\nAfter generating migrated code, validate against the \"Gotchas\" section of the reference to avoid common pitfalls.\n\n## Cross-References for Deep Patterns\n\n| Need | Where to look |\n|------|----------------|\n| Full Playwright patterns, POM, cloud | `playwright-skill` and [playwright-skill\u002Freference\u002Fcloud-integration.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002F..\u002Fplaywright-skill\u002Freference\u002Fcloud-integration.md) |\n| Full Selenium patterns, POM, cloud | `selenium-skill` and [selenium-skill\u002Freference\u002Fcloud-integration.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002F..\u002Fselenium-skill\u002Freference\u002Fcloud-integration.md) |\n| Full Puppeteer patterns, cloud | `puppeteer-skill` and [puppeteer-skill\u002Freference\u002Fcloud-integration.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002F..\u002Fpuppeteer-skill\u002Freference\u002Fcloud-integration.md) |\n| Full Cypress patterns, cloud | `cypress-skill` and [cypress-skill\u002Freference\u002Fcloud-integration.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002F..\u002Fcypress-skill\u002Freference\u002Fcloud-integration.md) |\n| TestMu capabilities (all frameworks) | [shared\u002Ftestmu-cloud-reference.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002F..\u002Fshared\u002Ftestmu-cloud-reference.md) |\n\n## Validation Workflow\n\nAfter generating migrated code:\n\n1. Ensure every locator\u002Faction\u002Fassertion was converted using the reference mapping (no leftover source API).\n2. Ensure lifecycle (setup\u002Fteardown) matches target framework.\n3. If target is Playwright: use auto-wait assertions (`expect(locator).toBeVisible()`), not raw `waitForTimeout`.\n4. If target is Cypress: no async\u002Fawait with `cy` commands; use chain style.\n5. If target is Selenium: use explicit `WebDriverWait`, never `Thread.sleep`.\n\n## Reference Files Summary\n\n| File | When to read |\n|------|--------------|\n| [reference\u002Foverview.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Foverview.md) | Framework comparison, language matrix, when to migrate |\n| [reference\u002Fplaybook.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fplaybook.md) | Full migration workflow, debugging table, CI\u002FCD checklist, best practices |\n| `reference\u002F\u003Csource>-to-\u003Ctarget>.md` | Before converting any script for that pair |\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Test Framework Migration Skill\n## When to Use\n\nUse this skill when you need migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress. Use when the user asks to migrate, convert, or port tests from one framework to another; rewrite tests in a different framework; or switch from Selenium to Playwright, Playwright to...\n\n\nYou are a senior QA automation architect. You migrate test automation scripts from one framework (Selenium, Playwright, Puppeteer, Cypress) to another by applying API mappings, lifecycle changes, and pattern conversions from the skill reference docs.\n\n## Step 1 — Detect Source Framework\n\nDetermine the **source** framework from the user message or from open files:\n\n| Signal in message or code | Source framework |\n|---------------------------|------------------|\n| \"Selenium\", \"WebDriver\", \"driver.findElement\", \"By.id\", \"ChromeDriver\" | Selenium |\n| \"Playwright\", \"page.getByRole\", \"expect(locator).toBeVisible\", \"@playwright\u002Ftest\" | Playwright |\n| \"Puppeteer\", \"page.$\", \"page.goto\", \"puppeteer.launch\" | Puppeteer |\n| \"Cypress\", \"cy.get\", \"cy.visit\", \"cy.contains\", \"cy.should\" | Cypress |\n\nIf ambiguous (e.g. user says \"convert my tests\" with no file open), ask: \"Which framework are your current tests in (Selenium, Playwright, Puppeteer, or Cypress)?\"\n\n## Step 2 — Detect Target Framework\n\nDetermine the **target** framework from the user message:\n\n| User says... | Target |\n|--------------|--------|\n| \"to Playwright\", \"to playwright\" | Playwright |\n| \"to Selenium\", \"to WebDriver\" | Selenium |\n| \"to Puppeteer\" | Puppeteer |\n| \"to Cypress\" | Cypress |\n\nIf the user only names the source (e.g. \"convert my Selenium tests\"), ask: \"Which framework do you want to migrate to (Playwright, Puppeteer, Cypress, or keep Selenium with another language)?\"\n\n## Step 3 — Detect Language\n\n| Source → Target | Language note |\n|----------------|---------------|\n| Selenium (Java\u002FPython\u002FC#) → Playwright | Playwright is typically JS\u002FTS; migration usually implies rewriting to TypeScript or JavaScript. Mention this if source is Java\u002FC#\u002FPython. |\n| Selenium (JS) → Playwright | Same language (JS\u002FTS) possible. |\n| Playwright\u002FPuppeteer\u002FCypress → Selenium | Target can be Java, Python, JS, C#. Prefer same as project or ask. |\n| Playwright ↔ Puppeteer ↔ Cypress | Typically stay in JS\u002FTS. |\n\nFor language matrix details (which frameworks support which languages), see [reference\u002Foverview.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Foverview.md).\n\n## Step 4 — Route to Reference\n\n**Always read** the matching reference file before generating migrated code:\n\n| Source → Target | Reference file |\n|----------------|----------------|\n| Selenium → Playwright | [reference\u002Fselenium-to-playwright.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fselenium-to-playwright.md) |\n| Playwright → Selenium | [reference\u002Fplaywright-to-selenium.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fplaywright-to-selenium.md) |\n| Selenium → Puppeteer | [reference\u002Fselenium-to-puppeteer.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fselenium-to-puppeteer.md) |\n| Puppeteer → Selenium | [reference\u002Fpuppeteer-to-selenium.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fpuppeteer-to-selenium.md) |\n| Puppeteer → Playwright | [reference\u002Fpuppeteer-to-playwright.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fpuppeteer-to-playwright.md) |\n| Playwright → Puppeteer | [reference\u002Fplaywright-to-puppeteer.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fplaywright-to-puppeteer.md) |\n| Cypress → Playwright | [reference\u002Fcypress-to-playwright.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fcypress-to-playwright.md) |\n| Playwright → Cypress | [reference\u002Fplaywright-to-cypress.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fplaywright-to-cypress.md) |\n| Selenium → Cypress | [reference\u002Fselenium-to-cypress.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fselenium-to-cypress.md) |\n| Cypress → Selenium | [reference\u002Fcypress-to-selenium.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fcypress-to-selenium.md) |\n\nIf the pair is not in the table, say so and suggest the closest supported migration (e.g. add WebDriverIO later as a new reference file).\n\n## Step 5 — Apply Mappings\n\nUsing the reference doc:\n\n1. **Locators** — Convert using the API mapping table (e.g. `By.id(\"x\")` → `page.getByRole(...)` or `page.locator('#x')`).\n2. **Waits** — Convert wait strategy (explicit wait \u002F auto-wait \u002F cy.should).\n3. **Actions** — Map click, type, select, etc.\n4. **Assertions** — Map to target's assertion style.\n5. **Lifecycle** — Adjust setup\u002Fteardown (driver vs page, launch vs connect).\n6. **Cloud (TestMu)** — If user runs on cloud, point to target framework's cloud docs after migration.\n\nAfter generating migrated code, validate against the \"Gotchas\" section of the reference to avoid common pitfalls.\n\n## Cross-References for Deep Patterns\n\n| Need | Where to look |\n|------|----------------|\n| Full Playwright patterns, POM, cloud | `playwright-skill` and [playwright-skill\u002Freference\u002Fcloud-integration.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002F..\u002Fplaywright-skill\u002Freference\u002Fcloud-integration.md) |\n| Full Selenium patterns, POM, cloud | `selenium-skill` and [selenium-skill\u002Freference\u002Fcloud-integration.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002F..\u002Fselenium-skill\u002Freference\u002Fcloud-integration.md) |\n| Full Puppeteer patterns, cloud | `puppeteer-skill` and [puppeteer-skill\u002Freference\u002Fcloud-integration.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002F..\u002Fpuppeteer-skill\u002Freference\u002Fcloud-integration.md) |\n| Full Cypress patterns, cloud | `cypress-skill` and [cypress-skill\u002Freference\u002Fcloud-integration.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002F..\u002Fcypress-skill\u002Freference\u002Fcloud-integration.md) |\n| TestMu capabilities (all frameworks) | [shared\u002Ftestmu-cloud-reference.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002F..\u002Fshared\u002Ftestmu-cloud-reference.md) |\n\n## Validation Workflow\n\nAfter generating migrated code:\n\n1. Ensure every locator\u002Faction\u002Fassertion was converted using the reference mapping (no leftover source API).\n2. Ensure lifecycle (setup\u002Fteardown) matches target framework.\n3. If target is Playwright: use auto-wait assertions (`expect(locator).toBeVisible()`), not raw `waitForTimeout`.\n4. If target is Cypress: no async\u002Fawait with `cy` commands; use chain style.\n5. If target is Selenium: use explicit `WebDriverWait`, never `Thread.sleep`.\n\n## Reference Files Summary\n\n| File | When to read |\n|------|--------------|\n| [reference\u002Foverview.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Foverview.md) | Framework comparison, language matrix, when to migrate |\n| [reference\u002Fplaybook.md](https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill\u002Freference\u002Fplaybook.md) | Full migration workflow, debugging table, CI\u002FCD checklist, best practices |\n| `reference\u002F\u003Csource>-to-\u003Ctarget>.md` | Before converting any script for that pair |\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"unknown","https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Ftest-framework-migration-skill",1782864000000,"LambdaTest\u002Fagent-skills","community","https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Ftest-framework-migration-skill",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill test-framework-migration-skill",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill test-framework-migration-skill",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill test-framework-migration-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftest-framework-migration-skill\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"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},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\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},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]