pom-patterns

Generate Cypress Page Object Models with base classes and API interceptors.

3|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/NextSpark-js/nextspark --skill pom-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pom-patterns
Source: https://github.com/NextSpark-js/nextspark/tree/main/.claude/skills/pom-patterns
Command: npx skills add https://github.com/NextSpark-js/nextspark --skill pom-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a standardized, robust framework for creating Page Object Models (POMs) in Cypress, ensuring consistency, maintainability, and efficiency in your test automation suite.

Core Features & Use Cases

  • Standardized POM Structure: Enforces a clear hierarchy and naming convention for Page Objects.
  • Reusable Base Classes: Offers BasePOM and DashboardEntityPOM for common functionalities like navigation, form handling, and API intercepting.
  • Automated POM Generation: Includes a script to quickly scaffold new entity POMs.
  • Use Case: When building new end-to-end tests for a complex SaaS application, use this Skill to generate and structure the POMs for managing entities like "Products" or "Users", ensuring all tests follow the same reliable pattern.

Quick Start

Use the pom-patterns skill to generate a new entity POM for 'products' in the 'default' theme.

Frequently Asked Questions about pom-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure Page Object Models in Cypress for a complex SaaS application?

Generate new Cypress Page Object Models by running the included scaffolding script to quickly create entity POMs like 'products', automatically applying standardized naming conventions, fluent interfaces, and API interceptors for consistent test automation.

What is the best way to manage entities like Users and Products in Cypress e2e testing?

Fluent interfaces in Cypress Page Object Models allow chained method calls for UI interactions, which this framework enforces as a best practice to improve test readability and maintainability when building scalable end-to-end test automation suites.

Can I use this framework to scaffold new Cypress page objects automatically?

You need a working Cypress environment and a complex application requiring structured test automation; this framework provides the standardized tooling and base classes necessary to build consistent, scalable end-to-end tests without external dependencies.

Why should I use a Page Object Model framework for Cypress test automation?

Limitations of this POM framework include its strict standardization, which enforces a specific hierarchy and naming convention that may require refactoring existing Cypress tests to fit the BasePOM and DashboardEntityPOM structure for complex applications.