Testing
Unit tests, integration tests, test automation
ring:using-dev-team
by LerianStudio
9 specialist developer agents for backend (Go/TypeScript), DevOps, frontend, design, UI implementation, QA (backend + frontend), and SRE. Dispatch when you need deep technology expertise.
ring:using-git-worktrees
by LerianStudio
Isolated workspace creation - creates git worktrees with smart directory selection and safety verification for parallel feature development.
ring:exploring-codebase
by LerianStudio
Autonomous two-phase codebase exploration - first discovers natural perspectives (layers, components, boundaries), then dispatches adaptive deep-dive explorers based on what was discovered. Synthesizes findings into actionable insights.
ring:verification-before-completion
by LerianStudio
Evidence-first completion gate - requires running verification commands and confirming output before making any success claims.
ring:dev-integration-testing
by LerianStudio
Gate 6 of development cycle - ensures integration tests pass for all external dependency interactions using real containers via testcontainers.
ring:dev-frontend-accessibility
by LerianStudio
Gate 2 of frontend development cycle - ensures all components pass axe-core automated accessibility scans with zero WCAG 2.1 AA violations.
ring:test-driven-development
by LerianStudio
RED-GREEN-REFACTOR implementation methodology - write failing test first, minimal implementation to pass, then refactor. Ensures tests verify behavior.
ring:dev-sre
by LerianStudio
Gate 2 of the development cycle. VALIDATES that observability was correctly implemented by developers. Does not implement observability code - only validates it.
ring:dev-property-testing
by LerianStudio
Gate 5 of development cycle - ensures property-based tests exist to verify domain invariants hold for all randomly generated inputs.
ring:dev-frontend-visual
by LerianStudio
Gate 4 of frontend development cycle - ensures all components have snapshot tests covering all states, viewports, and edge cases.
ring:condition-based-waiting
by LerianStudio
Flaky test fix pattern - replaces arbitrary timeouts with condition polling that waits for actual state changes.
ring:testing-anti-patterns
by LerianStudio
Test quality guard - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies.
ring:dispatching-parallel-agents
by LerianStudio
Concurrent investigation pattern - dispatches multiple AI agents to investigate and fix independent problems simultaneously.
ring:testing-agents-with-subagents
by LerianStudio
Agent testing methodology - run agents with test inputs, observe outputs, iterate until outputs are accurate and well-structured.
ring:testing-skills-with-subagents
by LerianStudio
Skill testing methodology - run scenarios without skill (RED), observe failures, write skill (GREEN), close loopholes (REFACTOR).
ring:dev-unit-testing
by LerianStudio
Gate 3 of development cycle - ensures unit test coverage meets threshold (85%+) for all acceptance criteria using TDD methodology.
ring:dev-fuzz-testing
by LerianStudio
Gate 4 of development cycle - ensures fuzz tests exist with proper seed corpus to discover edge cases, crashes, and unexpected input handling.
ring:dev-cycle-frontend
by LerianStudio
Frontend development cycle orchestrator with 9 gates. Loads tasks from PM team output or backend handoff and executes through implementation → devops → accessibility → unit testing → visual testing → E2E testing → performance testing → review → validation.
ring:dev-cycle
by LerianStudio
Main orchestrator for the 10-gate development cycle system. Loads tasks/subtasks from PM team output and executes through implementation → devops → SRE → unit testing → fuzz testing → property testing → integration testing (write) → chaos testing (write) → review → validation gates (Gates 0-9), with state persistence and metrics collection. Gates 6-7 (integration/chaos) write and update test code per unit but only execute tests at end of cycle (deferred execution).
flutter
by alinaqi
Flutter development with Riverpod state management, Freezed, go_router, and mocktail testing
naming-6-gates
by guia-matthieu
Use when creating brand names, product names, or company names in 2026. Use when naming needs to work across languages, voice assistants, and AI recommendation engines. Use when previous name candidates failed trademark or had conflicts.
brand-strategy
by guia-matthieu
"Create distinctive brands that customers choose because they believe there's no substitute, using Marty Neumeier's Brand Gap and Zag frameworks Use when: Building a new brand from scratch (startup, product, service); Repositioning an existing brand that's become commoditized; Defining brand differentiation when competitors all look the same; Creating brand guidelines for consistent execution; Evaluating brand strength through structured testing"
ab-test-analysis
by nimrodfisher
Rigorous A/B test statistical analysis. Use when analyzing experiment results, calculating statistical significance, checking for sample ratio mismatch, or validating test design before launch.
swe
by knoopx
Applies software engineering best practices, design principles, and avoids common anti-patterns. Use when designing systems, reviewing code quality, refactoring legacy code, making architectural decisions, or improving maintainability.