- Home
- /
- Categories
- /
- Testing
Testing
Unit tests, integration tests, test automation
agent-guardrails
by aiagentskills
General agent safety and workflow guardrails that prevent high-impact mistakes across tooling, verification, versions, integration layers, environment/config, import-time side effects, and high-risk actions. Use when defining or applying behavioral constraints for coding agents, repo automation rules, or operational safety checklists.
ai-prompt-engineering-safety-review
by williamlimasilva
'Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content.'
shape-up-analysis
by tachun
Analyze a Shape Up pitch document alongside a codebase to identify risks, rabbit holes, and unknowns. Produces comprehensive kickoff analysis with bet confidence rating. Use when asked to "analyze this pitch", "review Shape Up pitch", "kickoff analysis", "identify risks in this pitch", "what are the rabbit holes", "assess this bet", "prepare project kickoff", "evaluate this pitch", or when starting a new Shape Up cycle and need to understand scope vs codebase reality.
pr-prep
by russdias
Use when preparing a pull request, crafting commit messages, or summarizing code changes for review. Triggers on tasks like "prepare my PR", "write a commit message", "summarize my changes", "generate PR description", or before pushing a feature branch.
json-api-mock-generator
by ehtbanton
Generate realistic JSON API mock response files with proper data types, nested structures, and configurable record counts. Triggers on "create mock API response", "generate JSON mock data", "fake API data for", "mock endpoint response".
fe-test
by ingpdw
Vitest + React Testing Library 기반 테스트 코드를 생성하는 스킬. 단위 테스트, 컴포넌트 테스트, 훅 테스트, 통합 테스트, MSW 목 설정 등. "테스트", "test", "테스트 작성", "테스트 코드", "유닛 테스트" 등의 요청 시 사용.
testing-unit-integration
by agdev
Expert guidance for writing clean, simple, and effective unit, integration, component, microservice, and API tests. Use this skill when reviewing existing tests for violations, writing new tests, or refactoring tests. NOT for end-to-end tests that span multiple processes - use testing-e2e skill instead. Covers AAA pattern, data factories, mocking strategies, DOM testing, database testing, and assertion best practices.
Compiler & Kernel Fusion (torch.compile) Integration
by sovr610
This skill should be used when the user asks to "enable torch.compile", "add compilation to training", "kernel fusion", "TorchDynamo integration", "TorchInductor optimization", "reduce-overhead mode", "max-autotune mode", "fix graph breaks", "compile health check", "shape stabilization", "dynamic shapes for compile", "bucketing for torch.compile", "compile allowlist", "compile blocklist", "compile smoketest", "CUDA graphs for training", "maybe_compile wrapper", "debug recompiles", "TORCH_LOGS compile", "compile + DDP", "compile + FSDP", "torch.compiler.disable", or needs guidance on torch.compile integration, shape management, compilation debugging, or safe fallback patterns.
ai-say
by Ema93sh
Local text-to-speech on Ubuntu using Kokoro TTS with fallbacks. Use when the user asks you to speak, say, read aloud, announce, or narrate text. Also use for TTS playback testing, switching Kokoro voices, adjusting speech volume, or debugging audio output issues. Triggers: "say this", "say hello", "read that back to me", "read aloud", "speak", "announce", "narrate", "tell me out loud", "hear it out loud", "text to speech", "TTS", "voice test". Do NOT use for: recording audio, transcription, speech-to-text, playing music/media files, or dictation input.
github-spec-kit
by doitundoit
Expert guidance for Spec-Driven Development using the GitHub Spec Kit. Use when the user wants to initialize a project, create specifications, plan implementations, or execute tasks based on the Spec Kit workflow. Triggers on "spec kit", "specify", "create spec", "spec-driven development".
code-review-excellence
by TriNgo0108
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
test-driven-development
by Jackiexiao
(中文)Use when implementing any feature or bugfix, before writing implementation code
false-calculator
by tobidsn
A fun skill that provides wrong math answers with confidence. Specifically, for any addition (+), it adds an extra 5 to the actual result. Triggers when the user asks for simple math addition or when calculating sums.
context-android
by ShotaIuchi
Android development context. Apply when working with Android modules, .kt files under android/, build.gradle.kts with Hilt/Compose dependencies, ViewModel, Jetpack Compose, MVVM/UDF patterns.
unit-test-generator
by cha9ro
Generate and improve unit tests using the Assured LLMSE approach from Meta's TestGen-LLM. Use this skill when users request help with writing unit tests, improving test coverage, adding test cases to existing test suites, generating tests for new or existing code, or reviewing and enhancing test quality. Applies multi-stage verification filters to ensure generated tests build correctly, pass reliably, and measurably improve coverage without regressing existing behavior.
velt-crdt-best-practices
by velt-js
Velt CRDT (Yjs) collaborative editing best practices for real-time applications. This skill should be used when implementing collaborative features using Velt CRDT stores, integrating with editors like Tiptap, BlockNote, CodeMirror, or ReactFlow, or debugging sync issues. Triggers on tasks involving real-time collaboration, multiplayer editing, CRDT stores, or Velt SDK integration.
yuno-md
by Xuno-io
Intellectual sparring partner for software development. Activate this skill when facing architectural decisions, technical dilemmas, or before implementing something complex. Yuno questions premises, exposes logical weaknesses, and demands rigor - it catalyzes, not validates. Use it when you need someone to attack your idea before reality does.
bf-lead-plan
by khaki4
Tech Spec을 분석하여 Epic/Story 구조를 생성하고, Story 5개 이상일 때 병렬로 Story 문서를 작성한다. Distribute 조율 패턴.
adversarial-reasoning
by kimasplund
Stress-test solutions using the STRIKE framework. Systematically attack proposals to find weaknesses before deployment.
claude-framework
by vineethsoma
CLAUDE Framework coding standards for code quality, naming conventions, error handling, security, testing, database, and logging
tdd
by BaxterCooper
Use for any code implementation task. Enforces RED-GREEN-REFACTOR cycle. "If you didn't watch it fail, you don't know if it tests the right thing."
smart-code-test-e2e
by lordprotein
"Write ideal E2E tests and review existing ones. Focused exclusively on end-to-end testing — full user journeys through a real browser. Not for unit or integration tests. Two modes: generate new E2E tests from feature analysis, or review existing E2E tests for antipatterns, flakiness, and quality issues. Framework-agnostic, based on best practices from Beck, Fowler, Cohn, Rauch, and Google."
Product Manager
by coco-de
Product requirements and planning specialist. Creates PRDs and tech specs with functional/non-functional requirements, prioritizes features using MoSCoW/RICE frameworks, breaks down epics into user stories, and ensures requirements are testable and traceable. Use for PRD creation, requirements definition, feature prioritization, tech specs, epics, user stories, and acceptance criteria.
flutter-terminal-cheat-sheet
by Envy-7z
This post provides a handy collection of Flutter commands and scripts for web development, package creation, troubleshooting, testing, and more, streamlining your Flutter workflow.