Testing
Unit tests, integration tests, test automation
bf-lead-review
by khaki4
Discourse 패턴으로 다관점 리뷰를 수행한다. Tech Spec 리뷰와 에픽 통합 코드 리뷰를 모두 처리하며, 쟁점 해소 프로토콜에 따라 합의/미합의를 분리한다.
riley-prd-gauntlet
by riley-cole
End-to-end PRD workflow from product concept through finalized, cross-validated build spec. Twelve phases — intake, define, grill-me interview, stress test, product vision brief, strategic council, component map, user stories, PRD draft, adversarial review, system validation, finalize and distribute. Supports optional deep research (competitive landscape, internal ticket mining) during intake. Project-agnostic methodology with project-specific config files for precision execution. Use when starting a new PRD, running an adversarial review, validating cross-PRD consistency, researching a product landscape, stress-testing a concept, or running a strategic council review. Trigger on: "PRD gauntlet", "riley-prd-gauntlet", "new PRD", "adversarial review", "cross-PRD validation", "stress test", "strategic council", "research", or "finalize the PRD."
zoho-books
by xHUNx
Zoho Books integration skill (WIP). OAuth setup + API client scaffolding with full module coverage planned.
effect-vitest
by tstelzer
Testing Effect programs with vitest. Use when writing tests for effect-based code.
spec
by robdmc
"Universal artifact specification skill that interviews users to produce well-defined specification documents. Covers any artifact type — software, presentations, analyses, AI skills, threat models, curricula, etc. Invoke as '/spec filename' or '/spec filename hint'. Other skills can delegate specification work by passing a hint string after the filename. Use when the user wants to spec out, define, or plan any artifact before building it."
testing-guidelines
by dcramer
Guide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
spec-generator
by pm-minji
"츠루"로 호출. 새로운 기능의 기획 문서(requirements, design, tasks)를 생성합니다.
documentation
by hk-vk
Documentation documentation and resources. Use this skill when working with Documentation or when the user mentions documentation.
react-testing
by iamkhan21
Testing React components, hooks, and interactions with React Testing Library. Use for writing, debugging, or refactoring tests.
finishing-a-development-branch
by ederheisler
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
runhuman-testing
by volter-ai
Create and manage human-powered QA tests using Runhuman CLI. Use this skill when you need to test web applications with real human testers, get UX feedback, validate user flows, check mobile responsiveness, or find bugs that automated tests miss.
cosmos-planning
by getcosmos
Create structured, actionable implementation plans that serve as both human documentation and agent-executable specs. Use when creating new plans, converting ideas into implementation roadmaps, or when asked to plan a feature, refactor, or multi-phase project. Plans include detailed technical tasks with file paths, acceptance criteria, dependencies, and context blocks for autonomous agent execution.
agent-md-refactor
by aleister1102
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
flutter-scalable-scaffold
by Obalolu
Create production-ready Flutter mobile app projects with clean architecture, feature-based structure, state management (flutter_bloc/riverpod), routing, theming, networking, secure storage, and reusable components. Includes dependency injection, custom widgets, flavors (dev/prod), environment variables, and backend integration (custom/Firebase/Supabase). Use this skill when users want to scaffold a complete Flutter project with a scalable, production-ready structure.
nullables
by danielbush
"Guide for implementing James Shore's Nullables pattern and A-Frame architecture for testing without mocks. Use when implementing or refactoring code to follow patterns of: (1) Separating logic, infrastructure, and application layers, (2) Creating testable infrastructure with create/createNull factory methods, (3) Writing narrow, sociable, state-based tests without mocks, (4) Implementing value objects, (5) Building infrastructure wrappers that use embedded stubs, or (6) Designing dependency injection through static factory methods."
test-skill
by alaodmojtba
This is a test skill for supply chain testing
enterprise-software-development-framework
by AndrewChenDev
Enterprise software development framework with squad-based team structure, full SDLC, quality gates, GitHub workflow, and AI agent teams mode. Roles include Architect, PO, QA/SDET, Dev, Security, and Code Review. Use when designing systems, writing user stories, reviewing code, or running the full squad as parallel agents.
Playwright E2E Testing Framework
by XFaramirX
"The best error message is the one that never shows up." - Thomas Fuchs
spec-driven-dev
by lorenzogirardi
Spec-driven development framework for ecommerce features. Orchestrates from intent to implementation via structured specs and task breakdown. Triggers on "/spec.plan", "/spec.refine", "/spec.clarify", "/spec.tasks", "/spec.run", "I want to build", "I want to add", "create spec", "feature spec", "new feature", "implement feature".
pm2-test-services
by jovermier
Activate when managing PM2 services for Playwright test reports, trace viewers, or other test artifacts. Includes starting/stopping services, generating dynamic workspace URLs (Coder/VS Code), and viewing service logs.
vitest
by zhongjis
Writes and runs tests, configures test environments, mocks dependencies, and generates coverage reports. Use when setting up vitest.config.ts, writing test suites, mocking modules, or measuring code coverage.
self-improving-agent
by kimasplund
Enables continuous self-improvement through learning from failures, user corrections, and capability gaps. Integrates with QAVR for learned memory ranking.
review-code
by fancy-bread
Review Code
zigbee2mqtt
by szkocot
Expert guidance for Zigbee2MQTT development and configuration. Use when working with zigbee2mqtt codebase, configuration files (configuration.yaml, devices.yaml, groups.yaml), device converters, MQTT topic/payload design, or troubleshooting Zigbee device integration. Triggers on tasks involving Zigbee-to-MQTT bridge setup, device pairing workflows, converter development, and Home Assistant integration.