1 connerkward

lookdev Skill

当用户说「lookdev」（或要求调整/迭代某物的外观，或要求审阅/编辑/批注博客文章、文档、文案或媒体）时，搭建一个本地交互式工作室——为视觉参数提供实时控件（滑块、取色器、拖拽手柄），或为文本/文档/媒体审阅提供直接内联编辑+高亮+边栏评论+媒体标注——而不是靠猜数值或输出静态对比图。Lookdev = 人类对 AI 输出的任何手动调优，包括文本和媒体，不只是滑块。

安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。

查看源码

技能指令原文(SKILL.md)

Lookdev

When the user says "lookdev" — or any of: tune, dial in, iterate on the look of, compare variations of, let me adjust, let me edit/annotate/mark up, review this post/doc/copy — they mean build an interactive in-browser tool the user directly manipulates. Not a static grid of N variations. Not a Q&A where they specify numbers. Not a wall of prose they're asked to read and reply to in chat. A real-time studio where they act on the artifact and the change is captured.

Two studio shapes — pick by what's being tuned:

Visual-parameter lookdev — the artifact's look is set by numbers/choices (color, type, layout, image treatment, animation, 3D). Controls = sliders, pickers, drag handles. This is the bulk of this skill (below).
Text & media lookdev — the artifact is a document, blog post, copy, or media set and the user is editing/curating it: rewriting sentences, cutting boring paragraphs, highlighting, leaving margin comments, flagging "diagram goes here" / "wrong image, replace." Controls = direct inline editing + selection highlight + anchored comments + media annotation. See the dedicated section below. A blog post / doc / script review IS this mode — never hand back a long markdown file and ask the user to react in chat. Stand up the annotation studio.

What it covers

Any visual decision the user picks by feel, not by spec. Expand this list as needed:

Image processing — dither, halftone, posterize, ASCII, blur, edge, quantize, mosaic, color-grade
Color — palette extraction (show coverage %), per-band pickers, saturation / contrast / gamma curves, harmony presets, theme tokens
Typography — font selector, size / weight / leading / tracking / measure, live sample text, fallback stack
Layout, positioning, framing, spacing — draggable & selectable elements; resize handles; margin / padding rulers; alignment guides; snap-to-grid; aspect-lock toggles
Crop & framing — draggable crop rectangle with aspect lock; live cropped preview at production size
Animation / transitions — easing curve editor, duration sliders, scrubber, replay
Component variants — render hover / focus / disabled / loading / dark side by side on one page
Iconography — stroke weight, corner radius, glyph on canvas
AI-generated content — prompt input + param sliders + side-by-side regeneration grid
Anything else where "show me, I'll pick" beats "ask me to specify a number"

Controls must stay reachable while inspecting

If the studio shows a list, grid, or scroll-long set of variations, controls must be visible from every scroll position. The user has to be able to drag a slider while looking at row 14, not scroll back to the top each time.

Two approaches, pick by layout:

