Testing
Unit tests, integration tests, test automation
Core Patterns
by takeokunn
Base templates for error escalation, decision criteria, and enforcement. Referenced by agents and commands to avoid duplication.
Execution Workflow
by takeokunn
This skill should be used when the user asks to "execute task", "implement feature", "delegate work", "run workflow", "review code", "code quality check", or needs task orchestration and code review guidance. Provides execution, delegation, and code review patterns.
Testing Patterns
by takeokunn
This skill should be used when the user asks to "write tests", "test strategy", "coverage", "unit test", "integration test", or needs testing guidance. Provides testing methodology and patterns.
PHP Ecosystem
by takeokunn
This skill should be used when the user asks to "write php", "php 8", "composer", "phpunit", "pest", "phpstan", "psalm", "psr", or works with modern PHP language patterns and configuration. Provides comprehensive modern PHP ecosystem patterns and best practices.
Haskell Ecosystem
by takeokunn
This skill should be used when working with Haskell projects, "cabal.project", "stack.yaml", "ghc", "cabal build/test/run", "stack build/test/run", or Haskell language patterns. Provides comprehensive Haskell ecosystem patterns and best practices.
team-lifecycle
by catlog22
Unified team skill for full lifecycle - spec/impl/test. All roles invoke this skill with --role arg for role-specific execution.
gepetto
by softaworks
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
qa-test-planner
by softaworks
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
quantitative-analysis
by poemswe
You must use this when selecting statistical tests, interpreting effect sizes, or conducting power analysis.
ideation
by nicknisi
Transform raw brain dumps (dictated freestyle) into structured implementation artifacts. Use when user has messy ideas, scattered thoughts, or dictated stream-of-consciousness, or when they want to plan a feature, spec something out, or turn rough ideas into actionable specs. Produces contracts and implementation specs written to ./docs/ideation/{project-name}/.
payment-integration
by unclecatvn
Integrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
interview-master
by Zal4DW
This skill should be used when the user asks to "prepare for an interview", "do a mock interview", "what do interviewers look for", "I got rejected", or "help me after an interview". Provides interview preparation with STAR frameworks, interviewer perspective reports, realistic mock interview simulation, and post-interview coaching for rejection recovery.
owasp-ai-testing
by mastepanoski
AI trustworthiness testing using OWASP AI Testing Guide v1. Execute 44 test cases across 4 layers (Application, Model, Infrastructure, Data) with practical payloads and remediation.
verification-before-completion
by rileyhilliard
Run verification commands before claiming work is complete or fixed. Use before asserting any task is done, bug is fixed, tests pass, or feature works.
condition-based-waiting
by rileyhilliard
Fixes flaky tests by replacing arbitrary timeouts with condition polling. Use when tests fail intermittently, have setTimeout delays, or involve async operations that need proper wait conditions.
refactoring-code
by rileyhilliard
Improves code structure while preserving behavior through test verification. Use when cleaning up code, reducing duplication, simplifying complexity, or reorganizing modules.
fixing-flaky-tests
by rileyhilliard
Diagnose and fix tests that pass in isolation but fail when run concurrently. Covers shared state isolation and resource conflicts. References condition-based-waiting for timing issues.
resolve-checks
by flowglad
Resolve all failing CI checks and address PR review feedback on the current branch's PR. Runs tests locally, fixes failures, incorporates valid review comments, and resolves addressed feedback. Use when CI is red, after receiving PR feedback, or before merging.
elixir-code-review
by existential-birds
Reviews Elixir code for idiomatic patterns, OTP basics, and documentation. Use when reviewing .ex/.exs files, checking pattern matching, GenServer usage, or module documentation.
hig-technologies
by raintree-technology
Apple HIG guidance for Apple technology integrations: Siri, Apple Pay, HealthKit, HomeKit, ARKit, machine learning, generative AI, iCloud, Sign in with Apple, SharePlay, CarPlay, Game Center, in-app purchase, NFC, Wallet, VoiceOver, Maps, Mac Catalyst, and more. Use when asked about: "Siri integration", "Apple Pay", "HealthKit", "HomeKit", "ARKit", "augmented reality", "machine learning", "generative AI", "iCloud sync", "Sign in with Apple", "SharePlay", "CarPlay", "in-app purchase", "NFC", "VoiceOver", "Maps", "Mac Catalyst". Also use when the user says "how do I integrate Siri," "what are the Apple Pay guidelines," "how should my AR experience work," "how do I use Sign in with Apple," or asks about any Apple framework or service integration. Cross-references: hig-inputs for input methods, hig-components-system for widgets.
Experiment
by simota
A/Bãã¹ãè¨è¨ã仮説ããã¥ã¡ã³ãä½æããµã³ãã«ãµã¤ãºè¨ç®ããã£ã¼ãã£ã¼ãã©ã°å®è£ ãçµ±è¨çæææ§å¤å®ãå®é¨ã¬ãã¼ãçæã仮説æ¤è¨¼ãå¿ è¦ãªæã«ä½¿ç¨ã
grow-sustainably
by slavingia
Evaluate business decisions through the lens of sustainable, profitable growth. Use when someone is making decisions about spending, hiring, fundraising, or scaling their business.
fix
by tkersey
Review+fix protocol with safety guardrails (unsoundness, invariants, footguns, incidental complexity). Use when prompts say "$fix this PR", "fix current branch", "fix this diff", "repair CI red", or "apply a minimal patch", and when crash/corruption/invariant-break issues need correction with a validation signal.
zig
by tkersey
"Use when requests involve Zig code or toolchain work: editing .zig, changing build.zig/build.zig.zon, defining or fixing zig build steps (for example zig build ci), handling .zig-cache/CI wiring, running or fixing zig build test run fmt fetch, debugging compile/runtime/test failures, comptime/reflection/codegen, allocator ownership, SIMD (std.simd/@Vector), threads (std.Thread/Thread.Pool), cross-compilation, zero-copy parsing, C interop (@cImport), or Zig 0.15.2 pin/migration issues. Enforce correctness-first validation with tests, std.testing.fuzz, and allocation-failure checks."