Testing
Unit tests, integration tests, test automation
swift-testing
by bocato
'Expert guidance on Swift Testing best practices, patterns, and implementation. Use when developers mention: (1) Swift Testing, @Test, #expect, #require, or @Suite, (2) "use Swift Testing" or "modern testing patterns", (3) test doubles, mocks, stubs, spies, or fixtures, (4) unit tests, integration tests, or snapshot tests, (5) migrating from XCTest to Swift Testing, (6) TDD, Arrange-Act-Assert, or F.I.R.S.T. principles, (7) parameterized tests or test organization.'
generate-tests
by iskysun96
"Creates comprehensive test suites for Move contracts with 100% coverage requirement. Triggers on: 'generate tests',
agent-estimation
by ZhangHanDong
Accurately estimate AI agent work effort using the agent's own operational units (tool-call rounds) instead of human time. Use when asked to estimate, scope, plan, or evaluate how long a coding task will take. Prevents the common failure mode where agents anchor to human developer timelines and massively overestimate. Outputs a structured breakdown with round counts, risk factors, and a final wallclock conversion.
update-claude-md
by doodledood
Create or update CLAUDE.md with best practices - brevity, universal applicability, progressive disclosure
analyze-code
by doodledood
Deep code analysis using consultant agent. Identifies technical debt, risks, and improvement opportunities.
rive-script-builder
by sanqiushili
Build and revise Rive Luau scripts across Node, Layout, Converter, Path Effect, Transition Condition, Listener Action, Util, and Test protocols. Use when the user asks to write or modify Rive scripts, choose protocols, wire script inputs or data binding, debug runtime behavior, or plan unit tests for script logic.
setup-fastlane
by greenstevester
Set up Fastlane for iOS/macOS app automation
response-quality-analysis
by m31uk3
"Analyze whether your response addresses the actual question asked before posting. Use when: (1) About to post response to forum/Slack question, (2) Want to validate response coverage, (3) Need to ensure solving the right problem, (4) Want specific improvement suggestions for gaps in response"
clean-code
by jackjin1997
"Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functions, comments, error handling, and class design."
javascript-unit-testing
by el-feo
Writing high-quality unit tests for JavaScript and TypeScript using Jest. Covers test structure (AAA pattern, USE naming), breaking dependencies (stubs, mocks, dependency injection), testing async code (promises, callbacks, timers), avoiding flaky tests, and test-driven development. Use when writing tests, debugging test failures, refactoring tests for maintainability, or questions about Jest, TDD, mocks, stubs, or test best practices.
dev
by Tyler-R-Kendrick
Use when working with fundamental software development knowledge — patterns, algorithms, architecture, and craftsmanship principles drawn from canonical published works. USE FOR: development fundamentals, pattern selection, architecture decisions, algorithm choice, code quality principles, choosing between architectural styles DO NOT USE FOR: specific pattern implementations (use sub-skills: design-patterns, integration-patterns, algorithms, etc.), testing strategy (use testing), infrastructure (use iac)
clerk-auth
by phrazzld
"Clerk authentication integration patterns for Next.js and Convex. Invoke for: user authentication, session management, JWT templates, webhook handling, middleware configuration, protected routes, Convex auth integration."
integration-patterns
by Tyler-R-Kendrick
Use when designing or evaluating enterprise integration architectures based on Hohpe & Woolf's Enterprise Integration Patterns. USE FOR: Enterprise Integration Patterns, messaging architecture, choosing integration patterns, pipes and filters, message-oriented middleware DO NOT USE FOR: specific pattern implementations in code (use sub-skills), API design (use dev/backend/api-design), event sourcing (use dev/architecture/event-driven)
ap2
by Tyler-R-Kendrick
Use when implementing the Agent Payments Protocol (AP2) for secure, compliant AI-driven commerce. Covers intent mandates, cart mandates, payment flows, and merchant integration. USE FOR: agent-driven purchases, secure commerce mandates, user-authorized shopping flows, payment credential verification DO NOT USE FOR: API micropayments (use x402), agent communication (use a2a), tool integration (use mcp)
study-habits
by jackjin1997
Build effective study habits with spaced repetition, active recall, and session tracking
ab-test-setup
by phrazzld
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
billing-security
by phrazzld
Apply billing and security best practices for payment/auth integrations. Invoke when: setting up Stripe/Clerk/auth, debugging payment issues, configuring webhooks, before prod deployment, after billing incidents.
autopilot
by phrazzld
Full autonomous delivery from issue to PR. Finds highest-priority issue, specs it, designs it, builds it, ships it. Use when: shipping an issue end-to-end, autonomous delivery, sprint execution. Composes: /spec, /architect, /build, /refactor, /update-docs, /pr.
agents-md
by Tyler-R-Kendrick
Use when creating or updating AGENTS.md files to guide AI coding agents. Covers file structure, placement, content guidelines, and best practices for project-level agent instructions. USE FOR: project-specific agent instructions, build/test commands for agents, coding conventions, repository-level guidance DO NOT USE FOR: reusable cross-project skills (use agent-skills), agent runtime definition (use adl)
simplecov
by el-feo
Comprehensive test coverage analysis and improvement for Ruby and Rails applications using SimpleCov and SimpleCov Console formatter. Automatically runs coverage reports, identifies gaps, suggests tests, and enforces coverage standards. Integrates with RubyCritic for holistic code quality. Use when running tests, analyzing coverage, improving test suites, or setting up coverage tracking in Ruby/Rails projects.
bonfire
by vieko
Session context persistence for AI coding. Start/end sessions, create outcome specs and docs, review work. Use for session management, "start session", "end session", outcome specs, documentation, code review, or questions about previous work, decisions, blockers, "last time", "what we decided".
rspec
by el-feo
Comprehensive RSpec testing for Ruby and Rails applications. Covers model specs, request specs, system specs, factories, mocks, and TDD workflow. Automatically triggers on RSpec-related keywords and testing scenarios.
docker-in-docker
by Tyler-R-Kendrick
Use when configuring Docker-in-Docker inside a dev container or Codespace. Covers the DinD feature, Docker Compose, building images, and running containers from within the dev environment. USE FOR: running Docker inside dev containers, DinD feature configuration, building images in Codespaces, Compose inside containers DO NOT USE FOR: general devcontainer.json schema (use devcontainer), sidecar services via Compose (use multi-container-workspaces), production Docker builds (use iac/docker)
specsmith
by ngvoicu
Structured spec management for AI coding workflows. Converts ephemeral plans into persistent, resumable specs with phases, tasks, and progress tracking that survive across sessions. Use this skill whenever the user: exits plan mode (automatically offer to save the plan as a spec), says "resume" or "what was I working on", wants to switch between projects, mentions specs/phases/tasks, says "spec new/list/resume/status/pause/activate", says "forge", "research", "create a spec for X", "plan X", says "generate openapi", "update api spec", "create api docs", "openapi", or any workflow involving structured planning that should persist. Also trigger when the user starts a new session in a project that has a .specs/ directory — check for an active spec and offer to resume.