Operations
Social
Skills
A skill is a packaged workflow: one word in, a complete multi-step job out. The engine ships 59 of them across two plugins — 45 in kun-company, 15 in kun-stack (build ships in both).
You don't type slash commands. Say the keyword in prose and the engine routes — see Keywords.
The pipeline
Idea to production, one stage per skill. /feature chains all of them.
IDEA → SPEC → [PLAN → TASKS] → SCHEMA → CODE → WIRE → CHECK → SHIP → WATCH
└─ human gate ─┘
| Skill | Stage |
|---|---|
idea | Capture a feature idea as a structured GitHub issue |
spec | Technical spec — data model, file plan, acceptance criteria (human approval gate) |
plan | Architecture decisions from the approved spec |
tasks | Dependency-ordered work list |
schema | Data layer — Prisma model, migration, Zod validation |
code | Logic layer — server actions with auth, validation, tenant isolation |
wire | UI layer — page, content, form, table columns, i18n |
check | Quality gate — typecheck + build + visual verify |
ship | Promote the checked build to Vercel production |
watch | Post-deploy verification — visual + console + smoke |
feature | Chains every stage above |
Everyday
| Skill | What it does |
|---|---|
dev | Kill port 3000, start the dev server, open Chrome |
build | tsc + production build with an auto-fix loop |
quick | Lint, fix, commit, push |
deploy | Vercel deploy (staging/preview) |
release | One spell: handover → check → ship → watch → close the issue |
fix | Auto-fix TypeScript, lint, and build errors |
Quality
| Skill | What it does |
|---|---|
handover | Runs the niche quality keywords on a URL or a whole block |
qa | Autonomous block QA — detect, verify, fix safe tiers, hand the residual to a human |
report | Auto-fix a user-reported issue end to end |
test | Vitest + Playwright generation and runs |
security | OWASP Top 10 + dependency scan |
performance | Core Web Vitals, bundle, database queries |
Creation
| Skill | What it does |
|---|---|
atom | Compose 2+ shadcn/ui primitives |
template | Full-page layouts |
block | UI with integrated business logic |
saas | Schema + actions + UI + pages in one pass |
clone | Mirror a live URL section, a Figma frame, or code from another repo |
shadcn | Load the full shadcn/ui knowledge pack |
Business & operations
| Skill | What it does |
|---|---|
captain | CEO brain — synthesize state, suggest the next action |
weekly | Monday plan · Wednesday check · Friday review |
canon | The right CEO book + one operating move for a decision |
decide · premortem | Decision journal (Type 1/2) and Klein-style premortem |
proposal · pricing | Client proposals and tier calculation |
monitor · incident · health | Deploy sweep, P0–P3 response, engine drift check |
costs · economy | Spend breakdown; token audit and delegation |
issue | File a GitHub issue in the right repo |
Content & media
| Skill | What it does |
|---|---|
social | The whole chain for one brand post — see Social |
calendar | Which brand publishes what, on which day |
draft | The copy — Arabic crafted first, one variant per channel |
approve | The human gate — stage for sign-off, then stop |
publish | Deliver to the channels, or hand out a copy-out block |
measure | Read reach and engagement back off published posts |
carousel | Multi-slide bilingual brand carousels |
higgs | Generate marketing images and video via Higgsfield |
convert | Any file or URL → clean Markdown |
docs | Component MDX, API docs, Storybook stories |
Engine maintenance
| Skill | What it does |
|---|---|
sync | Read upstream releases, diff against the engine, adopt or propose |
learn | Mine repos and git history into memory |
analyze | Generate a tailored config for any repo |
pattern | Look up a canonical cross-repo pattern card |
package | Cross-repo dependency audit |
auth · credentials | Authenticate to a service; manage keys via Keychain |
profile | Load a role-scoped config profile |
How a skill is defined
A skill is a directory holding SKILL.md — frontmatter plus the playbook:
---
name: check
description: Quality gate — typecheck + build + visual verify before shipping
when_to_use: Use when work is about to ship and needs the pre-ship gate...
---
Steps, exit gates, and failure handling...| Scope | Path |
|---|---|
| Project | .claude/skills/<name>/SKILL.md |
| User | ~/.claude/skills/<name>/SKILL.md |
| Plugin | plugins/<plugin>/skills/<name>/SKILL.md |
The when_to_use field is the routing truth — it's what lets Claude activate a skill from prose instead of a typed command.
Availability
Every machine gets every skill. Config is universal — the machine, not the person, is the unit of capability. Role is a label and a secrets-trust tier; a skill that calls a service whose key you don't hold simply can't complete that call.