Workflow Recipes

Ready-to-use command sequences for common development tasks.

New to ClaudeKit?
These workflows consist of sequences of commands that work together to accomplish common tasks. Perfect for getting started!

Workflow Recipes

Getting Started

3 workflows

Build a New Feature

Beginner

Best for: Adding new functionality to your app

~15-30 min 4 steps
1
/ck:brainstorm Explore ideas

Use /ck:brainstorm or say "brainstorm ideas for [feature]" to explore possibilities

2
/ck:plan Create implementation plan

AI creates a detailed step-by-step plan for building your feature

3
Review → /clear → Implement

Review plan, run /clear to free context (mandatory), then implement

4
/ck:cook @plan.md Implement the plan

AI writes the code following the plan, runs tests, and reviews the work

/clear is mandatory after /ck:plan before /ck:cook

Quick Implementation

Intermediate

Best for: Small features when you know what you want

~10-20 min 1 steps
1
/ck:cook "your task" All-in-one skill

AI researches, plans, implements, tests, and reviews the feature automatically

What /ck:cook "your task" does automatically:
  • Research best approaches and technologies
  • Create and execute implementation plan
  • Write and test the code
  • Review for quality and best practices
/ck:cook Flags
--interactive

Step-by-step with approval (default)

--fast

Skip research, quick implementation

--parallel

Run phases in parallel

--auto

Auto-approve all steps

--no-test

Skip test runs after coding

--interactive is default, uses native Claude Tasks API.

Start New Project

Advanced

Best for: Creating a complete app from scratch

~1-2 hours 1 steps
1
/ck:bootstrap "describe your app" Complete project setup

AI builds your entire project: research, architecture, design, implementation, and documentation

What /ck:bootstrap "describe your app" does automatically:
  • Research and tech stack selection
  • Project structure and architecture
  • UI/UX design and wireframes
  • Complete implementation with tests
  • Comprehensive documentation
Warning: This uses significant AI tokens

Design & Frontend

2 workflows

Frontend Design Aesthetics

Advanced

Best for: Creating distinctive, production-grade frontend interfaces that avoid generic AI slop

~30-60 min 4 steps
1
/ck:ui-ux-pro-max Design Intelligence

Activate ui-ux-pro-max logic to formulate styling references

2
Mandatory Gate

Commit to a BOLD direction. Define Purpose, Tone, Constraints, and Differentiation.

3
Design Rules

Ensure font size >= 16px for inputs, mobile-first layouts, and Anti-slop Google Fonts.

4
/ck:frontend-design Implement Interface

Execute the spec following the design dials: Motion, Variance, Density.

What /ck:frontend-design does automatically:
  • Design Dials: Variance, Density, Motion Intensity
  • Mandatory strict Design Thinking gates
  • Motion rules: CSS for HTML, Motion for React
  • Production-ready aesthetic choices
Anti-slop typography demands trending Google Fonts with Vietnamese coverage (e.g. Satoshi, Inter)

AI Design Generation (Stitch)

Intermediate

Best for: Generating high-fidelity UI designs from text prompts via Google Stitch

~5-15 min 3 steps
1
/ck:stitch generate "prompt" Generate design

Create UI designs from text prompts using Google Stitch AI

2
/ck:stitch export --format all Export assets

Export as Tailwind/HTML + DESIGN.md spec for implementation

3
/ck:frontend-design Implement components

Build React components from the exported design spec

What /ck:stitch generate "prompt" does automatically:
  • Text-to-UI design via Google Stitch API
  • Export to Tailwind/HTML and DESIGN.md
  • Design-to-code pipeline with existing skills
  • Supports mobile, desktop, and tablet layouts
  • Quota: 200 credits/day (Flash), 50/day (Pro)
Set up Stitch MCP server in .claude/.mcp.json for direct tool integration

Debugging & Fixes

4 workflows

Fix a Bug

Beginner

Best for: Structured diagnosis and repair of bugs

~10-20 min 6 steps
1
/ck:fix 6-step pipeline

Runs the full pipeline: Scout → Diagnose → Assess → Fix → Verify → Prevent

2
① Scout

Gather evidence — logs, stack traces, affected files

3
② Diagnose → ③ Assess

Root-cause analysis based on evidence, then severity/impact assessment

4
④ Fix

Apply targeted fix based on diagnosed root cause

5
⑤ Verify

Run tests to confirm fix works and no regressions

6
⑥ Prevent

Add guards, tests, or documentation to prevent recurrence

/ck:fix Flags
--auto

