How ClaudeKit Works

ClaudeKit is not a standalone app or a new IDE. It is an advanced Framework integrated directly into your native Claude Code configuration (.claude) on your machine, transforming your terminal chat into a professional task automation system.

1. Hooks (Background System)

Background scripts that run automatically. They initialize configs and project rules so you don't have to copy-paste them manually.

2. Skills (Pre-built Knowledge)

Specialized capability packages with prompts, references, and scripts. The primary execution unit when you type /ck:* commands.

3. Agents (Specialists)

Specialized models (Planner, Tester, Reviewer) with internal prompts and tools, focusing on a single task domain.

4. Workflows (Pipelines)

Pipelines of Hooks, Skills and Agents running sequentially from your command input to handle complex workflows end-to-end.

Let's see how Hooks, Skills, Agents and Workflows coordinate a real command. Pick a workflow below and press Play to explore the internal mechanism.

No matching skills. Try another command, skill name, or keyword.

No combos for this kit

Guide coming soon...

VividKit is finalizing the detailed guide for Marketing Kit.

Step / Playing...

Quick Ref / Brainstorm command

Before /ck:plan

/ck:brainstorm

Use it when the right approach is still unclear. Scout first, lock exact requirements, debate trade-offs, then write a report and hand off to /ck:plan.

01

Scout

02

Exact reqs

03

Debate

04

Report path

Scout first

Summarize 3-6 findings before Discovery.

Report first

The plan handoff receives the brainstorm report path.

No Task-spawn

planner/docs-manager are inline consultation.

Execution Map

Four lanes: scout, clarify, evaluate, then close with report/handoff.

01

Scout

Context before questions

  1. 1 Scout MANDATORY first step — map project type, modules, patterns, docs, plans
02

Clarify

Lock the 5 exact fields

  1. 2 Discover AskUser loop — extract 5 exact items: output, acceptance, scope, constraints, touchpoints
  2. 3 Scope Decompose if 3+ independent subsystems
03

Evaluate

Trade-offs and brutal honesty

  1. 4 Research planner agent + WebSearch + docs-seeker
  2. 5 Analyze Evaluate 2-3 approaches with pros/cons via YAGNI/KISS/DRY
  3. 6 Debate Brutal honesty — challenge assumptions, present options
  4. 7 Consensus Align on chosen approach
04

Handoff

Report, then plan/end

  1. 8 Report Markdown summary via ck:project-organization
  2. 9 Handoff AskUser: /ck:plan --tdd (refactor/critical) · /ck:plan (default) · end
  3. 10 Journal /ck:journal — concise technical entry

Sample Prompt

Use different prompts for a new brainstorm, a same-session plan handoff, and a fresh-session plan.

Start brainstorm
/ck:brainstorm Choose the best auth approach for our current SaaS app

Use when: The direction is unclear and needs repo scouting plus trade-off debate first.

Expected: Writes the report at plans/reports/brainstorm-260524-1908-auth-approach.md.

Same session
/ck:plan Create an implementation plan for the auth approach we selected in brainstorm, using the report just created as context

Use when: You are still inside the brainstorm session and the agent just wrote the report.

Expected: Plan uses current context plus the report path handed off by brainstorm.

Fresh session Recommended
/ck:plan plans/reports/brainstorm-260524-1908-auth-approach.md

Use when: After a long brainstorm, start a fresh session to avoid context bloat.

Expected: Mention the file path so plan reads the correct brainstorm artifact.

Plan Handoff

Inside the brainstorm session, offer only after proposal approval, no open questions, and a written report. If starting a fresh session, make sure the brainstorm artifact exists and pass its file path to plan.

/ck:plan --tdd

Recommend when: Refactor, critical logic, or strong existing test contracts.

Result: Same session: use the report context just created. Fresh session: include the artifact path.

/ck:plan

Recommend when: Standard new feature or moderate change.

Result: Phase-by-phase implementation plan from the brainstorm report.

End session

Recommend when: Plan later or hand off elsewhere.

Result: Stop after report/journal.

Artifacts Produced

Markdown Summary Report

Brainstorm ends with one Markdown file. This file is the primary context for the /ck:plan handoff.

1 Markdown file

Concrete path

plans/reports/brainstorm-YYMMDD-HHMM-slug.md plans/reports/brainstorm-260524-1908-auth-approach.md

Report Contents

This is the outline inside the report file, not separate artifacts.

  1. 1 Problem statement The problem, target outcome, and scouted repo context.
  2. 2 Evaluated approaches 2-3 viable approaches with the main trade-offs.
  3. 3 Final recommendation The selected direction and why it won.
  4. 4 Implementation risks Failure points, dependencies, or assumptions to verify.
  5. 5 Success metrics How to know the solution is correct and complete.
  6. 6 Next steps How to hand off to /ck:plan or stop here.

Do Not Skip Design

Rule: Anti-Rationalization

Common-sounding excuses the workflow blocks before planning or coding.

1

Thought

This is too simple to need a design

Reality

Simple work wastes time when assumptions stay implicit.

2

Thought

I already know the solution

Reality

Then writing it down is quick. The written design is the alignment checkpoint.

3

Thought

The user wants action, not talk

Reality

Bad action wastes more time than a short planning loop.

4

Thought

Let me explore the code first

Reality

Brainstorming decides how to explore. Follow the process first.

5

Thought

I'll just prototype quickly

Reality

Prototypes become production code. Design first.

Quick Ref / Command

Engineer Kit

/ck:predict

Pre-implementation impact prediction: five personas debate a proposal, then optional chain modes refine tradeoffs or missing constraints.

01

Input

02

Context

03

Personas

04

Agreements

No implementation

Architecture risk

Independent persona analysis first

Security risk

STOP blocks work

Performance impact

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Input Read proposal, --files, and optional --chain
  2. 2 Context Read relevant code when --files is provided
02

Work

Agent / skill execution

  1. 3 Personas Architect, Security, Performance, UX, Devil's Advocate
  2. 4 Agreements Find 4+ persona alignments
03

Verify

Gate, review, validation

  1. 5 Conflicts Resolve meaningful disagreements
  2. 6 Verdict GO / CAUTION / STOP with risk table
04

Close

Report, handoff, artifact

  1. 7 Chain Optional --chain reason or --chain probe
  2. 8 Handoff Feed risks into ck:scenario, ck:plan, or ck:cook

Modes / Routes

--files <glob>

Read affected files before analysis

--chain reason

Use critics and blind judge for subjective tradeoffs after CAUTION

--chain probe

Generate constraint probes when CAUTION/STOP comes from missing information

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Proposal only Recommended
/ck:predict "Move notification delivery from polling to WebSockets"
Use when:
You need pre-implementation risk debate without file context.
Expected:
Five-persona GO/CAUTION/STOP report with risks and recommendations.
--files <glob>
/ck:predict "Replace REST user endpoints with GraphQL" --files src/api/**/*.ts
Use when:
Affected files should be read before persona analysis.
Expected:
Source-aware prediction with file-backed risk rows.
--chain reason
/ck:predict "Move auth sessions to Redis" --chain reason
Use when:
Verdict may involve subjective architecture tradeoffs.
Expected:
Critique/synthesis/blind-judge appendix after the base verdict.
--chain probe
/ck:predict "Use WebSockets for live notifications" --chain probe
Use when:
CAUTION/STOP may come from missing constraints or assumptions.
Expected:
Constraint probes and questions to resolve before planning.

Handled Scope

  • Architecture risk
  • Security risk
  • Performance impact
  • UX impact
  • Assumption testing

Artifacts Produced

Prediction Report

Pattern

verdict + agreements + conflicts + risks + recommendations + optional chain appendix

The report gives GO/CAUTION/STOP plus risk rows that can become scenario tests, plan constraints, or cook acceptance gates.

Quick Ref / Planning command

After brainstorm / when scope is clear

/ck:plan

Use it when the brief is clear enough to split into phases, validation gates, and a clean /ck:cook handoff.

handoff

/ck:cook {absolute-path}

01

Clear brief

02

Plan phases

03

Validate / red-team

04

/ck:cook

No implementation

Only creates plan and phase files.

CLI managed

Create and update status through ck plan.

ck plan CLI reference

Clear handoff

Ends with validate, red-team, cook, or stop.

Execution Map

Four lanes: orient scope, research, stress test, then hand off.

01

Orient

Set context before planning

  1. 1 Pre-Check Check Plan Context: active / suggested / none
  2. 2 Cross-Scan Scan unfinished plans, detect blockedBy/blocks
  3. 3 Scope Scope Challenge (skip if --fast or trivial)
  4. 4 Mode Auto-detect or explicit flag
02

Research

Collect enough evidence

  1. 5 Research Spawn researcher agents (skip in fast)
  2. 6 Analyze Read docs, scout codebase if stale
  3. 7 Plan Planner writes plan.md + phase files via ck CLI
03

Stress Test

Find weak points early

  1. 8 Red Team Adversarial review (2-4 reviewers)
  2. 9 Validate Verification pass + critical questions
04

Handoff

Make the plan executable

  1. 10 Hydrate Create Claude Tasks per phase + critical steps
  2. 11 Handoff Boundary reminder → AskUser: validate/red-team/cook/end

Mode Selection

Start with auto. Escalate only when scope or risk demands it.

--auto Auto-detect
Research
Follows mode
Red-team
Follows mode
Validate
Follows mode
Cook
Follows mode
--fast Fast
Research
Skip
Red-team
Skip
Validate
Skip
Cook

Sample prompt

/ck:plan --fast Change the CTA copy in the Pricing section

Use when

The task is small, low-dependency, and easy to roll back.

Expected

A quick plan without heavy research, red-team, or validation.

--hard Hard
Research
2 researchers
Red-team
Yes
Validate
Optional
Cook

Sample prompt

/ck:plan --hard Refactor auth flow while preserving backward compatibility

Use when

There are real technical constraints, but not a per-phase deep refactor.

Expected

Research and red-team catch architectural risk early.

--deep Deep
Research
2-3 + per-phase scout
Red-team
Yes
Validate
Yes
Cook

Sample prompt

/ck:plan --deep Split billing into subscription, invoice, webhook modules

Use when

The refactor is large, dependency-heavy, and touches multiple modules.

Expected

Deeper research, stronger validation, and evidence-backed phases.

--parallel Parallel
Research
2 researchers
Red-team
Yes
Validate
Optional
Cook
--parallel

Sample prompt

/ck:plan --parallel Optimize dashboard loading and chart rendering

Use when

The work can be split into independent tracks.

Expected

Clear boundaries that can be handed to cook with --parallel.

--two Two approaches
Research
2+ researchers
Red-team
After select
Validate
After select
Cook

Sample prompt

/ck:plan --two Choose an offline-first data sync architecture

Use when

Two approaches must be compared before committing to a plan.

Expected

Both approaches are analyzed first, then one direction is selected.

Extra Flags

Combine with a mode to change how the plan handles tests or tasks.

--tdd

Tests-first per phase

Composable flag: adds tests-first structure to each phase.

Sample prompt

/ck:plan --deep --tdd Refactor billing module

Use when

--deep --tdd is the main combo for major refactors or logic with important contracts.

--no-tasks

Skip task hydration

Do not create Claude Tasks after the plan is generated.

Sample prompt

/ck:plan --fast --no-tasks Update guide copy

Use when

Best for small or docs-only plans where extra task creation is not needed yet.

Compose With Modes

--tdd can combine with any mode, but pick the mode from scope first.

--hard --tdd

Complex, needs research

Use when the task is complex but not a major multi-area refactor.

--deep --tdd Recommended

Recommended for risky refactors

Use for large refactors, 5+ areas, architectural debt, or per-phase scouting.

--parallel --tdd

Niche: parallel + tests-first

Use only when independent workstreams can run in parallel and each lane still needs test gates.

Guide Deep dive: when to use --deep and --tdd Open the guide for when to increase planning depth or force tests-first planning. --deep --tdd

Quick Ref / Implementation command

After /ck:plan or feature brief

/ck:cook

Use it when a plan or feature brief must become working code. Scout first, lock 5 requirements, pass plan gates, implement, test, review, then sync plan/docs/git/journal.

01

Plan path / brief

02

Scout + reqs

03

Code + test

04

Review + sync

Plan-first

Even small work needs plan review before code.

Scout-first

Summarize 3-6 repo findings before any AskUser.

No side effects

Acceptance, tests, contracts, lint/type/build must stay clean.

Execution Map

Four lanes: orient intent, create an evidence-backed plan, implement/test, then review and sync artifacts.

01

Orient

Mode, scout, requirements

  1. 1 Intent Detect mode from input (plan path / keywords / explicit flag)
  2. 2 Scout MANDATORY codebase scan: project type, modules, patterns, docs, plans, contracts (skip only on plan path)
  3. 3 Summarize 3-6 bullet codebase context to user before any clarifying question
  4. 4 Requirements AskUser loop — 5 exact items: output, acceptance, scope, constraints, touchpoints
02

Plan

Research + plan review

  1. 5 Research researcher agent (skip in --fast / code mode) → Review Gate
  2. 6 Plan planner agent → plan.md + phase-XX files → Review Gate
03

Build

Implement, simplify, test

  1. 7 Implement Execute phase tasks; conditional simplify via code-simplifier
  2. 8 Test tester + debugger agents, 100% pass (skip if --no-test) → Review Gate
04

Close

Review, sync, journal

  1. 9 Review code-reviewer agent — 5 checks (acceptance, regression, contracts, patterns, lint/type/build); STOP via AskUser if side effect
  2. 10 Finalize /ck:project-management plan sync-back → docs-manager → git-manager → /ck:journal

Mode Selection

Interactive is the default. Use flags to skip research, auto-approve, run in parallel, or execute an existing plan path.

plan path

Code mode

Skip scout/research/plan and execute existing phase files.

Prompt

/ck:cook /abs/plans/260524-auth/plan.md

Use when: A reviewed plan was produced by /ck:plan or handed off from another session.

Expected: Reads phase files, implements each phase, then tests/reviews/finalizes.

--fast

Fast

Skip heavy research but still run scout -> plan -> code.

Prompt

/ck:cook --fast Change CTA copy in Pricing

Use when: Small scope, easy rollback, few dependencies.

Expected: Short plan with user gates still held before code.

--auto

Auto

Auto-approve low-risk work when artifacts + validator pass; high-risk changes still stop for user approval before finalize/commit/ship.

Prompt

/ck:cook --auto Add cache to the stats endpoint

Use when: You trust the agent, risk is low, and acceptance is clear.

Expected: Runs low-risk phases continuously while still testing and reviewing; score is advisory, never approves on its own.

--parallel

Parallel

Split independent features into separate lanes.

Prompt

/ck:cook --parallel Implement search, filters, export CSV

Use when: 3+ workstreams have clear file ownership.

Expected: Multi-agent lanes merge through review gates.

Sample Prompt

Plan path Recommended
/ck:cook /abs/plans/260524-auth/plan.md

Use when: A plan.md and phase files already exist.

Expected: Uses plan context instead of rediscovering the task.

Feature brief
/ck:cook Add email/password login with httpOnly session

Use when: No plan exists, but the desired output is clear.

Expected: Scout -> 5 requirements -> research/plan -> implement.

--tdd
/ck:cook --tdd Refactor billing calculation while preserving behavior

Use when: Refactor or critical logic.

Expected: Tests current behavior first, then verifies after implementation.

Artifacts Produced

Implementation Complete

Commits + plan status synced + journal entry
1

Code merged via git-manager

2

Tests 100% pass

3

code-reviewer approved (no regression, contracts intact)

4

plan.md + all phase-XX.md status synced via /ck:project-management

5

docs updated

6

/ck:journal entry recorded

Shortcuts Blocked

1

Thought

This is simple, just code it

Reality

Simple tasks still hide contracts. Planning is cheaper than rewriting.

2

Thought

Ask the user before reading the repo

Reality

AskUser options must come from scout findings, not generic questions.

3

Thought

Tests pass, done

Reality

Touchpoints, contracts, lint/type/build, and code-review still have to clear.

Quick Ref / Command

Engineer Kit

/ck:frontend-design

Polished frontend interface creation from briefs, screenshots, videos, 3D ideas, or redesign audits. Design-first, anti-slop, visually verified.

01

Classify

02

Design Intel

03

Dials

04

Analyze

Design intelligence first

Screenshot/video replication

Anti-slop beats generic defaults

3D/WebGL hero experiences

Analyze source media before implementation

Design dials and aesthetic direction

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Understand

Classify + design intel

  1. 1 Classify Brief, screenshot, video, describe-only, 3D, quick, immersive, redesign, or from scratch
  2. 2 Design Intel Activate ck:ui-ux-pro-max first
02

Define

Dials + analyze source

  1. 3 Dials Set variance, motion, and density unless user overrides
  2. 4 Analyze Use multimodal analysis for source media and assets
03

Build

Direction + implementation

  1. 5 Direction Commit purpose, tone, constraints, and differentiation
  2. 6 Build Implement real UI with assets, motion, accessibility, and existing stack
04

Verify

Anti-slop + responsive

  1. 7 Verify Compare visually, check anti-slop, performance, and mobile

Mode Selection

Screenshot Screenshot Replication

Pixel, spacing, color, and font matched replication from a static image.

Prompt

/ck:frontend-design Recreate this checkout UI from @checkout.png
Use when:
You have a static screenshot and need close visual replication.
Expected:
Pixel-matched UI with screenshot verification.
Video Video Replication

Layout, timing, easing, and interaction behavior from video source.

Prompt

/ck:frontend-design Replicate this onboarding animation from @demo.mp4
Use when:
Source includes interaction behavior and animation timing.
Expected:
Working UI with matched animation beats and responsive checks.
3D/WebGL 3D / WebGL

Three.js immersive scene with 60fps target and full-bleed layout.

Prompt

/ck:frontend-design Build an immersive Three.js hero for the launch page
Use when:
The primary experience requires a real 3D/WebGL scene.
Expected:
Full-bleed Three.js scene with movement, framing, and pixel checks.
Redesign Redesign

Audit and improve existing UI without rewriting the stack.

Prompt

/ck:frontend-design Redesign the pricing page without changing the stack
Use when:
An existing page needs design improvement while preserving stack.
Expected:
Audit-led redesign patch with before/after verification.

Shortcuts Blocked

💭

"Start building, we can analyze the screenshot later"

Always analyze source media before implementation. Missing details in screenshots lead to wrong spacing, colors, and interactions.

💭

"Use a generic card component, it is good enough"

Anti-slop rules override generic defaults. Design intelligence must be activated first; generic components are only acceptable when they match the specific design direction.

💭

"Redesign by switching to a different UI framework"

Redesigns must keep the existing stack and routes. Framework swaps require separate planning and are outside the redesign scope.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Screenshot Recommended
/ck:frontend-design Recreate this checkout screenshot exactly from @checkout.png
Use when:
You have a static screenshot and need close visual replication.
Expected:
Pixel/spacing/color/font matched UI plus screenshot verification.
Video
/ck:frontend-design Replicate this onboarding animation from @demo.mp4
Use when:
The source includes timing, easing, or interaction behavior.
Expected:
Working UI with matched animation beats and responsive checks.
Describe only
/ck:frontend-design Describe this settings screen from @settings.png for handoff only
Use when:
You need implementation notes without touching code.
Expected:
Developer-ready layout, style, interaction, and asset notes.
3D/WebGL
/ck:frontend-design Build an immersive Three.js hero for a developer tools dashboard
Use when:
The primary experience should be a real 3D/WebGL scene.
Expected:
Full-bleed Three.js scene with movement, framing, and pixel checks.
Quick task
/ck:frontend-design Polish the command palette empty state and mobile spacing
Use when:
The UI change is narrow and does not need full design discovery.
Expected:
Focused UI patch with responsive and anti-slop verification.
Complex / award
/ck:frontend-design Create an award-quality interactive launch page for VividKit Desktop
Use when:
The request needs a distinctive, high-craft experience.
Expected:
Immersive interface with assets, motion, performance checks, and screenshots.
Redesign
/ck:frontend-design Redesign the current pricing page without changing the stack
Use when:
An existing page needs improvement while preserving stack and routes.
Expected:
Audit-led redesign patch with before/after verification.

Handled Scope

  • Screenshot/video replication
  • 3D/WebGL hero experiences
  • Design dials and aesthetic direction
  • Asset generation and verification
  • Responsive performance guardrails

Artifacts Produced

Working UI + Verification

Pattern

implemented files + visual check notes + optional docs/design-guidelines.md

Final delivery includes working code, visual verification notes, anti-slop/performance checks, and documentation updates when approved.

Quick Ref / Review command

After /ck:cook or /ck:fix, before /ck:ship

/ck:code-review

Use it when code needs adversarial-rigor review. Resolve input mode, pass the spec-compliance gate, scout edge cases, run the code-reviewer sub-agent, then let the adversarial red-team actively try to break the code before verify + report.

01

Input + diff

02

Spec gate

03

Quality + scout

04

Adversarial + report

Spec-first gate

Stage 1 must pass — never skip to Stage 2 with spec mismatch.

Adversarial always-on

Stage 3 red-team runs every time. Scope gate exempts only trivial.

Fresh evidence

No "done" claim without rerunning tests/build with new output.

Review Map

Four lanes: resolve input + diff, pass the spec gate, run quality review with scout, then adversarial red-team + verify + report.

01

Resolve

Input mode + diff acquisition

  1. 1 Input Resolution Auto-detect mode from argument: #PR | commit | --pending | codebase | codebase parallel. If ambiguous, AskUserQuestion to choose review target.
  2. 2 Diff Acquisition Main agent fetches diff: gh pr diff #N · git show <sha> · git diff (staged + unstaged) · full codebase scan. No sub-agents at this step.
02

Spec gate

Stage 1 — code matches plan/spec?

  1. 3 Stage 1: Spec Compliance HARD GATE — main agent verifies code matches plan/spec. Missing requirements? Unjustified extras (YAGNI)? PASS → Stage 2 | FAIL → fix → re-run Stage 1.
03

Quality

Scout edge cases + Stage 2 code-reviewer

  1. 4 Edge Case Scouting Invoke /ck:scout with edge-case focus — 2-6 parallel Explore sub-agents scan data flows, error paths, boundary conditions. Findings feed Stage 2.
  2. 5 Stage 2: Code Quality code-reviewer sub-agent — standards, security, performance, edge cases from scout. For 3+ files: parallel scoped reviewers (e.g. backend + frontend).
04

Adversarial + Prove

Stage 3 red-team, verify, report

  1. 6 Stage 3: Adversarial Adversarial reviewer sub-agent (red team) actively tries to break the code — security holes, false assumptions, race conditions, resource exhaustion, supply chain. Verdicts: Accept / Reject / Defer.
  2. 7 Verification Gate IRON LAW — run build + tests, read output, confirm 0 failures with FRESH evidence before any completion claim. No "should" / "probably" / "seems to".
  3. 8 Review Report Findings grouped by severity (Critical / Important / Minor) with verdict per finding. Recommendation: APPROVE | REQUEST CHANGES | BLOCK. Critical → merge blocked.

Input Modes

Input mode picks the review target. Pick ONE — agent auto-detects from the argument, or AskUserQuestion when ambiguous. No "fast/auto" flag — every mode runs through all 3 stages.

#123

PR mode

Fetch full PR diff via gh pr diff #N.

Prompt

/ck:code-review #123

Use when: Reviewing an open GitHub PR.

Expected: Full PR diff → 3-stage review → APPROVE / REQUEST CHANGES / BLOCK recommendation.

--pending

Pending

Review staged + unstaged changes in the working tree.

Prompt

/ck:code-review --pending

Use when: Before commit, right after /ck:cook or /ck:fix.

Expected: git diff (staged + unstaged) → 3-stage review → inline findings.

abc1234

Commit

Review a specific commit via git show <sha>.

Prompt

/ck:code-review abc1234

Use when: Auditing an old commit, post-mortem regression.

Expected: That commit's diff → 3-stage review scoped to the commit.

codebase parallel

Codebase parallel

Ultrathink edge cases, then spawn adversarial reviewers in parallel.

Prompt

/ck:code-review codebase parallel

Use when: Deep audits — security review, pre-launch hardening.

Expected: Multiple scoped reviewers, dedupe + prioritize by severity.

Sample Prompt

Pending changes Recommended
/ck:code-review --pending

Use when: Just finished /ck:cook or /ck:fix, not yet committed.

Expected: Reviews all staged + unstaged before commit / ship.

PR review
/ck:code-review #42

Use when: PR is open, needs adversarial review before merge.

Expected: Findings grouped by severity + verdict per item.

Codebase audit
/ck:code-review codebase parallel

Use when: Pre-launch or whole-project security audit.

Expected: Multiple scoped reviewers, severity-dedupe in the report.

Artifacts Produced

Adversarial Review Report

Findings grouped by severity (Critical / Important / Minor) + verdict per finding + merge recommendation
1

Each finding: description, file:line, severity, verdict (Accept / Reject / Defer)

2

Critical → BLOCK merge

3

Deferred → GitHub issue

4

Recommendation: APPROVE | REQUEST CHANGES | BLOCK

5

Verification gate (tests + build) MUST pass before report finalizes

Shortcuts Blocked

1

Thought

Code compiles → review passes

Reality

Stage 1 spec compliance must verify intent matches plan/spec — compile says nothing.

2

Thought

Small diff, just skim it

Reality

Adversarial Stage 3 is still mandatory unless the scope gate hits (≤2 files, ≤30 lines, no security).

3

Thought

Tests pass = safe to merge

Reality

Critical findings still block merge. Need fresh build + test evidence — no "should/probably".

Quick Ref / Command

Engineer Kit

/ck:review-pr

Evidence-based GitHub PR review for correctness, security, breaking changes, and AI-slop — with optional fix loop and a formal reply posted back to GitHub.

01

Acquire

02

Gates

03

Review

04

Anti-slop

Evidence over rubber-stamp

Correctness and security review

Duplicate, standards, and value gates first

Breaking-change detection

Read full files, not just hunks

AI-slop taxonomy

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Acquire PR metadata, diff, CI checks, scope stat
  2. 2 Gates Duplicate, project standards, strategic necessity
02

Work

Agent / skill execution

  1. 3 Review Correctness, security, breaking changes, testing
  2. 4 Anti-slop Structural and micro slop with calibrated severity
03

Verify

Gate, review, validation

  1. 5 Fix --fix: remediate, push, watch CI, re-review
  2. 6 Verdict Approve / Request changes / Comment, optional reply

Modes / Routes

default

Review-only, findings to chat

Research:
gates
Review:
anti-slop
Validate:
verdict
--fix

Remediation loop on PR head

Research:
gates
Review:
anti-slop
Validate:
CI green
--reply

Post formal review to GitHub

Research:
gates
Review:
anti-slop
Validate:
gh review
--fix --reply

Fix loop, then post final re-review

Research:
gates
Review:
anti-slop
Validate:
CI + gh

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Review only Recommended
/ck:review-pr 123
Use when:
You want findings printed to chat with no edits to the PR.
Expected:
Risk level, gate results, findings by severity, and a verdict.
URL
/ck:review-pr https://github.com/org/repo/pull/123
Use when:
You have the PR URL instead of just the number.
Expected:
Same review-only flow resolved from the URL.
--fix
/ck:review-pr 123 --fix
Use when:
Actionable findings, conflicts, or CI failures should be remediated.
Expected:
Fix loop: ck:fix, push, watch CI, re-review until clean.
--reply
/ck:review-pr 123 --reply
Use when:
The review should land on GitHub as a formal review.
Expected:
Posts verdict via gh pr review, or prints locally if gh fails.
--fix --reply
/ck:review-pr 123 --fix --reply
Use when:
You want the fix loop and the final re-review posted to GitHub.
Expected:
Fix loop runs, then only the final re-review is posted.
Duplicate check
/ck:review-pr 456
Use when:
You suspect the change may already be merged or open elsewhere.
Expected:
Duplicate / prior-work gate flags overlap as Important.

Handled Scope

  • Correctness and security review
  • Breaking-change detection
  • AI-slop taxonomy
  • Duplicate / prior-work checks
  • CI and merge-conflict triage

Artifacts Produced

Review Report + Optional GitHub Review

Pattern

Summary + gate results + findings by severity + verdict; gh pr review on --reply

Prints a structured review (risk level, duplicate/standards/strategic gates, Critical/Important/Suggestion findings, verdict). With --reply, posts the body to GitHub mapped to the verdict, with a traceability footer and local-print fallback.

Quick Ref / Command

Engineer Kit

/ck:test

Testing and QA workflow for unit, integration, e2e, build, coverage, and browser/UI validation.

01

Dispatch

02

Scope

03

Pre-flight

04

Execute

Never ignore failing tests

Test runner detection

Root cause over symptom

Failure analysis

Pre-flight before test execution

Coverage reporting

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Dispatch

Scope + pre-flight

  1. 1 Dispatch [context] runs code tests; ui [url] runs UI tests; no args asks operation
  2. 2 Scope Recent changes, bug fix, refactor, coverage, or build validation
  3. 3 Pre-flight Typecheck/analyze before executing tests
02

Execute

Runner + analyze

  1. 4 Execute Run detected test runner
  2. 5 Analyze Failures, flakes, slow tests, skipped tests
03

Measure

Coverage + UI verify

  1. 6 Coverage Line/branch coverage and critical paths
  2. 7 UI Verify Browser, screenshot, responsive, a11y when requested
04

Report

Structured QA output

  1. 8 Report Structured QA report and organized output

Mode Selection

[context] Code Tests

Run unit, integration, e2e, coverage, and build validation for a code scope.

Prompt

/ck:test recent changes in auth module
Use when:
Code changes need automated test validation.
Expected:
Runner output, failures, coverage notes, QA report.
ui [url] UI / Browser QA

Browser, screenshot, responsive, and a11y checks on a running page.

Prompt

/ck:test ui http://localhost:4321/guides
Use when:
A rendered page needs visual and accessibility QA without code changes.
Expected:
Screenshots, console findings, a11y report, responsive notes.
(no args) Operation Picker

Asks which test operation to run when no context is provided.

Prompt

/ck:test
Use when:
You want to choose between test types interactively.
Expected:
Clarifying prompt for test scope before execution.

Shortcuts Blocked

💭

"Tests fail but the feature works, ignore them"

Never ignore failing tests. Fix root causes, not symptoms. Failing tests protect future changes.

💭

"Mock the dependency to make the test pass"

No mocks or cheats to force passing builds. Tests must reflect real behavior or they provide false confidence.

💭

"UI report mode will fix the issues it finds"

