Skills
Skill overview

Start with the workflow, then open the skill you need.

CafeKit skills are local operating procedures. The overview shows how the runtime thinks about work first, then links to detailed pages for the main skills that control delivery, debugging, documentation, and release.

Core workflow

specsdeveloptestcode-reviewsyncgit

Pre-spec discovery

questionbrainstorminspectresearch

Debug and change safety

debughotfix

Frontend and product

frontend-designfrontend-developmentreact-best-practicesui-ux-pro-maxweb-testing

Backend and platforms

backend-developmentmobile-developmentdevops

Artifacts and media

docsgenerate-graphagent-browserchrome-devtoolsai-multimodaldocxpdfpptxxlsx

How to read this page#

The main workflow skills deserve their own pages because they change how work moves through the repo. Domain skills stay in the catalog because they support specific surfaces such as frontend, backend, browser automation, documents, spreadsheets, and deployment.

Main skill pages

Start with the workflow skills. Each page explains when to use the skill, its operating flow, output, traps, and handoff.

/hapo:question

Question

Evidence-backed Q&A for project behavior, source code, specs, docs, configuration, dependencies, and external technical topics.

/hapo:brainstorm

Brainstorm

Scout-first ideation before a spec exists. It turns raw intent into spec-ready decisions without writing implementation code.

/hapo:specs

Specs

Creates the durable feature contract: requirements, research, design, task packets, and validation state.

/hapo:develop

Develop

Implements approved task packets with scope fidelity, task-aware inspection, verification, review, and state sync.

/hapo:test

Test

Runs real verification and returns a concrete verdict instead of treating green-looking commands as proof.

/hapo:code-review

Code Review

Findings-first review for spec compliance, code quality, security, regressions, and contract drift.

/hapo:sync

Sync

Updates task status, task_registry, task markdown, phase, and audit results so future agents can trust the project record.

/hapo:debug

Debug

Diagnostic-only root-cause workflow for bugs, failing tests, CI issues, performance issues, and UI regressions.

/hapo:hotfix

Hotfix

Narrow, evidence-backed repair after diagnosis. It fixes the cause without expanding scope.

/hapo:docs

Docs

Creates, refreshes, summarizes, or reconstructs project documentation from source code.

/hapo:inspect

Inspect

Fast codebase discovery for file finding, task context, entrypoints, call paths, and blast radius.

/hapo:git

Git

Safe branch, commit, push, PR, finish, and worktree operations with secret scanning and focused commits.

Support skill catalog

hapo:research
External technical research and source validation.
hapo:generate-graph
Technical diagrams exported as SVG/PNG.
hapo:frontend-design
Polished frontend redesign and visual execution.
hapo:frontend-development
React/TypeScript frontend implementation patterns.
hapo:react-best-practices
React and Next.js performance guidance.
hapo:ui-ux-pro-max
UI/UX rules, accessibility, layout, motion, and design intelligence.
hapo:web-testing
Playwright, Vitest, k6, visual, a11y, and performance testing.
hapo:agent-browser
Context-efficient browser automation snapshots.
hapo:chrome-devtools
Puppeteer automation, screenshots, console, and ARIA checks.
hapo:ai-multimodal
Image, audio, video, OCR, transcript, and document analysis.
hapo:backend-development
APIs, auth, databases, services, security, and backend patterns.
hapo:devops
Cloudflare, Docker, GCP, Kubernetes, CI/CD, and deployment work.
hapo:mobile-development
React Native, Flutter, SwiftUI, Kotlin, and mobile UX.
hapo:docx
Word document creation, extraction, editing, comments, and redlines.
hapo:pdf
PDF extraction, creation, forms, merge, split, and batch work.
hapo:pptx
PowerPoint creation, editing, templates, and slide generation.
hapo:xlsx
Spreadsheet creation, formulas, charts, analysis, and recalculation.

Routing rule#

Choose the smallest skill that fits the task. Do not force a full spec workflow for tiny fixes, and do not start coding when the request is still ambiguous.