qa-tester
Comprehensive quality assurance and testing workflow that orchestrates test strategy design, automated testing implementation, performance testing, and quality metrics. Handles everything from unit testing and integration testing to end-to-end testing, performance testing, and quality assurance automation.
What this skill does
# QA Tester - Complete Quality Assurance and Testing Workflow ## Overview This skill provides end-to-end quality assurance and testing services by orchestrating QA architects, test automation engineers, and quality specialists. It transforms testing requirements into comprehensive testing strategies with automated test suites, performance validation, and quality metrics. **Key Capabilities:** - ๐งช **Multi-Layer Testing Strategy** - Unit, integration, end-to-end, and acceptance testing - ๐ค **Test Automation** - Automated test suite development and maintenance - โก **Performance Testing** - Load testing, stress testing, and performance optimization - ๐ **Quality Metrics & Reporting** - Comprehensive quality metrics and test reporting - ๐ **Quality Assurance** - Quality gates, defect management, and continuous improvement ## When to Use This Skill **Perfect for:** - Test strategy design and implementation - Automated testing framework setup and development - Performance testing and load testing implementation - Quality assurance process establishment - Test-driven development (TDD) and behavior-driven development (BDD) - Continuous testing and quality monitoring **Triggers:** - "Create comprehensive testing strategy for [application]" - "Implement automated testing framework for [project]" - "Set up performance testing and load testing" - "Establish quality assurance process and metrics" - "Implement TDD/BDD testing practices" ## QA Expert Panel ### **QA Architect** (Test Strategy & Design) - **Focus**: Test strategy design, testing frameworks, quality assurance processes - **Techniques**: Test pyramid, risk-based testing, quality metrics, test planning - **Considerations**: Test coverage, automation ROI, quality gates, risk assessment ### **Test Automation Engineer** (Automated Testing) - **Focus**: Test automation frameworks, automated test development, CI/CD integration - **Techniques**: Selenium, Cypress, Jest, Playwright, test-driven development - **Considerations**: Test reliability, maintenance, execution speed, integration ### **Performance Test Specialist** (Performance & Load Testing) - **Focus**: Performance testing, load testing, stress testing, optimization - **Techniques**: JMeter, Gatling, K6, performance profiling, bottleneck analysis - **Considerations**: Performance metrics, scalability, resource utilization, user experience ### **Quality Assurance Specialist** (Quality Management) - **Focus**: Quality assurance processes, defect management, quality metrics - **Techniques**: Quality gates, defect tracking, root cause analysis, continuous improvement - **Considerations**: Quality standards, process compliance, team collaboration, metrics ### **Security Test Engineer** (Security Testing) - **Focus**: Security testing, vulnerability assessment, penetration testing - **Techniques**: OWASP testing, security scanning, threat modeling, security automation - **Considerations**: Security standards, compliance, risk assessment, remediation ## QA Testing Workflow ### Phase 1: Test Requirements Analysis & Strategy Design **Use when**: Starting testing implementation or QA process establishment **Tools Used:** ```bash /sc:analyze testing-requirements QA Architect: test strategy design and requirements analysis Quality Assurance Specialist: quality standards and process definition Test Automation Engineer: automation feasibility and tool selection ``` **Activities:** - Analyze testing requirements and quality objectives - Define test strategy and testing approach - Identify testing tools and frameworks - Establish quality metrics and success criteria - Plan test environment and resource requirements ### Phase 2: Test Framework Design & Implementation **Use when**: Setting up testing frameworks and automated test infrastructure **Tools Used:** ```bash /sc:design --type testing automation-framework Test Automation Engineer: test framework design and implementation QA Architect: testing patterns and best practices Performance Test Specialist: performance testing framework setup ``` **Activities:** - Design test automation architecture and frameworks - Implement unit testing frameworks and utilities - Set up integration testing infrastructure - Create end-to-end testing frameworks - Implement test data management and fixtures ### Phase 3: Automated Test Development **Use when**: Writing automated tests and building test suites **Tools Used:** ```bash /sc:implement automated-tests Test Automation Engineer: automated test development and maintenance QA Architect: test design patterns and best practices Quality Assurance Specialist: test coverage and quality validation ``` **Activities:** - Develop unit tests with high code coverage - Create integration tests for component interactions - Implement end-to-end tests for user workflows - Build API tests for service validation - Create UI tests for user interface validation ### Phase 4: Performance Testing & Optimization **Use when**: Implementing performance testing and optimization validation **Tools Used:** ```bash /sc:implement performance-testing Performance Test Specialist: performance testing design and implementation Test Automation Engineer: performance test automation QA Architect: performance requirements and validation criteria ``` **Activities:** - Design performance testing scenarios and metrics - Implement load testing and stress testing - Conduct performance profiling and bottleneck analysis - Create performance monitoring and alerting - Validate performance requirements and optimization ### Phase 5: Quality Assurance & Process Implementation **Use when**: Establishing quality assurance processes and quality gates **Tools Used:** ```bash /sc:implement quality-assurance Quality Assurance Specialist: QA process design and implementation QA Architect: quality standards and compliance Test Automation Engineer: continuous testing integration ``` **Activities:** - Implement quality gates and acceptance criteria - Set up defect tracking and management systems - Create quality metrics and reporting dashboards - Establish code review and quality check processes - Implement continuous testing in CI/CD pipelines ### Phase 6: Security Testing & Vulnerability Assessment **Use when**: Implementing security testing and vulnerability management **Tools Used:** ```bash /sc:implement security-testing Security Test Engineer: security testing design and implementation QA Architect: security requirements and validation Quality Assurance Specialist: security compliance and reporting ``` **Activities:** - Implement security testing frameworks and tools - Conduct vulnerability scanning and assessment - Create security test cases and scenarios - Implement security automation in CI/CD - Validate security requirements and compliance ## Integration Patterns ### **SuperClaude Command Integration** | Command | Use Case | Output | |---------|---------|--------| | `/sc:design --type testing` | Test strategy | Complete testing strategy and framework | | `/sc:implement automated-tests` | Test automation | Comprehensive automated test suite | | `/sc:implement performance-testing` | Performance testing | Load testing and performance validation | | `/sc:implement quality-assurance` | QA process | Quality assurance process and metrics | | `/sc:implement security-testing` | Security testing | Security testing and vulnerability assessment | ### **Testing Framework Integration** | Framework | Role | Capabilities | |-----------|------|------------| | **Jest/Mocha** | Unit testing | JavaScript/TypeScript unit testing | | **Selenium/Playwright** | E2E testing | Browser automation and UI testing | | **JMeter/Gatling** | Performance testing | Load testing and performance validation | | **Cypress** | Frontend testing | Modern frontend testing framework | ### **MCP Server Integration** | Server | Expertise | Use Case | |--------|----------|---------| | **Sequential** | Test reasoning | Complex test
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.