UI workflow with url argument is report-only. It captures evidence; fixes require a separate implementation step.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Default
/ck:test
Use when:
You need the command to ask which testing operation to run.
Expected:
Clarifying operation prompt instead of guessing.
[context] Recommended
/ck:test recent changes in checkout
Use when:
A code scope needs unit/integration/e2e/build validation.
Expected:
Detected runner output, failures, coverage/build notes, QA report.
ui [url]
/ck:test ui http://localhost:4321/guides/how-ck-works
Use when:
A local or deployed UI needs browser, responsive, visual, or a11y QA.
Expected:
Screenshots, console/a11y/responsive findings, no implementation in report mode.

Handled Scope

  • Test runner detection
  • Failure analysis
  • Coverage reporting
  • Build verification
  • UI/browser QA

Artifacts Produced

QA Report

Pattern

test results + coverage + failures + UI findings + build status

Reports pass/fail counts, failure root causes, coverage, UI findings, build status, recommendations, and unresolved questions.

Quick Ref / Fix command

Bug, failing CI, regression, production issue

/ck:fix

Use it when a failure needs an evidence-based repair. Pick mode, scout first, diagnose root cause, fix the cause, verify/prevent, review, then finalize.

01

Mode

02

Scout + diagnose

03

Root-cause fix

04

Verify + prevent

Root cause first

No symptom patches, no probably.

Exact repro

Capture pre-fix failure and rerun the same path.

Prevention

Regression test, blast-radius sweep, guards against recurrence.

Execution Map

Four lanes: mode/scout, root-cause diagnosis, targeted repair, then verify/prevent + finalize.

01

Start

Mode + scout evidence

  1. 0 Mode AskUser: Autonomous (default) · Review · Quick · Parallel — or pass --auto/--review/--quick/--parallel
  2. 1 Scout MANDATORY — ck:scout or 2-3 parallel Explore: affected files, deps, tests, git log, patterns
02

Diagnose

RCA with file:line

  1. 2 Diagnose MANDATORY — ck:debug + ck:sequential-thinking, capture pre-fix state, evidence-based RCA, no guessing
  2. 3 Route Classify Simple/Moderate/Complex/Parallel → workflow + TaskCreate dependency chain (Moderate+)
03

Repair

Address the root cause

  1. 4 Fix Implement ROOT CAUSE fix — minimal changes, follow existing patterns
04

Prove

Verify, prevent, finalize

  1. 5 Verify + Prevent MANDATORY — re-run exact pre-fix repro, regression test, blast-radius sweep, code-reviewer delegate, artifact gate (workflow-artifact-gate.cjs --stage finalize), prevention gate, parallel typecheck/lint/build/test
  2. 6 Finalize MANDATORY chain: /ck:project-management → docs-manager → TaskUpdate completed → git-manager (AskUser commit) → /ck:journal

Mode Selection

Autonomous is the default. Use review for high risk, quick only for tiny lint/type fixes, and parallel for independent issues.

--auto

Autonomous

Auto-approve only when artifacts + validator pass.

Prompt

/ck:fix --auto login button returns 500

Use when: The bug is clear, risk is low/moderate, and verification is straightforward.

Expected: Still runs scout/diagnose/review before finalize.

--review

Human review

Pause at each step for user approval.

Prompt

/ck:fix --review webhook duplicate charge

Use when: Production, billing, auth, data loss, or public contract risk.

Expected: Stops after diagnosis/fix/verify with concrete findings.

--quick

Quick

Scout -> diagnose -> fix -> lighter review.

Prompt

/ck:fix --quick TypeScript error in pricing card

Use when: Trivial lint/type/single-file issue.

Expected: Faster cycle without skipping root-cause checks.

--parallel

Parallel

One fullstack-developer lane per independent issue.

Prompt

/ck:fix --parallel checkout errors and dashboard chart crash

Use when: 2+ independent failures with separate touchpoints.

Expected: Separate task trees; main agent surfaces cross-issue conflicts.

Sample Prompt

Standard bug Recommended
/ck:fix Login submit returns 500 in local dev

Use when: Let the agent choose mode and scout the repo.

Expected: Mode -> Scout -> Diagnose -> Root-cause fix -> Verify.

High risk
/ck:fix --review Payment webhook double-charges paid orders

Use when: You want a user gate at every step.

Expected: No finalize/commit before user approval.

CI failure
/ck:fix --quick npm run build fails after latest merge

Use when: Build/type/lint failure appears small.

Expected: Fast repair while rerunning the exact failing command.

Artifacts Produced

Bug Fix Report

Step markers + confidence score + journal entry
1

Root cause cited file:line

2

Fix targeted

3

Regression test added

4

Blast-radius swept

5

Prevention guards in place

6

Plan/tasks synced

7

Docs updated

8

Journal recorded

Shortcuts Blocked

1

Thought

I can see the bug, just fix it

Reality

Seeing symptoms is not root cause. Scout + diagnose first.

2

Thought

Try changing X and see

Reality

Random fixes create new bugs. Build an evidence chain.

3

Thought

Fixed, tests pass

Reality

The prevention gate still needs to stop this bug class from recurring.

Quick Ref / Command

Engineer Kit

/ck:security-scan

Lightweight security scanner for hardcoded secrets, dependency issues, and common OWASP-style code patterns.

01

Detect

02

Secrets

03

Deps

04

Patterns

Secrets run first

Secret detection

No raw secret output

Dependency audit

Report-only, no automatic code changes

OWASP-style code patterns

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Detect Project type and scope
  2. 2 Secrets Grep secret patterns, verify, redact
02

Work

Agent / skill execution

  1. 3 Deps npm audit or pip audit when applicable
  2. 4 Patterns OWASP-style code pattern analysis
03

Verify

Gate, review, validation

  1. 5 Env Check .env tracking and .gitignore coverage
  2. 6 Report Markdown findings and recommendations

Modes / Routes

--secrets-only

Only secret and credential detection

Validate:
redacted output
--deps-only

Only dependency audit

Validate:
severity parse
--full

Full project scan

Validate:
secrets + deps + code patterns

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Scope Recommended
/ck:security-scan src/api/
Use when:
You want a focused scan of one app area.
Expected:
Report-only findings for secrets, deps when relevant, and code patterns.
--secrets-only
/ck:security-scan --secrets-only
Use when:
You only need credential/secret exposure detection.
Expected:
Redacted secret findings and rotation guidance for real credentials.
--deps-only
/ck:security-scan --deps-only
Use when:
You only need dependency vulnerability audit.
Expected:
npm/pip audit summary with severity parsing.
--full
/ck:security-scan --full
Use when:
You need the full lightweight security sweep.
Expected:
Secrets, dependency, OWASP-style pattern, .env exposure report.

Handled Scope

  • Secret detection
  • Dependency audit
  • OWASP-style code patterns
  • .env exposure check
  • Severity-ranked reporting

Artifacts Produced

Security Scan Report

Pattern

chat markdown report or plans/reports/security-scan-{date}.md in cook --auto

Includes project, scan date, files checked, severity summary by Secrets/Deps/Code, findings, and recommendations.

Quick Ref / Command

Engineer Kit

/ck:ship

Unified ship pipeline from feature branch to PR URL: issue trace, merge target, test, review, version, changelog, commit, push, and PR.

01

Pre-flight

02

Issues

03

Merge

04

Tests

One command from branch to PR URL

Branch safety

Never force push

Issue/PR traceability

Tests and critical review issues block

Test runner detection

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Pre-flight

Branch, mode, issues

  1. 1 Pre-flight Branch, mode, target, status, diff/log, dry-run
  2. 2 Issues Find/create GitHub issues for traceability
  3. 3 Merge Fetch + merge origin/<target>
02

Validate

Tests + code review

  1. 4 Tests tester sub-agent runs auto-detected tests
  2. 5 Review code-reviewer two-pass review
03

Release

Version, changelog, commit

  1. 6 Release Notes Version bump, changelog, journal, docs
  2. 7 Commit Stage, scan secrets, conventional commit
04

Ship

Push + PR URL

  1. 8 PR URL Push without force, create or edit PR

Mode Selection

official Official

Full pipeline targeting main/master with docs and changelog.

Prompt

/ck:ship
Use when:
Feature complete, ready for production.
Expected:
Full test + review + version bump + PR to main.
beta Beta

Target dev/beta/develop; skip docs update.

Prompt

/ck:ship beta
Use when:
Intermediate merge for testing.
Expected:
Tests + review + PR to dev branch, no docs.
--dry-run Dry Run

Show plan and stop after pre-flight check.

Prompt

/ck:ship --dry-run
Use when:
Preview what ship would do before committing.
Expected:
Prints planned steps without executing.

Shortcuts Blocked

💭

"Tests pass, just push"

Code review must pass too. Review catches logic bugs that tests miss.

💭

"Force push to fix the commit"

Ship never force pushes. Create a new commit instead.

💭

"Skip version bump, it is just a small fix"

Every ship produces a version. Patch for fixes, minor/major requires user approval.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

official Recommended
/ck:ship official
Use when:
Shipping a completed feature branch to main/master.
Expected:
Full pipeline: tests, review, version/changelog, docs, push, PR URL.
beta
/ck:ship beta
Use when:
Shipping to dev/beta/develop with lighter docs handling.
Expected:
Target beta branch, run tests/review, skip official docs update.
--skip-tests
/ck:ship official --skip-tests
Use when:
Tests already passed and you explicitly accept skipping that gate.
Expected:
Ship pipeline skips test step but still reviews and creates PR.
--skip-review
/ck:ship beta --skip-review
Use when:
A trusted review already happened and you only need the remaining ship steps.
Expected:
Pipeline skips pre-landing review and reports the skipped gate.
--skip-journal
/ck:ship official --skip-journal
Use when:
You do not want background journal generation for this ship.
Expected:
PR pipeline runs without journal output.
--skip-docs
/ck:ship official --skip-docs
Use when:
Docs are unchanged or will be handled separately.
Expected:
Official ship skips docs-manager background update.
--dry-run
/ck:ship --dry-run
Use when:
You want the exact ship plan before any mutation.
Expected:
Pre-flight plan only; no merge, commit, push, or PR.

Handled Scope

  • Branch safety
  • Issue/PR traceability
  • Test runner detection
  • Pre-landing review
  • Version/changelog automation

Artifacts Produced

Pull Request Created

Pattern

PR URL + linked issues + test/review results + ship mode

Final visible output is the PR URL with structured body and linked issues.

Quick Ref / Command

Engineer Kit

/ck:vibe

Full autonomous pipeline that takes a GitHub issue or feature request from planning through implementation, PR review, and optional merge with CI convergence.

01

Parse

02

Worktree

03

Plan + Gates

04

Issue

One command from request to PR

Issue-to-PR orchestration

Treat the GitHub issue as source of truth

Worktree isolation

Always validate and red-team the plan

TDD planning gates

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Intake

Parse + worktree

  1. 1 Parse Resolve repo, classify feature/bugfix route
  2. 2 Worktree Isolated branch via /ck:worktree
02

Plan

Plan gates + issue

  1. 3 Plan + Gates TDD plan, validate, red-team
  2. 4 Issue Create/update issue and labels
03

Build

Cook or fix

  1. 5 Cook / Fix ck:cook (feature) or ck:fix (bugfix)
04

Ship

Review PR + merge

  1. 6 Ship + Review code-review, ship PR, review-pr --fix --reply
  2. 7 Merge + CI With --ship: merge, watch and fix CI

Mode Selection

default PR Only (Default)

No --ship: stops once the PR is reviewed, fixed, replied, and labeled ready to ship stable.

Prompt

/ck:vibe https://github.com/org/repo/issues/42
Use when:
You want a human to approve the merge.
Expected:
Worktree, validated plan, cook/fix, reviewed PR, ready label.
--ship Ship + CI Watch

Merges the PR per branch protection and watches/fixes target-branch CI until green or a true external blocker.

Prompt

/ck:vibe --ship https://github.com/org/repo/issues/42
Use when:
You trust the pipeline to merge and converge CI.
Expected:
Full pipeline plus merge and post-merge CI convergence.
--beta Beta Target

Ships to beta/dev via /ck:ship beta with final label ready to ship beta.

Prompt

/ck:vibe --ship --beta https://github.com/org/repo/issues/42
Use when:
The change goes to the beta/dev branch first.
Expected:
Beta ship target with beta-labeled issue and PR.
route Cook vs Fix Routing

Bug, regression, or failing CI routes to /ck:fix --auto; net-new or refactor routes to /ck:cook --tdd --auto.

Prompt

/ck:vibe https://github.com/org/repo/issues/57
Use when:
The issue type decides the implementation skill.
Expected:
Route-appropriate skill with its own hard gates honored.

Shortcuts Blocked

💭

"Vibe writes the production code itself"

It orchestrates /ck:plan, /ck:cook, /ck:fix, /ck:ship, and /ck:review-pr. Each underlying skill keeps its own gates; vibe never bypasses them.

💭

"--ship will merge no matter what"

--ship merges per branch protection and required checks. It never force-pushes or direct-pushes a protected branch, and stops on a true external blocker.

💭

"CI failures can be hidden to get green"

Missing secrets, unavailable services, or required human approval are recorded as external blockers. Tests are never weakened to pass.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Issue → PR Recommended
/ck:vibe https://github.com/org/repo/issues/42
Use when:
You want one command to take a GitHub issue through plan, implementation, and a reviewed PR.
Expected:
Worktree, validated TDD plan, cook/fix, PR reviewed/fixed/replied, labeled ready (no merge).
--ship
/ck:vibe --ship https://github.com/org/repo/issues/42
Use when:
You want the full run to also merge and watch CI until green.
Expected:
Same pipeline plus merge per branch protection and CI convergence.
--beta
/ck:vibe --ship --beta https://github.com/org/repo/issues/42
Use when:
You target the beta/dev branch instead of stable.
Expected:
Ships via /ck:ship beta; final label "ready to ship beta".
Feature request
/ck:vibe --ship "Add CSV export to the reports page"
Use when:
Input is natural language and no issue exists yet.
Expected:
Creates the issue after plan validation, then runs the full pipeline.
Bugfix route
/ck:vibe https://github.com/org/repo/issues/57
Use when:
The issue is a bug, regression, or failing CI.
Expected:
Routes to /ck:fix --auto with failure evidence and the validated plan.
Reuse plan
/ck:vibe https://github.com/org/repo/issues/61
Use when:
The issue or worktree already links a valid plan.md.
Expected:
Skips /ck:plan --tdd but still validates and red-teams the plan.

Handled Scope

  • Issue-to-PR orchestration
  • Worktree isolation
  • TDD planning gates
  • Cook/fix routing
  • PR review and CI convergence

Artifacts Produced

Vibe Result Report

Pattern

Source, branch/worktree, plan, issue URL, PR URL, mode, route, review, merge, CI status

Ends with a Vibe Result block linking the issue and PR, plus mode (official/beta), route (feature/bugfix), review outcome with fix iterations, merge status (skipped/merged/blocked), and CI status (green/failed/blocked).

Quick Ref / Command

Engineer Kit

/ck:deploy

Auto-detects deployment target, runs the selected platform deploy, verifies the URL, and records docs/deployment.md.

01

Detect

02

Recommend

03

Ask

04

CLI/Auth

Detect-first deployment

Platform config detection

Ask before choosing if no target is detected

Cost-aware recommendation

Secret-safe output

CLI auth/deploy

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Detect

Target + platform

  1. 1 Detect Read deployment docs, config, and project type
  2. 2 Recommend Cost-ordered platform options
  3. 3 Ask AskUserQuestion when target is unknown
02

Deploy

CLI + run

  1. 4 CLI/Auth Install/check CLI and authentication
  2. 5 Deploy Run platform deploy command
03

Confirm

URL + docs

  1. 6 Verify Verify deployment URL
  2. 7 Document Create/update docs/deployment.md or escalate to ck:devops

Mode Selection

(auto) Auto-detect

Reads deployment docs, config files, and project type to choose the best platform.

Prompt

/ck:deploy
Use when:
The repo has deployment config and you want the smart default.
Expected:
Detected platform, deploy run, verified URL, updated docs/deployment.md.
[platform] Named Platform

Target a specific hosting platform by name.

Prompt

/ck:deploy vercel
Use when:
You already know the desired provider and want to skip detection.
Expected:
Loads that platform reference only, deploys, verifies URL, updates docs.
[platform] [env] Platform + Env

Specify both provider and environment for production-safe deploy.

Prompt

/ck:deploy cloudflare production
Use when:
Multiple environments exist and production safety gates matter.
Expected:
Provider-specific deploy with production checks and rollback docs.

Shortcuts Blocked

💭

"Just deploy, docs can come later"

Deployment docs must be created or updated every time. They become the source of truth for rollback and future deploys.

💭

"I can put the API key in the deploy command"

Never expose secrets in deploy output or logs. Use platform environment variable vaults.

💭

"The deploy command succeeded so the app is live"

Always verify the deployment URL after every deploy. A successful CLI exit does not guarantee the URL is reachable.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Auto-detect Recommended
/ck:deploy
Use when:
The repo has deployment docs/config and should choose from source signals.
Expected:
Detected platform or AskUserQuestion if target stays unclear.
[platform]
/ck:deploy vercel
Use when:
You already know the desired hosting platform.
Expected:
Loads only that platform reference, deploys, verifies URL, updates docs.
[environment]
/ck:deploy production
Use when:
The target environment matters more than the provider name.
Expected:
Production deploy path with URL verification and docs/deployment.md update.
Platform + env
/ck:deploy cloudflare production
Use when:
You need a specific provider/environment pair.
Expected:
Provider-specific deploy with production-safe checks and documented rollback.

Handled Scope

  • Platform config detection
  • Cost-aware recommendation
  • CLI auth/deploy
  • URL verification
  • Rollback documentation

Artifacts Produced

Deployment Docs

Pattern

docs/deployment.md

Records platform, production URL, deploy command, env vars, custom domain, rollback, and troubleshooting.

Quick Ref / Project bootstrap From blank idea to running project

/ck:bootstrap

End-to-end project bootstrapping from idea to running code. Default is interactive; autonomous behavior requires an explicit flag.

01

Repo + scope

02

Research + design

03

Plan -> Cook

04

Docs + handoff

Default interactive

New project architecture

Delegate plan then cook

Stack selection

Docs under ./docs and plans under ./plans

Design scaffolding

Bootstrap Pipeline

Main pipeline: initialize repo, research/design, plan, cook the implementation, then close with docs and handoff.

01

Start

Repo, requirements, mode

  1. 1 Git Init Ensure repo exists
  2. 2 Clarify Gather requirements by mode
02

Discovery

Research, stack, design gate

  1. 3 Research Short researcher reports
  2. 4 Stack Choose tech stack and docs
  3. 5 Design Wireframes and design gate
03

Build

ck:plan -> ck:cook

  1. 6 Plan ck:plan with mapped mode
  2. 7 Cook ck:cook implements, tests, reviews
04

Close

Docs, onboard, report

  1. 8 Finalize Docs, onboarding, report, commit prompt, journal

Modes / Flags

--full Recommended

Default interactive; gates every major phase; ck:plan --hard

Research:
Yes
Cook:
interactive cook
--auto

Explicit autonomous; design gate only; ck:plan/cook --auto

Research:
Yes
Cook:
auto cook
--fast

Fast path; ck:plan --fast; interactive cook gates remain

Research:
Light
Cook:
interactive cook
--parallel

Parallel plan/cook with design gate

Research:
Parallel
Cook:
parallel cook

Sample Prompt

Each row is a concrete invocation for a supported mode.

--full Recommended
/ck:bootstrap "Customer support portal with auth and ticket inbox" --full
Use when:
You want the default interactive route with gates at major phases.
Expected:
Research, stack, design, ck:plan --hard, interactive ck:cook, docs.
--auto
/ck:bootstrap "Internal CRM with import/export" --auto
Use when:
You explicitly opt into autonomous execution while keeping design approval.
Expected:
ck:plan/cook --auto after design gate and final report.
--fast
/ck:bootstrap "Static docs site for API examples" --fast
Use when:
You need a faster scaffold with lighter research.
Expected:
ck:plan --fast, interactive cook gates, concise docs.
--parallel
/ck:bootstrap "SaaS analytics app with billing and dashboard" --parallel
Use when:
Work can be split across file ownership and parallel cook execution.
Expected:
Parallel plan/cook path with design gate and dependency graph.

Artifacts Produced

Bootstrapped Project

./docs + ./plans + final report + unresolved questions

Creates project docs, plans, implementation, onboarding notes, final report, and journal entry.

Quick Ref / Command

Engineer Kit

/ck:autoresearch

Autoresearch family router: chooses loop, predict, scenario, or security workflows for bounded autonomous iteration.

01

Ask

02

Classify

03

Route

04

Bound

Router first

Autonomous metric loops

Bound every loop

Persona prediction

Verify before keep

Scenario generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Classify

Intent → family

  1. 1 Ask Autoresearch-style request or discovery question
  2. 2 Classify Metric, prediction, scenario, security, or missing mode
02

Route

Dispatch to skill

  1. 3 Route Send work to loop, predict, scenario, or security
  2. 4 Bound Resolve inputs, flags, iterations, verify/guard rules
03

Iterate

Bounded loops

  1. 5 Iterate Run chosen family workflow with stop conditions
  2. 6 Verify Metric, novelty, STRIDE/OWASP, tests, or guard proof
04

Emit

Artifact + follow-up

  1. 7 Report Emit routed artifact and follow-up path

Mode Selection

/ck:loop Metric Loop

Bounded atomic keep/discard loop until a numeric goal is met.

Prompt

/ck:loop Goal: branch coverage >80 | Scope: src/**/*.ts | Verify: npm run coverage:score | Iterations: 8
Use when:
You have a measurable metric to improve autonomously.
Expected:
Atomic iteration log with metric delta and kept/discarded changes.
/ck:predict Predict

Five-persona GO/CAUTION/STOP debate on a proposal before implementation.

Prompt

/ck:predict "Add Redis sessions" --files src/auth/**
Use when:
A risky proposal needs architecture debate before code changes.
Expected:
Verdict with ranked risk table and chain options.
/ck:scenario Scenario

Edge-case discovery with novelty deduplication and saturation stop.

Prompt

/ck:scenario src/checkout.ts --saturation --domain security
Use when:
A feature or code area needs comprehensive risk and edge-case mapping.
Expected:
Scenario report with severity, coverage matrix, saturation condition.
/ck:security Security

STRIDE/OWASP audit with optional red-team and fix loop.

Prompt

/ck:security full --red-team --iterations 12
Use when:
Security discovery needs attacker-persona iteration.
Expected:
Severity-ranked findings with bounded red-team search.

Shortcuts Blocked

💭

"Just run autoresearch, it will figure out the workflow"

autoresearch is a router, not an executor. It maps you to the right family skill; it does not run loops or audits directly.

💭

"The loop succeeded, keep all changes"

Only keep changes verified by the Verify command. Failed Verify or Guard condition means discard and revert.

💭

"Increase iterations for better results"

Unbounded loops risk runaway cost and inconsistent state. Always set a finite Iterations value and a Guard condition.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Router Recommended
/ck:autoresearch Which autoresearch-family command should improve coverage safely?
Use when:
You need the family map before choosing a concrete workflow.
Expected:
Routes to loop, predict, scenario, or security instead of pretending to execute directly.
Metric loop
/ck:loop Goal: raise branch coverage | Scope: src/**/*.ts | Verify: npm run coverage:score | Iterations: 8 | Direction: higher
Use when:
A measurable metric should improve over bounded iterations.
Expected:
Atomic keep/discard loop with fresh metric evidence.
Predict
/ck:predict "Add organization roles and project permissions" --files src/**/*.ts
Use when:
A risky proposal needs persona debate before implementation.
Expected:
GO/CAUTION/STOP report with file-aware risks.
Reason chain
/ck:predict "Choose session cookies vs JWT" --chain reason
Use when:
The decision is subjective and needs critique/synthesis.
Expected:
Reasoning chain appendix after the base verdict.
Probe chain
/ck:predict "Move guide data loading to runtime API" --chain probe
Use when:
Missing constraints may change the answer.
Expected:
Constraint probes before planning.
Scenario loop
/ck:scenario src/middleware/auth.ts --saturation --domain security --focus security
Use when:
Risk discovery should continue until novelty is exhausted.
Expected:
Scenario report with saturation stop condition.
Security red-team
/ck:security src/api/**/*.ts --red-team --iterations 16
Use when:
Security discovery needs attacker-persona iteration.
Expected:
Severity-ranked findings with bounded red-team search.
Security fix
/ck:security full --red-team --fix --iterations 10
Use when:
You explicitly allow remediation after audit.
Expected:
Audit, targeted fixes, guard verification, and stop report.

Handled Scope

  • Autonomous metric loops
  • Persona prediction
  • Scenario generation
  • Security red-team
  • Guarded rollback

Artifacts Produced

Routed Autoresearch Artifacts

Pattern

family map, prediction/scenario/security reports, loop-results.tsv, security-audit-results.tsv

Outputs depend on routed workflow: family map, bounded loop metrics, prediction verdict, scenario coverage, or security audit/fix report.

Quick Ref / Command

Engineer Kit

/ck:backend-development

Backend capability router for APIs, auth, databases, performance, microservices, tests, and production operations.

01

Target

02

Scout

03

Contract

04

Data + Auth

Contract before code

REST/GraphQL/gRPC APIs

Security on every public endpoint

Authentication and RBAC

Migrations need rollback

Database schema and performance

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Target Framework, API style, datastore, runtime
  2. 2 Scout Routes, modules, schemas, auth, tests, deploy files
02

Work

Agent / skill execution

  1. 3 Contract REST/OpenAPI, GraphQL schema, or proto
  2. 4 Data + Auth Schema, indexes, validation, RBAC, rate limits
03

Verify

Gate, review, validation

  1. 5 Build Implement idiomatic modules/services
  2. 6 Verify Unit, integration, E2E, contract, load, security
04

Close

Report, handoff, artifact

  1. 7 Operate Docker, CI/CD, health, logs, metrics, tracing

Modes / Routes

API design

REST, GraphQL, or gRPC contract route

Research:
contract
Review:
versioning
Validate:
docs/tests
Auth/security

OAuth, JWT, RBAC, MFA, OWASP route

Research:
threats
Review:
security
Validate:
tests/scan
Data/perf

Postgres, MongoDB, Redis, indexes, caching

Research:
query plans
Review:
stale data
Validate:
benchmarks
Architecture

Monolith, microservices, CQRS, saga, events

Research:
boundaries
Review:
failure modes
Validate:
contracts
Ops

Docker, Kubernetes, CI/CD, observability

Research:
platform
Review:
rollback
Validate:
health checks

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

NestJS REST Recommended
/ck:backend-development NestJS build a REST orders API with PostgreSQL migrations, RBAC, and OpenAPI docs
Use when:
A TypeScript backend needs contract, auth, data, and docs.
Expected:
API modules, migrations, RBAC, tests, OpenAPI output.
FastAPI auth
/ck:backend-development FastAPI design OAuth 2.1 login with PKCE, refresh rotation, and Redis sessions
Use when:
The main backend concern is auth/session architecture.
Expected:
Auth design and implementation plan with security gates.
Django performance
/ck:backend-development Django optimize slow admin reports using indexes, query plans, and caching
Use when:
Queries or reports are too slow.
Expected:
Query plan, indexes/cache path, benchmarks, regression checks.
Go gRPC
/ck:backend-development Go Gin create a gRPC inventory service with protobuf contracts and contract tests
Use when:
Service-to-service contracts matter.
Expected:
Proto contracts, service handlers, contract tests.
Cache
/ck:backend-development Node.js add Redis cache-aside for product search without stale pricing
Use when:
Performance needs caching but correctness matters.
Expected:
Cache policy, invalidation path, tests for stale data.
Microservices
/ck:backend-development microservices split billing into invoice, subscription, and webhook services with saga compensation
Use when:
A domain boundary split needs ownership and failure handling.
Expected:
Service boundaries, saga compensation, contract tests.
Testing
/ck:backend-development testing add unit, integration, E2E, migration, and load tests for checkout APIs
Use when:
Backend quality gates are missing or weak.
Expected:
Layered test plan and runnable validation commands.
DevOps
/ck:backend-development devops containerize the API with Docker, Kubernetes health checks, canary deploy, and OpenTelemetry
Use when:
The backend must be production-operated.
Expected:
Container/deploy/health/observability assets.

Handled Scope

  • REST/GraphQL/gRPC APIs
  • Authentication and RBAC
  • Database schema and performance
  • Microservices boundaries
  • CI/CD and observability

Artifacts Produced

Backend Deliverables

Pattern

API contracts + modules/services + migrations + tests + deploy/observability assets

Outputs depend on route: contracts, backend modules, auth policies, schemas, migrations, tests, containers, CI, monitoring, docs, and runbooks.

Quick Ref / Command

Engineer Kit

/ck:better-auth

Better Auth setup for TypeScript apps: email/password, OAuth, MFA, passkeys, organizations, sessions, and production hardening.

01

Detect

02

Choose

03

Configure

04

Schema

TypeScript app first

Email/password auth

Database before schema

OAuth providers

Never expose secrets

MFA and passkeys

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Detect Framework, package manager, DB/ORM, existing auth
  2. 2 Choose Email, OAuth, passwordless, MFA, orgs, sessions
02

Work

Agent / skill execution

  1. 3 Configure Server auth instance, providers, plugins
  2. 4 Schema Generate/migrate after adapter and plugins
03

Verify

Gate, review, validation

  1. 5 Mount Framework API handler and client instance
  2. 6 Wire UI Sign-up, sign-in, session, reset, MFA/passkey screens
04

Close

Report, handoff, artifact

  1. 7 Harden Cookies, rate limits, email callbacks, protected routes
  2. 8 Verify End-to-end auth flows and production checks

Modes / Routes

email/password

Built-in credential auth

Research:
DB
Review:
password policy
Validate:
signup/signin
oauth

GitHub, Google, or social providers

Research:
provider app
Review:
redirects
Validate:
callback
2FA/passkeys

MFA and passwordless plugins

Research:
browser/device
Review:
recovery
Validate:
schema regen
organizations

Teams, tenants, roles, invites

Research:
role model
Review:
permissions
Validate:
membership tests
production

Sessions, cookies, rate limits, email

