appium-page-objects

Structure and locator/wait discipline for Appium/WDIO Page Object classes: a shared NativeBase contract, locator construction via the typed testID catalog, verify* assertion methods, one file per screen, and a hard line between page structure and business/domain flow logic.

What it covers

• A shared NativeBase base class that every page object extends, with locators constructed via the typed testID catalog.
• verify* assertion methods that assert internally rather than returning a boolean.
• A deterministic screen-to-class naming rule, one page-object file per screen.

Use it

Read SKILL.md for the invariants and the red flags that call them out. Copy references/WidgetsCreatePage.ts as the template for a new page object (root testID via super(), $(nativeUtils.buildSelector(...)) locator getters typed ChainablePromiseElement, verify* assertions, one action composing a sibling-skill wait), references/widgets-create.spec.ts as the template for the spec that drives it, and references/behavior.test.ts as the executable proof that the catalog → waits → page-object → spec chain composes.

Install globally

skills add [email protected]:catesandrew/next-starters.git --skill skills/appium-page-objects -g

Companion

Pairs with a sibling skill that owns the wait-helper implementations this skill's page objects call into around their interactions, and with another sibling skill that owns the typed testID catalog this skill's page objects pull ids from. This skill only defines the page-object class shape and locator/wait discipline that consumes those two.