cypress-pom
Skill0 starsChanged 35 days agoMITView on GitHub
Test-architecture skill for Cypress page objects, fixtures, helpers, and custom commands. Use when the agent needs to decide whether to introduce a Page Object Model, how to structure page objects, and how to separate browser state, UI behavior, and stateless utilities cleanly.
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
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 main decision is architectural rather than tactical.
- Distinctive: line 23
Use fixtures and setup hooks for setup, teardown, seeded state, and reusable inputs.
- Distinctive: line 24
Use page objects to encapsulate repeated or complex UI behavior.
- Distinctive: line 25
Use helpers for stateless utilities such as data generation, formatting, or pure transformations.
- Very specific: line 26
Use custom commands or cy.task() only when they provide a real integration benefit rather than becoming a dumping ground for page behavior.
- Distinctive: line 31
Keep assertions close to the test unless a reusable page-level assertion adds clarity.
- Distinctive: line 32
Avoid helpers that silently own browser state.
- Distinctive: line 33
Keep support code organized with the tests it serves.
≈ “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 Page Object Model
Use this skill when the main decision is architectural rather than tactical.
Decision Model
- Use fixtures and setup hooks for setup, teardown, seeded state, and reusable inputs.
- Use page objects to encapsulate repeated or complex UI behavior.
- Use helpers for stateless utilities such as data generation, formatting, or pure transformations.
- Use custom commands or
cy.task()only when they provide a real integration benefit rather than becoming a dumping ground for page behavior.
Practical Rules
- Reach for a page object when the same UI behavior appears in multiple tests or when the flow is complex enough to deserve a named abstraction.
- Keep assertions close to the test unless a reusable page-level assertion adds clarity.
- Avoid helpers that silently own browser state.
- Keep support code organized with the tests it serves.
Guide Index
| Need | Guide |
| Page object design | page-object-model.md |
| POM vs fixture vs helper tradeoffs | pom-vs-fixtures-vs-helpers.md |
| Broader architecture decisions | ../core/test-architecture.md |
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-migrationSkill
- cypress-orchestratorSkill
- cypress-skillSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.