skills.rest
PT-Perkasa-Pilar-Utama
PT-Perkasa-Pilar-UtamaOFFICIAL
Explore all skills by this author →
Website𝕏@perkasaidGitHub

add-maestro-flow

Create Maestro end-to-end flows for Axentra web UI acceptance criteria.

Updated Sep 16, 2026
Search Tags:#test automation#React#UI testing#acceptance criteria#vite#e2e testing#maestro
One-click install
npx skills add https://github.com/PT-Perkasa-Pilar-Utama/axentra --skill add-maestro-flow-pt-perkasa-pilar-utama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-maestro-flow
Source: https://github.com/PT-Perkasa-Pilar-Utama/axentra/tree/main/.claude/skills/add-maestro-flow
Command: npx skills add https://github.com/PT-Perkasa-Pilar-Utama/axentra --skill add-maestro-flow-pt-perkasa-pilar-utama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need repeatable, browser-visible end-to-end tests for approved UI acceptance criteria in the Axentra Document Management System, and writing Maestro flows ad hoc leads to inconsistent assertions, unstable filenames, and unverified results. ## Core Features & Use Cases - Standardized Flow Placement: Places Maestro flows under e2e/maestro/ with stable, descriptive filenames. - User-Visible Assertions: Asserts text, navigation, and persisted outcomes rather than implementation details, with deterministic cleanup and negative paths when required. - Use Case: When an acceptance criterion requires a user to log in and see a dashboard, create a Maestro flow that starts the API and Vite web app, signs in with seeded test credentials, asserts the visible outcome, and then run bun run complete-check to verify. ## Quick Start Add a Maestro flow for the approved acceptance criterion that verifies a user can sign in and view the document list.

Frequently Asked Questions about add-maestro-flow

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

FAQPage Schema
How do I add a Maestro flow for an Axentra acceptance criterion?▼

Place the flow under e2e/maestro/ with a stable descriptive filename, start the API and web app with the documented local commands, and assert user-visible text, navigation, and persisted outcomes using seeded test credentials.

What should Maestro flows assert in end-to-end UI tests?▼

Maestro flows should assert user-visible text, navigation, and persisted outcomes rather than implementation details. Add a negative or error path when the acceptance criterion requires it, and keep cleanup deterministic.

Can I use production credentials in Maestro test flows?▼

No. Maestro flows must use seeded, non-production credentials from test configuration only. This keeps tests safe and reproducible against local infrastructure.

When should I not write a Maestro flow for a criterion?▼

Only use Maestro flows for acceptance criteria that require browser-visible behavior. Criteria without UI-visible outcomes should be verified through other means, since Axentra web runs through Vite and React Router.

What do I do if an external dependency is unavailable during a Maestro run?▼

Document the unavailable external dependency as unverified rather than passed. Run the flow locally and then bun run complete-check, and never mark a blocked verification as successful.

Related Skills

Explore More Software Engineering Skills→
Lobbi-DocsLobbi-Docs
18

Infrastructure Foundation Skill

Deploy and operate Vault, Traefik, Authentik, PostgreSQL, Redis, and MinIO infrastructure.

Official
Advanced
AlphaCompositeAlphaComposite
4

sp-verification-before-completion

Run verification commands and inspect outputs before declaring task completion.

Community
Advanced
verivendverivend

vitest-testing

Generate Vitest unit test templates for Vue 3 TypeScript Vite projects.

Official
Intermediate
vecearvecear

e2e-test-builder

Automate end-to-end browser test creation and maintenance with Playwright or Cypress.

Community
Advanced