Sticky bar (position: sticky; top: 0) at the top of the scroll container. Keep the bar visually distinct — paper background + blur backdrop + bottom border — so it doesn't muddy the specimens scrolling behind it. Sticky pins relative to the nearest scrolling ancestor with a defined boundary; if you nest it inside a sized parent (a
with margin-bottom, a
with a fixed height), it stops sticking at that parent's bottom edge. Lift it to be a direct child of (or the page-wrap) so stickiness spans the whole page.
Floating overlay (position: fixed) for hotkey-toggled controls — e.g. press d to reveal. The portfolio's .debug-ctl pattern is this: pinned top-left, transparent until summoned. Use when the controls shouldn't occupy permanent screen real estate (final viewers shouldn't see them; the author can summon on demand).

Anti-pattern: a top-of-page control panel that the user scrolls past and never sees again. They will tune blindly, give up, or guess. Either keep the controls in view or duplicate a compact control bar next to each variation row.

Text & media lookdev — direct edit, highlight, comment, annotate

When the artifact is a blog post, doc, copy deck, script, or media set, the user is not turning knobs — they're marking up the work the way an editor marks a manuscript. The studio renders the real artifact WYSIWYG (the actual rendered blog with its real components/media, not a raw-markdown textarea) and lets the user act on it directly. Building this for a doc review is mandatory: do not paste a long file into chat and ask "what do you think?" — that's the boring wall of text the user is rejecting. Stand up the annotation studio and let them edit in place.

The four affordances (build all that apply)

Direct inline editing. Every text block is editable in place — click a paragraph/heading and type. Use contentEditable per block (or click-to-swap-to-</code>), each block carrying a stable <code>data-block-id</code> that maps back to a source location (markdown/MDX line range, JSX node, or content key). Capture the edited text per block; the agent applies the diff to source. Don't make them retype in a separate field — they edit the rendered sentence.</li> <li>Selection highlight. Select text → toolbar (or hotkey) applies a colored highlight (<code></code>). Multiple colors = a legend the user defines (e.g. yellow "cut this", green "love it", red "wrong/fact-check"). Each highlight stores <code>{blockId, startOffset, endOffset, color, optional note}</code>.</li> <li>Anchored comments / margin notes. Select text or click a media region → attach a comment shown in a margin rail (pin in the gutter, expand on hover/click) or as a numbered superscript. Comment = <code>{anchor, text}</code> where anchor is a block+range or a media region. This is how the user says "diagram goes here", "too long, cut to two sentences", "needs a real screenshot".</li> <li>Media annotation. For images/figures: draw a box / drop a pin / arrow on the image and attach a note (<code>{mediaId, x, y, w, h, note}</code>); plus a per-media flag menu — "replace", "wrong model", "regenerate", "missing — generate one here". Placeholders ("DIAGRAM HERE", "MEDIA?") render as visible drop-zones the user clicks to specify what they want, directly addressing "where are the diagrams / where is the media."</li> </ol> <h3>Round-trip is MANDATORY (same rule as the settings JSON)</h3> The studio is worthless if the agent can't read the markup back out. Every edit, highlight, comment, and media-flag must export as one machine-readable patch with a single Copy button (and persist to <code>localStorage</code>/URL so a refresh doesn't lose work — this is human-labeled data; see <code>human-labeled-data-rule</code>). Shape: <pre><code class="language-json">{ "edits": [{ "blockId": "p-12", "text": "new rewritten text" }], "highlights": [{ "blockId": "p-3", "range": [40, 88], "color": "cut", "note": "boring, drop" }], "comments": [{ "anchor": "p-7", "text": "diagram goes here — flow of the save loop" }], "media": [{ "mediaId": "fig-2", "flag": "replace", "note": "use a real screenshot, not ASCII" }] }</code></pre> The agent ingests this and bakes: applies the inline edits to the source file, acts on every comment/flag, swaps/generates the flagged media, resolves the highlights (cut the "cut" spans, etc.). Then re-serve the updated artifact for another pass. No markup may exist that isn't in the export blob — otherwise you're back to the user narrating changes by hand. <h3>Mechanics</h3> <ul> <li>Render the real thing. MDX/React blog → mount the actual components; static page → render the real HTML/CSS. WYSIWYG per Architecture #5. An annotation layer over a fake-looking preview lies about the result.</li> <li>Selection → offsets. Use the <code>Selection</code>/<code>Range</code> API; store character offsets relative to the block's text content (not DOM node paths, which break on re-render). Re-apply highlights/comments on load by walking each block's text to the stored offsets.</li> <li>Editing toolbar floats with the selection (a small popover at the selection rect) or a sticky top bar — controls stay reachable (see section above). Hotkeys: highlight on a key (e.g. <code>h</code>), comment on <code>c</code>.</li> <li>Keep edit/annotate modes distinct so a stray click doesn't garble text while they meant to highlight — a mode toggle (Edit · Highlight · Comment) or modifier key.</li> <li>Everything else — serve locally on a free port, verify headless, tear down after baking — is identical to the visual-parameter workflow below.</li> </ul> <h2>Control patterns</h2> Pick controls by what the decision actually is. | Decision type | Control | |---|---| | Continuous value (intensity, size, opacity, k) | <code><input type=range></code> paired with an editable <code><input type=number></code> (not a static label) — drag OR click-and-type; they two-way sync | | Discrete choice (mode, blend, easing kind) | segmented buttons or radio chips | | Color | <code><input type=color></code> swatches; pre-extract dominant palette with coverage % when relevant | | Position / size on a canvas | drag the element itself — handles, not numeric inputs | | Crop region | draggable rectangle + aspect-lock toggle | | Multiple discrete states | render each in a labeled card on one page | | Font choice | searchable picker + editable sample-text input | Spatial rule: if the user could point at the thing and drag it, that is the control. Don't add an <code>x:</code> slider when a drag handle is the obvious affordance. Gesture capture — never make the gesturing hand leave the gesture. When a control toggles a live mouse action the user is performing — recording a cursor path, scrubbing, freehand-drawing, demonstrating a motion — the start/stop must not be a button they have to click. Clicking it drags the mouse off the path, pollutes the start/end of the very motion being captured, and forces a round-trip back to where they were. Bind start/stop to the keyboard (spacebar by default) — <code>keydown</code> on <code>Space</code>, <code>e.preventDefault()</code> to kill page scroll, toggle the same handler the button would. Keep the button too (discoverability), but the hotkey is the real control. Generalize: any modal capture where one hand is committed to the primary input gets the other modality for mode-switching — gesture→key, and conversely a keyboard-heavy capture gets a foot/mouse toggle. The test: if triggering the control would move the thing you're capturing, it's the wrong modality. <h2>Coherent control ranges — bounds must propagate</h2> When one control sets a bound on another (a min, a max, a threshold, an allowed set), the bounded control's UI must reflect the new bound the instant you change it. A "scrub" slider whose <code>min</code>/<code>max</code> attributes drift out of sync with its declared bounds is the most common silent bug — the user moves the bounding slider, nothing visible changes downstream, they assume both are broken. Rules: <ul> <li>Single source of truth. Hold the bound in state once. Every input that displays it (its own slider, the dependent control's <code>min</code>/<code>max</code>, anything else) reads from that state on every update.</li> <li>Re-render <code>min</code>/<code>max</code> on every state change. Don't rely on browser-cached attribute values; rewrite them via JS each render. <code>dependent.min = state.lo; dependent.max = state.hi</code>.</li> <li>Clamp the dependent value into the new range immediately. If the user shrinks the upper bound below the current dependent value, the dependent must snap into range, NOT silently stay outside while the slider shows it pinned to the rail.</li> <li>No-op regions are slider bugs. If dragging a slider past some value has zero downstream effect (because some other control's bound caps it), that's a coherence bug — either narrow this slider's range to where it actually does something, OR change behavior so it does. Sliders with dead zones train the user to think the studio is broken.</li> <li>Test by visualisation, not numeric snapshots. Take a screenshot, change the bounding slider, take another. The two must look meaningfully different — or the slider is decorative. A numeric <code>snapshot()</code> showing state changed doesn't prove the pixels did.</li> </ul> Pattern: every time <code>applyState()</code> runs (or its split equivalents), call a <code>syncBounds()</code> helper that walks the dependent-input registry and pushes the live bounds into every <code>min</code>/<code>max</code>/<code>disabled</code> attribute. Clamp values into the new bounds in the same pass. <h3>Paired controls must not cross</h3> A common shape is two sliders that together define an interval — <code>min ⟷ max</code>, <code>near ⟷ far</code>, <code>tightEnd ⟷ wideEnd</code>, <code>start ⟷ end</code>. If the user can drag one past the other, the interval inverts or collapses. Downstream math typically does <code>(x - lo) / (hi - lo)</code> which divides by zero or returns negative <code>t</code> — producing <code>NaN</code> coordinates, collapsed views, or inverted lerps. The user sees the studio "break" but no error fires. Both ends of the defense: <ul> <li>UI invariant. Keep the two sliders from crossing. On every <code>syncBounds()</code> pass: <code>lower.max = upper.value - MIN_SPAN</code> and <code>upper.min = lower.value + MIN_SPAN</code> (small epsilon, e.g. 2 units, so they can't even touch). The user can't physically drag past the other anchor.</li> <li>Math invariant. The consuming code (lerp, normalisation, ratio) must guard <code>denominator > 0</code> and pick a sane fallback for the degenerate case (e.g. clamp <code>t = 1</code> or <code>t = 0</code>). UI can race the math — always assume the math could be hit with crossed bounds anyway (URL hash, JSON paste-back, programmatic state mutation).</li> <li>Test the boundary explicitly. When the lookdev exposes both ends of an interval, write a quick check: drag <code>tightEnd</code> to the same value as <code>wideEnd</code>, verify the scene doesn't break. Drag <code>tightEnd</code> past <code>wideEnd</code>, verify same. If you can crash the studio with two slider drags, that's a release blocker.</li> </ul> <h2>Architecture</h2> <ol> <li>Single-page HTML — <code><canvas></code> and/or DOM, vanilla JS, a sidebar of controls. No build step, no framework, no deps unless one is genuinely required. Lives in a project-local scratch dir (e.g. <code>scripts/.lookdev-<name>/</code> or <code>scripts/.preview-<name>/</code>), gitignored.</li> <li>Live re-render on every <code>input</code> event. Debounce heavy work via <code>requestAnimationFrame</code>. Keep the loop tight enough to feel like a real slider, not a survey.</li> </ol> <ul> <li>Every numeric control is dual-input (MANDATORY): a range slider AND an editable <code><input type=number></code>, two-way synced. The drag is for exploring; the typed number is for hitting an exact value (and reading the current one). A static <code></code> readout is not enough — the user must be able to click it and type. Sync rule: on slider <code>input</code>, write the number field; on number <code>input</code>/<code>change</code>, update state and re-render — but do not overwrite a field while it has focus (guard with <code>document.activeElement</code>), or typing gets clobbered mid-keystroke. Clamp to [min,max] on commit (<code>change</code>), not on every keystroke, so intermediate values like "1" before "12" aren't snapped.</li> <li>Always include a Reset control that restores every control to its defaults in one click (keep a <code>DEFAULTS</code> object; <code>Object.assign(state, DEFAULTS)</code> then re-render). Cheap to add, and essential once the user has wandered far from baseline.</li> <li>Always build undo/redo history (MANDATORY). Dialing-in is iterative and lossy — the user will overshoot a good look and need to step back. Bind Ctrl/Cmd-Z (undo) and Ctrl/Cmd-Shift-Z / Ctrl-Y (redo), and surface visible ↶ Undo / ↷ Redo buttons. Snapshot the full serialized state — every control plus any drawn/spatial state (polygons, crop rects, dragged handles, palettes), i.e. the same blob as the settings round-trip (#3), not just slider scalars. Debounce so a continuous drag collapses into one history step (snapshot ~350 ms after the last <code>input</code>, not per event), keep a bounded stack (~100–120 entries), and on a new edit after undo, truncate the redo branch. Restore by re-applying a snapshot through the same <code>applyState</code> path the loader uses (so it can't drift). Guard the key handler when focus is in an <code><input></code>/<code><textarea></code> so native text-undo still works. A lookdev without undo punishes exploration — the whole point of the tool.</li> </ul> <ol> <li>Structured settings round-trip (MANDATORY). Every lookdev MUST expose its full current state as machine-readable, copy-pasteable text — a settings JSON (or equivalent) covering every control, with a one-click Copy button and a visible live readout. This is non-negotiable: the agent cannot bake by eyeballing a screenshot, and the user shouldn't have to describe what they dialed in. The round-trip is: user drags → studio serializes the exact state → user pastes the blob back (or it persists to URL/localStorage) → agent bakes from those literal values with identical math. No control may be tweakable without appearing in the export blob. Mirror the state into the URL query so a look is shareable by link, too.</li> <li>Reproducible export. Beyond the settings blob, pick by what gets committed:</li> </ol> <ul> <li>Copy settings JSON — user pastes back, agent bakes with identical math (port the renderer to Python / build script / etc. and verify the bake matches).</li> <li>Download asset — page renders the final artifact at full resolution and triggers a download (PNG / SVG / WebP / JSON).</li> <li>Make exported artifacts re-loadable — sidecar + embedded metadata. When the download is a non-JSON artifact (STL, PNG, GLB, SVG, WebP, video…), the look that produced it shouldn't be strandable. Do BOTH, where the format allows:</li> <li>Sidecar: download a zip containing the artifact and its <code>settings.json</code>, so the exact state ships next to the result.</li> <li>Embed the settings inside the file itself, so the bare artifact alone restores the look — then add a drag-drop / file-input loader that reads it back through the same <code>applyState</code> path as the JSON paste. Per-format hooks: binary STL → append <code>MAGIC + uint32 len + JSON</code> after the triangle data (CAM ignores trailing bytes; parse <code>count</code> at byte 80, footer at <code>84 + count*50</code>) and drop a human note in the 80-byte header; PNG → a <code>tEXt</code>/<code>iTXt</code> chunk; SVG/XML → a <code><metadata></code> element or comment; JPEG/MP4 → EXIF/XMP <code>UserComment</code>; GLB → an <code>extras</code> field. The payoff: the user drops last week's STL back on the viewport and the studio re-dials itself — no "which settings made this?" archaeology. Verify the round-trip (export → reset → load → assert state matches) and confirm the artifact still opens in its native tool (the trailing/edge metadata must not corrupt it). Skip only when the format has nowhere safe to stash bytes; the sidecar zip always works as the fallback.</li> </ul> <ol> <li>WYSIWYG. The preview frame must match the production context — same background color, same fonts loaded, same container max-width, same <code>object-fit</code>. A generic centered canvas is not WYSIWYG.</li> <li>Framework-route variant. When the lookdev is for UI layout inside an existing app, build it as a temporary route in the app (<code>app/dev/...</code> or equivalent) so the real components, styles, and tokens are in the comparison. Delete the route once baked.</li> </ol> <h2>3D lookdev — orientation gizmo (MANDATORY when the camera orbits)</h2> Any lookdev with a non-fixed camera (OrbitControls, trackball, free fly — anything where the user can spin/tumble the view) MUST include a CAD-style ViewCube in a corner. Free orbit alone disorients: the user loses which way is up, can't get a repeatable canonical view, and can't tell whether they're looking at the front or the back. The cube fixes both problems — it's an orientation indicator and a controller in one. Copy the Autodesk/Fusion 360 ViewCube — that's the interaction users expect; don't invent a different gizmo. Required behaviour (this is cheap — ~70 lines of Three.js, no excuse to skip): <ul> <li>Live orientation readout. A small second scene/renderer in a corner draws a labeled cube (FRONT/BACK/LEFT/RIGHT/TOP/BOTTOM). Each frame, drive the gizmo camera from the main camera's view direction (<code>gizmoCam.position = (mainCam.position − target).normalize() * d; gizmoCam.up = mainCam.up; gizmoCam.lookAt(0,0,0)</code>) so the cube always mirrors the scene's current orientation.</li> <li>Click a face / edge / corner to snap (the defining Fusion behavior; it's 26 preset views — 6 faces, 12 edges, 8 corners). Raycast the gizmo and snap each component of the local hit point (<code>|c|>0.55 ? sign(c) : 0</code>) to derive a view direction. One pickable cube then yields faces → ortho views, edges → 45° edge views, corners → iso views from a single mesh — no separate hit zones needed. Animate the main camera to <code>target + dir*currentDist</code> with a short lerp (~0.28/frame), not an instant cut — the motion is what keeps the user oriented.</li> <li>Drag the cube to orbit freely (also Fusion, also mandatory — the user WILL try to grab it). Use pointer events with click-vs-drag discrimination: on <code>pointerdown</code> record the start and <code>setPointerCapture</code>; on <code>pointermove</code>, once travel exceeds ~4px flip into drag mode and orbit the main camera by the pointer delta (convert the camera offset to spherical around the target, <code>theta -= dxk; phi = clamp(phi - dyk, ε, π−ε)</code>); on <code>pointerup</code>, if it never became a drag, treat it as a snap-click. Capture means the drag keeps working when the pointer leaves the little canvas. Cancel any in-flight snap tween when a drag starts.</li> <li>Roll arrows = Fusion's "rotate". Two curved-arrow buttons (⟲ ⟳) beside the cube that roll the current view 90° about the view axis (rotate <code>camera.up</code> by ±90° around the normalized <code>position−target</code> axis). This is the rotate users mean when they say the gizmo "can't rotate" — drag-orbit is not a substitute for it. Snap-cleanup the rolled up so near-cardinal components land exactly on 0/±1 (keep genuine diagonals). Let it roll in ANY view, including iso — do NOT gate it to face-on views or auto-snap-to-face first. (I tried that "Fusion only rolls in standard views" guard and it backfired: it stops the user rolling an isometric view into the exact orientation they want, which is a primary reason they reach for the arrows. Rolling an iso view is a valid, common move.)</li> <li>Perspective ⇄ orthographic toggle. Any 3D lookdev should expose a projection toggle. Perspective for a natural read; orthographic for CAD/measure/section work (parallel edges, true elevation, no foreshortening — essential when judging a thickness or aligning a face). Swap by building the other camera, copying <code>position</code>/<code>up</code>/<code>target</code>, and rebuilding controls; size the ortho frustum from the current target distance (<code>h = 2·dist·tan(fov/2)</code>) so the switch doesn't jump scale. Handle resize for both (<code>isPerspectiveCamera</code> → set <code>aspect</code>; ortho → recompute <code>left/right</code> from aspect keeping height).</li> <li><code>camera.up</code> + OrbitControls is a TRAP — read this. Three's OrbitControls (r160) captures its orbit-axis quaternion from <code>camera.up</code> once, at construction. If you mutate <code>camera.up</code> afterward (e.g. to "fix" a top view, or to roll) and leave it, the main-viewport drag silently breaks — OrbitControls keeps orbiting around the old up while the camera renders with the new one. Two consequences for the gizmo: (a) Do NOT flip <code>camera.up</code> for top/bottom snaps. Leave it <code>(0,1,0)</code> and instead nudge the snap direction a hair off the pole (<code>dir = (0,±1,0.0009)</code>) so <code>lookAt</code> with <code>up=+Y</code> doesn't gimbal-lock. (b) When you DO need a new up (the roll arrows), dispose and recreate OrbitControls after setting <code>camera.up</code>, copying <code>target</code> across, so it re-captures the axis. Snaps and Home should reset to <code>up=(0,1,0)</code> and rebuild if currently rolled.</li> <li>Home / reset-view button beside the cube (Fusion's house icon) that re-frames the object, resets <code>camera.up=(0,1,0)</code>, and rebuilds controls if rolled.</li> <li>Hover highlight the exact zone, not just the face. Fusion subdivides each face into a 3×3 grid — center cell = face, edge cells = edges, corner cells = corners — and lights the hovered cell wrapping across the adjacent faces. Implement with a small pool of up to 3 translucent quads: from the hovered direction <code>d</code> (1/2/3 nonzero axes), for each nonzero axis place one quad on that face at the cell offset <code>(other-axis sign)*⅔</code>. A corner lights 3 quads (one per adjacent face), an edge 2, a face 1. A plain whole-face tint is wrong — the user can't tell a corner-pick from a face-pick. Also set a <code>grab</code>/<code>grabbing</code> cursor so the cube reads as draggable.</li> </ul> Orient the model so FRONT is the face the user cares about. The cube's labels are fixed to world axes, so how you place the model decides what "FRONT" shows. For a relief/panel/anything with a hero face, stand it so the hero face points world +Z (= FRONT) and image-up points +Y — don't lay it flat facing +Y, or FRONT shows a meaningless edge and TOP shows the hero (surprising and "wrong" to the user). Watch the displaced-axis sign too: Three's <code>PlaneGeometry</code> pushes <code>-y</code>, so vertex row 0 is +Y (top) — map image row 0 (top) to it with no flip, or your relief comes out upside-down. Verify by snapping FRONT and eyeballing against the source image; don't trust the index math. Build solids, not floating sheets. A displaced <code>PlaneGeometry</code> is a single hollow surface — fine for a quick look, wrong the moment the user inspects it. In X-ray (or any side view) the raised bumps read as hollow domes floating above the base with a gap, and it's not watertight for STL/CAM. If the thing is a real object (relief, terrain block, carved panel), build a solid heightfield: displaced top surface + perimeter skirt walls + flat bottom, so it's rooted on its base. The user will notice "the back doesn't touch the backplate." Set the material <code>DoubleSide</code> so hand-wound walls never render black. Section / X-ray for hidden internal dimensions. When a control sets something you can't see from outside — wall thickness, a backing/backplate, internal clearance, draft — add an X-ray/section toggle so the user can actually see what they're dialing. Cheapest version: ghost the outer shell (<code>transparent, opacity~0.15, depthWrite:false</code>) and render the measured solid (the backplate slab, the remaining wall) as an opaque distinctly-colored mesh with a bright edge line at the critical boundary; pair it with a side ortho snap so the dimension reads as a clean band. (A true clipping-plane section with caps is the fancier version; usually not worth the stencil work.) Don't make the user infer a hidden thickness from a number alone when one toggle can show it. Keep it in world/view space aligned to how the model is displayed (account for any root rotation you applied). Verify by visualization, not math (these all bit me): click TOP then drag the main viewport and screenshot — confirm it still orbits (catches the <code>camera.up</code> trap); hover a corner and screenshot the cube — confirm the corner zone lights across faces, not the whole face; click a roll arrow from an iso view and screenshot — confirm it snaps to a face (not a diagonal roll); snap FRONT and confirm the hero face is upright. Genuinely-optional Fusion extras: the adjacent-face triangle arrows (drag-orbit covers them), the N/E/S/W compass ring, and the right-click "set current view as Home" menu — skip unless asked. <h2>Workflow</h2> <ol> <li>Build the studio for the specific question. Don't make it generic. If the user is choosing a hero crop, the studio shows the actual hero. If they're choosing a font, the studio is reading sample text.</li> <li>Serve locally. Never hardcode a port — bind a static server to port 0 (the OS hands back a free port) for static HTML, or use the project's dev server for framework routes. Give the user the URL.</li> <li>Verify it works headlessly before handing it over (headless Playwright). Don't ask the user to debug your scaffolding.</li> <li>User iterates. They paste back a settings JSON, click a Download button, or say "go with N" / "use this".</li> <li>Bake. Render the chosen state into committed assets / production code with reproducible math. Verify the baked result matches what they dialed in (a quick screenshot diff is fair).</li> <li>Tear down the scaffolding. Delete the lookdev dir / dev route — it was decision-time scaffolding, not production code. Commit + deploy.</li> </ol> <h2>Anti-patterns</h2> <ul> <li>Static N×M comparison grid — limits the user to your guesses; takes longer than a switcher; doesn't give them the in-between point they actually wanted.</li> <li>Numeric prompt before the slider — "what saturation do you want?" is the wrong question; let them drag.</li> <li>Numeric inputs for spatial decisions — drag the element. Sliders for opacity, drag handles for position.</li> <li>Drift between preview math and bake math — when both JS preview and Python bake exist, port one to match the other and verify on a known input.</li> <li>Building inside production routes — keep scaffolding isolated and trivially deletable. Reach for <code>app/dev/...</code> then nuke it.</li> <li>Skipping the WYSIWYG details — preview without the real font / container / background lies to the user.</li> <li>No structured way to read the state back out — a studio with no copy-able settings blob forces the agent to bake from a screenshot and the user to narrate values by hand. Every control must round-trip through a machine-readable export (see Architecture #3).</li> <li>Handing back a wall of prose for "review" — pasting a long doc/blog into chat (or shipping the markdown file) and asking the user to react is NOT lookdev. For any document/copy/media review, build the text & media annotation studio (direct edit + highlight + comment + media-flag) so the user marks up the rendered artifact and the markup round-trips back as a patch. A boring text dump the user has to read and reply to in chat is the exact thing this skill exists to replace.</li> </ul> <h2>Working example</h2> A worked example — an image-treatment studio: extracts a Lab-k-means dominant palette with coverage %, exposes sliders (resolution, colorize, saturation, gap, glyph, contrast), per-band color pickers, a luminance-vs-nearest mapping toggle, a Copy-settings-JSON button, and a <code>--bake-json</code> Python path that renders the chosen state to committed PNG/WebP with math identical to the JS preview. The preview canvases match the production thumb and hero shapes exactly. <h2>Related (the studio / narrative family)</h2> lookdev is one of two flagship narratives — human-in-the-loop (you, the human, judge and tune). Its determinism-narrative sibling is deterministic-design (render → measure the UI, numbers not vibes). The family it chains with: <ul> <li>deterministic-design — the other flagship; measure/judge design output deterministically.</li> <li>screenstudio-alternative — human-in-the-loop video/demo polish studio (NLE timeline).</li> <li>macos-screen-recorder — capture a studio session or demo (display + system audio).</li> <li>lookdev-auto — the automated counterpart: a vision model judges instead of you.</li> </ul> The foil to lookdev's thesis — use when there's no human to sit the loop.