Auto-apply fix without confirmation

--review

Review fix before applying

--quick

Fast fix without deep analysis

--parallel

Fix multiple issues in parallel

/ck:fix v2.0: evidence-based RCA, no guessing. Flags: --auto, --review, --quick, --parallel

Security Audit

Intermediate

Best for: Finding security vulnerabilities and secrets

~15-25 min 3 steps
1
/ck:security-scan Scan for vulnerabilities

Scan codebase for OWASP issues, hardcoded secrets, and dependency vulnerabilities

2
/ck:code-review --security Security-focused review

Deep code review focusing on authentication, authorization, and data handling

3
/ck:fix --security Apply security fixes

AI applies recommended security fixes with detailed explanations

What /ck:security-scan does automatically:
  • Hardcoded secrets detection
  • Dependency vulnerability scan
  • OWASP Top 10 coverage
  • Security fix recommendations
Detects SQL injection, XSS, CSRF, and other OWASP Top 10 issues

Generate Test Scenarios

Beginner

Best for: Comprehensive edge case discovery before implementation or testing

~5-10 min 1 steps
1
/ck:scenario beta 12-dimension analysis

Decompose features across 12 dimensions to generate comprehensive test scenarios

What /ck:scenario does automatically:
  • 12-dimension feature decomposition
  • Edge case and boundary condition discovery
  • Test scenario generation with priorities
  • Integration with /ck:test for execution
Use before writing tests to ensure complete coverage of edge cases

STRIDE Security Audit

Intermediate

Best for: Comprehensive STRIDE + OWASP security analysis with optional auto-fix

~10-20 min 1 steps
1
/ck:security beta STRIDE audit

STRIDE threat modeling + OWASP scan with severity categorization and optional auto-fix

What /ck:security does automatically:
  • STRIDE threat modeling framework
  • OWASP vulnerability pattern matching
  • Severity categorization and prioritization
  • Optional iterative auto-fix using autoresearch pattern
Combine with /ck:security-scan for comprehensive vulnerability + threat coverage

Planning & Review

5 workflows

Code Review with Edge Cases

Intermediate

Best for: Thorough code review with edge case scouting

~20-30 min 4 steps
1
/ck:cook @plan.md Implement the plan

AI writes the code following the plan with auto test & review cycles

2
/ck:scout Scout edge cases

AI scouts affected files, data flows, error paths, and boundary conditions

3
Code-reviewer review

Code-reviewer subagent reviews findings from scout and evaluates code quality

4
/ck:git cm Merge & commit

Commit the reviewed code with conventional commit message

What /ck:scout does automatically:
  • Edge case detection via /ck:scout
  • Boundary condition analysis
  • Data flow & error path scouting
  • Automated code-reviewer integration
/ck:scout integrates with code-reviewer for edge case detection before review

Plan + Validate + Implement

Intermediate

Best for: Validated plans with auto-propagated decisions

~20-40 min 4 steps
1
/ck:plan Create plan

AI creates a detailed implementation plan with phases

2
/ck:plan validate Validate plan decisions

Interview-style validation gate. Decisions auto-propagate to phase files

3
/clear (mandatory)

Free context before implementation. Mandatory step

4
/ck:cook @plan.md Implement validated plan

AI implements with validated decisions already propagated to each phase

What /ck:plan validate does automatically:
  • Interview-style plan validation
  • Auto-propagation to phase files
  • Validated decisions guide implementation
  • Reduced rework from unclear plan decisions
/ck:plan Flags
--hard

Complex multi-phase plan with red-team review

--parallel

Plan designed for parallel agent execution

--two

Two-phase plan (plan → implement)

validate

Interview-style validation gate

red-team

Spawn adversarial reviewers

/ck:plan validate decisions auto-propagate to phase files

Adversarial Plan Review

Advanced

Best for: Finding flaws in plans before implementation

~10-20 min 2 steps
1
/ck:plan --hard "feature" Create plan

Create a detailed plan. Hard/parallel/two modes auto-run red-team after creation

2
/ck:plan red-team plans/ Adversarial review

Spawn hostile reviewers: Security, Failure Mode, Assumption Destroyer, Scope Critic

What /ck:plan --hard "feature" does automatically:
  • Security Adversary (auth bypass, injection, OWASP)
  • Failure Mode Analyst (race conditions, data loss)
  • Assumption Destroyer (unstated deps, false claims)
  • Scope & Complexity Critic (over-engineering, YAGNI)
Auto-scales reviewers based on plan complexity (2-4 adversarial lenses)

