Menu
Create BO page object classes in the ui-testing-library for a new migrated page. Follows the Page Object Model pattern: encapsulate selectors and interactions, never assert. Trigger: "create page objects for {Domain}".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Complete PrestaShop module development workflow using modern architecture and best practices. Use when: creating new PrestaShop modules, updating legacy modules to modern code, implementing hooks and actions, setting up module configuration pages, adding front office features, handling database operations, implementing security measures, managing translations, creating cart rules and vouchers, building Symfony console commands, or modernizing existing PrestaShop modules from legacy patterns to current standards.
Create the form page actions in the admin controller: create (add) and edit, plus any entity-specific actions. Uses FormBuilder/FormHandler pattern — never builds commands directly. Trigger: "create form actions for {Domain}", "create add/edit for {Domain}".
Create the repository in the Adapter layer. This is the ONLY class that touches the database — all handlers delegate to it. Covers multistore patterns with ShopConstraint when the entity requires it. Trigger: "create repository for {Domain}".
Create the form data flow layer: DataProvider (loads entity data for edit form), DataHandler (dispatches commands on create/update), error handling, and service registration. This bridges the form layer with the CQRS layer. Read Component/Forms/CONTEXT.md for conventions. Trigger: "create form data handling for {Domain}".
Create a multi-tab form layout using PrestaShop's NavigationTabType. This is a specific pattern for complex forms with many fields organized by tabs — NOT the default form layout. Most forms do not need tabs. Trigger: "create tab layout for {Domain} form", "add tabs to {Domain} form".
Create the Symfony form type for an entity's add/edit form. Covers standard field types, translatable fields, money fields, file uploads, and choice providers. For multi-tab layout with NavigationTabType, see create-form-tab-layout. Trigger: "create form type for {Domain}".
| name | create-playwright-page-objects |
| description | Create BO page object classes in the ui-testing-library for a new migrated page. Follows the Page Object Model pattern: encapsulate selectors and interactions, never assert. Trigger: "create page objects for {Domain}". |
| needs | ["create-controller-listing","create-controller-form-actions","create-admin-routing"] |
| produces | Page object classes in ui-testing-library: bo{Domain}Page + bo{Domain}CreatePage |
Read @.ai/Component/Playwright/CONTEXT.md for the POM pattern and ui-testing-library architecture.
Page objects live in the ui-testing-library, not in the core repo.
Create bo{Domain}Page (extends the appropriate BO base page):
getNumberOfElementInGrid(page): Promise<number>filterTable(page, filterBy, value): Promise<void>resetAndGetNumberOfLines(page): Promise<number>getTextColumn(page, row, column): Promise<string>goToAddNewPage(page): Promise<void>goToEditPage(page, row): Promise<void>deleteRow(page, row): Promise<string> — returns alert textbulkAction(page, action): Promise<string> — returns alert textgetToggleColumnValue(page, row): Promise<boolean>setToggleColumnValue(page, row, value): Promise<string>Selector naming: {name}{Type} camelCase — e.g. gridTable, filterNameInput, bulkActionDropdownButton, confirmDeleteButton
Create bo{Domain}CreatePage (extends BO base page):
createEdit{Domain}(page, data): Promise<string> — fills all fields, clicks save, returns alert textgetPageTitle(page): Promise<string>getValue(page, inputName): Promise<string> — for verification after reloadpageTitleCreate: string — expected page title for create modepageTitleEdit: string — expected page title for edit modesuccessfulCreationMessage: stringsuccessfulUpdateMessage: stringSee Playwright/CONTEXT.md for POM conventions (never assert, selector naming, inheritance, library location). Skill-specific reminders:
data-test attribute selectors when available over CSS classesReference: check existing page objects in the ui-testing-library for the exact inheritance pattern and method signatures.