Testing
Unit tests, integration tests, test automation
loom-builder-complexity
by rjwalters
"This document covers complexity assessment, issue decomposition, and scope management for the Builder role. For the core builder workflow, see builder.md."
microdose
by edmundmiller
A subtle creativity mode for escaping obvious solutions without losing coherence. Use when the work feels technically correct but predictable, flat, or overly constrained.
loom-cargo-target-isolation
by rjwalters
"Load when: you are about to run (or just ran) a local cargo build/cargo test/cargo run whose result will inform a verdict — a Judge approval or rejection, a Doctor \"the fix works\", or a Builder \"tests pass\" before opening a PR."
brand-archetype-selection
by mike-coulbourn
Provides Jungian brand archetype frameworks, the 12 archetypes with profiles, the 70/30 primary/secondary rule, archetype combinations, and selection templates. Auto-activates during brand archetype selection, emotional positioning, and brand personality work. Use when discussing brand archetypes, Jungian archetypes, 12 archetypes, Hero, Outlaw, Magician, Creator, Lover, Jester, Everyman, Caregiver, Ruler, Sage, Explorer, Innocent, 70/30 rule, Mark-Pearson, or archetype combinations.
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."
deep-research
by mcouthon
"Exhaustive investigation with citations and structured findings. Use when thorough coverage is needed, all sources must be cited, or research will inform critical decisions. Triggers on: 'use deep-research mode', 'deep research', 'exhaustive investigation', 'thorough research', 'cite all sources', 'comprehensive analysis', 'leave no stone unturned', 'research everything'. Read-only mode - investigates and documents but doesn't modify code."
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."
deep-research
by mcouthon
"Exhaustive investigation with citations and structured findings. Use when thorough coverage is needed, all sources must be cited, or research will inform critical decisions. Triggers on: 'use deep-research mode', 'deep research', 'exhaustive investigation', 'thorough research', 'cite all sources', 'comprehensive analysis', 'leave no stone unturned', 'research everything'. Read-only mode - investigates and documents but doesn't modify code."
tts-internals
by drakulavich
Use when working on kesha TTS internals — voice routing and which engine serves which voice-id prefix, Kokoro/Vosk ONNX I/O shapes, the CharsiuG2P vs FluidAudio G2P split, SSML handling, multilingual behaviour (es/fr/it/pt on ONNX, hi/ja/zh on darwin-arm64), or the KESHA_* TTS environment variables. Explains why darwin-arm64 routes differently from every other build.
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."
tdd
by joelhooks
"Test-Driven Development workflow with RED-GREEN-REFACTOR, lore from Kent Beck, Michael Feathers, and Ousterhout's counterpoint"
vue-test-utils-skilld
by harlan-zw
"ALWAYS use when writing code importing \"@vue/test-utils\". Consult for debugging, best practices, or modifying @vue/test-utils, vue/test-utils, vue test-utils, vue test utils, test-utils, test utils."
lead-sourcing-and-enrichment
by NadavShanun-design
Use when building a target list - finding the right people at ICP-fit companies, getting verified contact data (email, phone, LinkedIn), and keeping the list clean. Covers the waterfall enrichment concept (multiple data sources in sequence, cheapest first), email finding and verification, catch-all handling, intent and signal data, list hygiene and suppression, and consent/compliance (GDPR, CAN-SPAM) at a practical level.
Python Standards
by AmnadTaowsoam
Python coding standards define best practices for writing clean, maintainable,
functional-programming-developer
by sideeffect-io
Functional architecture guidance for Swift (immutability, pure functions, reducers, DI via functions).
capacitor-ci-cd
by Cap-go
Complete CI/CD guide for Capacitor apps covering GitHub Actions, GitLab CI, build automation, app signing, and deployment pipelines. Use this skill when users need to automate their build and release process.
fixture-complete-skill
by daishiman
テスト用完全構成スキル - skill-creator出力検証用フィクスチャ。 全ディレクトリ（agents/, references/, scripts/, assets/, schemas/）を含む完全な構造。 Anchors: Clean Code (Robert C. Martin) / 適用: コード品質 / 目的: テスト可能な構造設計 Test-Driven Development (Kent Beck) / 適用: テスト駆動 / 目的: フィクスチャ検証 Trigger: fixture validation, complete skill test, skill-creator output verification
fixture-boundary-skill-name-padded-to-sixty-four-characters-long
by daishiman
Boundaries
test-skill
by daishiman
E2Eテスト用のスキル
test-generator
by armanzeroeight
Generates dbt tests including schema tests, data quality tests, and freshness checks. Use when adding tests to dbt models or implementing data quality validation.
verify-keybinding-reachability
by topcheer
"After adding TUI key handlers, trace the full key event dispatch chain to confirm no competing handler intercepts the event before it reaches your new code."
tk
by tkersey
"Software surgery protocol for proof-backed, minimal-diff implementation: Contract to Invariants to Creative Frame to inevitable incision to Proof. Use when users say \"run $tk\", \"patch-first\", \"keep the diff small\", \"state contract + invariants\", \"one clear incision\", \"fix it with a validation signal\", or orchestration cues like \"workers use $tk\" / \"internally use $tk\"."
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.
prove-it
by tkersey
Gauntlet for absolute claims (always/never/guaranteed/optimal); pressure-test, then refine with explicit boundaries. Use when users ask to prove or disprove strong certainty claims, request devil's-advocate challenge rounds, or want the $prove-it gauntlet to run in default autoloop/full-auto style.