Automated Research Loop

Intermediate

Best for: Iterative metric optimization with automated experiments

~10-30 min 1 steps
1
/ck:autoresearch beta Research loop

Run N iterations against a metric, auto-keep/discard changes based on results

What /ck:autoresearch does automatically:
  • Autonomous iteration loop
  • Git history learning between rounds
  • Auto-keep/discard based on metric delta
  • Works with any measurable metric
Set a clear, measurable metric (coverage %, bundle size, latency) for best results

Predict Impact Before Coding

Intermediate

Best for: Catching architectural, security, and performance issues before implementation

~5-10 min 1 steps
1
/ck:predict beta 5-persona debate

5 expert personas debate proposed changes — architect, security, performance, UX, ops

What /ck:predict does automatically:
  • 5 expert personas with distinct viewpoints
  • Architecture, security, performance analysis
  • UX and ops impact assessment
  • Consensus report with risk ratings
Run before major features or risky refactors to catch issues early

Research & Docs

3 workflows

Visual Documentation

Beginner

Best for: Creating visual explanations and diagrams for your plan

~10-20 min 3 steps
1
/ck:plan Create plan first

Create a structured plan. Visuals are saved into the plan directory

2
/ck:preview --explain "topic" Generate explanation

Create ASCII + Mermaid diagrams with prose explanation for your topic

3
/ck:preview --diagram "topic" Generate focused diagram

Create a focused Mermaid + ASCII diagram for a specific data flow or architecture

What /ck:preview does automatically:
  • ASCII + Mermaid diagrams (--explain)
  • Presentation format (--slides)
  • Focused diagrams (--diagram)
  • Terminal-friendly output (--ascii)
/ck:preview generates visual content. Also: --slides, --ascii

Research & Documentation

Beginner

Best for: Research topics and create technical documentation

~10-20 min 3 steps
1
/ck:research "topic" Deep research

AI researches the topic thoroughly using web search and documentation

2
/ck:docs-seeker "library" Search library docs

Search official documentation via llms.txt for up-to-date API info

3
/ck:docs Generate project docs

Create or update project documentation based on codebase analysis

What /ck:research does automatically:
  • Web search and synthesis
  • Library documentation lookup
  • Project documentation generation
  • Technical writing assistance
/ck:docs-seeker uses context7 for latest library documentation

LLMs.txt Generation

Beginner

Best for: Making your project AI-friendly for LLM consumption

~5-10 min 1 steps
1
/ck:llms [path] Generate index

Create llms.txt following llmstxt.org spec — makes your docs AI-readable

What /ck:llms [path] does automatically:
  • Follows llmstxt.org specification
  • Generates from docs, README, or codebase
  • Includes reference files and structure overview
  • Works with any project type
/ck:llms generates standardized llms.txt so AI tools can quickly understand your codebase

Shipping

3 workflows

DevOps & Deployment

Advanced

Best for: Setting up CI/CD and deployment pipelines

~20-40 min 3 steps
1
/ck:devops "setup CI/CD" Configure DevOps

Set up CI/CD pipelines for GitHub Actions, GitLab CI, or other platforms

2
/ck:deploy Deploy to platform

Deploy to Cloudflare, Vercel, GCP, or Kubernetes with auto-detection

3
/ck:test --e2e Run E2E tests

Verify deployment with end-to-end tests

What /ck:devops does automatically:
  • CI/CD pipeline generation
  • Multi-platform deployment
  • Environment configuration
  • Rollback and monitoring setup
Supports Docker, Kubernetes, serverless, and container deployments

Ship a Feature

Intermediate

Best for: Shipping feature branches with automated test, review, and PR creation

~5-10 min 1 steps
1
/ck:ship [--official|--beta] [--skip-tests] [--skip-review] Ship pipeline

Merge main, run tests, pre-landing review, bump version, update changelog, push, create PR

What /ck:ship [--official|--beta] [--skip-tests] [--skip-review] does automatically:
  • Supports official (→main) and beta (→dev) ship modes
  • Merges origin/main (or dev for beta) before testing
  • Auto-detects npm/pytest/cargo/go test
  • Two-pass code review + adversarial review (stage 3)
  • Bumps version and updates CHANGELOG.md
  • Creates PR with summary, test results, and linked issues
/ck:ship auto-detects test runner, version file format, and changelog style

Deploy Your App

Intermediate

Best for: Deploying to Vercel, Netlify, Railway, Fly.io, AWS, GCP and more

~5-15 min 1 steps
1
/ck:deploy [platform] Auto-deploy

