Testing
Unit tests, integration tests, test automation
ghost
by tkersey
Create a language-agnostic ghost package (spec + portable tests) from an existing repo by extracting SPEC.md, exhaustive tests.yaml (operations and/or scenarios), INSTALL.md, README.md, VERIFY.md, and upstream LICENSE files with provenance and regeneration instructions. Use when prompts say "$ghost", "ghostify this repo", "spec-ify/spec-package this library", "ghost library", or ask to extract portable spec/tests for libraries or tool-using agent loops (scenario testing); do not use for implementation work or editing skills.
app-store-optimization
by alirezarezvani
Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
confidence-scoring
by laurigates
"Assess quality of PRPs and work-orders using systematic confidence scoring. Use when evaluating readiness for execution or subagent delegation."
systematic-debugging
by ed3dai
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
writing-skills
by ed3dai
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
writing-implementation-plans
by ed3dai
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Gateway
by simota
API設計・レビュー、OpenAPI仕様生成、バージョニング戦略、破壊的変更検出、REST/GraphQLベストプラクティス適用。API開発の品質と一貫性を確保。API設計、OpenAPI仕様が必要な時に使用。
Anvil
by simota
Terminal UIæ§ç¯ãCLIéçºæ¯æ´ãéçºãã¼ã«çµ±åï¼Linter/ãã¹ãã©ã³ãã¼/ãã«ããã¼ã«ï¼ãã³ãã³ãã©ã¤ã³ä½é¨ã®è¨è¨ã»å®è£ ãå¿ è¦ãªæã«ä½¿ç¨ãè¨èªéä¾åã§Node.js/Python/Go/Rustããµãã¼ãã
Probe
by simota
OWASP ZAP/Burp Suiteé£æºããããã¬ã¼ã·ã§ã³ãã¹ãè¨ç»ãDASTå®è¡ãèå¼±æ§ã¹ãã£ã³ãåçã»ãã¥ãªãã£ãã¹ããä¾µå ¥ãã¹ããå®è¡æèå¼±æ§æ¤è¨¼ãå¿ è¦ãªæã«ä½¿ç¨ãSentinelã®éçåæãè£å®ã
Guardian
by simota
Git/PRの番人。変更の本質を見極め、適切な粒度・命名・戦略を提案する。PR準備、コミット戦略が必要な時に使用。
founder-playbook
by tenequm
Decision validation and thinking frameworks for startup founders. Use when you need to pressure-test a decision, validate your next steps, think through strategic options, or sanity-check your approach. Triggers on phrases like "should I", "help me think through", "is this the right move", "validate my thinking", "what am I missing". Covers fundraising, customer development, runway management, prioritization, and crypto/web3 founder challenges.
Condition-Based Waiting
by bobmatnyc
Replace arbitrary timeouts with condition polling for reliable async tests
testing-essentials
by j-morgan6
MANDATORY for ALL test files. Invoke before writing any _test.exs file.
Frontend Design Skill
by gotar
Web Design Guidelines - MDN reference
atdd
by swingerman
This skill should be used when the user asks to "build a feature", "implement a feature", "add functionality", "start development", "write acceptance tests", "write specs", "use ATDD", "use TDD with acceptance tests", or begins any feature implementation work. Also triggered by the /atdd command. Enforces the Acceptance Test Driven Development workflow: write Given/When/Then specs before code, generate a project-specific test pipeline, and maintain two test streams.
cairo-testing
by keep-starknet-strange
Use when writing tests for Cairo smart contracts — snforge test structure, contract deployment in tests, cheatcodes, event testing, fuzzing, fork testing.
nav-loop
by alekspetrov
Run tasks until complete with structured completion signals. Auto-invoke when user says "run until done", "keep going until complete", "iterate until finished", "loop mode", "autonomous mode".
backend-test
by alekspetrov
Generate backend tests (unit, integration, mocks). Auto-invoke when user says "write test for", "add test", "test this", or "create test".
frontend-test
by alekspetrov
Generate frontend component tests (unit, snapshot, e2e). Auto-invoke when user says "test this component", "write component test", or "add component test".
crossplane
by cosmix
Cloud-native infrastructure management with Crossplane using Kubernetes APIs. Build internal platform APIs for self-service infrastructure provisioning. Use when implementing infrastructure as code, platform engineering, composite resources, XRDs, compositions, claims, provider configuration, or multi-cloud provisioning. Triggers: crossplane, XRD, composition, claim, provider, managed resource, composite resource, infrastructure API, platform engineering, platform API, infrastructure abstraction, self-service infrastructure, kubernetes infrastructure, cloud control plane.
post-dev-test
by sd0xdev
"Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report."
debug
by mcouthon
"Systematic debugging with hypothesis-driven investigation. Use when something is broken, tests are failing, unexpected behavior occurs, or errors need investigation. Triggers on: 'this is broken', 'debug', 'why is this failing', 'unexpected error', 'not working', 'bug', 'fix this issue', 'investigate', 'tests failing', 'trace the error', 'use debug mode'. Full access mode - can run commands, add logging, and fix issues."
makefile
by mcouthon
"Use when creating Makefiles for process lifecycle management with PID tracking, logging, and status monitoring. Triggers on: 'use makefile mode', 'makefile', 'create makefile', 'process management', 'background jobs', 'start/stop services'. Full access mode - can create/modify Makefiles."
testing
by mcouthon
"Behavioral testing strategy — deciding what to test and how. Use when writing tests, reviewing test quality, or fixing tests that test mocks instead of behavior. Triggers on: 'use testing mode', 'write tests', 'test strategy', 'tests are brittle', 'tests test mocks', 'improve test quality', 'what should I test'. Full access mode - can write and run tests."