Agent skill · yeachan-heo
loft
Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks. Use when a design question stalls in words, when a navigator map carries a loft ticket, or when a spec discussion reaches "we would have to see it".
What it needs
About 4k tokens when loaded.
What this skill does
Loft Cut no steel until the shape is fair. Shipwrights loft the hull's lines full-scale and fair them before a single plate is cut. Loft applies the same order to design questions: when words have run out — two plausible answers, neither falsifiable by talk — build a cheap runnable artifact, let the captain react to it, and fold that reaction into the decision. The role contract. The crew builds the artifact; the captain's only job is to react — and that reaction is the decision. The artifact is an instrument for seeing, never a head start on the deliverable. When to loft a design question stalls in prose: repeatedly rephrased, still not settleable ("how should the path page look", "does this state model feel right") a navigator map carries a loft ticket a spec discussion reaches "we would have to see it first" Do not loft when: the question is answerable from repo evidence or by asking the captain (that is interviewing, not lofting) the destination itself is unclear (that is fog — /oh-my-claudecode:ask-navigator) the answer already lives in an ADR (do not re-loft settled decisions) the "design question" is actually a bug (that is the debugger's jurisdiction) Choose the fork Pick by what the question is asking. A wrong fork wastes the whole artifact. Logic fork — is the model right? For questions about state, business rules, data shape, or algorithms ("does unlocking regress on a retake?", "does this reducer hold at the edges?"): 1. Isolate the decision-bearing core — the state machine, reducer, schema, or algorithm — as a pure module: no DOM, no I/O, no framework. Written so that, once the shape is confirmed, it moves into the real codebase unchanged. 2. Wrap it in a single clickable HTML shell: one button per scenario, the tricky edge cases walked through in order, full state visible after every click. 3. On confirmation the module is ready to lift — it re-enters as real work through launch. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yeachan-heo/loft