Path-scoped. Loaded only when relevant.
Open a test file → the right rules attach. Zero token cost the rest of the time.
What this pillar does for you.
Failing test -> minimum code -> refactor. Tight RED-GREEN-REFACTOR loop, baked in.
Visual diff + behavioral checks run on every PR. Regressions are caught before review.
Headless run of critical flows on the preview env. No flaky tests in main.
4 rules.
Each rule is a markdown file the AI loads when it edits a matching path. Click any to see related skills and where it's referenced.
Three layers (unit/integration/e2e), jest + msw + Playwright, test behavior not implementation, no library internals, co-located specs.
RTL with role-first queries, userEvent over fireEvent, renderWithProviders helper, real Redux store, never assert on store state - assert on what the user sees.
Jest + Testing Library for components, mock Capacitor plugins at service boundary, Playwright for web routes, native smoke check on requested platform before release.
jest + jest-expo + @testing-library/react-native, role/label-first queries, renderWithProviders helper, msw or typed service fakes, Maestro .yml for device E2E flows.
21 skills.
Skills are intent-triggered workflows. The AI router loads them by description; bodies on demand.
Sandbox-mode API testing without DB dependencies, automated bug-check workflows, and patterns that catch AI blind spots where the same model writes and reviews code.
Visual testing, Lighthouse and Core Web Vitals checks, accessibility audits, and UI interaction verification via browser automation after deploy or build.
Trace UI touchpoints through handlers, state stores, effects, async calls, and final visible state when controls look wired but do the wrong thing.
GoogleTest/CTest configuration, diagnosing failing or flaky C++ tests, adding coverage and sanitizers.
C#/.NET testing with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.
TDD for Django with pytest-django, factory_boy, mocking, coverage, and DRF API testing.
Verification loop for Django: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
Playwright E2E patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky-test strategies.
Library-agnostic Flutter/Dart review checklist: widget practices, BLoC/Riverpod/Provider/GetX/MobX/Signals, Dart idioms, performance, accessibility, security, clean architecture.
Go testing patterns: table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
Kotlin testing with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD with idiomatic Kotlin.
TDD for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.
Verification loop for Laravel: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.
Perl testing patterns: Test2::V0, Test::More, prove runner, mocking, Devel::Cover coverage, and TDD methodology.
Python testing with pytest, TDD, fixtures, mocking, parametrization, and coverage requirements.
Rust testing patterns: unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD.
TDD for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo - for new features, fixes, and refactors.
Verification loop for Spring Boot: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
Protocol-based dependency injection for testable Swift code - mock file system, network, and external APIs using focused protocols and Swift Testing.
Red-green-refactor for new features, bug fixes, and refactors. Enforces 80%+ coverage across unit, integration, and E2E - only after onboarding is resolved.
Comprehensive verification system: local-evidence production audits and Production-Readiness Score audits for SPA + Supabase and Ionic releases.
One plugin, eight pillars.
Every rule and skill is part of a system. Jump across pillars to see how they reinforce each other.
Use the AI you already pay for.
Add superpowers.
One plugin. Senior-engineer rules, security, a backend, and one-command deploys — inside the editor you already use.