Research:
env
Review:
secrets
Validate:
e2e

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Email/password Recommended
/ck:better-auth add email/password auth to this Next.js app with PostgreSQL
Use when:
You need standard account signup/signin.
Expected:
Server/client config, schema, route handler, UI and tests.
OAuth
/ck:better-auth configure GitHub and Google OAuth with account linking
Use when:
Social login is the primary auth path.
Expected:
Provider config, callback handling, account-linking checks.
Prisma schema
/ck:better-auth set up Better Auth with Prisma and generate the schema
Use when:
Database adapter and migrations are the main risk.
Expected:
Adapter config plus schema generation/migration path.
2FA
/ck:better-auth add 2FA with TOTP, backup codes, and admin-only enforcement
Use when:
Extra account security is required.
Expected:
Plugin setup, schema regeneration, enrollment and recovery flows.
Passkeys
/ck:better-auth add passkeys as a passwordless option while keeping password fallback
Use when:
You want passwordless auth with fallback.
Expected:
WebAuthn/passkey route with fallback and browser checks.
Magic link
/ck:better-auth implement magic link login with short-lived links
Use when:
Email-first passwordless login is preferred.
Expected:
Magic link config, email callback, expiry and replay checks.
Organizations
/ck:better-auth add organization support with owner/admin/member roles
Use when:
The app needs team or tenant membership.
Expected:
Organization plugin, roles, invites, schema update.
Production hardening
/ck:better-auth harden sessions, secure cookies, revoke devices, and rate-limit sign-in
Use when:
Auth works but production risk remains.
Expected:
Session policy, cookie config, rate limits, validation report.

Handled Scope

  • Email/password auth
  • OAuth providers
  • MFA and passkeys
  • Organizations/RBAC
  • Session hardening

Artifacts Produced

Auth Implementation Assets

Pattern

auth server/client config + API route + schema/migrations + auth UI + protected routes

Outputs Better Auth server and client setup, generated schema or migrations, route handlers, UI flows, protected route middleware, and validation notes.

Quick Ref / Command

Engineer Kit

/ck:context-engineering

Diagnose context budgets, degradation, compression, memory, multi-agent isolation, evaluation, and tool design.

01

Classify

02

Load Narrow

03

Inspect

04

Score Risk

Context quality beats quantity

Token budgets

Measure before optimizing

Context degradation

Progressive disclosure

Compression quality

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Classify Runtime, degradation, optimization, memory, agents, tools
  2. 2 Load Narrow Smallest relevant topic/context only
02

Work

Agent / skill execution

  1. 3 Inspect Usage, context percent, transcript, or artifact signals
  2. 4 Score Risk Lost-in-middle, poisoning, stale docs, weak trail
03

Verify

Gate, review, validation

  1. 5 Choose Strategy Write, Select, Compress, or Isolate
  2. 6 Apply Budget, compaction, memory, probes, tool redesign
04

Close

Report, handoff, artifact

  1. 7 Return Diagnosis, thresholds, next actions, reusable artifact

Modes / Routes

runtime

Usage and context-window awareness

Research:
signals
Review:
thresholds
Validate:
70/80/90
degradation

Lost-in-middle, poisoning, stale context

Research:
transcript
Review:
contradictions
Validate:
diagnosis
optimization

Compaction, masking, cache ordering

Research:
budget
Review:
quality loss
Validate:
probe
memory

Cross-session memory architecture

Research:
entities
Review:
staleness
Validate:
retrieval
multi-agent

Context isolation and coordination

Research:
task split
Review:
cost
Validate:
handoff
tool design

Tool consolidation and clearer descriptions

Research:
tool list
Review:
overload
Validate:
recoverability

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Degradation Recommended
/ck:context-engineering why is this session getting worse after long debugging?
Use when:
Answer quality degraded as the session grew.
Expected:
Diagnosis of lost-in-middle, poisoning, stale context, or artifact drift.
Compaction
/ck:context-engineering check whether our current context needs compaction before continuing
Use when:
Context usage may be near warning thresholds.
Expected:
Threshold-based recommendation and continuation summary shape.
Budget
/ck:context-engineering design a token budget for an agent with tools, docs retrieval, and long history
Use when:
You need a context allocation plan.
Expected:
Budget split for system, tools, docs, history, and buffer.
Analyze file
/ck:context-engineering analyze this context file with a 200k token limit and auth, migration, rollback as critical keywords
Use when:
You have a transcript/context artifact to inspect.
Expected:
Context health report with keyword retention risks.
Probes
/ck:context-engineering generate probe questions to test whether this compacted handoff preserves file changes and decisions
Use when:
A summary needs quality checks.
Expected:
Probe set for recall, artifacts, continuation, decisions.
Multi-agent
/ck:context-engineering compare single-agent vs multi-agent design for this repo analysis pipeline
Use when:
Architecture depends on context isolation tradeoffs.
Expected:
Agent partition recommendation with cost/risk notes.
Memory
/ck:context-engineering design a memory system for cross-session project decisions
Use when:
Knowledge must persist across sessions.
Expected:
Memory layers, retrieval path, consolidation rules.
Tool design
/ck:context-engineering reduce our MCP tool list without losing capability
Use when:
Tool overload is hurting context quality.
Expected:
Tool consolidation audit and clearer descriptions.

Handled Scope

  • Token budgets
  • Context degradation
  • Compression quality
  • Memory architecture
  • Tool description design

Artifacts Produced

Context Engineering Artifacts

Pattern

context health report, budget JSON, compression evaluation, probe set, memory/tool design audit

Outputs diagnostics and reusable artifacts for context health, token budgets, compression quality, memory layers, and tool simplification.

Quick Ref / Command

Engineer Kit

/ck:docs-seeker

Current documentation lookup via llms.txt and Context7, with topic/general routing and repository fallback.

01

Parse

02

Detect

03

Fetch

04

Analyze

Scripts first

Context7 docs lookup

Official docs over tutorials

llms.txt analysis

Fallback deliberately

Versioned documentation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Parse Library, topic, version, language, or repo
  2. 2 Detect Topic-specific vs general docs query
02

Work

Agent / skill execution

  1. 3 Fetch Context7/llms path with automatic fallback
  2. 4 Analyze Prioritize URLs and choose agent fanout if broad
03

Verify

Gate, review, validation

  1. 5 Fallback Repo analysis with package/context pack if docs missing
  2. 6 Answer Concise docs answer with sources and caveats

Modes / Routes

topic-search

Specific feature, component, or API

Research:
1-5 URLs
Review:
fallback
Validate:
source
library-search

General documentation sweep

Research:
5-20 URLs
Review:
prioritize
Validate:
coverage
repo-analysis

Fallback when docs are missing

Research:
clone/pack
Review:
confidence
Validate:
caveats
version-specific

Versioned docs or explicit caveat

Research:
version
Review:
staleness
Validate:
version
plugin-focused

Narrow a broad ecosystem to one plugin

Research:
scope
Review:
overbreadth
Validate:
target

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Topic search Recommended
/ck:docs-seeker Next.js caching strategies
Use when:
You need docs for one specific API/topic.
Expected:
Topic-specific docs with fallback to general docs.
Component docs
/ck:docs-seeker shadcn/ui date picker
Use when:
A UI/library component API is needed.
Expected:
Current component docs and implementation caveats.
General library
/ck:docs-seeker Documentation for Astro
Use when:
You need broad library documentation.
Expected:
llms.txt analysis and priority URL grouping.
Auth docs
/ck:docs-seeker Better Auth OAuth setup
Use when:
A framework integration needs official setup details.
Expected:
OAuth setup docs with provider/config caveats.
Version docs
/ck:docs-seeker React Hook Form v8 migration docs
Use when:
Version-specific behavior matters.
Expected:
Versioned docs or explicit caveat if unavailable.
Language docs
/ck:docs-seeker SvelteKit docs in Japanese
Use when:
Docs language preference matters.
Expected:
Language-specific attempt with English fallback.
Plugin scope
/ck:docs-seeker Fastify plugins: auth only
Use when:
A broad ecosystem needs narrow plugin scope.
Expected:
Plugin-focused docs instead of broad sweep.
Repo fallback
/ck:docs-seeker analyze docs for github.com/org/obscure-library
Use when:
Context7 or llms.txt may not cover the project.
Expected:
Fallback to repository analysis with source confidence.

Handled Scope

  • Context7 docs lookup
  • llms.txt analysis
  • Versioned documentation
  • Repo fallback
  • Source confidence

Artifacts Produced

Documentation Lookup Result

Pattern

classification JSON + fetched docs/URL groups + source-cited answer or repo fallback report

Outputs query classification, fetched docs or URL priority groups, fallback notes, and a concise answer with source confidence.

Quick Ref / Command

Engineer Kit

/ck:ai-artist

Turns a visual concept into approved image prompts, then renders through Google or OpenRouter-backed image generation.

01

Parse

02

Interview

03

Follow-up

04

Preview

Interview before rendering

Prompt search

Preview before generation

Image generation

Edit loops before spend

Visual direction

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Parse Concept, mode, provider, skip flag
  2. 2 Interview Style, mood, colors, aspect ratio
02

Work

Agent / skill execution

  1. 3 Follow-up Ask extra questions for banner/poster/product outputs
  2. 4 Preview Build prompt and confirm before generation
03

Verify

Gate, review, validation

  1. 5 Mode Prompt Best match, creative remix, wild, or all
  2. 6 Render Route through ai-multimodal provider path
04

Close

Report, handoff, artifact

  1. 7 Save PNG output or per-mode variants

Modes / Routes

--mode search

Best prompt match from curated database

Research:
prompt search
Review:
preview
Validate:
approval
--mode creative

Remix top matching prompt elements

Research:
prompt remix
Review:
preview
Validate:
approval
--mode wild

Apply a strong random visual transformation

Research:
random transform
Review:
preview
Validate:
approval
--mode all

Generate search, creative, and wild variants

Research:
all modes
Review:
preview
Validate:
3 outputs
--provider

auto, google, or openrouter provider route

Research:
credentials
Review:
key check
Validate:
provider works
--skip

Bypass interview and use defaults

Research:
Skip
Review:
defaults
Validate:
approval still clear

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Default Recommended
/ck:ai-artist "tech conference banner"
Use when:
You want the default best-match prompt route.
Expected:
Validation interview, prompt preview, approved PNG output.
--mode search
/ck:ai-artist "developer dashboard hero image" --mode search
Use when:
You want the closest curated prompt match.
Expected:
One best-match image prompt and PNG render.
--mode creative
/ck:ai-artist "AI workshop social poster" --mode creative
Use when:
You want a remixed visual direction.
Expected:
Prompt combines top matching prompt elements.
--mode wild
/ck:ai-artist "product showcase for VividKit Desktop" --mode wild
Use when:
You want a stronger visual transformation.
Expected:
One wild transformation variant.
--mode all
/ck:ai-artist "futuristic city for launch campaign" --mode all
Use when:
You need search, creative, and wild variants.
Expected:
Three PNG variants saved per mode.
--provider google
/ck:ai-artist "minimal product mockup" --provider google
Use when:
You want direct Google provider routing.
Expected:
Generation uses the Google image path.
--provider openrouter
/ck:ai-artist "conference booth backdrop" --provider openrouter
Use when:
You want OpenRouter-backed provider routing.
Expected:
Generation uses OpenRouter-backed image route.
--skip
/ck:ai-artist "LinkedIn banner for AI coding tools" --skip
Use when:
Defaults are acceptable and you want to bypass the interview.
Expected:
Uses default style, mood, colors, and aspect ratio.

Handled Scope

  • Prompt search
  • Image generation
  • Visual direction
  • Provider routing
  • Asset variants

Artifacts Produced

Generated Image Assets

Pattern

PNG output path; --mode all creates -search, -creative, -wild variants

Outputs approved prompt preview, PNG image assets, and final status with output path, style, mood, and aspect.

Quick Ref / Command

Engineer Kit

/ck:agentize

Wrap existing code as a reusable CLI, MCP server, or both, with shared core, credentials, docs, tests, CI, and companion skill.

01

Track

02

Scout

03

Map

04

Decide

Track before work

CLI packaging

Scout before design

MCP servers

Core before adapters

Shared core design

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Track Plan folder, tasks, active context
  2. 2 Scout Map entry points, I/O, deps, credentials
02

Work

Agent / skill execution

  1. 3 Map Agentization map and high-value surfaces
  2. 4 Decide Mode, names, transports, metadata
03

Verify

Gate, review, validation

  1. 5 Scaffold Core boundary and package layout
  2. 6 Wrap Thin CLI and/or MCP adapters
04

Close

Report, handoff, artifact

  1. 7 Harden Tests, CI, docs, skill, security
  2. 8 Package Release checklist and publishable output

Modes / Routes

--both

Default; shared core plus CLI and MCP packages

Research:
Yes
Review:
mode gate
Validate:
both surfaces
--mcp

MCP server only

Research:
Yes
Review:
transport gate
Validate:
MCP tools
--cli

CLI package only

Research:
Yes
Review:
command gate
Validate:
CLI tests
--auto

Proceed with recorded decisions

Research:
Yes
Review:
credential fallback
Validate:
harden
--ask

Pause for clarification before scaffolding

Research:
Yes
Review:
user answers
Validate:
explicit decisions

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Default Recommended
/ck:agentize src/integrations/payments
Use when:
You want the default CLI plus MCP package route.
Expected:
Plan, shared core, adapters, docs, CI, release checklist.
--both
/ck:agentize packages/reporting --both
Use when:
You need both CLI and MCP surfaces.
Expected:
Core package plus CLI and MCP packages.
--mcp
/ck:agentize src/search --mcp
Use when:
Only MCP server exposure is needed.
Expected:
MCP server package and transport docs.
--cli
/ck:agentize scripts/importer --cli
Use when:
Only a reusable CLI package is needed.
Expected:
CLI package with commands, config, docs, and tests.
--auto
/ck:agentize src/billing --auto
Use when:
You want autonomous decisions with recorded rationale.
Expected:
Decisions recorded, workflow proceeds through scaffolding.
--ask
/ck:agentize src/billing --ask
Use when:
You want to answer key design questions before scaffolding.
Expected:
Analysis pauses for clarification before implementation.
MCP + ask
/ck:agentize src/browser-automation --mcp --ask
Use when:
Transport or tool boundaries need user confirmation.
Expected:
MCP-only route with explicit user decisions.

Handled Scope

  • CLI packaging
  • MCP servers
  • Shared core design
  • Credentials
  • Release automation

Artifacts Produced

Agentized Package Set

Pattern

plans/<plan>/plan.md + packages/core|cli|mcp + docs + CI + release checklist

Outputs shared core, CLI/MCP adapters, documentation, CI, companion skill, and release checklist.

Quick Ref / Command

Engineer Kit

/ck:cti-expert

Cyber threat intelligence and OSINT workflow for public-data investigations, exposure reviews, domain recon, breach checks, and structured reports.

01

Acquire

02

Enrich

03

Parallelize

04

Assess

Public data only

OSINT

Authorization before security testing

Threat intelligence

Corroborate high-risk findings

Exposure review

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Acquire Collect public evidence from scoped modules
  2. 2 Enrich Pivot identifiers and connect subjects
02

Work

Agent / skill execution

  1. 3 Parallelize Fan out enrichment for 3+ subjects
  2. 4 Assess Validate, coverage, trust, blind spots
03

Verify

Gate, review, validation

  1. 5 Gate Legal, ethics, corroboration, citations
  2. 6 Deliver Reports, briefs, visuals, IOC exports

Modes / Routes

--case

Structured case workflow

Research:
Yes
Review:
ethics
Validate:
report gates
--sweep

Broad evidence sweep

Research:
Yes
Review:
scope
Validate:
confidence
--query

Query-led OSINT investigation

Research:
Targeted
Review:
citations
Validate:
limitations
--flow

Guided person/domain/email/quick flow

Research:
Guided
Review:
prompts
Validate:
scope
--yolo

Autonomous mode with mandatory boundaries

Research:
Auto
Review:
legal/ethics
Validate:
validate/coverage

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

--case Recommended
/ck:cti-expert target.com --case
Use when:
You need a structured investigation case.
Expected:
Acquire, enrich, assess, and deliver with saved reports.
--sweep
/ck:cti-expert @alice --sweep
Use when:
You need broad public-data collection.
Expected:
Evidence sweep with confidence and source boundaries.
--query
/ck:cti-expert "Acme Corp" --query
Use when:
You have a specific OSINT question.
Expected:
Query-led findings with citations and limitations.
--flow
/ck:cti-expert person --flow
Use when:
You want guided person/domain/email/quick workflow.
Expected:
Guided prompts keep investigation scoped.
--yolo
/ck:cti-expert target.com --case --yolo
Use when:
Scope and authorization are already clear.
Expected:
Autonomous flow while legal/ethics and verification gates stay active.
IOC export
/report ioc --format stix
Use when:
You need machine-readable indicators from a case.
Expected:
STIX/flat/CSV IOC output with confidence threshold.

Handled Scope

  • OSINT
  • Threat intelligence
  • Exposure review
  • Domain recon
  • IOC reporting

Artifacts Produced

Structured Intelligence Report

Pattern

OSINT-REPORT-[CASE-ID]-[YYYY-MM-DD].md/.docx + optional IOC STIX/TXT/CSV

Auto-saves Markdown and Word reports with source citations, confidence levels, limitations, visuals, workspace artifacts, and optional IOC exports.

Quick Ref / Command

Engineer Kit

/ck:retro

Data-driven retrospective from git history: velocity, churn, hotspots, plans, and team activity.

01

Parse Period

02

Collect Git

03

Compute Health

04

Scan Plans

Read-only

Git metrics

No guessed metrics

Team activity

Date ranges are explicit

Code health

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Parse Period 7d, 2w, 1m, sprint, or date range
  2. 2 Collect Git Commits, LOC, authors, files, hotspots
02

Work

Agent / skill execution

  1. 3 Compute Health Frequency, test ratio, churn, active days
  2. 4 Scan Plans Plan files and checkbox completion
03

Verify

Gate, review, validation

  1. 5 Write Report Markdown retrospective from real metrics
  2. 6 Render HTML Optional self-contained HTML output

Modes / Routes

7d/default

Default last-seven-days retro

Research:
git
Review:
read-only
Validate:
real metrics
sprint

Sprint range; ask if start is unclear

Research:
git/plans
Review:
date gate
Validate:
range
--compare

Compare with previous equal-length period

Research:
two periods
Review:
same length
Validate:
delta
--team

Per-author breakdown

Research:
authors
Review:
git data
Validate:
team table
--format html

Self-contained HTML report

Research:
same data
Review:
render
Validate:
html file

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Default Recommended
/ck:retro
Use when:
You want the default last-seven-days retrospective.
Expected:
Markdown retro based on git and plan data.
2w
/ck:retro 2w
Use when:
You need a two-week window.
Expected:
Velocity, churn, hotspots, and plan progress for two weeks.
sprint
/ck:retro sprint
Use when:
You want sprint framing and may need start-date confirmation.
Expected:
Sprint retro with confirmation if date is unclear.
Date range
/ck:retro 2026-05-01:2026-05-31
Use when:
You need an exact historical range.
Expected:
Report bounded to explicit dates.
--compare
/ck:retro 2w --compare
Use when:
You need comparison to the previous equal-length period.
Expected:
Adds period-over-period comparison.
--team
/ck:retro 1m --team
Use when:
Per-author breakdown matters.
Expected:
Adds team activity table.
--format html
/ck:retro sprint --format html
Use when:
You need a self-contained visual report.
Expected:
HTML retrospective saved under plans/reports.

Handled Scope

  • Git metrics
  • Team activity
  • Code health
  • Plan progress
  • Retrospective reporting

Artifacts Produced

Retrospective Report

Pattern

plans/reports/retro-{YYMMDD}-{slug}.md or .html

Outputs velocity, code health, commit distribution, hotspots, plan progress, optional team breakdown, highlights, and recommendations.

Quick Ref / Command

Engineer Kit

/ck:graphify

Turn code, docs, papers, images, and media into a queryable architecture graph for planning and navigation.

01

Input

02

Local Extract

03

Semantic Extract

04

Tag Edges

Local-first code extraction

Knowledge graphs

Confidence tags on edges

Architecture navigation

Graph before planning

Semantic extraction

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Input Repo/path and optional flag
  2. 2 Local Extract Code via tree-sitter, media via Whisper
02

Work

Agent / skill execution

  1. 3 Semantic Extract Docs/images via configured provider when needed
  2. 4 Tag Edges EXTRACTED, INFERRED, AMBIGUOUS
03

Verify

Gate, review, validation

  1. 5 Artifacts HTML, report, JSON, cache
  2. 6 Handoff MCP, ck:plan, or ck:scout

Modes / Routes

[path]

Build graph for provided path

Research:
local
Review:
scope
Validate:
graph out
--watch

Incremental rebuild on file changes

Research:
cache
Review:
watch
Validate:
updates
--report

Generate/use graph report

Research:
graph
Review:
questions
Validate:
GRAPH_REPORT
--mcp

Expose graph through MCP tools

Research:
server
Review:
tools
Validate:
query_graph

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Default Recommended
/ck:graphify
Use when:
You want a graph for the current project.
Expected:
Graph artifacts in graphify-out for navigation/planning.
[path]
/ck:graphify /path/to/project
Use when:
You need to graph a specific folder.
Expected:
Graph scoped to the provided path.
--watch
/ck:graphify . --watch
Use when:
The graph should update as files change.
Expected:
Incremental rebuilds through cache.
--report
/ck:graphify . --report
Use when:
You need the graph report for architecture review.
Expected:
GRAPH_REPORT with god nodes, links, and questions.
--mcp
/ck:graphify . --mcp
Use when:
You want tools to query the graph.
Expected:
MCP server exposes graph query tools.
Plan handoff
/ck:graphify . --report
Use when:
You want graph context before planning.
Expected:
Report can feed ck:plan or ck:scout handoff.

Handled Scope

  • Knowledge graphs
  • Architecture navigation
  • Semantic extraction
  • MCP graph queries
  • Planning context

Artifacts Produced

Graphify Artifacts

Pattern

graphify-out/graph.html + GRAPH_REPORT.md + graph.json + cache/

Outputs an interactive graph, architecture report, queryable JSON graph, and cache for incremental rebuilds.

Quick Ref / Command

Engineer Kit

/ck:git

Guarded Git delivery for commits, pushes, pull requests, and merges with secret scanning and conventional messages.

01

Choose

02

Inspect

03

Scan

04

Split

Secret scan blocks commit

Conventional commits

Push only when asked

Commit splitting

Remote diff for PRs

Secret scanning

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Choose cm, cp, pr, merge, or picker
  2. 2 Inspect Changed files, stats, logical groups
02

Work

Agent / skill execution

  1. 3 Scan Secret scan before commit
  2. 4 Split Single vs split commit decision
03

Verify

Gate, review, validation

  1. 5 Commit Conventional message, no AI attribution
  2. 6 Push/PR Optional push or remote-diff PR
04

Close

Report, handoff, artifact

  1. 7 Merge Fetch, pull target, merge remote source

Modes / Routes

cm

Commit only

Research:
diff
Review:
secret scan
Validate:
commit
cp

Commit and push

Research:
diff
Review:
secret scan
Validate:
push
pr [to] [from]

Create GitHub PR from remote diff

Research:
remote branches
Review:
branch state
Validate:
PR URL
merge [to] [from]

Merge remote source into target branch

Research:
fetch/pull
Review:
conflicts
Validate:
pushed target
[no args]

Ask operation first

Research:
picker
Validate:
choice

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Chooser Recommended
/ck:git
Use when:
You want the command to ask commit, push, PR, or merge.
Expected:
Operation picker before any Git mutation.
cm
/ck:git cm
Use when:
You want staged/analyzed changes committed only.
Expected:
Secret scan, split decision, conventional commit.
cp
/ck:git cp
Use when:
You want commit and push in one guarded flow.
Expected:
Commit flow plus upstream push.
pr
/ck:git pr
Use when:
You want a PR from current branch to main.
Expected:
Remote diff PR with summary and test plan.
pr target
/ck:git pr develop
Use when:
Target branch is not main.
Expected:
PR from current branch into selected base.
pr target/source
/ck:git pr main feature/oauth-login
Use when:
Both base and source branch must be explicit.
Expected:
PR built from origin/main...origin/feature branch.
merge
/ck:git merge
Use when:
You want current branch merged to main after remote sync.
Expected:
Fetch, pull target, merge remote source, push target.
merge target/source
/ck:git merge develop feature/oauth-login
Use when:
You need a named source branch merged into a named target.
Expected:
Remote-source merge into target branch.

Handled Scope

  • Conventional commits
  • Commit splitting
  • Secret scanning
  • Pull requests
  • Branch merge flow

Artifacts Produced

Git Delivery Artifacts

Pattern

commits + optional pushed branch + PR URL + merge summary

Outputs one or more commits, optional push/PR/merge result, and a concise delivery summary.

Quick Ref / Command

Engineer Kit

/ck:ghpm

GitHub project management for humans and AI agents: turn requests into issues, track status and handoffs on Projects, and automate triage with gh, GraphQL, and Actions.

01

Orient

02

Choose Mode

03

Load References

04

Update GitHub

GitHub is the single source of truth

Issue/task intake

Update GitHub first, then local artifacts

Projects boards + fields

One mutually-exclusive live status

Label taxonomy

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Orient Read repo, auth, projects, open issues
  2. 2 Choose Mode Bootstrap, Intake, Execute, Handoff, or Audit
02

Work

Agent / skill execution

  1. 3 Load References Taxonomy, command cookbook, skill pipelines
  2. 4 Update GitHub Issues, labels, Project fields, comments
03

Verify

Gate, review, validation

  1. 5 Link + Automate Branch/PR/checks linked, Actions triage
  2. 6 Report Evidence Cited status: URLs, checks, next owner

Modes / Routes

Bootstrap

Create labels, project fields, templates, automation

Research:
existing labels
Review:
minimal taxonomy
Validate:
project scope
Intake

Turn request/plan/chat into GitHub issues

Research:
task contract
Review:
no secrets
Validate:
acceptance criteria
Execute

Link branch/PR/checks and advance status

Research:
PR/check state
Review:
one live status
Validate:
evidence linked
Handoff

Write state, blockers, commands, next owner

Research:
last verified
Review:
redact private
Validate:
next command
Audit

Compare GitHub state vs repo/plans/CI

Research:
drift scan
Review:
verified only
Validate:
cited URLs

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Intake Recommended
/ck:ghpm turn this plan into GitHub issues with owners and acceptance criteria
Use when:
A request, plan, or TODO list must become tracked GitHub issues.
Expected:
Issues written to the task contract with labels, owners, and dependencies.
Bootstrap
/ck:ghpm set up minimal labels and a Project board for this repo
Use when:
A repo needs a baseline label taxonomy, project fields, and automation.
Expected:
Minimal labels, Project Status/Owner/Lane fields, and triage workflow.
Execute
/ck:ghpm move issue #123 to in-progress and link the PR
Use when:
Work has started and GitHub state must reflect branch/PR/checks.
Expected:
Status advanced to one live value with PR and check links attached.
Handoff
/ck:ghpm write a handoff comment for issue #123 with commands run and next step
Use when:
Another human or AI session needs durable continuation context.
Expected:
Append-only handoff comment with state, evidence, owner, next command.
Audit
/ck:ghpm audit open issues and the board against local plans and CI
Use when:
GitHub state may have drifted from the repo, plans, or CI runs.
Expected:
Drift report citing issues, blocked items, PR checks, and branch state.
Status report
/ck:ghpm summarize current project status from GitHub state
Use when:
You need an evidence-based snapshot for a standup or stakeholder.
Expected:
GHPM status with repo, project URL, issue states, and Actions results.
Project field write
/ck:ghpm set the Status field for issue #123 to In Progress on the org Project
Use when:
A Projects single-select field needs a precise GraphQL write.
Expected:
gh api graphql resolves node IDs and updates the field value.
Trigger automation
/ck:ghpm run the project-triage workflow for issue #123
Use when:
A GitHub Actions automation worker should run for an issue.
Expected:
Workflow dispatched with GH_TOKEN and run result reported.

Handled Scope

  • Issue/task intake
  • Projects boards + fields
  • Label taxonomy
  • AI/human handoff logs
  • gh + GraphQL automation
  • Actions triage

Artifacts Produced

Evidence-Based GHPM Status

Pattern

GitHub issues (task contract) + Project fields + append-only handoff comments + cited status summary

Produces structured issues, live Project state, and a concise status citing repo, project URL, issue states/owners/priorities, Actions/check results, and the last handoff comment with next owner/action.

Quick Ref / Command

Engineer Kit

/ck:debug

Evidence-first debugging that proves root cause before routing into a fix.

01

Assess

02

Collect

03

Trace

04

Compare

Evidence before hypothesis

Root-cause tracing

One hypothesis at a time

CI log analysis

Fix root cause, not symptom

Performance debugging

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Gather

Symptoms, evidence, repro

  1. 1 Assess Symptoms, scope, severity, recent changes
  2. 2 Collect Logs, stack traces, CI, DB, metrics, repro
02

Analyze

Trace + compare + hypothesis

  1. 3 Trace Follow call/data chain backward
  2. 4 Compare Working examples and pattern differences
  3. 5 Test One hypothesis, smallest experiment
03

Fix

Root cause + regression

  1. 6 Fix Target root cause, add regression check
04

Prove

Fresh verification

  1. 7 Verify Fresh command/browser evidence

Modes / Routes

Code bug

Trace application error to root cause

Research:
stack
Review:
hypothesis
Validate:
repro/test
CI/CD

Compare CI logs and environment state

Research:
logs
Review:
env diff
Validate:
CI command
Performance

Quantify and isolate bottleneck layer

Research:
metrics
Review:
before/after
Validate:
measurement
Frontend

Use screenshot, DOM, console, responsive checks

Research:
browser
Review:
visual
Validate:
screenshot/console
Polluter helper

Find tests that leave unwanted files/state

Research:
helper
Review:
isolate
Validate:
polluter found

Shortcuts Blocked

💭

"I see the bug, fix it now"

Seeing a symptom is not diagnosing root cause. Collect evidence first.

💭

"Try changing X and see"

Random fixes create new bugs. Test one hypothesis with the smallest experiment.

💭

"Tests pass now, done"

