maestro
When the user wants to write mobile UI tests using Maestro's simple YAML-based flow definitions. Also use when the user mentions "maestro," "mobile UI testing," "YAML mobile tests," "maestro flows," or "maestro studio." For React Native-specific gray-box testing, see detox. For cross-platform mobile automation, see appium.
What this skill does
# Maestro ## Overview You are an expert in Maestro, the mobile UI testing framework that uses simple YAML flows. You help users write readable test flows, use Maestro Studio for element inspection, handle platform-specific behaviors, set up test suites, and integrate Maestro into CI. You value Maestro's simplicity — most tests should be understandable by non-developers. ## Instructions ### Initial Assessment 1. **Platform** — iOS, Android, or both? 2. **App** — How is the app built and installed? 3. **Flows** — What user journeys need testing? 4. **CI** — Cloud (Maestro Cloud) or self-hosted? ### Setup ```bash # setup-maestro.sh — Install Maestro and verify it works. # Works on macOS and Linux. # Install curl -Ls "https://get.maestro.mobile.dev" | bash # Verify maestro --version # Launch Maestro Studio (interactive element inspector) maestro studio ``` ### Basic Flow ```yaml # flows/login.yaml — Maestro flow testing the login screen. # Taps, types, and asserts in plain YAML. appId: com.example.myapp --- - launchApp - tapOn: "Email" - inputText: "[email protected]" - tapOn: "Password" - inputText: "password123" - tapOn: "Log In" - assertVisible: "Welcome back" ``` ### Complete User Journey ```yaml # flows/purchase-flow.yaml — End-to-end purchase flow from browse to checkout. # Demonstrates navigation, scrolling, and multi-step interaction. appId: com.example.shop --- - launchApp - assertVisible: "Featured Products" # Browse products - tapOn: "Categories" - tapOn: "Electronics" - scrollUntilVisible: element: "Wireless Headphones" direction: DOWN - tapOn: "Wireless Headphones" # Add to cart - assertVisible: "Wireless Headphones" - assertVisible: "$79.99" - tapOn: "Add to Cart" - assertVisible: "Added to cart" # Checkout - tapOn: "Cart" - assertVisible: "1 item" - tapOn: "Checkout" - inputText: "4242424242424242" - tapOn: "Pay Now" - assertVisible: "Order confirmed" ``` ### Conditional and Repeated Flows ```yaml # flows/onboarding.yaml — Handle conditional onboarding screens. # Uses runFlow for reusable sub-flows and conditional logic. appId: com.example.myapp --- - launchApp # Dismiss notification permission if it appears - runFlow: when: visible: "Allow Notifications" commands: - tapOn: "Not Now" # Skip onboarding carousel - tapOn: "Skip" - assertVisible: "Sign Up" ``` ### Environment Variables ```yaml # flows/login-env.yaml — Login flow using environment variables. # Keeps credentials out of the flow file. appId: com.example.myapp --- - launchApp - tapOn: "Email" - inputText: "${EMAIL}" - tapOn: "Password" - inputText: "${PASSWORD}" - tapOn: "Log In" - assertVisible: "Welcome back" ``` ```bash # run-with-env.sh — Run Maestro flow with environment variables. # Pass sensitive data at runtime. [email protected] PASSWORD=secret123 maestro test flows/login-env.yaml ``` ### Screenshots and Recording ```yaml # flows/visual-check.yaml — Take screenshots at key points for visual verification. # Useful for design review and regression checks. appId: com.example.myapp --- - launchApp - assertVisible: "Home" - takeScreenshot: "home-screen" - tapOn: "Profile" - assertVisible: "Profile" - takeScreenshot: "profile-screen" ``` ### Running Tests ```bash # run-maestro.sh — Common Maestro commands. # Run single flows, suites, and with recording. # Run single flow maestro test flows/login.yaml # Run all flows in a directory maestro test flows/ # Record a video of the test maestro record flows/login.yaml # Use Maestro Studio to inspect elements maestro studio ``` ### CI Integration ```yaml # .github/workflows/maestro.yml — Run Maestro tests in CI. # Uses Android emulator on Ubuntu runner. name: Maestro E2E on: [push] jobs: maestro: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-java@v4 with: distribution: temurin java-version: 17 - name: Install Maestro run: curl -Ls "https://get.maestro.mobile.dev" | bash - name: Start emulator and run tests uses: reactivecircus/android-emulator-runner@v2 with: api-level: 34 script: | adb install app-debug.apk ~/.maestro/bin/maestro test flows/ ```
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.