- Home
- /
- Categories
- /
- Testing
Testing
Unit tests, integration tests, test automation
precoil-emt
by Stripmined-reflation431
"Use this skill when the user wants to test a business idea, strategy, or initiative against real-world risk. Triggers include: 'test my idea', 'what are the riskiest assumptions', 'help me validate this', 'run EMT on this', 'extract assumptions', 'assumption mapping', 'what could go wrong with this plan', 'pressure test this', 'validate this plan', 'what could go wrong with this strategy', 'identify hidden risk in this idea', or any request to pressure-test a business decision before committing resources. Runs a guided Extract → Map → Test system based on David J. Bland's Precoil methodology."
design
by saselvan
"Design Ops v3.1. Journey → PRP → Issues → TDD. Tiered pipeline with invariant enforcement, devil's advocate, and e2e testing. USE WHEN design, PRP, validate, requirements, init project, review implementation."
forge
by vieko
Verification boundary CLI that delegates tasks to autonomous agents. Use when the user wants to run forge, execute specs, run specs in parallel, run pending specs, define specs from a description, resolve specs, audit code against specs, review changes, watch live logs, check run status, resume a session, or delegate complex multi-step work to an autonomous agent. Triggers include "forge run", "run this spec", "run specs in parallel", "run pending", "forge define", "define specs", "audit the codebase", "review changes", "forge watch", "forge status", "rerun failed", "resolve spec", "delegate this to forge". Do NOT use for simple edits you can make directly, questions that don't require implementation, or straightforward work in the current repo that doesn't need autonomous agent execution.
test-generation
by Protagonistss
分析源代码并生成对应的单元测试用例。
cc-skill-project-guidelines-example
by automindtechnologie-jpg
Project Guidelines Skill (Example)
vue-testing-best-practices
by hello-lizhihua
Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.
effective-questioning
by iamkaf
Use when the user asks you to gather requirements, or when the request is vague and needs clarity before acting.
KeePassXC Integration
by janjaszczak
Integracja KeePassXC z Cursorem do bezpiecznego zarządzania sekretami (hasła, tokeny API, klucze SSH)
spec-save-design
by nu1nux
Convert a /spec:brainstorm session into a structured design document saved under docs/designs.
problem-solving
by arielperez82
Apply systematic problem-solving techniques for complexity spirals (simplification
run
by xuesongjun
启动 Test Studio 应用
checkpoint
by Nomik94
Use when: 리팩토링, 삭제, 마이그레이션, 대규모 변경, 위험한 작업, 파일 삭제, 코어 변경, 스키마 변경, 구조 변경. NOT for: 단순 수정, 새 파일 추가, 테스트 추가.
parking-lot-consensus
by CakeRepository
"Use when you want an internal debate (Critic vs Solver + Judge) to converge on a high-confidence implementation plan before coding."
aave-integration
by 0xWeakSheep
This skill should be used when the user needs to interact with AAVE V3 protocol contracts directly, read on-chain data, get reserve configurations, fetch current APY rates, simulate position changes, or execute protocol operations programmatically. Provides low-level access to AAVE Pool contracts, UI Pool Data Provider, and quote generation for supply, borrow, repay, and withdraw operations on Ethereum and Arbitrum.
page-cro
by kunhai-88
"优化任何营销页面的转化时使用:首页、落地页、定价页、功能页、博客。触发词:CRO、conversion rate optimization、this page isn't converting、improve conversions、why isn't this page working。注册流程见 signup-flow-cro;注册后激活见 onboarding-cro;非注册表单见 form-cro;弹窗见 popup-cro。"
exec-plan
by bromanko
Write or implement execution plans (ExecPlans) — thorough, self-contained design documents that guide a coding agent through complex features or significant refactors. Use this skill when the user asks to "write a plan", "create an exec plan", "make an ExecPlan", "plan this feature", "design this refactor", "write a design doc for implementation", or when they ask to "implement a plan", "execute this plan", "follow the plan", "continue the plan", "pick up where the plan left off". Also trigger when the user mentions "ExecPlan", "execution plan", or references a PLAN.md or similar planning document. This skill covers both authoring plans and executing them.
nextjs
by yldgio
Next.js 14+ App Router patterns, Server Components, API routes, and performance optimization
writing-plans
by Jackiexiao
(中文)Use when you have a spec or requirements for a multi-step task, before touching code
dead-code-eliminator
by abpai
Audit a codebase for dead code — unreachable functions, unused imports, orphaned classes, unreachable branches, and stale feature flags — by tracing live call paths from all entry points. Also audits correctness (do implementations match their claimed purpose?) and algorithmic soundness. Produces an ASCII call graph and a categorized dead code report. Use when a codebase has gone through many iterations, a large refactor has landed, a feature was removed but its support code may remain, or the user asks to "find dead code", "clean up unused code", "audit what's actually used", or "find orphaned functions".
commit
by Tmeister
Generate a conventional commit message from staged changes and commit safely.
Broken Authentication Testing
by automindtechnologie-jpg
This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate password policies", "test for session fixation", or "identify authentication bypass flaws". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications.
feature-test
by ShotaIuchi
Test creation for new features. Apply when creating unit tests, integration tests, edge case coverage, and test fixtures for newly implemented functionality.
tdd-workflow
by vineethsoma
Test-Driven Development workflow with TDD commit convention, compliance tracking, and validation
kyverno
by kontrolplane
Kyverno Kubernetes policy engine for validation, mutation, and generation. Use when writing ClusterPolicies to enforce security standards, auto-mutate resources with defaults, generate companion resources, or verify container image signatures.