Need fresh verification from command/browser, not just test suite green.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Default Recommended
/ck:debug "checkout returns 500 after payment webhook"
Use when:
A symptom needs root-cause investigation.
Expected:
Evidence, hypothesis log, fix route, verification command.
Code bug
/ck:debug "TypeError: user.validate is not a function in auth middleware"
Use when:
A stack error points to application code.
Expected:
Trace through call/data chain before any fix.
CI failure
/ck:debug "npm test fails only in CI, passes locally"
Use when:
CI and local behavior disagree.
Expected:
Environment/log comparison and fresh verification.
Deep stack
/ck:debug "git init runs in the wrong directory during workspace creation"
Use when:
The failure source is several layers away.
Expected:
Backtrace to original trigger.
Incident
/ck:debug "API latency spiked after the last deploy"
Use when:
A system-level regression needs quantified evidence.
Expected:
Metrics, bottleneck layer, before/after proof.
Frontend
/ck:debug "settings page layout overlaps on mobile"
Use when:
The issue is visual or browser-specific.
Expected:
Screenshot, DOM, console, responsive verification.
Polluter
./find-polluter.sh ".git" "src/**/*.test.ts"
Use when:
Tests leave unwanted files or state behind.
Expected:
Polluting test isolated through helper run.

Handled Scope

  • Root-cause tracing
  • CI log analysis
  • Performance debugging
  • Frontend diagnostics
  • Test pollution isolation

Artifacts Produced

Debug Evidence

Pattern

repro steps + hypothesis log + verification output + optional debug report

Outputs the root-cause chain, confirmed/rejected hypotheses, regression check, and fresh verification evidence.

Quick Ref / Command

Engineer Kit

/ck:agent-browser

Browser automation and QA evidence workflow built around snapshot refs, actions, waits, and artifacts.

01

Verify

02

Load Guide

03

Open

04

Snapshot

Snapshot refs expire

Browser automation

Evidence is first-class

QA screenshots/video

Do not leak auth artifacts

CDP/Electron

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Setup

Verify + load + open

  1. 1 Verify Install, doctor, provider/session health
  2. 2 Load Guide Version-matched browser workflow reference
  3. 3 Open URL, CDP, Electron, or cloud provider
02

Observe

Snapshot refs

  1. 4 Snapshot Interactive refs and page state
03

Act

Interact + wait

  1. 5 Act Click, fill, type, press, upload, drag
  2. 6 Wait URL, text, load, network, function
04

Evidence

Capture artifacts

  1. 7 Capture Screenshot, video, HAR, trace, console

Mode Selection

open/snapshot/act Core Loop

Open a URL, take a snapshot for interactive refs, then act on those refs.

Prompt

agent-browser open http://localhost:3000 && agent-browser snapshot -i -c && agent-browser click @e7
Use when:
Automating a UI flow step by step.
Expected:
Page state with interactive map; element actions applied.
dogfood QA Dogfood QA

Exploratory testing of the live app through the browser only.

Prompt

agent-browser open http://localhost:3000 && agent-browser screenshot --full --annotate
Use when:
You need QA evidence without touching production code.
Expected:
Screenshots, console findings, and QA notes.
-p browserbase Cloud Browser

Run the session in a cloud browser provider.

Prompt

agent-browser -p browserbase open https://example.com
Use when:
Local browser is unavailable or cloud isolation is needed.
Expected:
Cloud browser session opened, ready for snapshot and act.

Shortcuts Blocked

💭

"I already took a snapshot, just keep clicking"

Element refs become stale after any navigation or DOM change. Always re-snapshot before the next action.

💭

"Save the auth state and share the screenshots freely"

Auth state, HAR files, and screenshots can contain sensitive session data and secrets. Review before sharing.

💭

"Use cloud browser for all tasks"

Cloud providers (Browserbase, AgentCore) incur cost per session. Use them only when local browser is insufficient.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Open Recommended
agent-browser open http://localhost:3000
Use when:
You need to start a browser session for a target URL.
Expected:
Page opened and ready for snapshot.
Snapshot
agent-browser snapshot -i -c
Use when:
You need current interactive element refs.
Expected:
Compact interactive map with @e refs.
Act
agent-browser fill @e3 "user@example.com" && agent-browser click @e7
Use when:
You are acting on current snapshot refs.
Expected:
Form action followed by wait/re-snapshot.
Evidence
agent-browser screenshot --full --annotate
Use when:
You need visual evidence for a report.
Expected:
Full annotated screenshot artifact.
Record
agent-browser record start && agent-browser record stop
Use when:
An interactive bug needs repro video.
Expected:
WebM video captured for issue report.
Auth state
agent-browser state save auth-state.json
Use when:
You need to reuse a logged-in session safely.
Expected:
Cookie/storage state saved with security caution.
React
agent-browser --enable react-devtools open http://localhost:3000 && agent-browser react tree
Use when:
React component inspection is required.
Expected:
React tree/renders available after enabled launch.
Cloud
agent-browser -p browserbase open https://example.com
Use when:
The browser should run in a cloud provider.
Expected:
Cloud browser session opened.
Doctor
agent-browser doctor --offline --quick
Use when:
Install, daemon, or provider behavior looks odd.
Expected:
Quick local diagnosis without network.

Handled Scope

  • Browser automation
  • QA screenshots/video
  • CDP/Electron
  • Cloud browsers
  • React and Web Vitals

Artifacts Produced

Browser Evidence

Pattern

screenshots/*.png + videos/*.webm + HAR/trace/profile + QA report

Outputs browser snapshots, screenshots, videos, HAR/trace/profile files, auth state when requested, and concise QA findings.

Quick Ref / Command

Engineer Kit

/ck:ai-multimodal

Media analysis and generation across Gemini, OpenRouter, MiniMax, document conversion, and media optimization routes.

01

Setup

02

Intent

03

Route

04

Model

Provider key first

Vision/audio/PDF analysis

Files for analysis, prompt for generation

Transcription

Chunk long media

Structured extraction

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Setup Keys, dependencies, provider availability
  2. 2 Intent Analyze, transcribe, extract, generate, optimize
02

Work

Agent / skill execution

  1. 3 Route Gemini, OpenRouter, MiniMax, converter, optimizer
  2. 4 Model Model/provider defaults or explicit choice
03

Verify

Gate, review, validation

  1. 5 Preflight Compress, resize, chunk long media
  2. 6 Execute Run CLI/API route
04

Close

Report, handoff, artifact

  1. 7 Save docs/assets or explicit output

Modes / Routes

--task analyze

Understand image/video/audio/PDF content

Research:
files
Review:
limits
Validate:
analysis
--task transcribe

Create timestamped transcript

Research:
audio/video
Review:
chunking
Validate:
markdown
--task extract

Extract structured data to JSON/CSV/markdown

Research:
docs
Review:
schema
Validate:
format
--task generate

Generate images via Google, OpenRouter, or MiniMax

Research:
prompt
Review:
quota
Validate:
image
--task generate-video

Generate video via Veo or MiniMax

Research:
prompt/frames
Review:
model
Validate:
mp4
media optimizer

Resize, compress, or split media before API call

Research:
size
Review:
limits
Validate:
chunks

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Setup Recommended
python scripts/check_setup.py
Use when:
You need to verify provider keys and dependencies.
Expected:
Setup report for Gemini/OpenRouter/MiniMax routes.
Analyze
python scripts/gemini_batch_process.py --files screenshot.png --task analyze --prompt "Extract UI layout, visual hierarchy, and likely component states"
Use when:
You need media understanding from images or screenshots.
Expected:
Structured analysis from the selected provider.
Transcribe
python scripts/gemini_batch_process.py --files meeting.mp3 --task transcribe --prompt "Generate timestamped transcript with speaker labels" --format markdown --output meeting.md
Use when:
Audio/video should become a transcript.
Expected:
Timestamped markdown transcript.
Extract JSON
python scripts/gemini_batch_process.py --files invoice.pdf --task extract --prompt "Extract vendor, date, line items, totals as JSON" --format json --output invoice.json
Use when:
A document needs structured extraction.
Expected:
JSON extraction output.
Google image
python scripts/gemini_batch_process.py --task generate --provider google --model gemini-3.1-flash-image-preview --prompt "Clean product mockup of a CLI dashboard" --aspect-ratio 16:9 --size 2K --num-images 2
Use when:
You want direct Google image generation.
Expected:
Generated image assets when quota/key allows.
OpenRouter image
python scripts/gemini_batch_process.py --task generate --provider openrouter --model google/gemini-3.1-flash-image-preview --prompt "Retro robot mascot for developer tooling" --output mascot.png
Use when:
You need OpenRouter-backed image routing.
Expected:
Primary image saved to requested output.
Video
python scripts/gemini_batch_process.py --task generate-video --model veo-3.1-generate-preview --prompt "Slow camera push across this interface mockup" --reference-images frame-start.png frame-end.png --resolution 1080p --aspect-ratio 16:9
Use when:
A prompt/reference frame should become video.
Expected:
Generated video asset if provider supports it.
MiniMax speech
python scripts/minimax_cli.py --task generate-speech --text "Welcome to the release walkthrough" --model speech-2.8-hd --voice English_Warm_Bestie --emotion happy --output-format mp3
Use when:
You need generated voice audio.
Expected:
MP3/WAV/FLAC speech asset.
Optimize
python scripts/media_optimizer.py --input long-video.mp4 --split --chunk-duration 900 --output-dir ./chunks
Use when:
Media exceeds comfortable upload/transcription size.
Expected:
Chunked or optimized media ready for processing.

Handled Scope

  • Vision/audio/PDF analysis
  • Transcription
  • Structured extraction
  • Image/video generation
  • Speech/music generation

Artifacts Produced

Media Artifacts

Pattern

docs/assets/*_generated_* + transcripts/extractions + optimized chunks

Outputs generated images/video/audio/music, transcripts, structured extractions, document markdown, or optimized media chunks depending on route.

Quick Ref / Command

Engineer Kit

/ck:ask

Technical and architecture consultation before implementation, grounded in context when needed.

01

Question

02

Context

03

Scout

04

Lenses

Consult before coding

Architecture decisions

Scout when context is thin

Technology choice

One clear position

Scalability tradeoffs

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Question Technical or architecture decision
  2. 2 Context Project, workflow, constraints
02

Work

Agent / skill execution

  1. 3 Scout Only when context is insufficient
  2. 4 Lenses Boundaries, technology, scale, risk
03

Verify

Gate, review, validation

  1. 5 Position One clear recommendation
  2. 6 Tradeoffs Alternatives and caveats
04

Close

Report, handoff, artifact

  1. 7 Validate Next checks before code

Modes / Routes

Question

Direct technical consultation

Research:
context
Review:
tradeoffs
Validate:
next checks
Compare

Evaluate two or more technical options

Research:
options
Review:
risks
Validate:
recommendation
Plan review

Critique an existing plan before coding

Research:
plan
Review:
overbuild
Validate:
changes
Context recovery

Scout first when local context is missing

Research:
ck:scout
Review:
assumptions
Validate:
answer

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Architecture Recommended
/ck:ask Should we split auth into a separate service or keep it in the monolith?
Use when:
You need a design decision before implementation.
Expected:
Direct recommendation with tradeoffs and validation steps.
Compare
/ck:ask Compare Postgres row-level security vs application-level tenant filters for this SaaS app.
Use when:
Two technical options need evaluation.
Expected:
Option comparison grounded in constraints.
Simplify
/ck:ask What is the simplest architecture for adding background job retries here?
Use when:
You want to avoid overbuilding.
Expected:
YAGNI/KISS answer with minimal path.
Plan review
/ck:ask Review this plan for scaling websocket fanout without overbuilding.
Use when:
A plan needs architecture critique before coding.
Expected:
Risks, tradeoffs, and recommended validation.
Migration
/ck:ask We need a migration path from REST to GraphQL. What should we avoid?
Use when:
Migration risks matter more than code changes.
Expected:
Cautions, route options, and next checks.

Handled Scope

  • Architecture decisions
  • Technology choice
  • Scalability tradeoffs
  • Risk analysis
  • Implementation strategy

Artifacts Produced

Consultation Answer

Pattern

Architecture analysis + recommendation + tradeoffs + next actions

Outputs a direct technical answer with recommendation, alternatives, risks, and validation actions.

Quick Ref / Command

Engineer Kit

/ck:security

STRIDE and OWASP security audit with optional red-team discovery and explicit fix mode.

01

Scope

02

Baseline

03

Audit

04

Red Team

Report-only unless --fix

STRIDE threat modeling

Never reveal raw secrets

OWASP code review

Critical blocks release

Secret handling

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Scope

Target + asset map

  1. 1 Scope Glob, folder, or full repository
  2. 2 Baseline Map assets, trust boundaries, dependencies
02

Audit

STRIDE, OWASP, secrets

  1. 3 Audit STRIDE, OWASP, secrets, dependency risk
  2. 4 Red Team Optional attacker-perspective loop
03

Remediate

Fix + verify

  1. 5 Fix Only when --fix is explicit
  2. 6 Verify Run checks and stop on guard failure
04

Report

Findings + export

  1. 7 Report Findings, TSV, coverage, fix summary

Mode Selection

<scope> Focused

Audit a specific glob or folder.

Prompt

/ck:security src/api/**
Use when:
You know the risky area already.
Expected:
Scoped findings with STRIDE + OWASP coverage.
--red-team Red Team

Add adversarial attacker-perspective discovery loop.

Prompt

/ck:security --red-team src/auth/
Use when:
Auth, payment, or public API surfaces.
Expected:
Multiple attacker personas probe the target.
--fix Auto-fix

Allow code changes for accepted findings.

Prompt

/ck:security --fix src/api/**
Use when:
Findings are clear and remediation is safe.
Expected:
Code patches + verification run for each fix.
--iterations N Bounded

Bound audit or fix loop by iteration count.

Prompt

/ck:security --red-team --iterations 3
Use when:
Control depth of red-team or fix loops.
Expected:
Stops after N iterations even if more findings exist.

Shortcuts Blocked

💭

"I found a vuln, fix it now"

Default route is report-only. Use --fix explicitly to enable remediation.

💭

"Red team found nothing, we are secure"

Absence of findings is not proof of security. Check coverage and iteration count.

💭

"Skip verify, the fix is obvious"

Every remediation must be verified. Obvious fixes can introduce new attack surfaces.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Scope audit Recommended
/ck:security src/api/**/*.ts
Use when:
You need a focused STRIDE/OWASP review without code changes.
Expected:
Security report with ranked findings and no raw secrets.
Full audit
/ck:security full
Use when:
The whole repository needs a broad security pass.
Expected:
Full-scope audit with coverage summary.
--red-team
/ck:security full --red-team
Use when:
You want adversarial attacker-perspective discovery.
Expected:
Adds red-team persona findings and attack paths.
--iterations
/ck:security src/ --red-team --iterations 20
Use when:
Discovery needs an explicit bounded loop.
Expected:
Runs bounded iterations and stops on guard conditions.
--fix
/ck:security src/ --fix
Use when:
You want accepted fixes after audit findings.
Expected:
Code changes only in fix mode with validation.
Fix budget
/ck:security src/ --fix --iterations 15
Use when:
Fixing should stay inside an iteration budget.
Expected:
Bounded fix loop with stop conditions.
Red-team fix
/ck:security full --red-team --fix
Use when:
You want red-team discovery followed by allowed remediation.
Expected:
Audit, red-team, fixes, and final verification.

Handled Scope

  • STRIDE threat modeling
  • OWASP code review
  • Secret handling
  • Dependency risk
  • Red-team discovery

Artifacts Produced

Security Audit Artifacts

Pattern

security report + security-audit-results.tsv + coverage/fix summary

Outputs ranked findings, evidence, remediation notes, TSV export, coverage summary, and fix verification when --fix is used.

Quick Ref / Command

Engineer Kit

/ck:repomix

Pack local or remote repositories into structured AI context with format, scope, token, and safety controls.

01

Target

02

Scope

03

Safety

04

Format

Scope before pack

Repository packing

Security warning must be resolved

Context shaping

Token budget is visible

Token budgeting

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Target Path or remote repository
  2. 2 Scope Include/exclude, gitignore, default patterns
02

Work

Agent / skill execution

  1. 3 Safety Security check and private-data review
  2. 4 Format XML, Markdown, plain, or JSON
03

Verify

Gate, review, validation

  1. 5 Token Map Optional token-count tree and large-file signals
  2. 6 Write/Copy Output file and optional clipboard copy

Modes / Routes

--style

Select xml, markdown, plain, or json

Research:
format
Review:
reader fit
Validate:
output
--remote

Pack a remote repository source

Research:
clone
Review:
private repo
Validate:
scope
--include / -i

Restrict files by glob filters

Research:
scope
Review:
missing context
Validate:
file list
--remove-comments

Reduce token count by stripping comments

Research:
tokens
Review:
context loss
Validate:
pack
--output / -o

Write to a custom path

Research:
path
Validate:
file exists
--copy / -c

Copy generated pack to clipboard

Research:
clipboard
Review:
share gate
Validate:
copied
--init

Create reusable repomix config

Research:
config
Validate:
config file
--token-count-tree

Show token-heavy file tree

Research:
token map
Review:
budget
Validate:
tree

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Default Recommended
/ck:repomix
Use when:
You need an AI-ready pack of the current repository.
Expected:
repomix-output.xml with token/security summary.
[path]
/ck:repomix packages/web
Use when:
Only one folder should be packed.
Expected:
Output scoped to the provided path.
--style
/ck:repomix --style markdown
Use when:
The consumer needs Markdown, XML, plain, or JSON.
Expected:
Output format matches selected style.
--remote
/ck:repomix --remote https://github.com/org/repo
Use when:
The source is a remote repository.
Expected:
Remote is cloned/packed with private-repo caution.
--include
/ck:repomix --include "src/**,docs/**"
Use when:
Only selected globs should enter context.
Expected:
Pack respects include filters.
--remove-comments
/ck:repomix --remove-comments
Use when:
You want lower token count and comments are not needed.
Expected:
Comments removed before output.
--output
/ck:repomix -o plans/context/auth-pack.md --style markdown
Use when:
Output path should be explicit.
Expected:
Pack written to the requested file.
--copy
/ck:repomix --copy
Use when:
You want the packed output in clipboard.
Expected:
Output is copied after generation when supported.
--init
/ck:repomix --init
Use when:
You need a reusable config file first.
Expected:
Creates repomix.config.json.
--token-count-tree
/ck:repomix --token-count-tree 200
Use when:
You need token hotspots before sharing.
Expected:
Token tree highlights large files above threshold.
No defaults
/ck:repomix --no-gitignore --no-default-patterns
Use when:
You intentionally want normally excluded files included.
Expected:
Pack bypasses default ignore behavior with review gate.
Security override
/ck:repomix --no-security-check
Use when:
You explicitly accept skipping safety scan.
Expected:
Security check skipped and risk is visible.

Handled Scope

  • Repository packing
  • Context shaping
  • Token budgeting
  • Secret warning review
  • Remote repository capture

Artifacts Produced

Repository Context Pack

Pattern

repomix-output.xml or custom output + repomix.config.json + token/security summary

Outputs a structured repository pack, optional config/ignore files, token-count tree, and security warnings for review.

Quick Ref / Command

Engineer Kit

/ck:llms

Generate llms.txt and optional full-context documentation indexes for LLM-friendly site discovery.

01

Source

02

Filter

03

Summarize

04

Full

Public docs only

llms.txt spec

No deploy side effects

Documentation indexing

Do not expose private config

URL/doc scanning

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Source Docs path, project scan, or URL
  2. 2 Filter Public docs only, exclude private config
02

Work

Agent / skill execution

  1. 3 Summarize Build concise LLM-readable entries
  2. 4 Full Optional llms-full.txt context
03

Verify

Gate, review, validation

  1. 5 Write Save to requested output path
  2. 6 Review Check privacy and docs coverage

Modes / Routes

[path]

Scan a local documentation path

Research:
files
Review:
privacy
Validate:
index
--url <base>

Use a public URL as source

Research:
URL
Review:
scope
Validate:
index
--full

Also generate full-context file

Research:
docs
Review:
token/privacy
Validate:
llms-full.txt
--output <path>

Write index to explicit path

Research:
path
Validate:
file exists

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Default Recommended
/ck:llms
Use when:
You want an llms.txt index from the current docs/project.
Expected:
llms.txt generated from public documentation context.
Path scan
/ck:llms docs/
Use when:
Only one documentation folder should be indexed.
Expected:
Index scoped to the provided path.
URL source
/ck:llms --url https://vividkit.dev/guides
Use when:
The docs source is a public URL.
Expected:
URL content becomes the base index source.
--full
/ck:llms --full
Use when:
You need both concise and full context files.
Expected:
Creates llms.txt plus llms-full.txt.
--output
/ck:llms --output public/llms.txt
Use when:
The target file path must be explicit.
Expected:
Writes llms.txt to the requested location.
--url + output
/ck:llms --url https://vividkit.dev --output public/llms.txt
Use when:
You want a hosted-site source and local output path.
Expected:
Crawled/indexed source written to selected file.

Handled Scope

  • llms.txt spec
  • Documentation indexing
  • URL/doc scanning
  • Privacy filtering
  • LLM context shaping

Artifacts Produced

LLM Documentation Index

Pattern

llms.txt + optional llms-full.txt

Outputs a concise docs index and, when requested, a larger full-context file for LLM consumers.

Quick Ref / Command

Engineer Kit

/ck:scenario

Generate edge cases, failures, security scenarios, and QA matrices from features or source files.

01

Input

02

Lens

03

Decompose

04

Iterate

Report only

Edge-case discovery

Novelty matters

Failure analysis

Rotate after repeated dimensions

Threat scenarios

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Input Feature text or source file path
  2. 2 Lens Domain, focus, and format
02

Work

Agent / skill execution

  1. 3 Decompose Explore dimensions and risk surfaces
  2. 4 Iterate Bounded loop with saturation stop
03

Verify

Gate, review, validation

  1. 5 Deduplicate Remove low-value and repeated cases
  2. 6 Score Severity, coverage, composite score
04

Close

Report, handoff, artifact

  1. 7 Report Scenario report and optional TSV

Modes / Routes

--iterations N

Cap discovery loop length

Research:
bounded
Review:
novelty
Validate:
iteration count
--saturation

Stop when new-value generation dries up

Research:
novelty
Review:
coverage
Validate:
stop rule
--domain

Use software, product, business, security, or marketing lens

Research:
domain
Review:
fit
Validate:
matrix
--focus

Prioritize edge-cases, failures, security, or scale

Research:
focus
Review:
risk
Validate:
coverage
--format

Choose table, use-cases, test-scenarios, or threat-scenarios

Research:
format
Validate:
handoff shape

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Feature text Recommended
/ck:scenario "User can reset password with email OTP"
Use when:
You need edge cases from a feature description.
Expected:
Scenario report with severity and coverage matrix.
File path
/ck:scenario src/auth/reset-password.ts
Use when:
A concrete implementation file needs scenario extraction.
Expected:
File-grounded scenarios and failure paths.
--iterations
/ck:scenario checkout flow --iterations 12
Use when:
You want a bounded generation loop.
Expected:
Runs up to the specified iteration budget.
--saturation
/ck:scenario checkout flow --saturation
Use when:
You want the loop to stop when novelty is exhausted.
Expected:
Stops after saturation conditions are met.
--domain
/ck:scenario onboarding --domain product
Use when:
The scenario lens should match a domain.
Expected:
Uses software/product/business/security/marketing framing.
--focus
/ck:scenario upload API --focus security
Use when:
One risk category matters most.
Expected:
Prioritizes edge cases, failures, security, or scale.
--format
/ck:scenario payment webhook --format threat-scenarios
Use when:
Output shape must match QA/security handoff.
Expected:
Formats as table, use cases, test scenarios, or threat scenarios.

Handled Scope

  • Edge-case discovery
  • Failure analysis
  • Threat scenarios
  • QA coverage
  • Risk scoring

Artifacts Produced

Scenario Discovery Report

Pattern

scenario report + severity summary + optional scenario-results.tsv

Outputs categorized scenarios, severity summary, coverage matrix, composite score, and optional TSV for QA handoff.

Quick Ref / Command

Engineer Kit

/ck:docs

Initialize, update, and summarize project documentation through a docs-only workflow.

01

Action

02

Scan

03

Route

04

Split

Docs-only workflow

Project documentation

Ask on no-args

README generation

Do not auto-init silently

Codebase summaries

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Action init, update, summarize, or picker
  2. 2 Scan Read project structure and existing docs
02

Work

Agent / skill execution

  1. 3 Route docs-manager for init/update
  2. 4 Split Oversized docs require split or accept choice
03

Verify

Gate, review, validation

  1. 5 Write README/core docs or codebase summary
  2. 6 Validate Warnings reported, not blocking

Modes / Routes

init

Create baseline project docs

Research:
project scan
Review:
doc size
Validate:
docs exist
update

Sync existing docs to current code

Research:
diff/code scan
Review:
stale docs
Validate:
warnings
summarize

Create or refresh codebase summary

Research:
code scan
Review:
coverage
Validate:
summary
[no args]

Ask which docs action to run

Research:
picker
Validate:
user choice

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Default Recommended
/ck:docs
Use when:
You want the command to ask init/update/summarize.
Expected:
Picker opens instead of auto-running documentation writes.
init
/ck:docs init
Use when:
The project needs baseline documentation.
Expected:
Creates README/core docs after docs-manager routing.
update
/ck:docs update
Use when:
Existing docs need syncing to current code.
Expected:
Updates affected docs and reports warnings.
summarize
/ck:docs summarize
Use when:
You need a codebase summary without broad docs rewrite.
Expected:
Writes or refreshes docs/codebase-summary.md.
Init target
/ck:docs init README.md docs/system-architecture.md
Use when:
Specific docs should be created or refreshed.
Expected:
Only requested documentation surfaces are handled.
Update scope
/ck:docs update src/auth
Use when:
Only docs affected by one code area should change.
Expected:
Scoped docs update with code-aware summary.

Handled Scope

  • Project documentation
  • README generation
  • Codebase summaries
  • Docs refresh
  • Documentation validation

Artifacts Produced

Documentation Artifacts

Pattern

