Menú
Browse available H·AI·K·U studios grouped by category with help links into each studio definition
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Quick mode for small tasks — single-stage intent with auto-advance
Start a new H·AI·K·U intent — describe what you want to accomplish and the system creates a structured lifecycle for it
Full autonomous workflow — elaborate, plan, build, review, and deliver in one command
Open the SPA review pane for an intent so the user can browse units, feedback, stage artifacts, and outputs. Non-blocking on the workflow — leaves feedback that the engine picks up on the next tick. Use whenever the user wants to "see," "open," "show," or "look at" the current intent or a specific stage.
Reverse-engineer an existing feature into H·AI·K·U intent artifacts
Zero-ceremony single-unit execution — run one task directly through a stage's hat loop without intent or workflow scaffolding
Basado en la clasificación ocupacional SOC
| name | haiku-studios |
| description | Browse available H·AI·K·U studios grouped by category with help links into each studio definition |
Browse the studio portfolio — every lifecycle template available in this project, grouped by category, with direct links to each studio's definition.
Call haiku_studio_list to get the full list of studios. The response
includes, for each studio: name, slug, aliases, description,
category, stages, source (plugin or project), path (directory),
and studio_md (absolute path to STUDIO.md — the canonical definition).
Group the studios by category and present them as a Markdown portfolio.
Inside each category, sort alphabetically by canonical name.
For each studio, render:
[project] tag if
source === "project"studio_md path, labelled "definition"If the user asks to drill into a studio, call haiku_studio_get with the
name, slug, alias, or dir — any of them resolves. For a specific stage,
use haiku_studio_stage_get.
## engineering
- **Application Development** (`appdev`) — Lifecycle for web, mobile, and desktop applications · 6 stages · [definition](/abs/path/to/STUDIO.md)
- aliases: `software`
- **Game Development** (`gamedev`) — Lifecycle for games · 5 stages · [definition](/abs/path/to/STUDIO.md)
- **Hardware Development** (`hwdev`) — Lifecycle for hardware products · 6 stages · [definition](/abs/path/to/STUDIO.md)
- **Library Development** (`libdev`) — Lifecycle for libraries, SDKs, CLI tools · 4 stages · [definition](/abs/path/to/STUDIO.md)
## go-to-market
...
studio_md) — discoverability is the whole
point of browse. Users should be able to click through to read any studio's
full definition.source: project) override plugin studios of the same
name. Surface this clearly with a [project] tag so users know they're
looking at a customization.