测试
单元测试、集成测试与测试自动化
testing-debugging
baz-scm
Ensuring software correctness and reliability by writing automated tests, using quality assurance tools, and systematically debugging issues.
test
whawkinsiv
"Use this skill when the user needs to test features before deployment, create test scenarios, find edge cases, or verify bug fixes. Covers manual testing workflows, cross-browser testing, edge case identification, and testing checklists for non-technical founders."
validate
whawkinsiv
"Use this skill when the user needs to validate a business idea, test demand before building, run a smoke test, create an MVP experiment, or decide whether an idea is worth pursuing. Covers demand validation, smoke tests, fake-door tests, landing page experiments, and go/no-go decision frameworks for bootstrapped founders."
testing
Tristan578
Write Vitest + RTL + Playwright tests for SpawnForge. Use when adding test coverage, fixing flaky tests, hitting coverage gaps, or running test suites (lint/tsc/vitest/e2e/mcp). Includes Vitest 4.x API reference.
architect-flow
Tristan578
Spec-first architecture workflow for SpawnForge features. Use when planning new features, designing multi-system changes, or asked "how should we build X?" — produces a spec in specs/ before any code is written.
cycle
Tristan578
Run the full Plan → Build → Verify loop for a SpawnForge feature. Orchestrates planner → builder → validator in sequence. Use when implementing a complete feature end-to-end from spec to passing tests.
viewport
Tristan578
Visually verify the SpawnForge editor renders correctly — Playwright canvas readback, scene graph inspection, WebGPU/WebGL2 output validation. Use when visual rendering may be broken, after engine changes, or for visual regression checks.
planner
Tristan578
Create a detailed spec in specs/ for a SpawnForge feature. Use when starting any new feature, asked to plan a complex change, or when "spec", "design", or "architect" appears in a request. Produces implementation-ready specs with acceptance criteria.
component-checklist
Tristan578
"Use when adding a new ECS component, MCP command, or engine capability. Checklist of all files that must be updated across Rust engine, web layer, and integration points."
tdd
Tristan578
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
vitest
Tristan578
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
troubleshoot
Tristan578
Diagnose SpawnForge failures — WASM build errors, CI pipeline breakage, dev server crashes, E2E test failures, Bevy ECS panics, external service outages. Use when something is broken and the cause is unclear.
generate-route
Tristan578
"Scaffold a new AI generation route using createGenerationHandler. Creates route file, adds pricing entry, adds integration test. Use when adding a new /api/generate/* endpoint."
builder
Tristan578
Implement a spec from specs/ into working code. Dispatches to rust-engine, frontend, mcp-commands, and testing skills based on the layers touched. Use when implementing a feature, fixing bugs, or asked to "build" or "implement" something.
engflow-artifacts
cockroachdb
Use when downloading test logs, artifacts, or outputs.zip from EngFlow build invocations. Use when investigating CockroachDB CI test failures hosted on mesolite.cluster.engflow.com.
spring-boot-event-driven-patterns
giuseppe-trisciuoglio
Provides Event-Driven Architecture (EDA) patterns in Spring Boot using ApplicationEvent, @EventListener, and Kafka. Use when building loosely-coupled microservices with domain events, transactional event listeners, and distributed messaging patterns.
aws-sdk-java-v2-rds
giuseppe-trisciuoglio
Provides AWS RDS (Relational Database Service) management patterns using AWS SDK for Java 2.x. Use when creating, modifying, monitoring, or managing Amazon RDS database instances, snapshots, parameter groups, and configurations.
technology-stack
ag-grid
'Technology stack and architectural constraints. Use when choosing technologies, adding dependencies, or understanding zero-dependency requirements.'
estimate-jira
ag-grid
Estimate complexity, effort, and risks for JIRA tickets, features, or projects. Generates structured reports with time estimates, dependencies, risk analysis, and known unknowns. Use when user asks to "estimate", "size", or "analyze complexity" of work items.
fuzzing
mohitmishra786
Fuzzing skill for automated input-driven bug finding in C/C++. Use when setting up libFuzzer or AFL++ fuzz targets, defining fuzz entry points around parsing or I/O boundaries, integrating fuzzing into CI, managing corpora, or combining fuzzing with sanitizers. Activates on queries about libFuzzer, AFL, afl-fuzz, fuzz targets, corpus management, coverage-guided fuzzing, or OSS-Fuzz integration.
justfile
oldwinter
This skill should be used when users want to create, convert, or manage Justfiles for command automation. It handles converting Makefile, npm scripts, or shell commands to Justfile format, generating project-specific templates, and providing Justfile syntax guidance. Triggers on requests mentioning justfile, just command, command runner, Makefile conversion, or task automation.
ai-evals
oldwinter
"Create an AI Evals Pack (eval PRD, test set, rubric, judge plan, results + iteration loop). Use for LLM evaluation, benchmarks, rubrics, error analysis/open coding, and ship/no-ship quality gates for AI features."
running-unit-tests
dotnet
Guide for running MSBuild unit tests efficiently. Use when running, scoping, filtering, or speeding up unit tests in this repository, or when finalizing a change with a heavier validation pass. Covers xUnit v3 + Microsoft.Testing.Platform (MTP) specifics and which dotnet test flags do and don't apply.
writing-specs-and-designs
oldwinter
Create clear product specs and design docs with implementation-ready acceptance criteria.