README.md + docs/*.md + docs/codebase-summary.md

Outputs initialized or refreshed documentation, codebase summary, and validation warnings when relevant.

Quick Ref / Command

Engineer Kit

/ck:xia

Feature extraction and porting front door for comparing, copying, improving, or rewriting behavior from another repository.

01

Recon

02

Map

03

Analyze

04

Challenge

Understand before copy

Feature extraction

Challenge before plan

Cross-stack porting

Adapt instead of transplant

Dependency mapping

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Recon Pack source safely and scout local integration points
  2. 2 Map Break feature into layers and dependency matrix
02

Work

Agent / skill execution

  1. 3 Analyze Trace behavior, contracts, config, and data flow
  2. 4 Challenge 5+ trade-off questions and decision matrix
03

Verify

Gate, review, validation

  1. 5 Plan Delegate approved anatomy to ck:plan
  2. 6 Deliver Comparison report or plan path for ck:cook

Modes / Routes

--compare

Report only; no implementation plan

Research:
Yes
Review:
challenge
Validate:
recommendation
--copy

Minimal transplant with compatibility checks

Research:
Yes
Review:
challenge
Validate:
ck:plan handoff
--improve

Borrow behavior and replace anti-patterns

Research:
Yes
Review:
challenge
Validate:
ck:plan handoff
--port

Idiomatic local-stack rewrite; default route

Research:
Yes
Review:
challenge
Validate:
ck:plan handoff
--fast

Skip research/challenge for low-risk speed

Research:
Skip
Review:
skipped
Validate:
explicit trade-off
--auto

Full workflow with auto-approved gates

Research:
Yes
Review:
auto-approved
Validate:
final handoff

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

--compare Recommended
/ck:xia vercel/next.js "metadata handling" --compare
Use when:
You need source-vs-local understanding without planning code changes.
Expected:
Head-to-head report with recommendation and no implementation handoff.
--copy
/ck:xia owner/repo "command palette" --copy
Use when:
The source feature should stay close to the original implementation.
Expected:
Challenge gate, compatibility gaps, minimal adaptation plan.
--improve
/ck:xia ../reference-app "billing checkout" --improve
Use when:
You want to borrow behavior but replace source anti-patterns.
Expected:
Decision matrix plus refactor-aware implementation plan.
--port
/ck:xia remix-run/react-router "nested route loaders" --port
Use when:
The source stack differs and should be rewritten idiomatically.
Expected:
Local-stack plan with rollback strategy and cook handoff.
--fast
/ck:xia owner/repo "toast notification UX" --fast
Use when:
You accept skipping research/challenge for a low-risk feature study.
Expected:
Faster source map and handoff; approval trade-off is explicit.
--auto
/ck:xia owner/repo "settings import flow" --auto
Use when:
You want the full workflow but allow gates to auto-approve.
Expected:
Full recon/map/analyze/challenge with auto-approved gates and final handoff.

Handled Scope

  • Feature extraction
  • Cross-stack porting
  • Dependency mapping
  • Trade-off analysis
  • Implementation handoff

Artifacts Produced

Feature Porting Packet

Pattern

plans/reports/feature-comparison-<slug>.md or ./plans/<plan-dir>/plan.md + source/dependency/decision matrices

Outputs source manifest, source anatomy, local map, dependency matrix, decision matrix, risk score, and either comparison recommendation or ck:cook handoff.

Quick Ref / Team orchestration

Parallel multi-session

/ck:team

Use it to spawn N independent Claude Code teammates in parallel — research from multiple angles, cook many files, review multiple focuses, or debug competing hypotheses.

01

Invoke

02

Pre-flight

03

Spawn N

04

Synth + close

Execution Map

Four lanes: setup pre-flight, parallel spawn, event-driven coordination, then synthesize and close.

01

Setup

Invoke + pre-flight check

  1. 1 Invoke /ck:team <template> <context> [flags] — pick research / cook / review / debug + optional --devs/--researchers/--reviewers/--debuggers N, --delegate, --worktree
  2. 2 Pre-flight MANDATORY — call TeamCreate(team_name) directly; success continues, error ABORTS (no subagent fallback). Env flag + CLI terminal + Opus 4.6 must all hold
02

Spawn

Derive N + spawn in parallel

  1. 3 Derive N Split input into N independent work items (default N=3) — angles (research) / file-owned tasks + tester blocker (cook) / focuses (review) / competing hypotheses (debug). TaskCreate × N
  2. 4 Spawn Agent tool × N in parallel — model: opus, run_in_background: true, isolation: worktree (cook devs only). Each prompt includes the mandatory CK Context Block
03

Coordinate

Hooks + teammate DM

  1. 5 Coordinate React to TaskCompleted / TeammateIdle hook events (60s TaskList fallback). Teammates DM each other via SendMessage — adversarial in debug, lead-routed in cook
04

Close

Synthesize + shutdown

  1. 6 Synthesize Lead reads all reports. research → research-summary-<slug>.md. cook → git merge --no-ff worktree branches sequentially + MANDATORY Docs impact eval. review → dedupe + prioritize CRITICAL/IMPORTANT/MODERATE. debug → surviving theory = root cause
  2. 7 Shutdown SendMessage(shutdown_request) × N → TeamDelete (NO params) → /ck:journal → report to user. Agent memory at $HOME/.claude/agent-memory/<name>/ persists separately

Templates

Pick a template by need. Each one has its own default N, behaviour, and artifact.

research Default N: 3

Research from N angles

Sample prompt

/ck:team research Compare auth strategies for our SaaS app

Use when

Architecture decisions, technology evaluation, multi-angle investigation.

Output

research-summary-<slug>.md — exec summary, comparative analysis, recommendations.

cook Default N: 4 devs + 1 tester

Cook with file-owned devs

Sample prompt

/ck:team cook plans/.../plan.md --devs 4 --worktree

Use when

Multi-file feature implementation with parallel devs in isolated worktrees.

Output

Merged branches via git merge --no-ff + MANDATORY docs sync eval + test results.

review Default N: 3

Review N focuses

Sample prompt

/ck:team review src/api --reviewers 3

Use when

Pre-merge review with security, performance, and test-coverage lanes in parallel.

Output

review-<slug>.md — severity-dedupe (CRITICAL / IMPORTANT / MODERATE) + action items.

debug Default N: 3

Debug competing hypotheses

Sample prompt

/ck:team debug "Webhook returns 500 intermittently" --debuggers 3

Use when

Hard-to-reproduce bugs where you want adversarial disproof to converge on root cause.

Output

debug-<slug>.md — root cause + evidence chain + disproven hypotheses.

Per-Template Artifacts

Per-Template Report

Lead synthesizes the report after every teammate finishes. Fixed location at plans/reports/.

plans/reports/
research-summary / cook merge+docs / review-<slug> / debug-<slug>.md

Core Principles

These five rules apply to every template — violating them breaks team execution.

  1. 1 TeamCreate-first — NEVER fall back to subagents on failure
  2. 2 File ownership boundaries — devs must not overlap on cook tasks
  3. 3 CK Context Block in EVERY spawn prompt — teammates need it to find reports/plans
  4. 4 Refer to teammates by NAME (not agent ID) in recipient + owner fields
  5. 5 Adversarial in debug — let competing hypotheses converge by mutual disproof

Quick Ref / Visual utility

Read-only · never modifies code

/ck:preview

View files or generate visual explanations, diagrams, and slide decks — in the browser or as a self-contained HTML page. A read/visualize utility that never modifies code.

01

Input

02

Route

03

Generate

04

Output

Execution Map

One input (file path or generate flag + topic) runs through four stages: receive, route, generate, then emit to the browser or a self-contained HTML page.

01

Receive

File path or generate flag + topic

  1. 1 Input A file path, or a generate flag + topic (add --html for a browser page)
  2. 2 Plan Context Hook injects active plan — visuals save to {plan_dir}/visuals/ (fallback plans/visuals/)
02

Route + generate

Pick a shape, build prose + ASCII + Mermaid

  1. 3 Route Path → file preview/walkthrough · Topic → pick explain/diagram/slides/ascii
  2. 4 Generate Build prose + ASCII + Mermaid (mermaidjs-v11 syntax); tech-graph for publish-grade SVG/PNG
03

Emit

Live browser or self-contained HTML

  1. 5 Output Markdown auto-opens in browser (Mermaid live) · --html = self-contained shareable page

Usage by Role

View (no flag) takes a path to read/walk through a file. Eight flags in three groups: Generate picks an output shape from a topic; --html wraps any generate flag into a standalone page; the Review group requires --html.

View · no flag

Read an existing file/dir — plans in novel UI

  • <file.md>

    View one markdown file (plan, phase, doc) in the novel-reader UI — Mermaid renders live.

    Sample prompt

    /ck:preview plans/.../plan.md
  • <dir/>

    Pass a folder to browse every doc inside — e.g. a whole plan folder (plan.md + all phase files).

    Sample prompt

    /ck:preview plans/260527-.../
  • <path>

    View reads the file as-is. Contrast with generate flags (--explain / --diagram / --slides / --ascii): they take a topic in plain words and build a new visual — not a path.

    Sample prompt

    /ck:preview src/auth/middleware.ts

Generate

Pick one output shape from a topic

  • --explain

    Visual explanation of code or a concept — narrative + ASCII + Mermaid diagrams

    Sample prompt

    /ck:preview --explain How does the auth middleware chain work in this repo
  • --diagram

    Architecture and data-flow diagrams

    Sample prompt

    /ck:preview --diagram Data flow from webhook to notification queue
  • --slides

    Step-by-step walkthrough as a slide deck

    Sample prompt

    /ck:preview --slides "onboarding flow"
  • --ascii

    Terminal-friendly ASCII diagram (no browser needed)

    Sample prompt

    /ck:preview --ascii "folder structure"

Output

Composes with any generate flag

  • --html

    Self-contained HTML page — composes with any generate flag, opens directly in browser

    Sample prompt

    /ck:preview --html --diagram "DB schema"

Review · implies --html

Diff, plan-vs-code, and recap views

  • --diff [ref]

    Visual diff review of changes (requires --html)

    Sample prompt

    /ck:preview --diff HEAD~3
  • --plan-review [plan-file]

    Compare a plan file against the actual codebase — implies --html. Omit the path to use the active plan.

    Sample prompt

    /ck:preview --plan-review plans/.../plan.md

    Omit path → active plan

    /ck:preview --plan-review
  • --recap [timeframe]

    Project context snapshot over a timeframe (requires --html)

    Sample prompt

    /ck:preview --recap "last week"

Delivery

Which modes need a local server, which are self-contained.

Local server

markdown-novel-viewer

  • View (file / dir)
  • Markdown generation

Self-contained

No server — opens in browser

  • --html + generate flag
  • Review (--diff / --plan-review / --recap)
Stop server /ck:preview --stop

Visual Output

  • Explanation / diagram / slides / ascii
  • Markdown auto-opens with live Mermaid
  • --html is shareable with no server
  • Diff / plan-review / recap produce review-grade visuals
Pattern
{slug}.md (browser) · {slug}.html (self-contained)
Location
Active plan {plan_dir}/visuals/
Fallback plans/visuals/

With an active plan, visuals live inside that plan folder. No plan → falls back to plans/visuals/.

Core Principles

Five rules that shape how preview behaves — always safe, always shareable.

  1. 1 Read/visualize only — never modifies code
  2. 2 --html is self-contained — opens in any browser, no server
  3. 3 Markdown mode renders Mermaid live via markdown-novel-viewer
  4. 4 Visuals colocate with the active plan folder
  5. 5 Pairs with ck:mermaidjs-v11 (syntax) and ck:tech-graph (publish-grade)
See all ClaudeKit commands

Quick Ref / Command

Engineer Kit

/ck:chrome-profile

Target a real Google Chrome profile — account, cookies, workspace, tenant — for browser automation through Chrome DevTools MCP, with profile discovery, bridge diagnostics, and URL-anchor tab selection.

01

Decide

02

Resolve Profile

03

Bridge

04

Open

Use only when real profile state matters

Real Chrome profile targeting

Resolve keys by account, not directory

Chrome DevTools MCP bridge

doctor is a heuristic — confirm with a live probe

Profile discovery

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Decide Is real profile state required?
  2. 2 Resolve Profile list/setup maps key by account/name
02

Work

Agent / skill execution

  1. 3 Bridge doctor heuristic + live MCP probe
  2. 4 Open open --json emits a cdp-open token
03

Verify

Gate, review, validation

  1. 5 Bind Tab Select the exact tab by token
  2. 6 Operate Snapshot, click, evaluate via MCP

Modes / Routes

list

Show resolvable profile keys

Research:
Local State
Review:
no secrets
Validate:
key resolves
setup

Map profiles to stable keys (per-machine)

Research:
Local State
Review:
user confirm
Validate:
profiles.json
doctor

Static bridge-readiness heuristic

Research:
config scan
Review:
not sole truth
Validate:
live MCP probe
open --json

Open URL in profile; emit bind selector

Research:
profile key
Review:
token bind
Validate:
tab matches token
--force

Open when CLI cannot classify a working bridge

Research:
live probe
Review:
probe first
Validate:
bind after open
--no-activate

Open in background, return focus (macOS)

Research:
none
Review:
background
Validate:
tab opened

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Open in profile Recommended
chrome-profile open --json work "https://github.com/org/repo/pulls"
Use when:
Automation needs the user's real logged-in Chrome profile.
Expected:
Tab opened with a cdp-open token to bind the exact MCP page.
List profiles
chrome-profile list
Use when:
You need to see which profile keys resolve on this machine.
Expected:
Resolvable keys by account email / display-name substring.
Setup mappings
chrome-profile setup --yes
Use when:
First-time bootstrap or a profile key does not resolve.
Expected:
Stable keys written to per-machine profiles.json.
Doctor + probe
chrome-profile doctor
Use when:
You need to know if the opened tab is readable via the bridge.
Expected:
Static readiness; confirm with a live Chrome DevTools MCP probe.
Background open
chrome-profile open --json --no-activate work "https://example.com"
Use when:
On macOS you want the tab opened without stealing focus.
Expected:
Profile tab opened, focus returns to the previous app.
Force open
chrome-profile open --json work "https://example.com" --force
Use when:
A live MCP probe works but an older CLI still refuses the bridge.
Expected:
Tab opened; immediately bind to the returned bind_selector.

Handled Scope

  • Real Chrome profile targeting
  • Chrome DevTools MCP bridge
  • Profile discovery
  • URL-anchor tab binding
  • Browser automation

Artifacts Produced

Bound Profile Tab + Open Payload

Pattern

open --json: { bind_selector, opened_url, profile_dir, profile_key, profile_marker }

Emits machine-readable binding data so the agent selects the exact profile tab from a flat MCP page list, then operates (snapshot/click/evaluate/screenshot) on the user's real session.

Quick Ref / Command

Engineer Kit

/ck:coding-level

Set coding experience level for tailored output. Use for adjusting explanation depth, code complexity, and response format to user expertise.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Beginner Recommended
/ck:coding-level beginner
Use when:
You want simplified explanations and basic code examples.
Expected:
Responses use plain language and beginner-friendly patterns.
Intermediate
/ck:coding-level intermediate
Use when:
You want standard explanations without over-simplification.
Expected:
Responses assume working knowledge of the stack.
Expert
/ck:coding-level expert
Use when:
You want terse, high-signal responses without hand-holding.
Expected:
Responses skip basics and use advanced patterns directly.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:copywriting

Conversion copywriting formulas, headline templates, email copy patterns, landing page structures, CTA optimization, and writing style extraction. Activate for writing high-converting copy, crafting headlines, email campaigns, landing pages, or applying custom writing styles from assets/writing-styles/ directory.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Headline formula Recommended
/ck:copywriting headline formula "VividKit early access launch"
Use when:
You need multiple headline variants using proven formulas.
Expected:
Headline options using AIDA/PAS and platform variants.
Landing page
/ck:copywriting landing page "ClaudeKit workflow visualizer feature"
Use when:
You need structured landing page copy with sections.
Expected:
Hero, benefits, social proof, CTA sections.
Email campaign
/ck:copywriting email "Reactivate beta users who signed up 30 days ago"
Use when:
You need email copy for a specific segment and goal.
Expected:
Subject lines, preview text, body, and CTA variants.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:databases

Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

schema/query

Design schemas, write queries, or optimize indexes

Research:
table/index map
Review:
edge cases
Validate:
SQL runs
migration

Write and validate database migration scripts

Research:
current schema
Review:
data safety
Validate:
dry-run
admin/ops

Configure replication, backup, users, or performance tuning

Research:
server config
Review:
production risk
Validate:
applied check

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Schema design Recommended
/ck:databases design schema for a multi-tenant SaaS with user, org, and billing tables in PostgreSQL
Use when:
You need a normalized schema with relationships and constraints.
Expected:
ERD, CREATE TABLE statements, indexes, foreign keys.
Query optimization
/ck:databases optimize this slow PostgreSQL query that times out on 5M rows
Use when:
A query is too slow and needs index or rewrite help.
Expected:
EXPLAIN ANALYZE output, index recommendations, rewritten query.
MongoDB aggregation
/ck:databases write MongoDB aggregation pipeline to group orders by user and sum revenue per month
Use when:
You need a complex aggregation with grouping and computed fields.
Expected:
Working aggregation pipeline with stage-by-stage explanation.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:devops

Deploy and manage cloud infrastructure on Cloudflare (Workers, R2, D1, KV, Pages, Durable Objects, Browser Rendering), Docker containers, and Google Cloud Platform (Compute Engine, GKE, Cloud Run, App Engine, Cloud Storage). Use when deploying serverless functions to the edge, configuring edge computing solutions, managing Docker containers and images, setting up CI/CD pipelines, optimizing cloud infrastructure costs, implementing global caching strategies, working with cloud databases, or building cloud-native applications.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

deploy

Deploy to edge, container, or cloud platform

Research:
platform config
Review:
rollback plan
Validate:
endpoint reachable
CI/CD

Set up or fix CI/CD pipelines and automation

Research:
pipeline config
Review:
secret exposure
Validate:
pipeline passes
infra/ops

Manage infrastructure, scaling, or cost optimization

Research:
resource map
Review:
availability risk
Validate:
health check

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Cloudflare Workers Recommended
/ck:devops deploy Edge API to Cloudflare Workers with KV storage and D1 database
Use when:
You need to deploy a serverless edge function with persistence.
Expected:
wrangler.toml, deploy commands, KV/D1 binding config.
Docker compose
/ck:devops containerize the app with Docker Compose, Nginx reverse proxy, and health checks
Use when:
You need a production-ready container setup.
Expected:
Dockerfile, compose.yml, nginx config, health endpoint.
GKE deployment
/ck:devops deploy to Google Kubernetes Engine with autoscaling and Cloud Run fallback
Use when:
You need a managed Kubernetes deployment on GCP.
Expected:
k8s manifests, HPA config, Cloud Run fallback strategy.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:find-skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Capability search Recommended
/ck:find-skills Is there a skill that can generate images?
Use when:
You want to know if a skill exists for a capability.
Expected:
Matching skill name with install command.
Domain discovery
/ck:find-skills What skills are available for marketing?
Use when:
You need an overview of skills in a domain.
Expected:
List of relevant skills with brief descriptions.
Task routing
/ck:find-skills How do I create a Mermaid architecture diagram?
Use when:
You have a task and want the best skill for it.
Expected:
Recommended skill and example command.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:frontend-development

Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

component

Build or refactor a React component with types and tests

Research:
design spec
Review:
a11y gaps
Validate:
render + types
state/data

Wire up state management, queries, or data fetching

Research:
data shape
Review:
stale state
Validate:
hooks pass
performance

Audit and fix React performance issues

Research:
profiler
Review:
regression
Validate:
metrics before/after

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

React component Recommended
/ck:frontend-development Build a reusable Pagination component with TypeScript, accessible keyboard nav, and Tailwind
Use when:
You need a type-safe, accessible React component from scratch.
Expected:
Component with props, tests, Storybook story, and a11y.
Performance audit
/ck:frontend-development Audit and fix React performance issues in the data table — too many re-renders
Use when:
A component is slow due to excessive re-renders.
Expected:
Profiling, memo/callback fixes, and before/after metrics.
State management
/ck:frontend-development Add Zustand state management for the cart without prop drilling across 5 components
Use when:
A shared state pattern needs a proper store solution.
Expected:
Zustand store, selectors, and updated component integration.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:gkg

Semantic code analysis with GitLab Knowledge Graph. Use for go-to-definition, find-usages, impact analysis, architecture visualization. Supports Ruby, Java, Kotlin, Python, TypeScript/JavaScript.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Symbol lookup Recommended
/ck:gkg go-to-definition AuthService
Use when:
You need to find where a class or function is defined.
Expected:
Definition location with file path and line context.
Find usages
/ck:gkg find-usages useCurrentUser
Use when:
You need all call sites for a hook or function.
Expected:
Usage list with file paths and call context.
Semantic search
/ck:gkg search "authentication token refresh logic"
Use when:
You need semantic code search beyond simple grep.
Expected:
Ranked results with relevance context.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:google-adk-python

Build AI agents with Google ADK Python. Multi-agent systems, tool integration, workflow orchestration.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

single agent

Build a single conversational agent with tools and memory

Research:
capability scope
Review:
prompt injection
Validate:
agent responds + tools call
multi-agent

Orchestrate planner and specialist sub-agents

Research:
routing logic
Review:
loop risk
Validate:
pipeline completes
streaming

Add real-time token streaming output to an agent

Research:
transport setup
Review:
backpressure
Validate:
tokens stream live

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Basic agent Recommended
/ck:google-adk-python Build a customer support agent with tool calling and session memory in Python ADK
Use when:
You need a conversational agent with tool use.
Expected:
Agent class, tool definitions, and session config.
Multi-agent
/ck:google-adk-python Create a multi-agent pipeline where a planner routes tasks to specialized sub-agents
Use when:
You need agent orchestration with routing.
Expected:
Planner agent, specialist agents, and routing logic.
Streaming
/ck:google-adk-python Add streaming output to the research agent for real-time token delivery
Use when:
An agent needs live streaming responses.
Expected:
Streaming handler with token-by-token output.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:journal

💡 Write some journal entries.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Session decisions Recommended
/ck:journal Document the decisions made in this session for the auth refactor
Use when:
You want to preserve architecture decisions for future reference.
Expected:
Journal entry with decisions, rationale, and next steps.
Post-ship
/ck:journal Write a post-ship journal for the webhook integration we just deployed
Use when:
A shipped feature needs documentation of lessons learned.
Expected:
Journal with what worked, what failed, and next improvements.
Technical debt
/ck:journal Log the technical debt we are accepting with the current pagination hack
Use when:
You want to formally record a trade-off decision.
Expected:
Debt entry with scope, impact, and planned resolution.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:loop

Autonomous iterative optimization loop — run N iterations against a mechanical metric, learn from git history, auto-keep/discard changes. Use for improving measurable metrics (coverage, performance, bundle size, etc.) through repeated experimentation.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Coverage goal Recommended
/ck:loop Goal: branch coverage >80 | Scope: src/**/*.ts | Verify: npm run coverage:score | Iterations: 8
Use when:
You need autonomous iteration to improve a numeric metric.
Expected:
Atomic keep/discard log with metric delta per iteration.
Performance goal
/ck:loop Goal: p95 response time <150ms | Scope: src/api/search.ts | Verify: npm run bench | Iterations: 5
Use when:
A performance metric needs bounded improvement loops.
Expected:
Optimization changes tracked against benchmark results.
Quality score
/ck:loop Goal: Lighthouse a11y score >95 | Scope: src/components/ | Verify: npm run lighthouse:a11y | Iterations: 6
Use when:
An automated quality score should improve iteratively.
Expected:
Components fixed with score evidence for each iteration.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:markdown-novel-viewer

View markdown files with calm, book-like reading experience. Background HTTP server for rendering markdown.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

default (open)

Open and render a markdown file in book-like reading view

Research:
file path
Validate:
browser opens + renders
--background

Start background HTTP server for persistent markdown viewing

Research:
server port
Validate:
server running at localhost
--stop

Stop the background markdown viewer server

Validate:
server stopped

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Long doc view Recommended
/ck:markdown-novel-viewer Open the RFC for the new authentication system for reading
Use when:
You need to read a long markdown document comfortably.
Expected:
Document opened in browser-friendly reading mode.
Spec view
/ck:markdown-novel-viewer Open plans/phase-02-auth-implementation.md for review
Use when:
You need to review a spec document with full formatting.
Expected:
Spec rendered with Mermaid diagrams and table of contents.
Research doc
/ck:markdown-novel-viewer Read the researcher-01-report.md from the plans folder
Use when:
You need to review a research report before acting on it.
Expected:
Research report in readable view with section navigation.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

new server

Scaffold a new MCP server with tool definitions and transport

Research:
API shape
Review:
schema drift
Validate:
server starts + tools listed
add tool

Add new tool handlers to an existing MCP server

Research:
existing tools
Review:
input edge cases
Validate:
tool responds
convert

Convert existing scripts or APIs into MCP tool endpoints

Research:
script signature
Review:
auth exposure
Validate:
tool callable via MCP

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

New MCP server Recommended
/ck:mcp-builder Build an MCP server exposing file search and grep tools over HTTP transport
Use when:
You need a new MCP server from scratch.
Expected:
MCP server package with tool definitions, transport config, and tests.
Add tools
/ck:mcp-builder Add a code-execution tool to the existing MCP server in src/mcp-server/
Use when:
An existing MCP server needs new tool capabilities.
Expected:
New tool handler integrated with proper schema and error handling.
Convert script
/ck:mcp-builder Convert the scripts/analysis.py script into an MCP tool endpoint
Use when:
An existing script should become an MCP-accessible tool.
Expected:
MCP tool wrapper with input schema, response format, and docs.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:media-processing

Process multimedia files with FFmpeg (video/audio encoding, conversion, streaming, filtering, hardware acceleration), ImageMagick (image manipulation, format conversion, batch processing, effects, composition), and RMBG (AI-powered background removal). Use when converting media formats, encoding videos with specific codecs (H.264, H.265, VP9), resizing/cropping images, removing backgrounds from images, extracting audio from video, applying filters and effects, optimizing file sizes, creating streaming manifests (HLS/DASH), generating thumbnails, batch processing images, creating composite images, or implementing media processing pipelines. Supports 100+ formats, hardware acceleration (NVENC, QSV), and complex filtergraphs.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

video (FFmpeg)

Encode, convert, trim, or compress video files

Research:
source codec/bitrate
Review:
quality regression
Validate:
output playable
image (ImageMagick)

Resize, convert, composite, or batch process images

Research:
input format/size
Review:
color profile
Validate:
output renders
background removal

AI-powered background removal from images via RMBG

Research:
subject complexity
Review:
edge quality
Validate:
transparency preserved

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Video compress Recommended
/ck:media-processing Compress the demo.mp4 to under 10MB for web delivery using FFmpeg
Use when:
A video file is too large for web use.
Expected:
Compressed MP4 with quality-size tradeoff report.
Image batch resize
/ck:media-processing Resize all images in assets/products/ to 800x800 WebP with ImageMagick
Use when:
You need to batch process and convert images.
Expected:
Converted WebP files with size comparison.
Audio chunk
/ck:media-processing Split the 2-hour podcast.mp3 into 15-minute chunks for transcription
Use when:
A long audio file needs splitting before processing.
Expected:
Chunked audio files ready for transcription pipeline.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:mermaidjs-v11

Create diagrams and visualizations using Mermaid.js v11 syntax. Use when generating flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, Gantt charts, user journeys, timelines, architecture diagrams, or any of 24+ diagram types. Supports JavaScript API integration, CLI rendering to SVG/PNG/PDF, theming, configuration, and accessibility features. Essential for documentation, technical diagrams, project planning, system architecture, and visual communication.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

flowchart/sequence

Create flowcharts, sequence, or state diagrams

Research:
flow structure
Review:
v11 syntax
Validate:
diagram renders
entity/ER

Model data structures with ER or class diagrams

Research:
domain model
Review:
cardinality errors
Validate:
diagram valid
architecture

Generate C4 container or architecture diagrams

Research:
component map
Review:
missing links
Validate:
all nodes render

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Flowchart Recommended
/ck:mermaidjs-v11 Draw a flowchart for the user authentication login flow with error paths
Use when:
You need a process flowchart with decision nodes.
Expected:
Valid Mermaid v11 flowchart code with render instructions.
Sequence diagram
/ck:mermaidjs-v11 Create a sequence diagram for the webhook delivery retry mechanism
Use when:
You need to document message flow between systems.
Expected:
Mermaid sequence diagram with actors, messages, and alt paths.
Architecture
/ck:mermaidjs-v11 Generate a C4 container diagram for the microservices backend
Use when:
You need an architecture diagram for system documentation.
Expected:
C4-style Mermaid diagram with containers and dependencies.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:mintlify

Build and maintain Mintlify documentation sites. Covers docs.json, MDX components, navigation, page frontmatter, theming, OpenAPI/AsyncAPI, AI docs assets such as llms.txt and skill.md, deployment targets, and local validation CLI commands.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Init docs site Recommended
/ck:mintlify init docs site for the ClaudeKit API with navigation, landing page, and quickstart
Use when:
You need a new Mintlify documentation site from scratch.
Expected:
mint.json, docs structure, navigation, and initial pages.
API reference
/ck:mintlify Add API reference pages for all REST endpoints with request/response examples
Use when:
Existing API needs Mintlify documentation pages.
Expected:
MDX pages with endpoint specs, examples, and SDK snippets.
Deploy
/ck:mintlify deploy the docs site to Mintlify hosting and configure the custom domain
Use when:
The docs site needs to be deployed and made public.
Expected:
Deployed URL with custom domain and DNS instructions.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:mobile-development

Build mobile apps with React Native, Flutter, Swift/SwiftUI, Kotlin/Jetpack Compose. Use for iOS/Android, mobile UX, performance optimization, offline-first, app store deployment.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

React Native screen Recommended
/ck:mobile-development Build a React Native onboarding flow with 3 screens, animations, and AsyncStorage
Use when:
You need a native mobile UI with state and storage.
Expected:
Screen components, navigation config, animation, and storage.
Flutter widget
/ck:mobile-development Create a Flutter reusable ProductCard widget with hero animation and responsive layout
Use when:
You need a reusable widget with animation.
Expected:
Flutter widget with state, animation, and responsive breakpoints.
Push notifications
/ck:mobile-development Integrate push notifications using Firebase Cloud Messaging for iOS and Android
Use when:
You need cross-platform push notification support.
Expected:
FCM config, permission handling, and notification payload.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:payment-integration

Integrate payments with SePay (VietQR), Polar (SaaS subscriptions), Stripe (global payments). Use for checkout, webhooks, QR codes, subscriptions, currency conversion, multi-provider order management, commission systems.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Stripe checkout Recommended
/ck:payment-integration Add Stripe Checkout for one-time payments with webhook handling and payment confirmation
Use when:
You need a complete Stripe payment flow.
Expected:
Checkout session, webhook handler, and confirmation page.
Subscription billing
/ck:payment-integration Set up Stripe subscriptions with monthly/annual plans, trial period, and customer portal
Use when:
You need recurring billing with plan management.
Expected:
Subscription plans, billing portal, and cancellation flow.
Polar.sh setup
/ck:payment-integration Configure Polar.sh for open-source sponsorship and one-time product purchases
Use when:
You want a developer-friendly alternative payment integration.
Expected:
Polar product config, webhook events, and purchase flow.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:problem-solving

Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Root cause analysis Recommended
/ck:problem-solving Why is the checkout conversion rate dropping after the last deploy?
Use when:
You need systematic root cause investigation.
Expected:
Evidence chain, hypotheses ranked by likelihood, verification steps.
Decision framework
/ck:problem-solving Should we use server-side sessions or JWTs for auth in this SaaS app?
Use when:
You need a structured approach to a technical decision.
Expected:
Decision matrix with tradeoffs, constraints, and recommendation.
Constraint analysis
/ck:problem-solving We need to support 100k concurrent users within 3 months with the current team of 4
Use when:
A complex goal needs constraint decomposition.
Expected:
Constraint map, feasibility assessment, and phased approach.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:project-management

Track progress, update plan statuses, manage Claude Tasks, generate reports, coordinate docs updates. Use for project oversight, status checks, plan completion, task hydration, cross-session continuity.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Sprint planning Recommended
/ck:project-management Create a 2-week sprint plan for the auth refactor with story points and dependencies
Use when:
You need a sprint plan with task breakdown.
Expected:
Sprint board with stories, points, dependencies, and risk flags.
Status report
/ck:project-management Generate a weekly status report for the Q2 roadmap progress
Use when:
Stakeholders need a progress summary.
Expected:
Status report with completed items, blockers, and next week plan.
Risk register
/ck:project-management Build a risk register for the database migration project
Use when:
You need to identify and track project risks.
Expected:
Risk register with likelihood, impact, and mitigation plans.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:react-best-practices

Apply React and Next.js performance optimization patterns from Vercel Engineering. Use for component optimization, rendering performance, bundle analysis.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Performance review Recommended
/ck:react-best-practices Review these components for unnecessary re-renders and missing memoization
Use when:
You need a React performance audit.
Expected:
Re-render analysis with memo/callback recommendations.
Hook patterns
/ck:react-best-practices Refactor the authentication logic into a custom useAuth hook following React best practices
Use when:
Custom logic needs proper hook extraction.
Expected:
Custom hook with clear API, error handling, and tests.
State architecture
/ck:react-best-practices Design the global state architecture for a multi-step form with validation
Use when:
A complex form needs a state management strategy.
Expected:
State shape, update patterns, validation integration, and tests.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:remotion

Best practices for Remotion - Video creation in React

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

composition

Create a new Remotion composition with timeline and props

Research:
scene design
Review:
frame rate
Validate:
previews in browser
animation

Add motion, easing, and Spring animations to scenes

Research:
animation spec
Review:
jank at fps
Validate:
smooth playback
export

Configure render pipeline and export final video

Research:
codec/resolution needs
Review:
file size
Validate:
exported file plays

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Intro animation Recommended
/ck:remotion Create a 5-second product intro animation with logo reveal and tagline for VividKit
Use when:
You need a short programmatic video intro.
Expected:
Remotion composition with timeline, easing, and export config.
Data visualization
/ck:remotion Build a bar chart race animation showing monthly user growth over 12 months
Use when:
Data should be visualized as an animated video.
Expected:
Remotion chart animation with interpolated data per frame.
Slide deck video
/ck:remotion Generate a video walkthrough of the ClaudeKit guide slides with voiceover timing
Use when:
A slide deck needs to become a shareable video.
Expected:
Video with slide transitions and synchronized audio timing.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:html-video

Turn HTML/CSS/JS templates into real local MP4 videos through headless Chromium and ffmpeg, with template discovery, Studio editing, and ffprobe-verified renders.

01

Brief

02

Setup

03

Discover

04

Build

Pin the brief before creating

HTML/CSS/JS video templates

Prefer binary, never vendor the engine

Template discovery

doctor passes before render

Studio editing

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Brief Pin audience, duration, aspect, output, proof vs polished
  2. 2 Setup Resolve CLI, run doctor and list-engines
02

Work

Agent / skill execution

  1. 3 Discover search-templates then inspect-template schemas
  2. 4 Build Create project, set template, add assets and vars
03

Verify

Gate, review, validation

  1. 5 Preview Open html_path or tune layout in Studio
  2. 6 Render + Verify project-render then ffprobe confirms the MP4

Modes / Routes

doctor

