loft · git:20261024.1a24667 · 2026-10-24 · sha256 1daf47a398ba5bec
loft git:20261024.1a24667A
Immutable. This exact content never changes and is served at /api/v1/blob/1daf47a398ba5bec.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ake6bjo6iigdw3df/1daf47a398ba5beca0178515f4437924612eb2dc6ca8543f94e04cfd8176ec64.json
Then /plugin install loft@markdownregistry-ake6bjo6iigdw3df in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: loft
description: "[oh-my-agy] Shape-before-steel prototyping: settle a design or logic fork that prose cannot resolve by building a throwaway artifact (pure zero-I/O logic module in an HTML harness, or 3 structurally distinct UI variants behind one switcher). Use for $loft or when a spec/interview stalls on 'we need to see/feel it first'."
---
# Loft — Shape Before Steel (`$loft`)
When a design question stalls in prose—two plausible models, neither falsifiable by talk—build a cheap, disposable runnable artifact so the user can react to it, then fold their decision back into the spec or plan.
## When to use
- A `$deep-interview` or `$ralplan` decision fork stalls in words ("does this state machine feel right?", "steps, cards, or split-pane?").
- The user invokes `$loft` or says "let's prototype both options" / "we'd have to see it first".
Do **not** use `$loft` when the answer is discoverable from repo code (`explore`), upstream docs (`researcher`), or a direct Socratic question (`$deep-interview`), or when diagnosing a bug (`debugger` / `$analyze`).
## Choose the fork
Pick exactly **one** fork per loft (one loft answers one question):
### 1. Logic Fork — "Is the state/rule model right?"
For questions about state machines, reducers, scoring formulas, or edge-case transitions:
1. Isolate the decision-bearing core as a **pure, zero-I/O module** (no framework, no network, no persistence).
2. Wrap it in a single self-contained clickable HTML harness under `.omagy/artifacts/loft/<slug>/index.html` (or render via Antigravity's `generative_ui` skill when available): one button per scenario/edge case, with the full state transition visible after every click.
3. Once confirmed, record the chosen state rules in the spec/plan; the pure function can be lifted into production work during `$ultragoal`.
### 2. UI Fork — "What structure holds the data best?"
For questions of layout, information architecture, navigation model, or density:
1. Build **three variants (`A`, `B`, `C`) that differ in structure** (information hierarchy, navigation flow, density)—never three color/font reskins.
2. Provide an on-page switcher cycling `A` / `B` / `C` using realistic data density (either in `.omagy/artifacts/loft/<slug>/index.html` or on an isolated git branch `loft/<slug>`).
3. Once the user picks a variant (or hybrid), record the structural decision in `DESIGN.md` or `.omagy/specs/` and leave the throwaway harness behind.
## Discipline
- **Disposable by design**: no database migrations, no new dependencies, no production wiring, and no commits to `main`. Keep artifacts in `.omagy/artifacts/loft/<slug>/` or on a non-merged `loft/<slug>` branch.
- **Fast feedback**: use `ask_question` after presenting the loft artifact so the user can select the winning variant or edge-case behavior in one click.
- **Fold the answer**: write the user's chosen option and 1-line rationale into the active `.omagy/specs/deep-interview-<slug>.md`, `.omagy/plans/prd-<slug>.md`, or `DESIGN.md`, then return to the calling workflow.