Testing
Unit tests, integration tests, test automation
replay-playwright
by replayio
Set up and run Playwright tests with Replay Browser to record test executions for debugging and performance analysis.
criteria-test-loop
by Hideturno
Drive coding by success criteria and tests; use for bugfixes, features with tests, and algorithmic changes. Emphasize naive-correct first, then optimize.
code-change-verification
by aiagentskills
Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents JS monorepo.
senior-project-manager
by arielperez82
Senior Project Manager for Software, SaaS, and digital web/mobile applications.
hook-runner
by grobomo
"Modular hook runner for Claude Code. Workflows group modules into enforceable pipelines."
skill-forge
by Cursedpotential
"Meta-skill creation and optimization system using pattern recognition, intelligent tool selection, and automated quality assurance."
test
by pmco23
Use to run the project test suite. Supports /test [file-or-pattern] to scope to specific files or test names. Detects jest, vitest, go test, pytest, dotnet test, and cargo test automatically. No pipeline artifacts required — can run at any time.
codebase-audit
by tomwangowa
Claims-first codebase audit that extracts documentation claims and verifies them against code. Use when asked to "audit", "verify docs match code", "check if README claims are true", or "validate documentation accuracy". Falsification-first approach.
demo-skill
by slezakattack
This is a "hello world" example for use with npx skills
apex
by CookSaw
Workflow autonome de développement complet en 10 étapes. Orchestre l'exploration, la planification et l'implémentation pour développer une feature de A à Z. Utiliser avec /apex [feature] pour mode interactif ou /apex --auto [feature] pour mode autonome. Triggers: "apex", "workflow complet", "feature to PR", "développement autonome", "implement feature end to end".
Dual-Brand Architecture
by tachfineamnay
SocioPulse/MedicoPulse multi-brand configuration, theming, and feature flags.
spec-driven-development
by Contaaltv4782
Use when starting features, projects, or refactors with AI coding agents and requirements feel informal, incomplete, or drift-prone. Triggers: AI generates code that ignores constraints, same prompt produces different implementations across sessions, team lacks shared technical understanding, complex features need traceable design decisions, or vibe-coding produces unreliable output. Keywords: spec-driven, SDD, specification-first, requirements.md, plan.md, tasks.md, constitution.md, design doc, PRD, acceptance criteria, MoSCoW, drift detection, AI planning, feature spec, context drift, hallucination, constrained generation, boundaries, risks-identification, assumption-surface, living-document.
webapp-testing
by enoch-robinson
Webåºç¨æµè¯å·¥å ·å ãä½¿ç¨ Playwright è¿è¡å端èªå¨åæµè¯ãUI è°è¯ãæªå¾æè·ãæµè§å¨æ¥å¿æ¥çãå½éè¦æµè¯æ¬å° Web åºç¨ãéªè¯å端åè½ãè°è¯ UI è¡ä¸ºæ¶ä½¿ç¨æ¤æè½ã
godot-tdd
by Chen19007
Godot TDD（测试驱动开发）流程总控，协调 godot-design、godot-dev、godot-test、godot-verify 完成开发闭环。
typer-patterns
by vanman2024
Modern type-safe Typer CLI patterns with type hints, Enums, and sub-apps. Use when building CLI applications, creating Typer commands, implementing type-safe CLIs, or when user mentions Typer, CLI patterns, type hints, Enums, sub-apps, or command-line interfaces.
testing
by paucasanellas
Unit testing with TypeScript, Vitest (with globals), Vue Testing Library, and Nuxt Test Utils using Happy DOM. Covers testing strategies, best practices, mocking, component testing, and integration with modern Vue ecosystem tools.
react-native-patterns
by keenranger
React Native mobile development patterns for authentication, platform-specific issues, navigation, and SDK integration. Use when debugging React Native apps, fixing iOS/Android issues, handling auth flows, or integrating native SDKs.
development
by leovido
Core development standards, patterns, and best practices for React and React Native projects. Use this when users need guidance on code quality (Biome, TypeScript), testing (Jest), project structure (Domain-Driven Design), React best practices (useEffect guidelines), or React Native development with Expo.
fe-migrate
by ingpdw
React/Next.js 프로젝트의 마이그레이션을 가이드하는 스킬. Pages Router에서 App Router, JavaScript에서 TypeScript, CSS에서 Tailwind, 라이브러리 업그레이드 등. "마이그레이션", "migrate", "업그레이드", "전환", "변환" 등의 요청 시 사용.
spec-tests
by ianphil
Intent-based specification tests evaluated by LLM-as-judge. Use when the user asks to "create spec tests", "write intent tests", "TDD with intent", "natural language tests", or wants tests that capture WHY, not just WHAT. NOT pytest/jest/unittest - natural language specs Claude evaluates.
Neuromodulation + Eligibility Traces (Three-Factor Learning)
by sovr610
This skill should be used when the user asks to "implement eligibility traces", "add three-factor learning", "implement neuromodulation", "add DA/ACh/NE/5-HT modulators", "implement STDP eligibility", "add synaptic plasticity", "implement online plasticity", "add reward-modulated learning", "implement trace dynamics", "add Dutch traces", "implement accumulating traces", "add replacing traces", "implement neuromodulatory gate", "add plasticity gain", "implement delayed reward association", "add eligibility decay", "implement spike-based traces", "add rate-based traces", "implement three-factor weight update", "add fast memory adapter", "implement bioplausible learning", or mentions eligibility traces, three-factor learning rules, neuromodulatory signals, STDP-based eligibility, reward-modulated plasticity, DA/ACh/NE/5-HT computation, or online synaptic updates in the cognitive pipeline.
app-store-optimization
by ncdevshiv
"Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store"
swe-implementer
by diegocanepa
"Development persona for writing clean, tested code and executing subtasks within the SWE workflow."
tech-planner
by jkappers
Use when (1) evaluating technical feasibility of a feature spec, (2) making technology or framework choices, (3) defining system architecture for a new feature, (4) documenting architectural decisions as ADRs, (5) analyzing integration points and data flow for a proposed change.