Skills
flowchart LR U["using-superlite"] --> I["inventing"] I -->|"design approved"| D["drafting"] D -->|"plan approved"| S["swarm"] S --> T["testing"] S --> P["proof"] P --> H["shipping"] H -->|"PR merged"| M["merged"] B["diagnosis"] -.->|"a bug or a failing test"| S
The main line runs left to right. diagnosis is the side door for a bug. The other skills (research, feature-prototype, mvp-prototype, upgrade-scan, writing-specs) load only in their own flow or on request.
The skills
Section titled “The skills”| Skill | Applies when |
|---|---|
using-superlite |
Any conversation starts, when it is injected at session start to size your request. |
inventing |
You ask to build a feature or change behavior, before any code. |
drafting |
A design is approved and a multi-step plan is needed. |
swarm |
A plan has a %% taskgraph: scheduler, selective reviews, packet-only final review. |
testing |
Implementing a feature or bugfix, before implementation code. |
diagnosis |
A bug, test failure or unexpected behavior, before proposing fixes. |
feature-prototype |
Feature mode, after the plan is approved: cut the smallest runnable container of your app. |
mvp-prototype |
MVP mode, after the .mvp.md plan: build the one-file clickable prototype and read your feedback. |
research |
You want a topic researched with sources, at a chosen language level. |
proof |
About to claim work is complete, fixed or passing. |
shipping |
Implementation is done and tests pass; decide how to integrate. |
merged |
You say a pull request was merged: clean up its session, branch and local main. |
upgrade-scan |
After a superlite upgrade: review changes and suggest adoption steps. |
writing-specs |
Only when agent_specs is on or you ask for a spec: what done looks like and why. |
All skills live in skills/<name>/SKILL.md.
Example: which skill runs when you ask for a feature
Section titled “Example: which skill runs when you ask for a feature”Say you ask for CSV export in an existing project.
-
You type the request:
Claude Code · ~/social Add CSV export to the reports pageusing-superliteis already loaded, because thesession-starthook injected it. It sizes the request as a feature, not a one-line fix, and picks the skill that fits. -
inventingreads the code and asks you questions about the design.You decide: answer the questions and approve the design. The skill stops before any implementation code exists, so a wrong idea costs you a conversation instead of a rewrite.
-
draftingturns the design into a plan with a task graph, andswarmbuilds it. Inside each task,testingcomes first: the test is written before the code it checks.swarmis the scheduler, with scripts for the mechanical steps. See Parallel build. -
Say a test fails during the build.
diagnosistakes over and finds the cause before anyone proposes a fix, so the fix is aimed at the real fault. -
proofruns the checks before superlite says “done”, andshippingoffers the ways to integrate the work.
What you end up with: a finished feature that was designed with you, tested as it was built, and checked before the claim. Each skill held back until its turn, which is why the order never changes.