Interactive migration from Cypress or Selenium to Playwright with file-by-file conversion.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmigrateExecute the skills CLI command in your project's root directory to begin installation:
Fetches migrate from alirezarezvani/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate migrate. Access via /migrate in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
9.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
9.7K
stars
Interactive migration from Cypress or Selenium to Playwright with file-by-file conversion.
$ARGUMENTS can be:
"from cypress" — migrate Cypress test suite"from selenium" — migrate Selenium/WebDriver testsUse Explore subagent to scan:
cypress/ directory or cypress.config.ts → Cypressselenium, webdriver in package.json deps → Selenium.py test files with selenium imports → Selenium (Python)Count files and categorize:
Migration Assessment:
- Total test files: X
- Cypress custom commands: Y
- Cypress fixtures: Z
- Estimated effort: [small|medium|large]
| Size | Files | Approach |
|---|---|---|
| Small (1-10) | Convert sequentially | Direct conversion |
| Medium (11-30) | Batch in groups of 5 | Use sub-agents |
| Large (31+) | Use /batch |
Parallel conversion with /batch |
Run /pw:init first if Playwright isn't configured.
For each file, apply the appropriate mapping:
Load cypress-mapping.md for complete reference.
Key translations:
cy.visit(url) → page.goto(url)
cy.get(selector) → page.locator(selector) or page.getByRole(...)
cy.contains(text) → page.getByText(text)
cy.find(selector) → locator.locator(selector)
cy.click() → locator.click()
cy.type(text) → locator.fill(text)
cy.should('be.visible') → expect(locator).toBeVisible()
cy.should('have.text') → expect(locator).toHaveText(text)
cy.intercept() → page.route()
cy.wait('@alias') → page.waitForResponse()
cy.fixture() → JSON import or test data file
Cypress custom commands → Playwright fixtures or helper functions
Cypress plugins → Playwright config or fixtures
before/beforeEach → test.beforeAll() / test.beforeEach()
Load selenium-mapping.md for complete reference.
Key translations:
driver.get(url) → page.goto(url)
driver.findElement(By.id('x')) → page.locator('#x') or page.getByTestId('x')
driver.findElement(By.css('.x')) → page.locator('.x') or page.getByRole(...)
element.click() → locator.click()
element.sendKeys(text) → locator.fill(text)
element.getText() → locator.textContent()
WebDriverWait + ExpectedConditions → expect(locator).toBeVisible()
driver.switchTo().frame() → page.frameLocator()
Actions → locator.hover(), locator.dragTo()
During conversion, upgrade selectors to Playwright best practices:
#id → getByTestId() or getByRole().class → getByRole() or getByText()[data-testid] → getByTestId()test.extend()After converting each file:
npx playwright test <converted-file> --reporter=list
Fix any compilation or runtime errors before moving to the next file.
After all files are converted:
package.jsoncypress.config.ts, etc.)Ask user before deleting anything.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
alirezarezvani/claude-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
We added migrate from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
migrate is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
migrate fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
migrate reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in migrate — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for migrate matched our evaluation — installs cleanly and behaves as described in the markdown.
We added migrate from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in migrate — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
migrate fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
migrate is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 57