メニュー
Author local Maestro iOS-Simulator E2E flows for the Kata Code mobile app using the reusable TS orchestrator and Kata-specific flows. Use when adding or updating flows under mobile-e2e/.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/gannonh/skills --skill mobile-e2e-test-authorコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Use this skill for multi-step, spec-driven, or acceptance-gated implementation work in a GitHub repository where specs live as GitHub Issues. Routes work through Plan, Build, and Verify phases, manages the roadmap through issue labels and sub-issues, and triages and grooms the backlog. Also handles migration from file-based specs to GitHub Issues.
Structured code review closeout. Codex review is the default when no engine is set and is the recommended reviewer. Use this for auto-review, autoreview, second-model review, CodeRabbit, Greptile, Cursor, Codex review, Claude review, PR review, and final quality/security review requests.
Use when finishing a ticket, feature branch, or pull request and the user asks to validate, demo, verify, sign off, show that it works, run UAT, provide acceptance evidence, or decide whether work is ready to merge. This skill gathers tangible evidence that completed work functions as intended, with videos, screenshots, terminal recordings, JSON responses, output files, logs, and a concise human test guide. Use for web apps, CLI and TUI apps, APIs and SDKs, and native apps including Electron-type apps. Trigger on phrases like "UAT", "verify", "show me it works", "demo this", "walk me through", "ready to merge", "can we merge?", "acceptance test", "validate the changes", "sign off", or any request for proof that a feature branch or PR works.
| name | mobile-e2e-test-author |
| description | Author local Maestro iOS-Simulator E2E flows for the Kata Code mobile app using the reusable TS orchestrator and Kata-specific flows. Use when adding or updating flows under mobile-e2e/. |
Local-only Maestro suite for the Kata Code mobile app on the iOS Simulator. The TS orchestrator owns server lifecycle, isolation, prereq gates, and artifacts; Maestro YAML owns on-device interaction. Real services only — no mocks.
Verified green on-device (iPhone 17 Pro): @smoke, @pairing, @agent. Open:
@auth (the native NativeClerk.presentAuth modal is not yet driven by Maestro).
Full verified locators and the run inventory live in the
Maestro Studio authoring guide
and the E2E test catalog.
Durable learnings to reuse, not relearn:
clearState: false on launchApp keeps the saved Metro URL so the dev client
loads past the Expo Dev Launcher; pair extendedWaitUntil for Metro bundling and
real provider round-trips.connection-status on ConnectionStatusDot, asserted as
connection-status-ready for the pairing ready-state.maestro/shared/ (e.g. open-add-environment.yaml), composed
via runFlow. shared/ is excluded from flow discovery (SUBFLOW_DIRS in
cli/flows.ts) so subflows are never run standalone.flows/agent.ts derives
them (providerMenuLabel: openai→Codex, anthropic→Claude; modelMenuLabel:
gpt-5.4-mini→GPT-5.4-Mini) mirroring the server's toDisplayName. Keep in sync.Read mobile-e2e/README.md and the design spec
(docs/specs/2026-06-24-mobile-e2e-testing-foundation-design.md).
Read Mobile E2E authoring (Maestro Studio) for the canonical Studio workflow.
Inspect existing flows under mobile-e2e/maestro/ and the TS building blocks in
mobile-e2e/src/harness/ and mobile-e2e/src/flows/.
Explore the live app with Maestro Studio first, then codify locators — do not guess selectors from product code alone. Full workflow: Mobile E2E authoring (Maestro Studio).
vp run e2e:mobile:studio # boots the sim, verifies the dev client, opens Studio
| Layer | Role |
|---|---|
src/harness/ (TS) | Generic: simulator control, server stack (serve + token + project add), isolated run, Maestro runner, artifacts, prereq gates |
src/flows/ (TS) | Kata-specific: pairing inputs, Clerk Connect gate, agent expected-text + normalization |
maestro/**/*.yaml | On-device UI — the only layer that references screen elements |
src/cli/run.ts | Orchestrates a run: gate → isolate → sim → server → Maestro → manifest → cleanup |
The TS layer injects dynamic values (one-time token, expected agent text, model)
into flows as -e KEY=VALUE (${KEY} in YAML). Keep dynamic plumbing in TS; keep
flows declarative.
src/harness/ and Kata UI/product
language in src/flows/ + maestro/.mobile-e2e/.auth/,
mobile-e2e/test-results/, mobile-e2e/artifacts/, local .env.local).@smoke, @pairing,
@auth, @agent). New surfaces get new tags; register them in src/config/tags.ts.accessibilityLabel
in product code only when no durable locator exists and it is a deliberate test
contract (e.g. a ConnectionStatusDot ready state).vp run e2e:mobile:build).@smoke and @pairing need no credentials (bearer loopback path).@auth needs CLERK_PUBLISHABLE_KEY, CLERK_SECRET_KEY, KATACODE_E2E_GOOGLE_EMAIL.
Mobile sign-in is a native auth modal (NativeClerk.presentAuth); Maestro may
not be able to drive it. Its green runtime pass is a maintainer responsibility.@agent needs KATACODE_E2E_AGENT_PROVIDER, KATACODE_E2E_AGENT_MODEL, and the
matching provider key. Select the model explicitly; the composer default is not
reliable for deterministic replies. Green runtime pass is a maintainer responsibility.vp run e2e:mobile --list # list flows + tags
vp run e2e:mobile --include-tags @smoke # smoke launch
vp run e2e:mobile --include-tags @pairing # bearer pairing
vp run e2e:mobile:studio # explore / author locators
vp test run mobile-e2e/src # harness + flow unit tests
vp check mobile-e2e # format + lint
Suggested rollout order: @smoke → @pairing → @auth → @agent, one at a time in
Studio, giving the maintainer the exact verify command after each passes.