Testing
Unit tests, integration tests, test automation
guiding-users
by ancoleman
Implements onboarding and help systems including product tours, interactive tutorials, tooltips, checklists, help panels, and progressive disclosure patterns. Use when building first-time experiences, feature discovery, guided walkthroughs, contextual help, setup flows, or user activation features. Provides timing strategies, accessibility patterns (keyboard, screen readers, reduced motion), and metrics for measuring onboarding success.
implementing-service-mesh
by ancoleman
Implement production-ready service mesh deployments with Istio, Linkerd, or Cilium. Configure mTLS, authorization policies, traffic routing, and progressive delivery patterns for secure, observable microservices. Use when setting up service-to-service communication, implementing zero-trust security, or enabling canary deployments.
managing-configuration
by ancoleman
Guide users through creating, managing, and testing server configuration automation using Ansible. When automating server configurations, deploying applications with Ansible playbooks, managing dynamic inventories for cloud environments, or testing roles with Molecule, this skill provides idempotency patterns, secrets management with ansible-vault and HashiCorp Vault, and GitOps workflows for configuration as code.
evaluating-llms
by ancoleman
Evaluate LLM systems using automated metrics, LLM-as-judge, and benchmarks. Use when testing prompt quality, validating RAG pipelines, measuring safety (hallucinations, bias), or comparing models for production deployment.
web3-btt
by sablier-labs
Write bulloak tree specifications (.tree files) for smart contract integration tests. Trigger phrases - write a tree, create test tree, BTT spec, bulloak tree, Branching Tree Technique, or when writing integration tests for contract functions.
spec-from-screenshot
by sablier-labs
This skill should be used when the user asks to "analyze a screenshot", "generate implementation spec", "create SPEC.md from screenshot", "extract design specs", "spec from image", or provides website screenshots and wants detailed implementation guidance.
vitest
by sablier-labs
This skill should be used when the user asks to "write tests", "add tests", "test coverage", "run tests", "debug failing tests", "mock functions", or mentions Vitest, unit tests, component tests, test-driven development, or testing utilities. Provides comprehensive Vitest v4 guidance for TypeScript React/Next.js projects.
web3-forge
by sablier-labs
Write Foundry-based tests and scripts. Trigger phrases - foundry testing, write test, fuzz test, fork test, invariant test, deploy script, gas benchmark, coverage, or when working in tests/ or scripts/ directories.
e2e-testing
by joabgonzalez
"End-to-end testing patterns and best practices. Trigger: When writing or reviewing E2E tests for any layer."
agent-orchestrator-standalone
by mrclrchtr
Orchestrate complex work via a phase-gated multi-agent loop (audit → design → implement → review → validate → deliver). Use when you need to split work into subsystems, run independent audits, reconcile findings into a confirmed issue list, delegate fixes in clusters, enforce PASS/FAIL review gates, and drive an end-to-end validated delivery. Do not use for small, single-file tasks.
jest
by joabgonzalez
"Unit, integration, and snapshot testing with Jest. Trigger: When writing or running tests with Jest."
react-native-testing-library
by joabgonzalez
"User-centric React Native component testing. Trigger: When testing React Native components with RNTL."
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
Ruby RSpec TDD Implementer
by viamin
Expert in Test-Driven Development using Ruby and RSpec framework
agent-evaluation
by boisenoise
"Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring\u2014where even top agents achieve less than 50% on re..."
bun
by joabgonzalez
"Fast JavaScript/TypeScript runtime with bundling and testing. Trigger: When using Bun for server apps, scripts, or tooling."
fixture-boundary-skill-name-padded-to-sixty-four-characters-long
by daishiman
Boundaries
popup-cro
by almeidamarcell
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
architecture-patterns
by joabgonzalez
"Architectural decision guide by complexity. Trigger: When choosing architecture, planning strategic refactoring, or evaluating pattern trade-offs."
code-review
by joabgonzalez
"Two-stage code review: spec compliance then code quality. Trigger: When reviewing code for correctness and quality."
react-testing-library
by joabgonzalez
"User-centric React component testing. Trigger: When testing React components with RTL."
business-feature-docs
by duc01226
Create or update EasyPlatform business feature documentation in docs/business-features/{Module}/. Use when asked to document a feature, create module docs, update feature documentation, or add detailed feature specs. Triggers on "feature docs", "business feature documentation", "module documentation", "document feature", "update feature docs".
action-cable
by RoleModel
Setup and use ActionCable for real-time features in Rails applications using WebSockets. Use when implementing real-time updates, live notifications, broadcasting changes, or when the user mentions WebSockets, ActionCable, channels, broadcasting, or Turbo Streams over cable.
ab-test-setup
by almeidamarcell
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.