Testing
Unit tests, integration tests, test automation
h3-pg
by postgis
PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.
project-conventions
by ReinaMacCredy
Discovers host project conventions from CLAUDE.md, package.json, linter configs, and other configuration files. Use when agents need to understand the target project's coding standards.
define-architecture
by mblode
Defines repo layout, workflow, and full-stack architecture patterns for TypeScript applications. Use when starting a project, setting team conventions, or designing backend modules, request context, middleware, and frontend/backend boundaries.
spec-kit-skill
by feiskyer
'GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow. Triggers: "spec-kit", "speckit", "constitution", "specify", ".specify/", "规格驱动开发", "需求规格".'
artillery
by TerminalSkills
When the user wants to perform load testing or performance testing using Artillery with YAML-based scenario definitions. Also use when the user mentions "artillery," "YAML load test," "WebSocket testing," "Socket.io load test," "scenario-based load testing," or "artillery run." For JavaScript-based load testing, see k6.
Test Quality Inspector
by bobmatnyc
Systematically inspect unit and E2E tests to verify they test the right behavior, provide meaningful coverage, and catch real regressions
prep-meeting
by bobmatnyc
Prepares for meetings by gathering context about attendees, topics, and relevant data across connected tools. Produces an agenda with talking points, supporting data, and anticipated questions.
Forge
by simota
ããã³ãã¨ã³ãï¼UIã³ã³ãã¼ãã³ã/ãã¼ã¸ï¼ã¨ããã¯ã¨ã³ãï¼APIã¢ãã¯/ç°¡æãµã¼ãã¼ï¼ä¸¡é¢ã®ãããã¿ã¤ããç´ æ©ãæ§ç¯ãæ°æ©è½ã®æ¤è¨¼ãã¢ã¤ãã¢ãå½¢ã«ãããæã«ä½¿ç¨ãå®ç§ããåããã®ãåªå ã
auth-system-setup
by TerminalSkills
When the user wants to set up authentication and authorization for a web application. Use when the user mentions "auth," "login," "OAuth," "SSO," "single sign-on," "role-based access," "RBAC," "permissions," "user roles," "access control," "authentication," or "authorization." Covers OAuth 2.0 provider integration, session management, and role/permission architecture. For JWT-specific tasks, see jwt-handler. For security review, see security-audit.
tdd
by AsiaOstrich
"[UDS] Guide through Test-Driven Development workflow"
deployment-pipeline-design
by rsmdt
Pipeline design, deployment strategies (blue-green, canary, rolling), and CI/CD platform patterns. Use when designing pipelines, implementing deployments, configuring quality gates, or setting up automated release workflows. Covers GitHub Actions, GitLab CI, and platform-agnostic patterns.
skill-creator
by zaggino
Create, improve, and test skills for the z-schema JSON Schema validator library. Use this skill whenever the user wants to create a new skill from scratch, turn a workflow into a reusable skill, update or refine an existing skill, write test cases for a skill, or organize reference material for a skill. Also use when someone mentions "skill", "SKILL.md", or wants to document a z-schema workflow for reuse by humans or AI agents.
contributing-to-z-schema
by zaggino
Guides contributors through the z-schema codebase, PR workflow, and common development tasks. Use when the user wants to contribute to z-schema, add a new feature or keyword, add an error code, add a format validator, modify options, write tests, run the test suite, fix a failing test, understand the validation pipeline, navigate the source code architecture, or submit a pull request. Also use when someone mentions contributing, PRs, the z-schema source code, or the JSON Schema Test Suite integration.
vitest-bdd-3layer
by solidSpoon
'DashPlayer 三层 Vitest-BDD 技能。Use when developers want business-readable BDD scenarios without coupling scenario writing to code implementation details. Triggers on: "BDD 三层", "行为测试分层", "给定当那么", "Vitest BDD", "不想在场景里写实现".'
pattern-detection
by rsmdt
Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices. Ensures new code aligns with project conventions.
matlab-test-generator
by matlab
Create comprehensive MATLAB unit tests using the MATLAB Testing Framework. Use when generating test files, test cases, unit tests, test suites, or when the user requests testing for MATLAB code, functions, or classes.
takopi-release
by banteg
Prepare and ship a Takopi release. Use when asked to cut a release, bump release versions, update changelog/spec/readme, tag v<major.minor.patch>, or trigger the GitHub release workflow.
go-testing
by cxuu
Go testing patterns from Google and Uber style guides including test naming, table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions. Use when writing or reviewing Go test code, creating test helpers, or setting up table-driven tests.
signup-flow-cro
by OpenClaudia
Optimize signup and registration conversion funnels. Use when asked to improve signup rates, reduce form abandonment, audit registration flows, or optimize conversion funnels. Trigger phrases: "signup optimization", "registration flow", "form conversion", "signup CRO", "reduce abandonment", "signup funnel", "form optimization", "conversion rate optimization", "registration page".
perf-theory-tester
by ComposioHQ
"Use when running controlled perf experiments to validate hypotheses."
financial-unit-economics
by lyndonkl
Use when evaluating business model viability, analyzing profitability per customer/product/transaction, validating startup metrics (CAC, LTV, payback period), making pricing decisions, assessing scalability, comparing business models, or when user mentions unit economics, CAC/LTV ratio, contribution margin, customer profitability, break-even analysis, or needs to determine if a business can be profitable at scale.
layered-rails
by palkan
Design and review Rails applications using layered architecture principles from "Layered Design for Ruby on Rails Applications". Use when analyzing Rails codebases, reviewing PRs for architecture violations, planning feature implementations, or implementing patterns like authorization, view components, or AI integration. Triggers on "layered design", "architecture layers", "abstraction", "specification test", "layer violation", "extract service", "fat controller", "god object".
solana-dev
by solana-foundation
End-to-end Solana development playbook (Jan 2026). Prefer Solana Foundation framework-kit (@solana/client + @solana/react-hooks) for React/Next.js UI. Prefer @solana/kit for all new client/RPC/transaction code. When legacy dependencies require web3.js, isolate it behind @solana/web3-compat (or @solana/web3.js as a true legacy fallback). Covers wallet-standard-first connection (incl. ConnectorKit), Anchor/Pinocchio programs, Codama-based client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists.
issue-tree-builder
by sruthir28
McKinsey-style issue tree framework for breaking down complex problems into MECE (Mutually Exclusive, Collectively Exhaustive) components. Use when users need to decompose strategic questions, structure analysis, create work plans, or prepare for case interviews. Apply hypothesis-driven approach to problem-solving.