Testing
Unit tests, integration tests, test automation
flutter-executing
by vp-k
Use when you have a written implementation plan to execute with review checkpoints
cro-methodology
by manojbajaj95
'Customer-centric conversion rate optimization methodology based on "Making Websites Win" by Karl Blanks and Ben Jesson (Conversion Rate Experts). Use when optimizing websites, landing pages, funnels, improving conversion rates, analyzing why visitors don''t convert, creating persuasive copy, designing A/B tests, auditing UX, or building customer-centric websites. Provides systematic CRO process, objection/counter-objection framework, and evidence-based optimization techniques.'
cold-email-sequence-generator
by manojbajaj95
Generate personalized cold email sequences (7-14 emails) with A/B test subject lines, follow-up timing recommendations, and integrated social proof. Creates multi-touch campaigns optimized for response rates. Use when users need outbound email campaigns, sales sequences, or lead generation emails.
building-sales-team
by manojbajaj95
Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.
brand-messaging-architecture
by manojbajaj95
Provides brand messaging architecture, value proposition, and brand pillar development frameworks including Peep Laja's Message Layers, Osterwalder's Value Proposition Canvas, Geoffrey Moore positioning template, April Dunford's Five Components, StoryBrand SB7, Andy Raskin's Strategic Narrative, the Messaging House, and MECLABS quality tests. Auto-activates during messaging framework development, value proposition creation, and brand pillar definition. Use when discussing messaging architecture, value proposition, brand pillars, message layers, messaging house, messaging hierarchy, elevator pitch, Peep Laja, Geoffrey Moore, April Dunford, StoryBrand, Andy Raskin, or MECLABS.
ab-test-setup
by manojbajaj95
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.
team-tasks
by win4r
"Coordinate multi-agent development pipelines using shared JSON task files. Use when dispatching work across dev team agents (code-agent, test-agent, docs-agent, monitor-bot), tracking pipeline progress, or running sequential/parallel workflows. Covers project init, task assignment, status tracking, agent dispatch via sessions_send, and result collection. Supports two modes: linear (sequential pipeline) and dag (dependency graph with parallel execution)."
circleci
by BagelHole
Configure CircleCI workflows and orbs for continuous integration and deployment. Create config.yml pipelines, use orbs for reusable configurations, and optimize build performance. Use when working with CircleCI for CI/CD automation.
interview-plan
by bahayonghang
通过苏格拉底式访谈细化需求，直接调用原生 Plan 模式生成可执行计划。适用于需求细化、技术方案设计等场景。
update-claude-md
by doodledood
Create or update CLAUDE.md with best practices - brevity, universal applicability, progressive disclosure
analyze-code
by doodledood
Deep code analysis using consultant agent. Identifies technical debt, risks, and improvement opportunities.
test-plan-generator
by kanopi
Automatically generate comprehensive QA test plans when user mentions testing requirements, QA needs, or asks what should be tested. Analyzes code changes and features to create structured test scenarios. Invoke when user mentions "test plan", "QA", "what to test", "testing requirements", or "test scenarios".
pyproject-toml
by vamseeachanta
Configure Python projects with pyproject.toml for modern packaging, tools, and dependency management
solo-review
by fortunto2
Final code review and quality gate — run tests, check coverage, audit security, verify acceptance criteria from spec, and generate ship-ready report. Use when user says "review code", "quality check", "is it ready to ship", "final review", or after /deploy completes. Do NOT use for planning (use /plan) or building (use /build).
analyze-ci-logs
by dykyi-roman
Analyzes CI/CD pipeline logs to identify failure causes. Parses error messages, detects common failure patterns, and provides fix recommendations.
critical-peer-personality
by NTCoding
"Professional, skeptical communication style. Never over-enthusiastic, verifies before agreeing, challenges constructively, proposes instead of asking preferences. Expert peer who coaches, not serves. Triggers on: composing responses, agreeing with user, making recommendations, giving feedback."
testing
by nth5693
Unified testing commands and patterns across frontend and backend.
beads-workflow
by Dicklesworthstone
"Converting markdown plans into beads (tasks with dependencies) and polishing them until they're implementation-ready. The bridge between planning and agent swarm execution. Includes exact prompts used."
agent-swarm-workflow
by Dicklesworthstone
"Jeffrey Emanuel's multi-agent implementation workflow using NTM, Agent Mail, Beads, and BV. The execution phase that follows planning and bead creation. Includes exact prompts used."
tactical-ddd
by NTCoding
"Design, refactor, analyze, and review code by applying the principles and patterns of tactical domain-driven design. Triggers on: domain modeling, aggregate design, 'entity', 'value object', 'repository', 'bounded context', 'domain event', 'domain service', code touching domain/ directories, rich domain model discussions."
tdd-process
by NTCoding
"Strict test-driven development state machine with red-green-refactor cycles. Enforces test-first development, meaningful failures, minimum implementations, and full verification. Activates when user requests: 'use a TDD approach', 'start TDD', 'test-drive this'."
writing-tests
by NTCoding
"Principles for writing effective, maintainable tests. Covers naming conventions, assertion best practices, and comprehensive edge case checklists. Based on BugMagnet by Gojko Adzic. Triggers on: writing any test, 'add tests', test review, test naming, assertion choices, edge case coverage, 'what should I test', test structure decisions."
futurist-analyst
by rysweet
Analyzes events through futures lens using scenario planning, trend analysis, weak signals, drivers of change, and forecasting methods (exploratory, normative, backcasting). Provides insights on possible futures, emerging trends, disruptive forces, strategic foresight, and alternative scenarios. Use when: Strategic planning, emerging trends, technology assessment, long-term planning, uncertainty navigation. Evaluates: Trends, weak signals, drivers of change, plausible futures, strategic options, uncertainty ranges.
module-spec-generator
by rysweet
Generates module specifications following amplihack's brick philosophy template. Use when creating new modules or documenting existing ones to ensure they follow the brick & studs pattern. Analyzes code to extract: purpose, public contract, dependencies, test requirements.