cypress-migration
Skill0 starsChanged 35 days agoMITView on GitHub
Migration skill for moving existing UI automation to Cypress. Use when the agent needs to translate Playwright or Selenium/WebDriver patterns, plan incremental migration, preserve coverage during framework change, or explain architectural differences that affect the suite design.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Use this skill when the user is moving from another browser automation stack to Cypress.
- Distinctive: line 41
Prefer migration plans, translated examples, and architecture notes over abstract comparisons.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cypress Migration Guides
Use this skill when the user is moving from another browser automation stack to Cypress.
Migration Workflow
- Inventory the existing suite structure, runner assumptions, and shared helpers.
- Map framework concepts to Cypress equivalents.
- Choose an incremental migration path that preserves confidence.
- Revisit architecture decisions such as waiting, selectors, network control, fixtures, and CI once the syntax translation is done.
Official References
- Cypress best practices: https://docs.cypress.io/guides/references/best-practices
Guide Index
| Migrating from | Guide |
| Playwright | from-playwright.md |
| Selenium / WebDriver | from-selenium.md |
Output Bias
Prefer migration plans, translated examples, and architecture notes over abstract comparisons.
Other versions1 project uses a version of this.
Word for word · 1
- jovd83/Cypress-skill★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- cypress-analysis-requirementsSkill
- cypress-ciSkill
- cypress-coreSkill
- cypress-cliSkill
- cypress-orchestratorSkill
- cypress-pomSkill
- cypress-skillSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.