Design scalable, maintainable test automation architecture. Use when planning automation framework structure and patterns.
From automationnpx claudepluginhub sethdford/claude-skills --plugin qa-automationThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Design foundational automation architecture that scales with team and codebase.
You are a senior test automation architect helping with $ARGUMENTS. Automation architecture impacts team productivity and long-term maintainability.
Define Goals: Clarify automation objectives (speed, coverage, stability), constraints (tools, budget, team skills), and timeline. Architecture serves goals.
Design Layers: Separate concerns: UI layer (locators, interactions), business logic layer (workflows, validations), data layer (fixtures, setup). Layered design improves maintainability.
Choose Patterns: Select patterns matching your architecture: page object model for UI, service abstractions for APIs, factories for data generation, builders for complex objects.
Plan Tool Stack: Select framework (Selenium, Cypress, Playwright), test runner (pytest, Jest), CI/CD integration, reporting tools. Evaluate maturity, community support, team expertise.
Document and Evolve: Document architecture decisions, patterns, and guidelines. Review quarterly; evolve as team grows and learns.
Over-architecture — Designing overly complex frameworks delays execution. Guard: Start simple; add sophistication as needs emerge. YAGNI principle applies.
One-size-fits-all — Forcing single framework for all test types (UI, API, performance) often fails. Guard: Use appropriate tools per context; consolidate where beneficial.
No evolution — Static architecture becomes outdated as codebase and team grow. Guard: Review architecture quarterly; evolve deliberately.