Evaluate Christian AI applications against the 5 unofficial rules using a 20-question testing framework with scoring rubrics.
End-to-end workflow for feature requests, enhancements, refactors, and tasks. Covers planning, TDD implementation, verification, integration testing, and PR creation.
Generic autonomous QA suite for any project — reads a test plan (markdown file or inline spec), runs all tests using Chrome CDP + iterate cycles, fixes bugs found, and produces a…
Help developers complete projects from 70-100% to production-ready status. Excels at gap analysis, task decomposition, database design, API specifications, and testing strategies.
Design, implement, review, debug, and operate risk-based testing for full-stack software in any language or framework.
Complete testing pipeline — full test suite, test everything, automated and manual tests.
Complete testing workflow from site discovery to test automation with Qase integration. Use when user wants end-to-end testing setup for a website.
Write functional tests that test public interfaces only (HTTP APIs via requests, libraries via exported functions, CLIs via command execution).
Efficient fuse-browser usage: web fetch, crawl, SERP, browser session, screenshot, webapp testing, console errors.
Compare testing strategies and choose the best coverage plan; use when deciding how to test a feature or fix.
Use when designing fuzz, property, randomized, or corpus-based tests and replaying failures. Triggers:
Fuzz a parser or protocol handler with a coverage-guided fuzzer, seed the corpus with real inputs, and triage crashes to unique root causes.
Fuzzing strategist persona specializing in dynamic testing guidance, fuzzing strategy development, and crash analysis
Generate Go fuzz tests (Go 1.18+ testing.F) for specified code when users ask for fuzzing/模糊测试/fuzz test generation, parser robustness, round-trip, or differential fuzzing.
Primes every session with the guitarist's perspective, GA architecture, and how to use the MCP tools during feature development.
Interact with the Galtea platform -- the AI product testing and evaluation platform for AI/LLM products -- and access its documentation.
The foundational theory of interactive experience design - loops, motivation, feel, and the art of meaningful playUse when "game design, core loop, game feel, player motivation,…
Plan, run, analyze, and review game playtests, usability sessions, player feedback, telemetry, onboarding tests, difficulty tests, controls tests, fun/enjoyability research,…
Route early browser-game work. Use when the user needs stack selection and workflow planning across design, implementation, assets, and playtesting before moving to a spe — from…
Capture game feature ideas during playtesting or brainstorming. Combines quick backlog entry with optional light thinking rounds.
Audit game user experience across HUD clarity, menu navigation, tutorial effectiveness, control responsiveness, camera systems, feedback loops, loading screens, and settings…
Human playtest verification with structured feedback and fix loop. Use with /game-verify after /game-build for manual testing of game features.
Professional gameplay tester and QA analyst persona for playtesting, bug finding, UX assessment, balance evaluation, and player experience feedback.
Configure Gamma CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Gamma tests into your build…
Generate your first Gamma presentation via the API. Use when learning the generate-poll-retrieve workflow, testing API connectivity, or creating a minimal example.
Create a minimal working Gamma example. Use when starting a new Gamma integration, testing your setup, or learning basic Gamma API patterns.
Set up local development workflow for Gamma API integration. Use when building automation scripts, testing API calls locally, or configuring a dev environment with mock responses.
Gate 4b validation: Integration test creation and no-hardcoded-values enforcement
Compare coverage reports against a git diff so an agent can flag newly changed lines that still lack tests before merge.
Expert skill for Gatling simulation development, load test execution, and performance analysis. Write Gatling simulations in Scala DSL, configure injection profiles and feeders,…
Gatling Scenario Creator - Auto-activating skill for Performance Testing. Triggers on: gatling scenario creator, gatling scenario creator Part of the Performance Testing skill…
Gc Log Analyzer - Auto-activating skill for Performance Testing. Triggers on: gc log analyzer, gc log analyzer Part of the Performance Testing skill category.
GDD review and research during playtest phase. Use during playtest phase BEFORE sending playtest_session_report to PM, after completing gameplay testing, after reviewing…
Playwright-based game playtesting and design validation. Use when validating implementation against GDD, testing gameplay mechanics, capturing screenshot evidence, performing game…
Sets up, tests, and tears down a GCS Data Store linked to a Gemini Enterprise engine, with support for Workforce Identity Federation (WIF) access.
Comprehensive guide for building production-quality Ruby gems. Use when creating new gems, structuring gem architecture, implementing configuration patterns, setting up testing,…
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest,…
Smoke test for the sagaflow generic interpreter. Writes a greeting to report.md and ends turn. Use only for testing the interpreter round-trip.
Analyze repo, detect stack, trace changes to user-facing entry points, generate E2E YAML test plan
General workflow instructions for Claude Code agents working in this repository. Covers environment setup, coding workflow, documentation, testing, and error-handling practices.
Generate comprehensive, systematic test suites for any system component using a structured test design methodology.
Use when the user wants to convert acceptance criteria into Cucumber/Gherkin feature files, write a .feature file, or produce BDD scenarios for a story.
Homeostatic actuator auto-generating missing tests for requirements with low coverage. Creates unit tests, edge cases, and error cases for REQ-* without sufficient test coverage.
Generate the conclaude-schema.json configuration schema file using src/bin/generate-schema.rs. USE WHEN the configuration format changes, new config fields are added, or the…
Create diverse synthetic test inputs for LLM pipeline evaluation using dimension-based tuple generation.
Generate comprehensive test cases from specification documents using AI in the QuickRail project. Use when users want to create test cases from requirements, spec documents, or…
Create comprehensive unit test plans for Swift code with TDD methodology. Use this when planning tests for new features, ensuring test coverage, creating test checklists, or…
TDD with RGRC cycle and Baby Steps methodology. Triggers: TDD, test-driven, RGRC, Baby Steps, テスト駆動, Red-Green-Refactor.
Generate realistic test data including edge cases and boundary conditions. Use when creating realistic fixtures or edge case test data.
Generate mocks, stubs, spies, and fakes for dependency isolation. Use when creating mocks, stubs, or test isolation fixtures.
Generate comprehensive test reports with metrics, coverage, and visualizations. Use when performing specialized testing.
Test automatically generate comprehensive unit tests from source code covering happy paths, edge cases, and error conditions.
Graph-informed mutation testing triage. Parses codebases with Trailmark, runs mutation testing and necessist, then uses survived mutants, unnecessary test statements, and call…
Testing external processes with gexec — compile binaries with Build/BuildWithEnvironment/BuildIn and CleanupBuildArtifacts, start them with Start returning a *Session, await exit…
Gherkin acceptance criteria authoring. Use when writing Given/When/Then scenarios, feature files, or BDD-style specifications.
Use git worktrees for parallel Claude Code workflows. Run multiple Claude instances on different features simultaneously without merge conflicts.
Use when working on multiple branches simultaneously, context switching without stashing, reviewing PRs while developing, testing in isolation, or comparing implementations across…
Use when when you need to verify that a software package (such as MassQL) passes its periodic integration test suite as indicated by CI workflow badges in the project…
Diagnose, fix, and optimize GitHub Actions workflows for Rust projects. Use when setting up CI/CD, troubleshooting workflow failures, optimizing build times with caching, or…
Use when writing or reviewing Gleam code on the Erlang target — especially Wisp + Mist HTTP services, OTP-based processes (gen_server / supervisor analogues), justfile workflows,…