Testing

axe-core

by claude-dev-suite

axe-core - accessibility testing engine for automated WCAG compliance checks. USE WHEN: user mentions "axe", "automated accessibility testing", "a11y tests", asks about "integrating accessibility checks", "CI/CD accessibility", "Playwright accessibility", "Jest accessibility", "Vitest axe" DO NOT USE FOR: manual accessibility audits - use wcag skill instead

ralph-wiggum

by fstandhartinger

Autonomous AI coding with spec-driven development. Implements Geoffrey Huntley's iterative bash loop methodology where agents work through specs one at a time, outputting a completion signal only when acceptance criteria are 100% met.

hai-idea

by hylarucoder

Evaluates whether an idea deserves attention and returns a clear verdict — Do / Validate first / Reframe / Defer / Kill — with a dimension-by-dimension scorecard (pain, audience, leverage, timing, cost, risk, proof path), the strongest objection, a stronger reframe, and the cheapest validation test. Use whenever the user wonders if an idea, feature, product, or project is good, worth doing, worth their time, too vague, risky, low-value, a distraction, or a fake need; wants two or more ideas compared and ranked; or asks whether to build, ship, kill, postpone, reframe, or turn it into a goal or PRD — even when they only say it casually and never ask for an evaluation. Trigger on 想法是不是好主意, 我有个想法, 帮我看看这个想法, 这个点子怎么样, 值不值得做, 值得投入吗, 要不要做, 该不该做, 这个需求要不要接, 是否应该验证, 该不该砍掉, 是不是伪需求, 是不是在瞎折腾, 哪个更值得做, and casual English like "should I build this", "is this worth my time", "worth doing? or kill it".

table-driven-test

by cockroachdb

Guidelines for creating clean, well-structured table-driven tests in Go following CockroachDB conventions.

python-peewee

by narumiruna

Patterns for using Peewee ORM with DatabaseProxy and scoped connections/transactions. Use when setting up DatabaseProxy, managing connection_context/atomic blocks, or writing tests with SQLite.

finishing-a-development-branch

by oyi77

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

brainstorming

by oyi77

Effective brainstorming skill for features and projects. Clarify intent, explore options, and guide design decisions to align with user goals.

subagent-driven-development

by oyi77

Use when executing implementation plans with independent tasks in the current session

code-reviewer

by oyi77

Professional code review skill. Review local changes or PRs for correctness, maintainability, and best practices. Based on playbooks.com community skill.

swift-testing-expert

by AvdLee

'Expert guidance for Swift Testing: test structure, #expect/#require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and XCTest migration. Use when writing new Swift tests, modernizing XCTest suites, debugging flaky tests, or improving test quality and maintainability in Apple-platform or Swift server projects.'

testing

by 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

by 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

by 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

by 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

by 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.

tdd

by 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

by 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

by 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.

integration-test

by cockroachdb

Guidelines for writing integration tests with CockroachDB test servers, including when to use them and how to use sqlutils.

Practice Question Generator

by https-deeplearning-ai

ai-assisted-development

by baz-scm

Leveraging AI coding assistants and tools to boost development productivity, while maintaining oversight to ensure quality results.

integrations

by whawkinsiv

"Use this skill when the user needs to connect third-party services, set up APIs, add OAuth, configure webhooks, or integrate tools like Slack, Zapier, email providers, or payment processors. Covers API integration patterns, auth flows, webhook handling, and building integrations that non-technical founders can maintain."

build

by whawkinsiv

"Use this skill when the user needs to build features with AI coding tools, choose between Claude Code, Lovable, Replit, or Cursor, write effective prompts for code generation, or iterate on AI-generated code. Covers tool selection, prompting strategies, and development workflows for non-technical founders."

testing-debugging

by baz-scm

Ensuring software correctness and reliability by writing automated tests, using quality assurance tools, and systematically debugging issues.