Standardizes the creation of Page Object Model classes using Page Factory for clean, maintainable Selenium testing.
Install
mkdir -p .claude/skills/page-factory-basics && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15376" && unzip -o skill.zip -d .claude/skills/page-factory-basics && rm skill.zipInstalls to .claude/skills/page-factory-basics
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create/maintain basic Page Object Model classes using Page Factory.Key capabilities
- →Create Page Object Model classes
- →Initialize page elements using `PageFactory.initElements`
- →Keep locators private with `@FindBy`
- →Expose domain/business actions
- →Receive `WebDriver` in the base constructor
How it works
The skill defines rules for creating Page Object Model classes, including using `PageFactory.initElements` for element initialization, keeping locators private, and exposing only business-level actions.
Inputs & outputs
When to use page-factory-basics
- →Build Page Object Model classes
- →Maintain UI test page definitions
- →Encapsulate web element locators
- →Create reusable web automation actions
About this skill
page-factory-basics
Create/maintain basic Page Object Model classes using Page Factory.
Rules
- Base constructor receives
WebDriver. - Initialize page elements with
PageFactory.initElements. - Keep locators private with
@FindBy. - Expose only domain/business actions.
Output
Reusable pages with clean separation from step definitions.
When not to use it
- →When not using Page Factory for element initialization
- →When not creating Page Object Model classes
- →When not using Java-based WebDriver automation
Limitations
- →Requires `WebDriver` in the base constructor
- →Relies on `PageFactory.initElements` for element initialization
- →Locators must be kept private with `@FindBy`
How it compares
This skill provides a specific set of rules for implementing Page Object Model with Page Factory, ensuring a clean separation of concerns and reusable page definitions, unlike a generic approach to UI automation.
Compared to similar skills
page-factory-basics side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| page-factory-basics (this skill) | 0 | 5mo | No flags | Beginner |
| webapp-testing | 353 | 3mo | Review | Intermediate |
| ui-ux-expert-skill | 91 | 9mo | Review | Advanced |
| accessibility | 42 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
webapp-testing
anthropics
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-ux-expert-skill
fercracix33
Technical workflow for implementing accessible React user interfaces with shadcn/ui, Tailwind CSS, and TanStack Query. Includes 6-phase process with mandatory Style Guide compliance, Context7 best practices consultation, Chrome DevTools validation, and WCAG 2.1 AA accessibility standards. Use after Test Agent, Implementer, and Supabase agents complete their work.
accessibility
tech-leads-club
Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
playwright-browser-automation
lackeyjb
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
svelte-expert
Raudbjorn
Expert Svelte/SvelteKit development assistant for building components, utilities, and applications. Use when creating Svelte components, SvelteKit applications, implementing reactive patterns, handling state management, working with stores, transitions, animations, or any Svelte/SvelteKit development task. Includes comprehensive documentation access, code validation with svelte-autofixer, and playground link generation.
browser-daemon
noiv
Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.