Diagnostics for Chromium, ffmpeg, engines

Research:
No
Review:
env
Validate:
doctor pass
search-templates

Rank templates by intent and aspect

Research:
Yes
Review:
schema
Validate:
inspect-template
project-set-var(s)

Set template variables by CLI

Research:
No
Review:
schema
Validate:
inspect-template
studio

Interactive editor for empty-schema templates

Research:
No
Review:
layout
Validate:
preview
project-render

Render MP4 to explicit output path

Research:
No
Review:
render
Validate:
ffprobe

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Brief Recommended
/ck:html-video short product promo for a developer tool, 16:9, 20s
Use when:
You have a video brief and want a template-driven local render.
Expected:
Brief pinned, template chosen, project rendered to a verified MP4.
Doctor
html_video doctor && html_video list-engines
Use when:
You need to verify Chromium, ffmpeg, and available engines first.
Expected:
Diagnostics report; missing browser/ffmpeg flagged before rendering.
Find template
html_video search-templates --intent "short product promo" --aspect 16:9 --top 5
Use when:
You want to discover and rank templates for the brief.
Expected:
Top templates by intent/aspect; inspect-template reads each schema.
Project + assets
html_video project-create --name "Promo" --intent "..." --aspect 16:9
Use when:
You need a project bound to a template with assets and vars.
Expected:
Project created, template set, assets/vars attached.
Studio
html_video studio --port 3071
Use when:
The template has an empty schema or needs interactive layout tuning.
Expected:
Studio UI for agent-assisted rewrite and layout, then export/render.
Render + verify
html_video project-render <id> --output ./assets/videos/promo.mp4 --stream-progress
Use when:
You want the final local MP4 with proof of a valid render.
Expected:
MP4 written; ffprobe must confirm nonzero duration and dimensions.
Repo summary
/ck:html-video https://github.com/org/repo summary video, 16:9
Use when:
A repo or article should become a short explainer video.
Expected:
Sourced project, template fill, preview, render to verified MP4.

Handled Scope

  • HTML/CSS/JS video templates
  • Template discovery
  • Studio editing
  • Local Chromium render
  • ffmpeg/ffprobe verification

Artifacts Produced

Verified Local MP4 + Project

Pattern

assets/videos/<slug>.mp4 (or plans/<plan>/visuals/<slug>.mp4) + project dir + ffprobe verification

Outputs a verified local MP4 and the html-video project state; finished exports in assets/videos, proof artifacts in plans/<slug>/visuals, scratch in tmp/html-video. Large MP4 files are not committed unless requested.

Quick Ref / Command

Engineer Kit

/ck:research

Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability/security/maintainability analysis.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Technology comparison Recommended
/ck:research Compare Astro vs Next.js for a documentation site with heavy static content
Use when:
You need an evidence-based technology comparison.
Expected:
Research report with trade-offs, benchmarks, and recommendation.
Market research
/ck:research What are the top developer tools pain points in 2025 for AI-assisted coding?
Use when:
You need market insights before building a feature.
Expected:
Synthesized findings with sources and confidence levels.
Library evaluation
/ck:research Find the best TypeScript ORM for a multi-tenant PostgreSQL SaaS app
Use when:
You need to evaluate libraries against specific constraints.
Expected:
Evaluated options with scoring matrix and recommended pick.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:scout

Fast codebase scouting via parallel Explore agents. Locates files, symbols, and context before planning or implementation.

01

Invoke

02

Context

03

Dispatch

04

Search

Scope before searching

File discovery

Read-only, never edit

Symbol search

Parallel agents for speed

Cross-file context gathering

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Target, scope, and optional keywords
  2. 2 Context Read project rules, docs, and active plans
02

Work

Agent / skill execution

  1. 3 Dispatch Spawn parallel Explore agents per target area
  2. 4 Search Glob, grep, read, or symbol search by agent
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report unavailable data

Modes / Routes

file discovery

Find files matching pattern or description

Research:
glob
Validate:
paths
symbol search

Find where a function, type, or constant is defined

Research:
grep
Validate:
location
task context

Gather all relevant files before planning

Research:
read+grep
Validate:
report

Shortcuts Blocked

💭

"Scout will edit the files it finds"

Scout is strictly read-only. It locates and reports. Edits belong to the implementation phase via ck:cook or manual work.

💭

"One broad search will find everything"

Parallel scoped agents are faster and more accurate than one broad search. Break large targets into focused sub-searches.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

File discovery Recommended
/ck:scout Find all API route files and auth middleware
Use when:
You need to locate files before planning a change.
Expected:
File list with paths and relevant context notes.
Symbol search
/ck:scout Where is useAuthSession defined and how is it used?
Use when:
You need to trace a function or type across the codebase.
Expected:
Definition location, usages, and cross-file dependencies.
Task context
/ck:scout Gather context for adding Stripe webhook support
Use when:
You want a targeted context report to hand off to ck:plan.
Expected:
Relevant files, patterns, and existing webhook handling notes.

Handled Scope

  • File discovery
  • Symbol search
  • Cross-file context gathering
  • Parallel agent dispatch
  • Handoff to planning

Artifacts Produced

Scout Report

Pattern

file paths + symbol locations + context notes + skipped checks

Returns file paths, symbol definitions, usage patterns, relevant context, and explicit notes on unavailable data.

Quick Ref / Command

Engineer Kit

/ck:sequential-thinking

Apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification. Use for complex problem decomposition, adaptive planning, analysis needing course correction, problems with unclear scope, multi-step solutions, and hypothesis-driven work.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Complex plan Recommended
/ck:sequential-thinking Plan the migration from REST to GraphQL for the existing API with zero downtime
Use when:
A multi-step plan needs revision capability and reflection.
Expected:
Step-by-step plan with risk notes and revision checkpoints.
Root cause trace
/ck:sequential-thinking Trace the root cause of the memory leak in the WebSocket connection pool
Use when:
A complex bug needs hypothesis-driven sequential investigation.
Expected:
Hypothesis log, elimination steps, and verified root cause.
Architecture decision
/ck:sequential-thinking Should we adopt microservices for the billing module or keep it in the monolith?
Use when:
An architecture decision needs structured multi-step reasoning.
Expected:
Reasoned analysis with constraints, options, and recommendation.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:shader

Write GLSL fragment shaders for procedural graphics. Topics: shapes (SDF), patterns, noise (Perlin/simplex/cellular), fBm, colors (HSB/RGB), matrices, gradients, animations. Use for generative art, textures, visual effects, WebGL, Three.js shaders.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

GLSL gradient Recommended
/ck:shader Write a GLSL fragment shader for an animated noise-based gradient background
Use when:
You need a procedural animated shader effect.
Expected:
Fragment shader code with uniforms and preview instructions.
WebGL particle
/ck:shader Create a WebGL particle system shader for 10,000 particles with gravity and friction
Use when:
You need a high-performance GPU particle effect.
Expected:
Vertex and fragment shaders with particle update logic.
Post-processing
/ck:shader Implement a chromatic aberration post-processing effect for a Three.js scene
Use when:
You need a post-processing shader for an existing 3D scene.
Expected:
Pass shader code integrated with Three.js EffectComposer.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:shopify

Build Shopify applications, extensions, and themes using GraphQL/REST APIs, Shopify CLI, Polaris UI components, and Liquid templating. Capabilities include app development with OAuth authentication, checkout UI extensions for customizing checkout flow, admin UI extensions for dashboard integration, POS extensions for retail, theme development with Liquid, webhook management, billing API integration, product/order/customer management. Use when building Shopify apps, implementing checkout customizations, creating admin interfaces, developing themes, integrating payment processing, managing store data via APIs, or extending Shopify functionality.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

theme

Develop or customise Shopify Liquid theme sections

Research:
schema/settings
Review:
storefront perf
Validate:
section renders in preview
app/extension

Build App Bridge or Checkout UI extensions

Research:
extension target
Review:
app review rules
Validate:
extension loads in sandbox
API integration

Integrate Shopify REST/GraphQL API for store data

Research:
API scope
Review:
rate limits
Validate:
data fetched correctly

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Custom theme section Recommended
/ck:shopify Create a Shopify theme section for product recommendations with Liquid and Polaris styling
Use when:
You need a custom theme section with Liquid templating.
Expected:
Liquid section file, schema JSON, and stylesheet.
App extension
/ck:shopify Build a Shopify App Block extension for displaying trust badges on product pages
Use when:
You need a Shopify App Bridge extension.
Expected:
App block with config schema and storefront rendering.
Checkout UI
/ck:shopify Add a gift message input to the Shopify checkout using Checkout UI Extensions
Use when:
You need a Checkout UI Extension for order customization.
Expected:
UI extension with input validation and order attribute.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:show-off

Create stunning self-contained HTML pages to showcase work. Use for demos, visual presentations, interactive showcases.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

TanStack Query Recommended
/ck:tanstack Add TanStack Query for the user profile data with optimistic updates and error boundaries
Use when:
You need server state management with caching.
Expected:
Query hooks, mutation handlers, and error boundary setup.
TanStack Form
/ck:tanstack Build a multi-step checkout form with TanStack Form, validation, and field-level errors
Use when:
A complex form needs TanStack Form with validation.
Expected:
Form config, validators, and step navigation.
TanStack Router
/ck:tanstack Migrate the existing React Router setup to TanStack Router with type-safe routes
Use when:
You need file-based type-safe routing.
Expected:
Route tree, loaders, and type-safe link components.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:skill-creator

Create or update Claude skills optimized for Skillmark benchmarks — new skills, scripts, references, and capability extensions.

01

Invoke

02

Context

03

Scaffold

04

Optimize

Benchmark-driven

Skill authoring

Clean skill structure

Skillmark benchmarks

Routing accuracy

SKILL.md structure

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Skill name, purpose, target benchmark
  2. 2 Context Existing skills, Skillmark criteria, project rules
02

Work

Agent / skill execution

  1. 3 Scaffold Generate SKILL.md, scripts, references
  2. 4 Optimize Tune for Skillmark benchmark scoring
03

Verify

Gate, review, validation

  1. 5 Validate Test skill activation and output quality

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Create new skill Recommended
/ck:skill-creator Create a new skill called "api-tester" that generates Postman collections from OpenAPI specs
Use when:
You need a new Claude skill from scratch.
Expected:
SKILL.md + install script + reference docs + benchmark score.
Optimize existing skill
/ck:skill-creator Optimize the /ck:debug skill to improve its Skillmark routing accuracy score
Use when:
An existing skill underperforms on benchmarks.
Expected:
Updated SKILL.md with improved routing + benchmark comparison.
Add skill scripts
/ck:skill-creator Add a Python analysis script and reference data to the /ck:security skill
Use when:
You want to extend a skill with scripts or data.
Expected:
New scripts directory + updated SKILL.md with script integration.

Handled Scope

  • Skill authoring
  • Skillmark benchmarks
  • SKILL.md structure
  • Script packaging
  • Reference curation

Artifacts Produced

Workflow Output

Pattern

Skill artifact path + Skillmark score + activation test result

The guide models skill creation as: define, scaffold, optimize for benchmark, validate activation.

Quick Ref / Command

Engineer Kit

/ck:stitch

AI design generation with Google Stitch — text prompt → UI prototype → Tailwind/HTML export → design-to-code pipeline.

01

Invoke

02

Context

03

Generate

04

Export

Prompt clarity

AI design generation

Brand consistency

Tailwind export

Export fidelity

Prototyping

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Text prompt describing desired UI
  2. 2 Context Design system, brand guidelines, project rules
02

Work

Agent / skill execution

  1. 3 Generate Stitch API produces UI design from prompt
  2. 4 Export Convert to Tailwind/HTML/DESIGN.md
03

Verify

Gate, review, validation

  1. 5 Validate Review output and report limitations

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Landing page prototype Recommended
/ck:stitch Generate a SaaS landing page with hero section, features grid, and pricing table
Use when:
You need a quick UI prototype from a text description.
Expected:
Stitch-generated design + exported Tailwind/HTML code.
Dashboard layout
/ck:stitch Create an admin dashboard with sidebar navigation, stats cards, and data table
Use when:
You need a dashboard wireframe converted to code.
Expected:
Dashboard design with Tailwind components ready to integrate.
Mobile-first form
/ck:stitch Design a mobile-first multi-step onboarding form with progress indicator
Use when:
You want AI-generated mobile form design.
Expected:
Multi-step form design exported as responsive Tailwind markup.

Handled Scope

  • AI design generation
  • Tailwind export
  • Prototyping
  • Design-to-code
  • UI composition

Artifacts Produced

Workflow Output

Pattern

Design preview + Tailwind/HTML export path + DESIGN.md + validation summary

The guide models Stitch as a prompt-to-code pipeline: describe, generate, export, validate.

Quick Ref / Command

Engineer Kit

/ck:tanstack

Build with TanStack Start (full-stack React), TanStack Form (headless forms), and TanStack AI (streaming/chat).

01

Invoke

02

Context

03

Route

04

Execute

Type safety first

TanStack Start

Server-client boundary

TanStack Form

Headless patterns

TanStack AI

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command with project scope
  2. 2 Context TanStack docs, project config, existing routes
02

Work

Agent / skill execution

  1. 3 Route Start / Form / AI — pick the right package
  2. 4 Execute Generate routes, server functions, forms, or AI chat
03

Verify

Gate, review, validation

  1. 5 Validate Type-check, test, and verify integration

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

TanStack Start route Recommended
/ck:tanstack Create a new /dashboard route with loader that fetches user stats via server function
Use when:
You need a new full-stack route with server-side data loading.
Expected:
Route file + server function + loader with type-safe params.
TanStack Form
/ck:tanstack Build a registration form with email/password validation using TanStack Form
Use when:
You need headless form management with validation.
Expected:
Form component with field validators and error handling.
TanStack AI chat
/ck:tanstack Add an AI chat panel using TanStack AI with streaming responses
Use when:
You want AI streaming/chat in a TanStack project.
Expected:
Chat component with streaming, message history, and error states.

Handled Scope

  • TanStack Start
  • TanStack Form
  • TanStack AI
  • Server functions
  • Type-safe routing

Artifacts Produced

Workflow Output

Pattern

Route/form/chat artifact + type validation + integration test summary

The guide models TanStack workflows as: route the sub-package, scaffold, validate types, test integration.

Quick Ref / Command

Engineer Kit

/ck:tech-graph

Generate publish-grade SVG+PNG technical diagrams — architecture, data flow, flowchart, sequence, agent/memory, or concept maps — across 8 visual styles, rendered via rsvg-convert.

01

Classify

02

Extract

03

Style

04

Write SVG

Classify before drawing

Architecture diagrams

Semantic arrows + legend

Data flow

Python list SVG method

Sequence

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Classify Pick diagram type from description
  2. 2 Extract Layers, nodes, edges, flows, groups
02

Work

Agent / skill execution

  1. 3 Style Load 1 of 8 style refs + icons
  2. 4 Write SVG Python list method, shapes + arrows
03

Verify

Gate, review, validation

  1. 5 Render rsvg-convert validate then PNG
  2. 6 Report SVG + PNG artifact paths

Modes / Routes

architecture

Architecture diagram

Research:
Layers + services
Review:
Layer grouping
Validate:
No arrows through boxes
data flow

Data flow diagram

Research:
Data transforms
Review:
Semantic arrows
Validate:
Labeled arrows + legend
flowchart

Flowchart / process

Research:
Decision steps
Review:
Grid alignment
Validate:
Diamond/box shapes
sequence

Sequence diagram

Research:
Message order
Review:
Lifelines
Validate:
No label/lifeline clash
agent/memory

Agent + memory map

Research:
Reasoning loop
Review:
Memory tiers
Validate:
Read/write path split
concept map

Mind / concept map

Research:
Central concept
Review:
Radial branches
Validate:
Curved bezier paths
--style N

Visual style 1-8

Research:
Style tokens
Review:
Type fit matrix
Validate:
Color tokens loaded

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Architecture Recommended
/ck:tech-graph architecture diagram for the microservices backend with CDN and data layers
Use when:
You need a publish-grade layered architecture diagram.
Expected:
SVG+PNG with Client→Gateway→Services→Data layers and a legend.
Data flow
/ck:tech-graph data flow for the OAuth login from browser to API to database
Use when:
You want arrows labeled by data type and category.
Expected:
Data flow diagram with semantic arrow colors and labels.
Flowchart
/ck:tech-graph flowchart for the checkout decision and retry process
Use when:
A sequential process with decisions needs a clean flowchart.
Expected:
Top-to-bottom flowchart with decision diamonds and process boxes.
Sequence
/ck:tech-graph sequence diagram of the payment webhook handshake
Use when:
You need time-ordered messages between participants.
Expected:
Lifelines, activation boxes, and alt/loop frames in SVG+PNG.
Agent/memory map
/ck:tech-graph agent memory architecture with working, episodic, and long-term tiers
Use when:
You want an agent reasoning + memory tier diagram.
Expected:
Agent core, memory tiers, tool layer, and read/write paths.
Concept map
/ck:tech-graph concept map for the ClaudeKit skill ecosystem
Use when:
You want a radial mind map from a central concept.
Expected:
Radial concept map with curved bezier branches.
Style select
/ck:tech-graph architecture diagram --style 3
Use when:
You want a specific visual style instead of the default.
Expected:
Same diagram rendered in Blueprint style tokens.
Custom output
/ck:tech-graph ER diagram for the orders schema --output ./docs/orders-er.svg
Use when:
You need the artifact written to an explicit path.
Expected:
ER diagram SVG+PNG saved to the requested location.

Handled Scope

  • Architecture diagrams
  • Data flow
  • Sequence
  • Agent/memory maps
  • Concept maps + UML/ER

Artifacts Produced

Diagram Artifacts

Pattern

./[derived-name].svg + ./[derived-name].png (1920px), or --output path

Produces a validated SVG source and a 2x-retina PNG export per diagram, with a legend when 2+ arrow types are used.

Quick Ref / Command

Engineer Kit

/ck:threejs

Build 3D web apps with Three.js (WebGL/WebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR/XR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

scene setup

Create a Three.js scene with camera, lighting, and geometry

Research:
visual spec
Review:
perf budget
Validate:
renders at target fps
3D model/shader

Load GLTF models or write custom GLSL shaders

Research:
asset spec
Review:
mobile compat
Validate:
model visible + shader compiles
interactivity

Add orbit controls, raycasting, scroll-driven camera, or physics

Research:
interaction spec
Review:
event conflicts
Validate:
interaction responsive

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

3D hero Recommended
/ck:threejs Create a Three.js hero section with rotating particle field and scroll-driven camera animation
Use when:
You need an immersive 3D hero experience.
Expected:
Three.js scene with particles, camera rig, and scroll integration.
3D product showcase
/ck:threejs Build a 3D product model viewer with orbit controls and environment lighting
Use when:
You need an interactive 3D product visualization.
Expected:
GLTF loader, orbit controls, HDR lighting, and responsive canvas.
WebGL shader effect
/ck:threejs Add a custom GLSL water ripple shader effect to the landing page hero mesh
Use when:
You need a custom shader effect on a 3D surface.
Expected:
Shader material with custom uniforms and animation loop.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:ui-styling

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

design system

Set up Tailwind tokens, theme, and brand config

Research:
brand guide
Review:
token conflicts
Validate:
tokens apply globally
shadcn component

Install and customise a shadcn/ui component

Research:
component API
Review:
a11y regression
Validate:
component renders + accessible
dark mode

Implement dark mode with CSS variables and system preference

Research:
color roles
Review:
contrast ratio
Validate:
toggle works in both modes

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Design system tokens Recommended
/ck:ui-styling Set up Tailwind design tokens for colors, typography, spacing aligned to the brand guide
Use when:
You need a consistent token system for the UI.
Expected:
Tailwind config with brand colors, type scale, and spacing.
shadcn component
/ck:ui-styling Add the shadcn DataTable component with sorting, filtering, and pagination
Use when:
You need a shadcn/ui component integrated into the project.
Expected:
Component installation, variant config, and usage example.
Dark mode
/ck:ui-styling Implement dark mode toggle with Tailwind and CSS variables supporting system preference
Use when:
You need a dark mode system with user preference.
Expected:
Theme provider, CSS variables, and toggle component.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:ui-ux-pro-max

UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn/ui MCP for component search and examples.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

design direction

Set visual direction: style, palette, typography, layout

Research:
brand brief
Review:
anti-patterns
Validate:
spec complete
visual audit

Audit existing UI for inconsistencies, a11y, UX issues

Research:
screenshot/component
Review:
contrast failures
Validate:
findings + fixes
motion design

Specify micro-interactions, transitions, and animation system

Research:
interaction spec
Review:
jank/distraction
Validate:
motion spec deliverable

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Design direction Recommended
/ck:ui-ux-pro-max Set design direction for the new settings page: minimal, high-density, dark-first
Use when:
You need expert design guidance before building.
Expected:
Design direction with specific token choices and anti-patterns.
Visual audit
/ck:ui-ux-pro-max Audit the current dashboard for visual inconsistencies and design anti-patterns
Use when:
You need a professional design quality review.
Expected:
Audit report with inconsistencies, severity, and fixes.
Motion design
/ck:ui-ux-pro-max Design the micro-interaction system for button states, toasts, and drawer transitions
Use when:
You need a motion language for the UI.
Expected:
Motion spec with duration, easing, and trigger conditions.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:watzup

💡 Review recent changes and wrap up the work

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Session handoff Recommended
/ck:watzup Generate a handoff summary for this session before switching to a new chat
Use when:
You need context preservation before ending a session.
Expected:
Session summary with decisions, files, and continuation hints.
EOD summary
/ck:watzup Write an EOD summary of today's development work
Use when:
You need a daily development summary.
Expected:
EOD report with completed items, blockers, and tomorrow plan.
Context snapshot
/ck:watzup Create a project context snapshot for onboarding a new team member
Use when:
A new team member needs project context quickly.
Expected:
Context doc with project state, active work, and key decisions.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:web-design-guidelines

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

A11y audit Recommended
/ck:web-design-guidelines Audit the current navigation component for WCAG 2.1 AA compliance
Use when:
You need an accessibility compliance review.
Expected:
A11y report with WCAG violations and remediation steps.
UX review
/ck:web-design-guidelines Review the onboarding form UX for friction points and cognitive load
Use when:
You need a UX quality review with improvement suggestions.
Expected:
UX findings with severity and actionable recommendations.
Design consistency
/ck:web-design-guidelines Audit button styles across all pages for design system consistency
Use when:
You need a cross-page design consistency check.
Expected:
Inconsistency report with pages, elements, and fix suggestions.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:web-frameworks

Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons in outlined/filled styles). Use when creating React applications, implementing server-side rendering, setting up monorepos with multiple packages, optimizing build performance and caching strategies, adding icon libraries, managing shared dependencies, or working with TypeScript full-stack projects.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Modes / Routes

Next.js

Build Next.js App Router pages with RSC, server actions, and ISR

Research:
page design
Review:
hydration mismatch
Validate:
page renders + types pass
Astro

Create Astro pages with component islands and integrations

Research:
content structure
Review:
island hydration
Validate:
page builds clean
monorepo (Turborepo)

Set up or optimise a Turborepo monorepo with shared packages

Research:
workspace map
Review:
dep cycles
Validate:
build cache hits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Next.js App Router Recommended
/ck:web-frameworks Build a Next.js App Router page with RSC, server actions, and Suspense loading
Use when:
You need a Next.js App Router implementation.
Expected:
Server component, client islands, server action, and loading.tsx.
Astro island
/ck:web-frameworks Create an Astro page with a React island for an interactive search component
Use when:
You need an Astro page with hydrated client component.
Expected:
Astro page, React island with client:load, and integration config.
TanStack Start
/ck:web-frameworks Implement a TanStack Start page with loader, mutation, and optimistic UI
Use when:
You need a TanStack Start full-stack route.
Expected:
File-based route with loader, action, and optimistic update.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:web-testing

Web testing strategy and runner: Playwright E2E, Vitest unit/integration, k6 load, visual regression, a11y, and Core Web Vitals.

01

Strategy

02

Setup

03

Write Tests

04

Execute

Strategy before runner

Playwright E2E and visual

Real browser for E2E

Vitest unit and integration

Fix flakiness, do not mask it

k6 load testing

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Strategy Assess test type, runner, and coverage gaps
  2. 2 Setup Configure Playwright, Vitest, or k6
02

Work

Agent / skill execution

  1. 3 Write Tests E2E flows, unit specs, load scenarios, a11y assertions
  2. 4 Execute Run selected runner with real browser or API
03

Verify

Gate, review, validation

  1. 5 Analyze Failures, flakiness, Core Web Vitals, coverage
  2. 6 Report Findings, gaps, recommended next fixes

Shortcuts Blocked

💭

"Flaky tests can just be retried automatically"

Flakiness must be diagnosed and fixed, not masked by retries. Retries hide real bugs and inflate CI time.

💭

"Visual tests always need a new baseline screenshot"

Only update visual baselines when the change is intentional and approved. Blindly updating baselines defeats the purpose of visual regression testing.

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

E2E Playwright Recommended
/ck:web-testing Write Playwright E2E tests for the checkout flow including mobile and a11y checks
Use when:
A critical user flow needs cross-browser automated coverage.
Expected:
Playwright spec files with page objects, assertions, and a11y checks.
Unit Vitest
/ck:web-testing Add Vitest unit tests for the useAuthSession hook covering token refresh logic
Use when:
A hook or utility needs isolated unit test coverage.
Expected:
Vitest specs with edge cases and coverage report.
Load k6
/ck:web-testing Create a k6 load test for the /api/search endpoint targeting p95 under 200ms at 500 VUs
Use when:
An API endpoint needs performance baseline and SLO validation.
Expected:
k6 script with scenarios, thresholds, and summary report.

Handled Scope

  • Playwright E2E and visual
  • Vitest unit and integration
  • k6 load testing
  • Core Web Vitals
  • Accessibility assertions

Artifacts Produced

Test Suite + QA Report

Pattern

test specs + runner output + coverage + failures + performance summary

Outputs test specs, runner results, coverage numbers, failure root causes, performance findings, and recommended next steps.

Quick Ref / Command

Engineer Kit

/ck:worktree

Create isolated git worktree for parallel development

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Create worktree Recommended
/ck:worktree Create an isolated worktree for the feature/auth-refactor branch
Use when:
You need an isolated development branch environment.
Expected:
Worktree created at worktrees/feature-auth-refactor.
List worktrees
/ck:worktree list
Use when:
You need to see all active worktrees.
Expected:
List of worktrees with branch names and paths.
Remove worktree
/ck:worktree remove feature/auth-refactor
Use when:
A merged branch worktree should be cleaned up.
Expected:
Worktree removed and branch reference cleaned.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/excalidraw

>-

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Architecture sketch Recommended
/excalidraw Draw a system architecture sketch for the ClaudeKit multi-agent workflow
Use when:
You need a quick architecture whiteboard diagram.
Expected:
Excalidraw diagram with components, connections, and labels.
Wireframe
/excalidraw Create a low-fidelity wireframe for the new dashboard navigation layout
Use when:
You need a quick UI layout sketch.
Expected:
Wireframe with navigation structure and content placeholders.
Flowchart
/excalidraw Map the user onboarding decision flowchart from signup to first workflow run
Use when:
You need a process flow visualization.
Expected:
Flowchart with decision nodes, happy path, and error branches.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:plans-kanban

Plans dashboard server with progress tracking and timeline visualization.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Plan board Recommended
/ck:plans-kanban Show the current plan phases as a Kanban board
Use when:
You need a visual overview of plan execution status.
Expected:
Kanban board with phases as columns and tasks as cards.
Update status
/ck:plans-kanban Mark phase-02 tasks as completed and move to phase-03
Use when:
You need to update plan progress on the board.
Expected:
Board updated with moved cards and status change.
Blocked view
/ck:plans-kanban Show all blocked tasks across the active plan
Use when:
You need to surface blockers across all phases.
Expected:
Blocked task list with blocking reason and owner.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Engineer Kit

/ck:project-organization

Organize files, directories, and content structure in any project. Use when creating files, determining output paths, organizing existing assets, or standardizing project layout.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Folder structure Recommended
/ck:project-organization Design a folder structure for a monorepo with web, mobile, and API packages
Use when:
You need a project directory organization plan.
Expected:
Folder structure with naming conventions and README guidance.
File naming
/ck:project-organization Define file naming conventions for the frontend TypeScript codebase
Use when:
You need consistent file naming rules.
Expected:
Naming guide with examples for components, hooks, and utilities.
Dependency audit
/ck:project-organization Audit package.json for duplicate, outdated, and unused dependencies
Use when:
You need a dependency health check.
Expected:
Dependency report with removal, update, and consolidation plan.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:persona

Customer persona management: create, analyze, update, and list market-validated ICP profiles.

01

Action

02

Gather

03

Qualify

04

Validate

Five dimensions before create

ICP profiling

Market validation for new personas

Audience segmentation

Existing profile validation before update

Market validation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Action create, analyze, update, list
  2. 2 Gather Ask for five dimensions in create flow
02

Work

Agent / skill execution

  1. 3 Qualify lead-qualifier defines or analyzes persona
  2. 4 Validate researcher validates market fit for create
03

Verify

Gate, review, validation

  1. 5 Analyze analytics-analyst handles behavior data when needed
  2. 6 Framework content-marketing frameworks shape ICP
04

Close

Report, handoff, artifact

  1. 7 Output Save ICP profile

Modes / Routes

create

Create a new persona from five dimensions

Research:
market validation
analyze

Analyze audience data and segments

Research:
analytics
update [name]

Load, revise, and validate existing persona

Validate:
existing profile
list

List saved personas

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

create Recommended
/ckm:persona create "AI-native solo developer using ClaudeKit daily"
Use when:
You need a new ICP/persona from five dimensions.
Expected:
Reusable persona profile with market validation.
analyze
/ckm:persona analyze assets/audience/beta-users.csv
Use when:
You have audience or behavior data to segment.
Expected:
Audience analysis and persona/segment findings.
update [name]
/ckm:persona update solo-dev-founder
Use when:
An existing persona should be revised.
Expected:
Loaded, revised, and validated persona profile.
list
/ckm:persona list
Use when:
You need to see saved personas before choosing one.
Expected:
List of available ICP/persona profiles.

Handled Scope

  • ICP profiling
  • Audience segmentation
  • Market validation
  • Pain point mapping
  • Buying behavior

Artifacts Produced

ICP Profile

Pattern

assets/leads/icp-profiles/{persona}.md

Outputs a reusable persona/ICP profile for campaign, SEO, writing, and email workflows.

