Skills That Ship
Skills are guided workflows you trigger with /. They orchestrate Rook’s tools
into multi-step processes — designing a Grasshopper definition, creating Chirp
components, or organizing a file. Rook ships 9 of them.
Grasshopper — routed design, planning, and execution
Section titled “Grasshopper — routed design, planning, and execution”Use execution directly for a clear, bounded request. Design is available when the brief needs material decisions, and planning is optional for larger or higher-risk work. See The Design Cascade.
| Skill | What it does |
|---|---|
/design-grasshopper | Explore the idea, ask questions, produce a validated design document |
/plan-grasshopper | Turn that design into an exact, ordered build plan |
/execute-grasshopper | Build the plan in batches, checking errors as it goes |
Chirp — AI reasoning on the canvas
Section titled “Chirp — AI reasoning on the canvas”See Chirp.
| Skill | What it does |
|---|---|
/chirp | Create a single Chirp component (planner, critic, gate, …) |
/chirp-cascade | Build a multi-component reasoning cascade from a brief |
Organizing & conventions
Section titled “Organizing & conventions”The everyday cleanup work. See Everyday Tasks.
| Skill | What it does |
|---|---|
/project-setup | Bootstrap a project directory with Rook instructions |
/capture-convention | Extract layer/material/block conventions from a reference file into .rook/conventions.yaml |
/clean-layers | Audit a file against your conventions and propose cleanup (never destructive without approval) |
/twisted-column | Create a parametric twisted column by lofting rotated profiles |
How skills compose
Section titled “How skills compose”The Grasshopper skills route by need rather than enforcing a ceremony: execute a clear request directly, use design to resolve ambiguity, and add a durable plan when risk or scope warrants it. You can also mix workflows freely: capture a convention, clean a file to match, then design new geometry on the tidy base.