AI detects your project type and deploys to 15+ platforms with zero manual config

What /ck:deploy [platform] does automatically:
  • Auto-detects project type (Next.js, Astro, Express, etc.)
  • Supports 15+ platforms out of the box
  • Handles env vars and build configuration
  • Vercel, Netlify, Railway, Fly.io, AWS, GCP, Azure
/ck:deploy auto-detects your stack and handles environment variables, build steps, and platform config

Backend & Infra

1 workflows

Database Operations

Intermediate

Best for: Database schema design and migrations

~15-30 min 3 steps
1
/ck:databases "schema design" Design schema

Design database schema with relationships, indexes, and constraints

2
/ck:plan "migration" Plan migration

Create a safe migration plan with rollback strategy

3
/ck:cook @plan.md Execute migration

Implement migration with proper error handling and validation

What /ck:databases does automatically:
  • Schema design with relationships
  • Index optimization
  • Migration script generation
  • Query performance analysis
Supports MongoDB, PostgreSQL, MySQL, and SQLite

Media & Creative

1 workflows

Create Video Content

Intermediate

Best for: Programmatic video creation with React

~20-40 min 2 steps
1
/ck:remotion Video creation

Create videos programmatically with React and Remotion

2
render Render output

Export to MP4, GIF, or image sequences

What /ck:remotion does automatically:
  • Animations and transitions
  • Text animations and captions
  • 3D graphics integration
  • Audio synchronization
Creates React-based video compositions

Session & Management

1 workflows

Sprint Retrospective

Beginner

Best for: Data-driven sprint reviews with git metrics, health indicators, and actionable recommendations

~2-5 min 1 steps
1
/ck:retro [timeframe] [--compare] [--team] [--format html|md] Analyze sprint

Gather git metrics (commits, LOC, hotspots, churn), compute health indicators, generate retrospective report

What /ck:retro [timeframe] [--compare] [--team] [--format html|md] does automatically:
  • Git metrics: commits/day, LOC added/removed, file hotspots
  • Health indicators: churn rate, test ratio, active day ratio
  • Period comparison with --compare flag
  • Per-author breakdown with --team flag
  • HTML or Markdown output format
/ck:retro 2w --compare --team generates a two-week retro with period comparison and per-author breakdown

Advanced

2 workflows

Agent Teams (Parallel)

Advanced

Best for: Large tasks with multiple parallel agents

~30-60 min 2 steps
1
/ck:plan --hard "feature" Create plan with phases

Create a detailed plan with parallelizable phases for team execution

2
/ck:team cook @plan Parallel team execution

Spawn parallel dev agents, each handling a phase. Auto test → review → merge

What /ck:plan --hard "feature" does automatically:
  • Parallel dev agents (--devs N)
  • Auto test → review → merge pipeline
  • Event-driven hooks + agent memory
  • Also: /ck:team research, /ck:team review, /ck:team debug
/ck:team Flags
--devs N

Number of parallel dev agents (default: 2)

--tester

Include dedicated tester agent

--reviewer

Include code reviewer agent

--worktree

Run each agent in isolated git worktree

Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in settings.json

Isolated Feature Branching

Intermediate

Best for: Parallel development in monorepos using git worktrees

~2-5 min 3 steps
1
/ck:worktree info Step 1: Get Repo Info

Parse repo type, base branch, and existing projects

2
Step 2: Detect Branch Naming Mode

Detect conventional prefix or use --no-prefix for exact Jira keys

3
Step 3: Convert to Slug

Format branch name to kebab-case (skipped if --no-prefix is active)

What /ck:worktree does automatically:
  • Isolated git worktrees per feature
  • Preserve exact issue keys (--no-prefix)
  • Auto-detect branch prefix conventions
  • Monorepo project scoping support
Use --no-prefix to preserve exact branch names for Jira keys (like ND-1377-cleanup-docs).

Pro Tips

Save tokens with /clear
Use /clear to clear conversation history before starting implementation
Reference files with @
Use @plan.md to reference specific files in commands
Use /ck:cook for implementation
After planning with /ck:plan, run /clear then /ck:cook to implement your plan
Scout before coding
Use /ck:scout to quickly find relevant files in your codebase
Debug before fixing
Use /ck:debug first to find root cause, then /ck:fix when ready
Always start with /ck:plan
Create a structured plan first, then use /ck:cook to execute it
Agent behavioral checklists
Skills include behavioral checklists that guide agent decision-making — check skill docs for details

Need more workflows? See full docs from official ClaudeKit site.