Quick Ref / Command

Marketing Kit

/ckm:campaign:*

Campaign planning, execution, status tracking, analysis, and email coordination across marketing channels.

01

Action

02

Context

03

Plan

04

Funnel

Action-specific routing

Campaign briefs

Campaign files are the source for status/analyze

Funnel strategy

Separate strategy from diagnostics

Budget/timeline planning

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Action create, status, analyze, or email
  2. 2 Context Brand, goal, audience, budget, channels
02

Work

Agent / skill execution

  1. 3 Plan campaign-manager builds campaign brief
  2. 4 Funnel funnel-architect designs channel strategy
03

Verify

Gate, review, validation

  1. 5 Track analytics-analyst reads status/performance
  2. 6 Diagnose campaign-debugger analyzes issues
04

Close

Report, handoff, artifact

  1. 7 Assets Save campaign briefs, creatives, reports

Modes / Routes

create

Comprehensive campaign creation

Research:
Brief
Validate:
funnel strategy
status

Read campaign files and display progress

analyze

Performance analysis and diagnostics

Research:
Metrics
Validate:
recommendations
email

Email campaign coordination

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

create Recommended
/ckm:campaign:create "Launch VividKit beta to ClaudeKit users"
Use when:
You need a new multi-channel campaign plan.
Expected:
Campaign brief, funnel strategy, channel plan, and assets folder.
status
/ckm:campaign:status campaigns/vividkit-beta
Use when:
Existing campaign files need progress/status reading.
Expected:
Progress summary from campaign source files.
analyze
/ckm:campaign:analyze campaigns/vividkit-beta
Use when:
Campaign performance needs diagnosis.
Expected:
Metrics, diagnosis, recommended actions, audit report.
email
/ckm:campaign:email "Reactivate waitlist users for beta invite"
Use when:
The campaign work centers on email coordination.
Expected:
Email campaign plan or assets connected to campaign context.

Handled Scope

  • Campaign briefs
  • Funnel strategy
  • Budget/timeline planning
  • Performance analysis
  • Email campaign coordination

Artifacts Produced

Campaign Assets

Pattern

assets/campaigns/{date}-{slug}/...

Outputs campaign briefs, creatives, reports, and diagnostics depending on action.

Quick Ref / Command

Marketing Kit

/ckm:write:*

Marketing Kit writing router for copy, blog, CRO, formula, audit, and publish-ready content.

01

Route

02

Context

03

Research

04

Write

One selected reference controls the workflow

Creative copywriting

Audit/publish gates protect generated content

SEO articles

Visuals only after content direction is clear

YouTube-to-blog

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Route Parse first argument and load reference
  2. 2 Context Topic, file, URL, video, screenshot, brand/style context
02

Work

Agent / skill execution

  1. 3 Research SEO, YouTube extraction, researchers, scout for heavier flows
  2. 4 Write copywriter/content-creator/planner output copy or article
03

Verify

Gate, review, validation

  1. 5 Visuals Create and verify illustrations when required
  2. 6 Gate Audit/publish score and auto-fix
04

Close

Report, handoff, artifact

  1. 7 Output Return or save content by reference

Modes / Routes

fast

Quick creative copy

good

Research + plan + write + optional design

Research:
Yes
Validate:
visual verify
blog

SEO blog with audit/publish gate

Research:
SEO
Validate:
score >= 8
publish

Audit, auto-fix, publish-ready output

Validate:
score >= 8

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

audit
/ckm:write:audit drafts/landing-page.md
Use when:
Existing content needs a quality score and fix list.
Expected:
0-10 audit across copywriting, SEO, platform, brand.
blog Recommended
/ckm:write:blog "How ClaudeKit plan/cook workflows work"
Use when:
You need an SEO-optimized article from a topic.
Expected:
Planned article with SEO structure and publish gate target.
blog-youtube
/ckm:write:blog-youtube https://youtube.com/watch?v=VIDEO_ID
Use when:
A YouTube source should become an SEO blog article.
Expected:
Extracted source, research, article draft, SEO/publish checks.
cro
/ckm:write:cro "Improve signup section copy for VividKit early access"
Use when:
Conversion copy needs CRO-focused improvement.
Expected:
CRO copy variants with rationale and CTA focus.
enhance
/ckm:write:enhance drafts/hero-copy.md
Use when:
A draft needs stronger clarity, structure, or tone.
Expected:
Enhanced copy preserving source intent.
fast
/ckm:write:fast "3 headline options for the launch banner"
Use when:
You need quick creative copy with minimal research.
Expected:
Short copy options returned inline.
formula
/ckm:write:formula AIDA "VividKit early access signup"
Use when:
You want a proven copywriting formula applied.
Expected:
Formula-structured copy such as AIDA/PAS/BAB/4Ps.
good
/ckm:write:good "Landing page copy for VividKit desktop beta"
Use when:
The copy needs research, planning, and optional visuals.
Expected:
Research-backed copy plan and polished output.
publish
/ckm:write:publish drafts/claudekit-workflows.md
Use when:
A draft must be audited, fixed, and made publish-ready.
Expected:
Publish-ready version that passes the score gate.

Handled Scope

  • Creative copywriting
  • SEO articles
  • YouTube-to-blog
  • CRO
  • Formula copy
  • Publish readiness scoring

Artifacts Produced

Reference-defined Output

Pattern

assets/articles/... | content/blog/... | assets/copy/... | {path}-published.md

Concrete save path depends on subcommand; lighter flows may return copy inline.

Quick Ref / Command

Marketing Kit

/ckm:design

Unified marketing design router for brand, tokens, UI styling, logo, CIP, slides, banners, social photos, icons, and posters.

01

Input

02

Route

03

Reference

04

Gate

Route by space arguments

Logo generation

Load only needed references

CIP deliverables

Research before generation

Social photo export

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Input /ckm:design [design-type] [context]
  2. 2 Route Brand, design-system, UI, logo, CIP, slides, banner, social photos, icon, poster
02

Work

Agent / skill execution

  1. 3 Reference Load only relevant route guide and KB files
  2. 4 Gate Ask missing requirements or concept approval
03

Verify

Gate, review, validation

  1. 5 Create Run external skill, script, HTML workflow, or prompt emitter
  2. 6 Verify Export exact sizes, inspect output, fix and re-export
04

Close

Report, handoff, artifact

  1. 7 Deliver Return assets, report path, and output locations

Modes / Routes

logo

Logo generation and preview gate

Validate:
white background
banner

Ask requirements, build, export exact PNG

Validate:
visual QA
social photos

Concept approval, HTML/CSS, screenshot export

Validate:
re-export until pass
poster

Model-agnostic prompt output

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

brand
/ckm:design brand "Identity direction for VividKit Desktop"
Use when:
You need brand identity direction before assets.
Expected:
Brand strategy and visual identity guidance.
design-system
/ckm:design design-system "Tokens for a documentation dashboard"
Use when:
You need reusable design tokens or system rules.
Expected:
Token/system recommendations aligned to the brand.
UI
/ckm:design ui "Polish the onboarding settings screen"
Use when:
A UI surface needs styling/design direction.
Expected:
UI styling guidance or delegated frontend-design workflow.
logo Recommended
/ckm:design logo "Minimal mark for an AI developer tools app"
Use when:
You need logo concepts or generated logo assets.
Expected:
Logo brief/variants with required white-background handling.
CIP
/ckm:design cip "Business card and letterhead mockups for VividKit"
Use when:
Logo/brand needs corporate identity deliverables.
Expected:
CIP mockups or presentation assets.
slides
/ckm:design slides "Investor update deck for VividKit beta"
Use when:
You need a strategic HTML presentation.
Expected:
Slide structure, copy, charts, and rendered deck assets.
banner
/ckm:design banner "Product Hunt launch banner for VividKit"
Use when:
You need exact-size web/social/ad/banner output.
Expected:
Dimension-specific PNG export with visual QA.
social photos
/ckm:design social photos "LinkedIn and X launch images for ClaudeKit workflows"
Use when:
You need platform-specific social images.
Expected:
HTML/CSS screenshot exports that pass visual QA.
icon
/ckm:design icon "Command palette icon set"
Use when:
You need SVG icon assets or variations.
Expected:
Icon variants and optional multi-size exports.
poster
/ckm:design poster "Facebook infographic for ClaudeKit workflow"
Use when:
You need a model-agnostic image-generation prompt.
Expected:
Poster prompt/brief only, ready for an image model.

Handled Scope

  • Logo generation
  • CIP deliverables
  • Social photo export
  • Poster prompt systems
  • Banner/icon design

Artifacts Produced

Design Assets + Report

Pattern

route-specific assets + plans/reports/<design-report>.md

Outputs logo PNGs, CIP mockups, slide HTML, exact-size banners/social exports, SVG icons, or poster prompts.

Quick Ref / Command

Marketing Kit

/ckm:seo:*

SEO audits, keyword research, pSEO templates, on-page optimization, and schema generation with explicit data-source gates.

01

Input

02

Route

03

Data

04

Agents

No invented metrics

Technical SEO audit

Credential-aware data use

Keyword research

Validate generated SEO assets

Programmatic SEO

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Input /ckm:seo [audit|keywords|pseo|optimize|schema] [target]
  2. 2 Route audit/keywords/pseo refs; optimize/schema secondary refs
02

Work

Agent / skill execution

  1. 3 Data Web, ReviewWeb, GSC, PageSpeed as credentials allow
  2. 4 Agents seo-specialist, attraction-specialist, content-creator
03

Verify

Gate, review, validation

  1. 5 Validate Scores, keyword minimums, pSEO samples, JSON-LD validation
  2. 6 Output Standardized SEO assets

Modes / Routes

audit

0-100 technical/content audit with data-source list

Research:
Yes
Validate:
score + priorities
keywords

Keyword research with availability-aware metrics

Research:
API
Validate:
20+ keywords
pseo

Programmatic SEO templates and sample validation

Research:
Yes
Validate:
3 samples
schema

JSON-LD generation and validation

Validate:
JSON-LD valid

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

audit Recommended
/ckm:seo:audit https://vividkit.dev/guides/how-ck-works
Use when:
A page or domain needs technical/content SEO audit.
Expected:
Scored audit with data-source availability and priority fixes.
keywords
/ckm:seo:keywords "ClaudeKit workflows"
Use when:
You need keyword research and clustering.
Expected:
Keyword report with available metrics and at least 20 candidates when possible.
pseo
/ckm:seo:pseo "ClaudeKit command pages by skill category"
Use when:
You need programmatic SEO templates and samples.
Expected:
Template set plus validated sample pages.
optimize
/ckm:seo:optimize content/how-ck-works.md
Use when:
Existing content needs on-page SEO improvement.
Expected:
Optimized headings, metadata, internal links, and content recommendations.
schema
/ckm:seo:schema https://vividkit.dev/guides/how-ck-works
Use when:
A page needs JSON-LD structured data.
Expected:
Generated and validated schema JSON.

Handled Scope

  • Technical SEO audit
  • Keyword research
  • Programmatic SEO
  • Structured data
  • Core Web Vitals

Artifacts Produced

SEO Assets

Pattern

assets/seo/audits | assets/seo/keywords | assets/attraction/pseo-templates | assets/seo/schemas

Outputs scored audits, keyword sets, pSEO templates/samples, and validated schema files.

Quick Ref / Command

Marketing Kit

/ckm:social:*

Social media content creation, platform formatting, engagement hooks, and scheduling across major channels.

01

Parse

02

Platform

03

Draft

04

Format

Platform first

Platform specs

Validate before scheduling

Hook writing

Hooks and format matter

Thread/carousel formats

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Parse Platform + content type or schedule
  2. 2 Platform social-media-manager applies platform rules
02

Work

Agent / skill execution

  1. 3 Draft content-creator and copywriter create post
  2. 4 Format Hashtags, character limits, thread/carousel structure
03

Verify

Gate, review, validation

  1. 5 Validate Validate content against platform rules
  2. 6 Schedule Optional API scheduling
04

Close

Report, handoff, artifact

  1. 7 Output Save under assets/posts

Modes / Routes

twitter/x

Posts and threads

Validate:
platform specs
linkedin

Professional posts and carousels

Validate:
platform specs
instagram/tiktok/youtube

Stories, reels, shorts, captions

Validate:
platform specs
schedule

Schedule posts via API

Validate:
rate limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

x/twitter Recommended
/ckm:social:x "Thread explaining /ck:plan vs /ck:cook"
Use when:
You need X/Twitter post or thread formatting.
Expected:
Platform-ready thread with hooks and limits checked.
linkedin
/ckm:social:linkedin "Post for VividKit beta launch"
Use when:
You need a professional LinkedIn post or carousel angle.
Expected:
LinkedIn-ready copy with professional framing.
instagram
/ckm:social:instagram "Carousel for ClaudeKit workflow"
Use when:
You need carousel, story, or caption direction for Instagram.
Expected:
Instagram-formatted post/caption structure.
tiktok
/ckm:social:tiktok "Short hook for VividKit workflow visualizer"
Use when:
You need short-form vertical video post copy.
Expected:
TikTok hook/script/caption with platform fit.
youtube
/ckm:social:youtube "Community post for How ClaudeKit Works guide"
Use when:
You need YouTube community, short, or video-supporting copy.
Expected:
YouTube-ready copy with title/caption angle as relevant.
facebook
/ckm:social:facebook "Launch post for ClaudeKit visual guide"
Use when:
You need Facebook post formatting.
Expected:
Facebook-ready post with engagement framing.
threads
/ckm:social:threads "Short thread about hidden ClaudeKit skills"
Use when:
You need Threads-native concise posts.
Expected:
Threads-ready sequence with concise hook.
schedule
/ckm:social:schedule assets/posts/linkedin/vividkit-beta.md
Use when:
A prepared post should be scheduled through API flow.
Expected:
Validated scheduling attempt with safe rate-limit/error handling.

Handled Scope

  • Platform specs
  • Hook writing
  • Thread/carousel formats
  • Scheduling APIs
  • Engagement templates

Artifacts Produced

Social Post Assets

Pattern

assets/posts/{platform}/{date}-{slug}.md

Outputs platform-ready copy, format notes, hashtag/engagement structure, and optional scheduling status.

Quick Ref / Command

Marketing Kit

/ckm:email:*

Email content, automation flows, drip sequences, subject-line variants, deliverability, and campaign copy.

01

Type

02

Context

03

Route

04

Structure

Audience/message/CTA first

Automation flows

Subject variants matter

Drip sequences

Flow structure before copy

Subject lines

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Type flow, sequence, newsletter, cold, launch, nurture
  2. 2 Context Ask audience, message, CTA
02

Work

Agent / skill execution

  1. 3 Route Load flow/sequence refs when selected
  2. 4 Structure email-wizard designs timing and branches
03

Verify

Gate, review, validation

  1. 5 Copy copywriter creates subjects, preview, body, CTA
  2. 6 Deliverability Check formulas and deliverability guidance
04

Close

Report, handoff, artifact

  1. 7 Output Save email or sequence files

Modes / Routes

flow

Automation flow with branches and implementation notes

Validate:
diagram/notes
sequence

Drip sequence with full copy

Validate:
email set
newsletter/cold/launch/nurture

Single or campaign email content

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

flow Recommended
/ckm:email:flow "Onboard new ClaudeKit users after signup"
Use when:
You need an automation flow with timing and branches.
Expected:
Flow doc with sequence structure, ASCII diagram, implementation notes.
sequence
/ckm:email:sequence "5-email launch sequence for waitlist"
Use when:
You need a drip sequence with full copy.
Expected:
Email set with subjects, preview text, body, CTA, timing.
newsletter
/ckm:email:newsletter "June VividKit product update"
Use when:
You need a newsletter-style email.
Expected:
Newsletter copy with subject variants and CTA.
cold
/ckm:email:cold "Invite OSS maintainers to try VividKit"
Use when:
You need outbound cold email copy.
Expected:
Cold email variants with deliverability-aware structure.
followup
/ckm:email:followup "Follow up after beta invite click"
Use when:
You need a follow-up email.
Expected:
Follow-up copy with next-step CTA.
launch
/ckm:email:launch "Announce VividKit Desktop beta"
Use when:
You need a product launch email.
Expected:
Launch email copy with urgency and clear CTA.
nurture
/ckm:email:nurture "Educate ClaudeKit users on visual workflows"
Use when:
You need lead nurturing content.
Expected:
Nurture email with educational framing and CTA.
welcome
/ckm:email:welcome "Welcome new early access subscribers"
Use when:
You need a welcome email.
Expected:
Welcome copy with expectation-setting and next step.
winback
/ckm:email:winback "Bring inactive beta users back"
Use when:
You need reactivation copy.
Expected:
Winback email with reason to return and low-friction CTA.

Handled Scope

  • Automation flows
  • Drip sequences
  • Subject lines
  • Deliverability
  • Email copywriting

Artifacts Produced

Email Assets

Pattern

assets/copy/emails/... or assets/emails/flows/...

Outputs single emails, flow docs, drip sequences, subject variants, preview text, body copy, CTAs, and platform notes.

Quick Ref / Command

Marketing Kit

/ckm:video:*

Video marketing pipeline for scripts, storyboards, AI video generation, platform optimization, thumbnails, and repurposing.

01

Route

02

Brief

03

Script

04

Storyboard

Route to one subcommand

Video scripts

Platform specs shape format

Storyboards

Review each production stage

AI video generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Route create, script-create, storyboard-create
  2. 2 Brief Topic, platform, audience, format, brand
02

Work

Agent / skill execution

  1. 3 Script Research and production-ready script
  2. 4 Storyboard Storyboard and START/END frames
03

Verify

Gate, review, validation

  1. 5 Generate Veo/Imagen/Nano Banana style generation as configured
  2. 6 Review Quality gates for script, storyboard, audio, frames, clips
04

Close

Report, handoff, artifact

  1. 7 Assemble FFmpeg post-production and platform export
  2. 8 Output Save video assets, scripts, storyboards

Modes / Routes

create

Full AI video generation pipeline

Research:
Yes
Validate:
5 review gates
script-create

Production-ready video script

Research:
brief
Validate:
script gate
storyboard-create

Storyboard with frame prompts/assets

Validate:
storyboard gate

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

create Recommended
/ckm:video:create "90-second VividKit product walkthrough"
Use when:
You need the full AI video production pipeline.
Expected:
Script, storyboard, frames, clips, reviews, assembly/export assets.
script-create
/ckm:video:script-create "90-second VividKit product walkthrough"
Use when:
You only need a production-ready script.
Expected:
Research-backed video script with brand/platform alignment.
storyboard-create
/ckm:video:storyboard-create scripts/vividkit-walkthrough.md
Use when:
A script needs storyboard frames/prompts.
Expected:
Storyboard with START/END frame pairs and review gate.

Handled Scope

  • Video scripts
  • Storyboards
  • AI video generation
  • FFmpeg assembly
  • Platform optimization

Artifacts Produced

Video Assets

Pattern

assets/videos/... + scripts/storyboards/exports

Outputs scripts, storyboards, generated clips, assembled exports, captions, thumbnails, and platform optimization notes depending on route.

Quick Ref / Command

Marketing Kit

/ckm:ask

💡 Answer technical and architectural questions.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Strategy question Recommended
/ckm:ask Should we prioritize SEO or paid ads for the VividKit launch?
Use when:
You need a strategic marketing decision.
Expected:
Recommendation with tradeoffs and next steps.
Copy question
/ckm:ask What headline formula works best for a developer tool landing page?
Use when:
You need expert copy guidance.
Expected:
Actionable answer with examples and rationale.
Channel selection
/ckm:ask What channels should we use to reach senior developers effectively?
Use when:
You need channel recommendation for a target audience.
Expected:
Channel prioritization with reasoning and quick wins.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:docs:*

ckm:docs command family

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Docs init Recommended
/ckm:docs:init marketing docs for VividKit including brand guide and campaign templates
Use when:
You need to initialize marketing documentation.
Expected:
Doc structure with brand guide, templates, and index.
LLMs docs
/ckm:docs:llms Generate LLM-friendly documentation for the ClaudeKit marketing skill set
Use when:
You need machine-readable docs for AI consumption.
Expected:
LLMs.txt file with condensed, AI-optimized documentation.
Docs update
/ckm:docs:update after the Q3 campaign retrospective
Use when:
Existing marketing docs need syncing with latest learnings.
Expected:
Updated docs with campaign findings and revised templates.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:journal

💡 Write some journal entries.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Campaign debrief Recommended
/ckm:journal Document the lessons learned from the Product Hunt launch campaign
Use when:
You need to record marketing learnings after a campaign.
Expected:
Journal entry with what worked, what failed, and next time plan.
Strategy decision
/ckm:journal Log the decision to pivot from paid ads to community-led growth
Use when:
A strategic pivot needs documentation.
Expected:
Decision log with rationale, stakeholders, and reversal criteria.
Weekly recap
/ckm:journal Write a weekly marketing recap for the beta launch week
Use when:
You need a weekly marketing progress entry.
Expected:
Recap with metrics, wins, blockers, and next week priorities.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:plan:*

💡💡💡 Intelligent plan creation with prompt enhancement

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Launch plan Recommended
/ckm:plan Create a plan for the VividKit beta launch campaign across all channels
Use when:
You need a structured marketing campaign plan.
Expected:
Plan with phases, tasks, owners, and success metrics.
SEO plan
/ckm:plan Plan a 3-month SEO content strategy for ClaudeKit targeting developer keywords
Use when:
You need a phased content and SEO execution plan.
Expected:
SEO plan with keyword clusters, content calendar, and link building.
Q4 marketing plan
/ckm:plan Build the Q4 marketing plan with budget allocation and OKRs
Use when:
You need quarterly planning with measurable goals.
Expected:
Q4 plan with OKRs, budget, channel mix, and milestones.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:preview

Path to markdown file, plan directory, or plans collection

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Campaign preview Recommended
/ckm:preview Show a visual preview of the VividKit launch campaign timeline
Use when:
You need a visual overview of a campaign.
Expected:
Timeline visualization with phases, milestones, and channel activations.
Content preview
/ckm:preview Diagram the content distribution flow from blog to social to email
Use when:
You need a visual content distribution map.
Expected:
Flow diagram showing content adaptation across channels.
Funnel preview
/ckm:preview Visualize the marketing funnel from awareness to trial for VividKit
Use when:
You need a funnel visualization for stakeholders.
Expected:
Funnel diagram with stages, metrics, and conversion rates.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:test:*

ckm:test command family

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

UI test Recommended
/ckm:test:ui Run visual regression tests on the VividKit landing page components
Use when:
You need UI visual regression testing.
Expected:
Test results with screenshots, diffs, and failed assertions.
Copy test
/ckm:test:copy Run A/B test analysis on the two landing page headline variants
Use when:
You need to analyze copy test results.
Expected:
Statistical analysis with winner, confidence level, and recommendation.
Campaign QA
/ckm:test:qa QA the email campaign content for accuracy, links, and brand consistency
Use when:
You need quality assurance before campaign launch.
Expected:
QA report with issues found and sign-off checklist.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:watzup

💡 Review recent changes and wrap up the work

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Marketing handoff Recommended
/ckm:watzup Summarize this marketing strategy session for handoff to the content team
Use when:
You need a marketing session handoff summary.
Expected:
Summary with decisions, action items, and next steps.
Campaign EOD
/ckm:watzup Write an EOD summary of today's campaign launch activities
Use when:
You need an end-of-day marketing summary.
Expected:
EOD with completed items, metrics, blockers, and tomorrow plan.
Week recap
/ckm:watzup Generate a weekly marketing recap for the team newsletter
Use when:
You need a weekly summary for internal communication.
Expected:
Weekly recap with wins, metrics, and next week focus.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:worktree

Create isolated git worktree for parallel development

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Campaign worktree Recommended
/ckm:worktree Create a worktree for the Q4 campaign assets to work in isolation
Use when:
You need an isolated workspace for campaign assets.
Expected:
Campaign worktree branch at worktrees/q4-campaign.
Brand update branch
/ckm:worktree Create a worktree for the brand refresh without affecting active campaigns
Use when:
You need isolated brand work while campaigns run.
Expected:
Brand worktree with clean branch separation.
List worktrees
/ckm:worktree list
Use when:
You need to see active marketing worktrees.
Expected:
List of active worktrees with branch and path.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:ab-test-setup

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.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

A/B test plan Recommended
/ckm:ab-test-setup Plan an A/B test for the hero CTA button color on the landing page
Use when:
You need to design a statistically valid A/B test.
Expected:
Test design with hypothesis, sample size, duration, and success metric.
Results analysis
/ckm:ab-test-setup Analyze the results of our last A/B test with 5000 users per variant
Use when:
Test results need statistical significance analysis.
Expected:
Statistical report with p-value, confidence intervals, and recommendation.
Multivariate
/ckm:ab-test-setup Design a multivariate test for the pricing page headline, subheading, and CTA
Use when:
You need to test multiple elements simultaneously.
Expected:
Multivariate test plan with factorial design and traffic allocation.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:ads-management

Activate for paid advertising campaigns on Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads. Includes ad copywriting, audience targeting, budget optimization, A/B testing, ROAS tracking, and AI creative asset generation (images & videos) with ai-multimodal and ai-artist skills using Gemini Nano Banana Pro and Veo 3.1.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Google Ads audit Recommended
/ckm:ads-management Audit our Google Ads campaigns for wasted spend and optimization opportunities
Use when:
Existing ad campaigns need a performance review.
Expected:
Audit report with wasted spend, quality score issues, and quick wins.
Facebook campaign
/ckm:ads-management Create a Facebook Ads campaign for the VividKit beta launch targeting developers
Use when:
You need a complete paid social campaign setup.
Expected:
Campaign structure, ad sets, targeting, creative brief, and budget.
Bid strategy
/ckm:ads-management Optimize bidding strategy for max conversions under $20 CPA for the signup campaign
Use when:
You need bid optimization for a specific CPA target.
Expected:
Bid strategy recommendation with targeting and budget adjustments.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:affiliate-marketing

Build high-converting SaaS affiliate programs with 20-40% commissions, KOL/KOC partnerships, and fraud prevention. Covers platform selection (PartnerStack, FirstPromoter, Rewardful), commission structures (recurring vs one-time, tiered), influencer outreach strategies, FTC/GDPR compliance, risk management, and case studies (Dropbox 3900%, PayPal 100M users). Use for designing affiliate programs, recruiting partners, optimizing conversion rates, preventing fraud, or scaling referral revenue.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Program design Recommended
/ckm:affiliate-marketing Design an affiliate program for VividKit with tiered commissions for developers and agencies
Use when:
You need a complete affiliate program structure.
Expected:
Commission tiers, tracking setup, payout rules, and onboarding guide.
Recruit affiliates
/ckm:affiliate-marketing Create an outreach plan to recruit developer bloggers as affiliates for ClaudeKit
Use when:
You need an affiliate recruitment strategy.
Expected:
Prospect list criteria, outreach templates, and approval process.
Performance report
/ckm:affiliate-marketing Analyze affiliate performance data and identify top performers and inactive affiliates
Use when:
You need to review and optimize the affiliate program.
Expected:
Performance breakdown with tier recommendations and win-back plan.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:analytics

Activate for marketing analytics, KPI tracking, reporting dashboards, attribution analysis, and performance optimization. Use when analyzing campaign data, creating reports, or measuring marketing ROI.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Dashboard design Recommended
/ckm:analytics Design a product analytics dashboard tracking activation, retention, and revenue KPIs
Use when:
You need a KPI tracking dashboard structure.
Expected:
Dashboard layout with metric definitions, chart types, and data sources.
Funnel analysis
/ckm:analytics Analyze the signup-to-activation funnel and identify the biggest drop-off point
Use when:
You need to find conversion leaks in the user journey.
Expected:
Funnel visualization with drop-off rates and root cause hypotheses.
Event tracking plan
/ckm:analytics Create an event tracking plan for the new onboarding flow using Segment
Use when:
You need to define events for a new product feature.
Expected:
Event taxonomy with properties, triggers, and implementation notes.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:analyze

💡💡 Analytics and performance reports

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Data analysis Recommended
/ckm:analyze Analyze this CSV of 10,000 user sessions and identify engagement patterns
Use when:
You need insights from raw data.
Expected:
Statistical summary, patterns, anomalies, and actionable findings.
Cohort analysis
/ckm:analyze Run a cohort analysis on user signups by week for the past 6 months
Use when:
You need retention patterns by cohort.
Expected:
Cohort table with week-by-week retention rates and insights.
Competitor analysis
/ckm:analyze Compare VividKit features against Cursor and Copilot across pricing, AI quality, and workflow
Use when:
You need a structured competitor comparison.
Expected:
Feature matrix with gaps, advantages, and positioning opportunities.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:assets-organizing

Organize all outputs from slash commands and subagents in assets/ directory by topics, date format, and slugs.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Media library Recommended
/ckm:assets-organizing Organize the assets/ folder with consistent naming and sub-folder structure for the rebrand
Use when:
You need a structured asset management system.
Expected:
Folder structure proposal with naming conventions and migration plan.
Brand kit
/ckm:assets-organizing Package brand assets into a structured kit with logos, colors, fonts, and usage guide
Use when:
You need a shareable brand asset package.
Expected:
Brand kit folder with organized assets and usage documentation.
Audit assets
/ckm:assets-organizing Audit the current marketing assets for outdated branding and missing formats
Use when:
You need to identify stale or incomplete assets.
Expected:
Audit report with stale assets list and recommended replacements.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:banner-design

Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Product Hunt banner Recommended
/ckm:banner-design Create a Product Hunt launch banner for VividKit at 1270x760px with hero screenshot
Use when:
You need a Product Hunt-sized launch banner.
Expected:
Banner HTML/CSS at 1270x760 with logo, screenshot, and tagline.
Social banner
/ckm:banner-design Design LinkedIn and Twitter header banners for the ClaudeKit launch at exact platform dimensions
Use when:
You need social platform header banners.
Expected:
Platform-sized banners with brand elements and visual hierarchy.
Ad banner set
/ckm:banner-design Create a set of Google Display Ad banners in 5 standard sizes for the launch campaign
Use when:
You need multiple ad banner sizes for a campaign.
Expected:
Five banner sizes with consistent design and responsive text.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:brand

Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Brand strategy Recommended
/ckm:brand Develop brand strategy for VividKit targeting AI-native developers with premium positioning
Use when:
You need a complete brand positioning strategy.
Expected:
Brand strategy with positioning, tone, values, and target persona.
Brand voice
/ckm:brand Define the brand voice and writing style guidelines for ClaudeKit marketing copy
Use when:
You need brand voice documentation for content consistency.
Expected:
Voice guide with tone spectrum and copy samples.
Visual identity
/ckm:brand Create visual identity direction: primary/secondary colors, type pairing, and logo usage rules
Use when:
You need a visual identity system with clear guidelines.
Expected:
Color palette, typography rules, logo guidelines, and usage examples.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:cip-design

