Testing
Unit tests, integration tests, test automation
dalle
by G1Joshi
DALL-E OpenAI image generation. Use for image creation.
Knack Data Cleaner
by willsigmon
Ensures accuracy for HTI compliance and performance dashboards through data validation, deduplication, normalization, and integrity checks. Critica...
ccpm-debugging
by duongdev
Systematic debugging with defense-in-depth approach (symptoms → immediate cause → root cause → systemic issues → prevention). Auto-activates when user mentions "error", "failing", "broken", "debug", "bug", "issue" or when /ccpm:verify runs. Uses Observe → Hypothesize → Test → Confirm → Fix → Verify → Document workflow. Updates Linear with findings and automatically logs blockers that require external fixes. Traces root causes instead of patching symptoms. Integrates with ccpm-code-review to verify fixes pass all gates before marking complete. Suggests binary search for intermittent issues and five-whys analysis for complex problems.
RSpec Testing Patterns
by Kaakati
"Complete guide to testing Ruby on Rails applications with RSpec. Use this skill when writing unit tests, integration tests, system tests, or when setting up test infrastructure including factories, shared examples, and mocking strategies."
planning-strategy-guide
by duongdev
Guides intelligent planning strategies with automatic phase detection and complexity assessment. Auto-activates when users mention epic breakdown, feature decomposition, scope estimation, dependency analysis, risk identification, or ask "how do I plan this complex task", "break down this feature", "what's the scope", "estimate effort", "identify dependencies", or "planning strategy". Provides interactive planning mode with 6 planning phases (complexity assessment, scope definition, dependency analysis, risk identification, task breakdown, effort estimation). Works with sequential-thinking for complex decomposition, docs-seeker for research, pm-workflow-guide for command suggestions, and linear-subagent-guide for Linear integration.
think
by johnlindquist
Deep multi-framework reasoning using Gemini. Use for complex problem analysis, challenging ideas, and evaluating multiple options with structured thinking.
testgen
by johnlindquist
Generate tests using AI and run test suites. Use for generating unit tests, running coverage reports, and mutation testing.
refactor
by johnlindquist
Code refactoring with AI assistance. Use for modernizing code, converting JavaScript to TypeScript, class to hooks conversions, and systematic renaming.
ts-testing
by johnlindquist
Design, implement, and maintain high‑value TypeScript test suites using popular JS/TS testing libraries. Use this skill whenever the user is adding tests, debugging failing tests, or refactoring code that should be covered by tests.
spec-driven-development
by 89jobrien
Spec-Driven Development (SDD) methodology based on GitHub's SpecKit.
setup-base
by kvnwolf
Bootstrap a new TypeScript project with Biome, t3-env, Knip, tsgo, and Vitest. Consult this skill whenever starting a new project, initializing a TypeScript codebase, setting up linting and formatting, or scaffolding a project from scratch.
setup-tanstack-start
by kvnwolf
Bootstrap a new web project with TanStack Start, React, Tailwind CSS v4, and shadcn/ui on top of the base tooling stack. Consult this skill whenever creating a web app, setting up a frontend project, starting a React application, or initializing anything involving TanStack Start, TanStack Router, TanStack Query, Tailwind, shadcn, or Vite.
developer-experience
by 89jobrien
Developer Experience specialist for tooling, setup, and workflow optimization.
create-component-test
by kvnwolf
Write component tests using Vitest Browser Mode with Playwright for real-browser testing. Consult this skill whenever testing React components, writing browser-based tests, verifying UI behavior, testing forms or interactive elements, or deciding whether a component needs a test.
debugging
by luan
"Systematic root cause investigation before proposing fixes. Triggers: bugs, test failures, unexpected behavior, 'why is this failing', 'not working', 'broken'. Do NOT use when: the bug is already identified and the fix is obvious — use /triage instead."
devops-runbooks
by 89jobrien
Operational runbook and procedure documentation specialist. Use when
idea-explorer
by ky1ejs
Collaborative exploration to refine ideas into clear requirements before spec writing. Explores user intent, requirements and design through iterative dialogue.
create-test
by kvnwolf
Write automated tests following TDD principles: red-green-refactor, vertical slices, behavior over implementation. Consult this skill whenever creating tests, adding test coverage, writing test-first code, fixing a bug with a regression test, or any task that involves verifying behavior through automated tests.
spec-writer
by ky1ejs
Transform ideas into detailed implementation specifications. Creates specs with requirements, design, and implementation steps.
ux-specification
by Abhsin
Translate PRDs into detailed UX specifications including user flows, screen descriptions, components, and interaction patterns. Use when a user has a PRD and needs to define the concrete UI/UX before generating development prompts. Bridges product requirements to implementation details.
obsidian-canvas-architect
by richfrem
"Programmatically create and manipulate Obsidian Canvas (.canvas) files using JSON Canvas Spec 1.0. Enables agents to generate visual flowcharts, architecture diagrams, and planning boards. Use when creating or editing visual canvas files."
capa-officer
by QuestNova502
Senior CAPA Officer specialist for managing Corrective and Preventive Actions within Quality Management Systems. Provides CAPA process management, root cause analysis, effectiveness verification, and continuous improvement coordination. Use for CAPA investigations, corrective action planning, preventive action implementation, and CAPA system optimization.
mcp-integration
by 89jobrien
Model Context Protocol (MCP) integration specialist. Use when creating
split-commit
by luan
"Collapse a branch into working tree and repackage as clean, tested, vertical commits. Triggers: 'split commits', 'repackage commits', 'reorganize commits', 'clean up branch history', 'consolidate commits into clean ones'. Do NOT use when: branch already has a single clean commit or only needs amending — use /commit instead."