Corporate Identity Program design with 50 deliverables, 20 styles, 20 industries. Generate CIP mockups with Gemini Nano Banana (Flash/Pro). Actions: design, create, generate brand identity. Deliverables: business card, letterhead, signage, vehicle, apparel, packaging. Styles: corporate, luxury, minimal, modern.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Business card Recommended
/ckm:cip-design Design professional business cards for VividKit team with QR code and minimalist style
Use when:
You need business card designs for the brand.
Expected:
Front/back business card layouts with print-ready specs.
Letterhead
/ckm:cip-design Create branded letterhead and email signature templates for VividKit
Use when:
You need corporate stationery templates.
Expected:
Letterhead template and HTML email signature with brand elements.
Brand deck
/ckm:cip-design Build a brand presentation deck for pitching VividKit to enterprise clients
Use when:
You need a brand-aligned presentation.
Expected:
Slide deck with brand story, product overview, and case studies.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:claude-code

Activate when users ask about Claude Code installation, slash commands (/plan, /fix, /content, /docs, /design, /git), creating/managing Agent Skills, configuring MCP servers, setting up hooks/plugins, IDE integration (VS Code, JetBrains), CI/CD workflows, enterprise deployment (SSO, RBAC, sandboxing), troubleshooting authentication/performance issues, or advanced features (extended thinking, caching, checkpointing).

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Setup guide Recommended
/ckm:claude-code Set up Claude Code with MCP servers, custom hooks, and project CLAUDE.md for this repo
Use when:
You need a complete Claude Code configuration.
Expected:
CLAUDE.md, hook config, MCP server setup, and validation.
Skill creation
/ckm:claude-code Create a custom ClaudeKit skill for automating API documentation generation
Use when:
You need a custom skill for a repetitive workflow.
Expected:
Skill SKILL.md with command, process flow, and prompt examples.
Hook setup
/ckm:claude-code Configure pre-tool-use hooks for secret scanning and post-message hooks for auto-journaling
Use when:
You need Claude Code hooks for automated safeguards.
Expected:
Hook scripts with trigger conditions and test validation.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:competitor

Competitive analysis, alternative pages, vs comparisons, SEO competitor content, market positioning, and battlecard generation.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Competitive analysis Recommended
/ckm:competitor Analyze Cursor, Copilot, and Windsurf as competitors to VividKit across features and pricing
Use when:
You need a structured competitive landscape analysis.
Expected:
Competitor profiles with strengths, weaknesses, and positioning gaps.
Win/loss analysis
/ckm:competitor Analyze 50 recent deal outcomes to identify why we win and lose against Cursor
Use when:
You need data-driven competitive intelligence.
Expected:
Win/loss patterns with root causes and strategy recommendations.
Battle cards
/ckm:competitor Create sales battle cards for competing against Copilot in enterprise deals
Use when:
Your sales team needs structured competitive positioning.
Expected:
One-page battle cards with differentiation and objection handling.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:content-hub

Browser-based asset gallery for managing marketing assets. Visual grid with filter/search, brand context sidebar, and actions (preview, edit, generate). R2-ready manifest for future cloud sync. Use when browsing assets, managing content library, or generating new assets with brand context.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Content calendar Recommended
/ckm:content-hub Create a 3-month content calendar for ClaudeKit across blog, social, and email channels
Use when:
You need a multi-channel content plan.
Expected:
Calendar with topics, formats, owners, and publication schedule.
Repurpose content
/ckm:content-hub Repurpose the How ClaudeKit Works guide into 5 Twitter threads and 3 LinkedIn posts
Use when:
Existing content needs multi-format distribution.
Expected:
Social-ready repurposed content variants per platform.
SEO cluster
/ckm:content-hub Design a content cluster for AI coding tools with pillar page and 8 supporting articles
Use when:
You need a topic cluster for SEO authority building.
Expected:
Pillar page outline, supporting article briefs, and internal linking plan.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:content-marketing

Activate for content strategy, editorial calendars, content pillar mapping, blog planning, and content audit. Use when planning content programs, creating editorial workflows, or building topic clusters.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Blog strategy Recommended
/ckm:content-marketing Develop a content marketing strategy for ClaudeKit targeting developer audiences
Use when:
You need a complete content marketing plan.
Expected:
Strategy with channels, content types, frequency, and KPIs.
Case study
/ckm:content-marketing Write a case study about how a team used ClaudeKit to ship 3x faster
Use when:
You need a customer success story.
Expected:
Case study with challenge, solution, results, and quotes.
Distribution plan
/ckm:content-marketing Create a distribution plan for the new ClaudeKit guide launch across owned and earned channels
Use when:
You need a content launch distribution strategy.
Expected:
Channel plan with timing, format adaptations, and amplification tactics.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:creativity

Creative direction intelligence. 55 styles, 18 platforms, 12 voiceover types, 17 music genres, 30 campaign categories. Actions: create, design, plan, direct, brief creative campaigns. Projects: ads, videos, social content, commercials, brand films. Styles: minimalist, maximalist, nostalgic, cinematic, UGC, luxury, futuristic, emotional. Topics: visual style, platform specs, voiceover, music, color palette, audience targeting.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Campaign concept Recommended
/ckm:creativity Brainstorm 10 creative campaign concepts for the VividKit beta launch targeting developers
Use when:
You need divergent creative ideas for a campaign.
Expected:
10 concepts with hook, format, and target emotion.
Naming ideas
/ckm:creativity Generate 20 product name ideas for an AI code review tool targeting senior developers
Use when:
You need creative naming options to evaluate.
Expected:
Name list with meaning, tone, and domain availability notes.
Tagline variants
/ckm:creativity Write 15 tagline variants for VividKit ranging from technical to emotional
Use when:
You need multiple tagline options across a tone spectrum.
Expected:
Taglines grouped by tone with recommended A/B test pairs.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:dashboard

Launch and manage the Marketing Dashboard

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Marketing dashboard Recommended
/ckm:dashboard Build a marketing performance dashboard with acquisition, activation, and retention KPIs
Use when:
You need a dashboard structure for marketing metrics.
Expected:
Dashboard layout with widget definitions and data source mapping.
Product dashboard
/ckm:dashboard Design a product analytics dashboard for feature adoption and user engagement
Use when:
You need product usage tracking in a dashboard.
Expected:
Dashboard with feature adoption charts and segmentation filters.
Revenue dashboard
/ckm:dashboard Create an MRR dashboard with growth rate, churn, expansion, and LTV tracking
Use when:
You need SaaS revenue metric visualization.
Expected:
Revenue dashboard with time-series charts and growth decomposition.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:debugging

Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and verification protocols. Use when encountering bugs, test failures, unexpected behavior, performance issues, or before claiming work complete. Prevents random fixes, masks over symptoms, and false completion claims.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Error investigation Recommended
/ckm:debugging Investigate why the checkout API returns 422 for valid card numbers in production
Use when:
You need systematic debugging for a production error.
Expected:
Error trace, root cause hypothesis, and verification steps.
Performance issue
/ckm:debugging Debug why the dashboard page takes 8 seconds to load after the latest deploy
Use when:
A performance regression needs root cause investigation.
Expected:
Profiling results, bottleneck identification, and fix recommendations.
Flaky test
/ckm:debugging Find the polluter causing the auth test suite to fail intermittently in CI
Use when:
A flaky test needs isolation and root cause analysis.
Expected:
Polluter identified with test ordering proof and isolation fix.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:design-system

Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Token system Recommended
/ckm:design-system Create a design token system for VividKit with semantic colors, spacing, and typography
Use when:
You need a complete design token foundation.
Expected:
Token definitions in JSON, CSS variables, and Tailwind config.
Component library
/ckm:design-system Audit the existing UI components for consistency and create a design system documentation
Use when:
You need a component inventory and documentation.
Expected:
Component catalog with variants, states, and usage guidelines.
Icon system
/ckm:design-system Design an icon system for VividKit with consistent weight, style, and grid alignment
Use when:
You need a systematic icon approach.
Expected:
Icon grid rules, style guide, and SVG optimization workflow.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:elevenlabs

Generate speech, clone voices, create sound effects & music with ElevenLabs API. TTS, voice design, audio generation, conversational AI agents.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Voice generation Recommended
/ckm:elevenlabs Generate narration for the VividKit product walkthrough video using the English_Warm voice
Use when:
You need AI-generated voice narration.
Expected:
MP3 audio file with the generated narration.
Voice cloning
/ckm:elevenlabs Clone the brand voice from the provided audio sample for consistent product narration
Use when:
You need a custom voice consistent with brand.
Expected:
Cloned voice profile available for reuse.
Podcast script
/ckm:elevenlabs Convert this blog post into a 5-minute podcast episode with natural speech patterns
Use when:
Text content needs an audio version.
Expected:
Audio file with natural pacing and pronunciation adjustments.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:form-cro

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Signup form audit Recommended
/ckm:form-cro Audit the signup form for friction and suggest CRO improvements to increase completion rate
Use when:
You need a conversion optimization audit.
Expected:
Friction map with field-by-field recommendations and priority order.
Checkout optimization
/ckm:form-cro Optimize the 3-step checkout form to reduce cart abandonment
Use when:
You need to reduce form abandonment.
Expected:
Optimized flow with progress indicators and autofill suggestions.
Form A/B test
/ckm:form-cro Design an A/B test for the lead capture form with fewer fields vs. more fields
Use when:
You need to test form length impact on conversion.
Expected:
Test plan with hypothesis, variants, and success metrics.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:free-tool-strategy

When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Tool concept Recommended
/ckm:free-tool-strategy Develop a free tool strategy for ClaudeKit to attract developers through workflow calculators
Use when:
You need a lead-gen free tool concept.
Expected:
Tool concept with value prop, build effort, and distribution plan.
SEO tool page
/ckm:free-tool-strategy Design an SEO-optimized landing page for the ClaudeKit token calculator tool
Use when:
A free tool needs an SEO landing page.
Expected:
Page outline with title, meta, schema, and content structure.
Tool funnel
/ckm:free-tool-strategy Map the conversion funnel from free tool usage to paid subscription for VividKit
Use when:
You need to design the free-to-paid conversion path.
Expected:
Funnel stages with CTAs, triggers, and nurture touchpoints.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:funnel

💡💡 Funnel design and optimization

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Funnel audit Recommended
/ckm:funnel Audit the signup-to-activation funnel and identify the top 3 drop-off points
Use when:
You need to diagnose a leaky conversion funnel.
Expected:
Funnel visualization with drop-off rates and fix priorities.
Funnel design
/ckm:funnel Design a product-led growth funnel for a B2B developer tool with freemium model
Use when:
You need a funnel architecture for PLG.
Expected:
Funnel map with stages, conversion events, and nurture tactics.
Funnel copy
/ckm:funnel Write copy for each stage of the trial-to-paid upgrade funnel
Use when:
Each funnel stage needs tailored conversion copy.
Expected:
Stage-by-stage copy with messaging that matches user intent.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:gamification-marketing

Design gamified marketing campaigns using points, badges, leaderboards, streaks, challenges. Use for loyalty programs, referral campaigns, onboarding flows, engagement boosts, email gamification. Provides mechanics selection, psychology alignment, strategy docs, templates, KPIs.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Points system Recommended
/ckm:gamification-marketing Design a points and badges system for ClaudeKit user engagement
Use when:
You need a gamification mechanics design.
Expected:
Points economy, badge definitions, and trigger conditions.
Referral game
/ckm:gamification-marketing Create a gamified referral system with milestones and unlockable rewards for VividKit
Use when:
You need gamification applied to a referral program.
Expected:
Referral game mechanics with milestone rewards and viral loop.
Leaderboard
/ckm:gamification-marketing Design a developer leaderboard for ClaudeKit usage streaks and skill completions
Use when:
You need competitive gamification for engagement.
Expected:
Leaderboard design with scoring rules and privacy considerations.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:hub

Open Content Hub + Marketing Dashboard

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Marketing hub Recommended
/ckm:hub Create a marketing resource hub with campaign templates, brand assets, and workflow guides
Use when:
You need a central resource repository.
Expected:
Hub structure with organized resources and search tags.
Knowledge base
/ckm:hub Build a knowledge base for the ClaudeKit marketing team with onboarding and playbooks
Use when:
You need a team knowledge management system.
Expected:
Knowledge base with categories, articles, and search.
Content library
/ckm:hub Organize all marketing copy and creative assets into a searchable content library
Use when:
You need structured content asset management.
Expected:
Content library with tags, metadata, and usage rights.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:init

💡💡💡💡 Initialize marketing project

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

New skill Recommended
/ckm:init skill analytics-reporting
Use when:
You need to bootstrap a new ClaudeKit skill.
Expected:
Skill folder with SKILL.md template and initial structure.
New project
/ckm:init project E-commerce API with Node.js and PostgreSQL
Use when:
You need to initialize a new project scaffold.
Expected:
Project folder with README, .gitignore, and initial config.
New workflow
/ckm:init workflow weekly-review for automated report generation
Use when:
You need a custom automation workflow scaffold.
Expected:
Workflow definition file with steps and trigger config.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:kit-builder

Build ClaudeKit Marketing components - skills, agents, commands, workflows. Use when creating new automation, extending marketing capabilities, or understanding kit structure. Includes templates, examples, and init scripts.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Starter kit Recommended
/ckm:kit-builder Create a Next.js SaaS starter kit with auth, Stripe billing, and dark mode
Use when:
You need a reusable project starter template.
Expected:
Kit with README, configuration, and quick-start guide.
CLI tool kit
/ckm:kit-builder Build a kit for creating TypeScript CLI tools with argument parsing and config management
Use when:
You need a reusable CLI tool development kit.
Expected:
CLI kit with commander, config loader, and test setup.
API client kit
/ckm:kit-builder Create a kit for building typed API clients from OpenAPI specs
Use when:
You need a reusable API client generation kit.
Expected:
Kit with OpenAPI codegen, type generation, and usage examples.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:launch-strategy

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Product launch plan Recommended
/ckm:launch-strategy Create a launch plan for VividKit beta targeting developer communities
Use when:
You need a go-to-market launch plan.
Expected:
Launch timeline, channel tactics, and success metrics.
Waitlist strategy
/ckm:launch-strategy Design a waitlist strategy for VividKit with referral incentives and anticipation building
Use when:
You need a pre-launch waitlist strategy.
Expected:
Waitlist mechanics, email sequence, and referral hook.
Community launch
/ckm:launch-strategy Plan a community launch for ClaudeKit on Hacker News, Product Hunt, and Dev.to
Use when:
You need a community-led launch approach.
Expected:
Platform-specific launch plan with timing and content strategy.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:logo-design

Logo design intelligence with 55 styles, 30 color palettes, 25 industries. Generate logos with Gemini Nano Banana model, search styles/colors/industries. Actions: design, create, generate logo. Industries: tech, healthcare, finance, food, fashion, fitness. Styles: minimalist, vintage, luxury, geometric, abstract, mascot, emblem. Features: AI prompt generation, design briefs, color psychology.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Logo concept Recommended
/ckm:logo-design Create 5 logo concepts for VividKit with minimalist, tech-forward aesthetic
Use when:
You need logo design concepts to evaluate.
Expected:
Logo concepts with rationale, color, and typographic direction.
Logo refinement
/ckm:logo-design Refine the selected logo mark with dark/light variants and icon-only version
Use when:
A chosen logo concept needs polish and variants.
Expected:
Logo variants: full, icon-only, dark, light, monochrome.
Logo usage guide
/ckm:logo-design Create a logo usage guide with clearspace, minimum size, and incorrect use examples
Use when:
The logo needs documented usage rules.
Expected:
Usage guide with do/dont examples and file formats.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:marketing-dashboard

Local-first marketing command center for solopreneurs. Manage campaigns, content, and assets with Claude Code AI automation.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

KPI overview Recommended
/ckm:marketing-dashboard Design a marketing KPI dashboard covering acquisition, engagement, and revenue
Use when:
You need a top-level marketing metrics view.
Expected:
Dashboard layout with KPI cards, trend charts, and data sources.
Campaign tracker
/ckm:marketing-dashboard Build a campaign performance tracker for all active paid and organic channels
Use when:
You need a campaign comparison dashboard.
Expected:
Multi-channel tracker with CPA, CTR, and conversion metrics.
Attribution model
/ckm:marketing-dashboard Set up multi-touch attribution tracking across email, social, and paid for the funnel
Use when:
You need attribution across marketing channels.
Expected:
Attribution model with touchpoint weights and revenue credit.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:marketing-ideas

When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' or 'ideas to grow.' This skill provides 140 proven marketing approaches organized by category.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Campaign ideation Recommended
/ckm:marketing-ideas Generate 10 creative campaign ideas for the ClaudeKit launch targeting senior developers
Use when:
You need creative campaign concepts.
Expected:
10 ideas with format, channel, and expected impact.
Growth hacks
/ckm:marketing-ideas List 15 growth hacking ideas for a developer tool with a freemium model
Use when:
You need unconventional growth ideas.
Expected:
Prioritized growth ideas with effort/impact ratings.
Viral mechanics
/ckm:marketing-ideas Design viral mechanics for VividKit referral program to increase developer word-of-mouth
Use when:
You need viral loop design ideas.
Expected:
Viral mechanics with trigger, incentive, and amplification.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:marketing-planning

Plan marketing strategies, campaigns, content calendars, and initiatives using proven frameworks (RACE, SOSTAC, STP). Activates marketing-research for data-driven insights.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Annual plan Recommended
/ckm:marketing-planning Create a Q3 marketing plan for VividKit with budget allocation and channel mix
Use when:
You need a quarterly marketing plan.
Expected:
Plan with goals, channels, budget, and success metrics.
GTM plan
/ckm:marketing-planning Develop a go-to-market plan for ClaudeKit entering the enterprise market
Use when:
You need a new market entry plan.
Expected:
GTM plan with ICP, channels, positioning, and milestones.
Channel strategy
/ckm:marketing-planning Define the optimal channel mix for reaching AI-native developers at low CAC
Use when:
You need a channel prioritization strategy.
Expected:
Channel ranking with estimated reach, cost, and conversion rates.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:marketing-psychology

When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Conversion copy Recommended
/ckm:marketing-psychology Apply loss aversion and social proof principles to the pricing page copy
Use when:
You need psychology-driven copy improvements.
Expected:
Revised copy with applied principles and A/B test suggestions.
Behavioral audit
/ckm:marketing-psychology Audit the onboarding flow for cognitive bias opportunities and friction points
Use when:
You need a behavioral psychology UX review.
Expected:
Audit with bias opportunities, friction points, and recommendations.
Nudge design
/ckm:marketing-psychology Design nudges for the free-to-paid upgrade flow using commitment and consistency
Use when:
You need behavioral nudges for a conversion flow.
Expected:
Nudge map with trigger points, message variants, and expected impact.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:marketing-research

Research market trends, competitors, audience insights, and marketing best practices. Use before marketing-planning for data-driven strategy.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

User interviews Recommended
/ckm:marketing-research Plan and conduct user interviews with 5 ClaudeKit beta users to understand workflow pain points
Use when:
You need qualitative user research.
Expected:
Interview guide, synthesis report, and key insights.
Survey design
/ckm:marketing-research Design a product-market fit survey for VividKit early access users
Use when:
You need a structured PMF measurement survey.
Expected:
Survey with PMF question, NPS, and open-ended follow-ups.
Market sizing
/ckm:marketing-research Size the TAM/SAM/SOM for AI developer tools targeting individual developers in 2025
Use when:
You need market size estimation.
Expected:
TAM/SAM/SOM with data sources and methodology.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:onboarding-cro

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Onboarding audit Recommended
/ckm:onboarding-cro Audit the current 5-step onboarding flow and identify where users drop off most
Use when:
You need to find onboarding conversion leaks.
Expected:
Drop-off analysis with each step rate and fix recommendations.
Activation redesign
/ckm:onboarding-cro Redesign the onboarding to get users to their aha moment within 3 minutes
Use when:
You need faster time-to-value for new users.
Expected:
Redesigned flow with aha moment defined and friction removed.
Tooltip optimization
/ckm:onboarding-cro Add contextual tooltips and progressive disclosure to the dashboard for new users
Use when:
You need progressive onboarding UI patterns.
Expected:
Tooltip placement plan with trigger conditions and copy.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:paid-ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Google Ads setup Recommended
/ckm:paid-ads Set up Google Search Ads for ClaudeKit targeting AI coding tools and competitor keywords
Use when:
You need a new Google Ads campaign.
Expected:
Campaign structure, ad groups, ad copy, and bidding strategy.
Retargeting
/ckm:paid-ads Create a retargeting campaign for VividKit pricing page visitors who did not convert
Use when:
You need to re-engage high-intent visitors.
Expected:
Retargeting segments, ad creative, and frequency caps.
Performance review
/ckm:paid-ads Analyze last month paid ad performance and recommend budget reallocation
Use when:
You need to optimize ad spend allocation.
Expected:
Performance report with reallocation recommendations.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:play

>

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Prototype idea Recommended
/ckm:play Build a quick prototype for a command palette feature to test the interaction model
Use when:
You need a fast no-stakes prototype to validate an idea.
Expected:
Working prototype with core interaction and no production concerns.
Experiment
/ckm:play Explore WebGL water simulation as a potential hero background
Use when:
You want to freely experiment with a visual concept.
Expected:
Experimental code with findings and viability notes.
Spike solution
/ckm:play Spike a WebSocket connection handler to understand the complexity before planning
Use when:
You need a technical spike to estimate complexity.
Expected:
Spike code with complexity notes and open questions.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:pricing-strategy

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Pricing model Recommended
/ckm:pricing-strategy Design a pricing model for VividKit with freemium, pro, and team tiers
Use when:
You need a pricing structure that maximizes conversion.
Expected:
Tier definitions with pricing, limits, and feature gates.
Pricing page copy
/ckm:pricing-strategy Write compelling pricing page copy highlighting value over cost for VividKit Pro
Use when:
You need conversion-focused pricing page copy.
Expected:
Pricing copy with value framing, feature highlights, and FAQ.
Price test
/ckm:pricing-strategy Design an A/B test to validate $29 vs $49 per month for the Pro plan
Use when:
You need to validate pricing with a controlled test.
Expected:
Test design with hypothesis, sample size, and success criteria.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:referral-program-building

Build referral programs for SaaS/digital products. Covers reward structures (two-sided, tiered, multi-step), platform selection (Rewardful, ReferralCandy, Viral Loops, FirstPromoter), technical implementation (tracking, attribution, API patterns), fraud prevention, email templates, and KPI metrics. Use for designing viral growth loops, implementing refer-a-friend features, or optimizing existing referral systems.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Referral design Recommended
/ckm:referral-program-building Design a referral program for VividKit with two-sided incentives for referrer and referee
Use when:
You need a referral mechanics design.
Expected:
Program structure with incentives, tracking, and reward delivery.
Referral launch
/ckm:referral-program-building Create a launch plan for the ClaudeKit referral program targeting existing beta users
Use when:
You need a referral program launch strategy.
Expected:
Launch plan with announcement copy, email, and tracking setup.
Referral optimization
/ckm:referral-program-building Analyze the referral program metrics and suggest improvements to increase viral coefficient
Use when:
Existing referral data needs optimization.
Expected:
Analysis with viral coefficient, leaks, and improvement tactics.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:slides

Create strategic HTML presentations with Chart.js, design tokens, responsive layouts, copywriting formulas, and contextual slide strategies.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Pitch deck Recommended
/ckm:slides Create an investor pitch deck for VividKit with problem, solution, market, and traction slides
Use when:
You need a structured investor presentation.
Expected:
Slide deck with narrative arc, key slides, and speaker notes.
Demo slides
/ckm:slides Build a product demo presentation for ClaudeKit showing the plan-cook-ship workflow
Use when:
You need a product demonstration presentation.
Expected:
Demo deck with screenshots, flow diagrams, and live demo notes.
Workshop slides
/ckm:slides Create workshop slides for a 45-minute session on AI coding workflows with exercises
Use when:
You need educational workshop materials.
Expected:
Workshop deck with agenda, exercises, and facilitator guide.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:storage

S3 storage operations - upload, sync, list, get URLs

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

S3 setup Recommended
/ckm:storage Configure AWS S3 bucket for user file uploads with presigned URLs and CloudFront CDN
Use when:
You need cloud storage for user uploads.
Expected:
S3 config, presigned URL generation, and CDN integration.
R2 migration
/ckm:storage Migrate existing S3 bucket to Cloudflare R2 for cost savings on egress
Use when:
You need to migrate storage for cost optimization.
Expected:
Migration plan with data transfer steps and config update.
Storage policies
/ckm:storage Set up bucket policies, lifecycle rules, and versioning for the media storage bucket
Use when:
You need storage configuration and data management.
Expected:
Bucket policy, lifecycle rules, and versioning config.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:youtube

Convert YouTube videos to blog posts, infographics, social content. Download video/audio, get captions/transcripts, generate AI summaries, analyze comments via VidCap.xyz API.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Video SEO Recommended
/ckm:youtube Optimize the ClaudeKit workflow demo video title, description, tags, and chapters for SEO
Use when:
You need YouTube video SEO optimization.
Expected:
Optimized metadata with keyword research and chapter markers.
Channel strategy
/ckm:youtube Create a YouTube channel strategy for VividKit targeting developer educators
Use when:
You need a YouTube content and growth strategy.
Expected:
Channel strategy with content pillars, cadence, and growth tactics.
Community post
/ckm:youtube Write a YouTube community post announcing the ClaudeKit How-CK-Works guide launch
Use when:
You need a YouTube community post for announcements.
Expected:
Community post copy with engagement hooks and CTA.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:youtube-thumbnail-design

Design YouTube thumbnails with 17 styles, niche-specific guides, and CTR optimization. Generate complete thumbnails with text using Gemini Nano Banana Pro (4K text rendering). Actions: design, create, generate thumbnail. Niches: tech, gaming, education, cooking, fitness, business. Styles: facecam, before-after, listicle, diagram, whiteboard, bold-text, mystery, dark-dramatic. Features: AI generation with text baked in, brand identity, reference face, arrows, Google Font support.

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Tutorial thumbnail Recommended
/ckm:youtube-thumbnail-design Create a thumbnail for a ClaudeKit workflow tutorial with bold text and a developer face
Use when:
You need a high-CTR YouTube tutorial thumbnail.
Expected:
Thumbnail at 1280x720 with text overlay and visual hierarchy.
Series thumbnail
/ckm:youtube-thumbnail-design Design a consistent thumbnail template for the VividKit guide series
Use when:
You need a reusable thumbnail template.
Expected:
Thumbnail template with variant slots and branding guide.
A/B thumbnail test
/ckm:youtube-thumbnail-design Create two thumbnail variants for A/B testing the launch video CTR
Use when:
You need thumbnail variants to test click-through rate.
Expected:
Two thumbnail variants with different text and visual hooks.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:kanban

AI agent orchestration board (Coming Soon)

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Board setup Recommended
/ckm:kanban Set up a Kanban board for the Q3 marketing campaign with columns and WIP limits
Use when:
You need a visual task management board.
Expected:
Kanban board with columns, WIP limits, and initial cards.
Sprint board
/ckm:kanban Create a sprint Kanban for the VividKit launch with designer and developer lanes
Use when:
You need a Kanban board with team swimlanes.
Expected:
Board with swimlanes, cards, and priority ordering.
Backlog triage
/ckm:kanban Triage the marketing backlog and prioritize the top 10 items for this sprint
Use when:
You need to prioritize and organize a task backlog.
Expected:
Prioritized list with sprint-ready cards and deferred items.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:skill:*

ckm:skill command family

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Default Recommended
/ckm:skill:add
Use when:
Use the primary route for the requested task.
Expected:
Scoped artifact plus validation summary.
Create
/ckm:skill:create
Use when:
Use this route for a narrower output.
Expected:
Scoped artifact plus validation summary.
FIX Logs
/ckm:skill:fix-logs
Use when:
Use this route for a narrower output.
Expected:
Scoped artifact plus validation summary.
Optimize
/ckm:skill:optimize
Use when:
Use this route for a narrower output.
Expected:
Scoped artifact plus validation summary.
Auto
/ckm:skill:optimize:auto
Use when:
Use this route for a narrower output.
Expected:
Scoped artifact plus validation summary.
Plan
/ckm:skill:plan
Use when:
Use this route for a narrower output.
Expected:
Scoped artifact plus validation summary.
Update
/ckm:skill:update
Use when:
Use this route for a narrower output.
Expected:
Scoped artifact plus validation summary.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Quick Ref / Command

Marketing Kit

/ckm:use-mcp

Utilize tools of Model Context Protocol (MCP) servers

01

Invoke

02

Context

03

Route

04

Execute

Scope first

Routing

Use real project context

Context audit

Prefer explicit routes

Artifact generation

Execution Map

Core lanes from input to output, aligned with the command's real execution path.

01

Start

Input, scope, route

  1. 1 Invoke Command, target, constraints
  2. 2 Context Rules, docs, files, active plans
02

Work

Agent / skill execution

  1. 3 Route Pick mode, flag, or subcommand
  2. 4 Execute Run workflow and create artifact
03

Verify

Gate, review, validation

  1. 5 Validate Check output and report limits

Sample Prompt

Concrete invocations for each flag, subcommand, mode, or route available in the live workflow.

Discover tools Recommended
/ckm:use-mcp List all available tools from the connected MCP servers
Use when:
You need to discover what MCP tools are available.
Expected:
Tool list with names, descriptions, and input schemas.
Execute tool
/ckm:use-mcp Execute the file_search tool to find all TypeScript files with auth patterns
Use when:
You need to run a specific MCP tool.
Expected:
Tool execution result with output and error handling.
Chain tools
/ckm:use-mcp Use the graph_query tool to find related files then read each one for context
Use when:
You need to chain multiple MCP tool calls.
Expected:
Chained tool results synthesized into a coherent context.

Handled Scope

  • Routing
  • Context audit
  • Artifact generation
  • Validation
  • Handoff

Artifacts Produced

Workflow Output

Pattern

Artifact path or inline result + validation summary + skipped checks

The guide models the command as a scoped pipeline: route, execute, validate, then summarize artifacts and limitations.

Pipeline

/

Keyboard: Space = Play/Pause · ← → = Prev/Next step

Ready to experience it yourself?