---
source_hash: 8e4f22a208e55cfa0c0ee04110f3893462054c027ac7e2f9ca0d5e7fc0f8f782
---

# Context Pack — Direct the screen, don't prompt the model

**Gist:** Directing a live website render like a film set — one note per round against a moving frame — beats writing a prompt-memo, because a feel can only be judged once the live thing is moving in front of you.

## NEEDLES (verbatim — do not confabulate)

- **Skill URL (open source):** `https://github.com/Pushing-Squares/art-direct`
- **Doctrine line, all-caps, in the body:** `DIRECT THE SCREEN, DON'T PROMPT THE MODEL.`
- **Closing tagline / sign-off:** `Stop prompting, start defining outcomes.` (sign-off glyph: `// A<3`)
- **MDX component imports (from `@/components/blocks`):** `Diagram`, `CrtKnockFidget`, `DialsToTokensFidget`
- **Image assets (referenced by `<Diagram>`):** `/posts/workflows/direct-the-screen/the-live-loop.png` (hero + first diagram), `/posts/workflows/direct-the-screen/prompt-vs-direct.png` (second diagram)
- **The 5-step loop, verbatim:**
  1. `Stand it up live and look. "Warmer" needs something to be warmer than.`
  2. `One move per round, so your reaction maps to one cause, not five.`
  3. `Make every value a named dial. Steer by feel, not by editing code.`
  4. `The agent proves its own edit compiled before it says done. You stay free to just watch.`
  5. `When a look locks, save it. The final dial values are your design system.`
- **Concrete build that emerged note-by-note (the proof scene):** wall of twelve CRT monitors, each playing a showreel at a different second, with scanlines, flicker, and a teal glow; the note `Make the cursor knock the screens.` → mouse sweep tears the signal, splits colour, sometimes cuts a screen to black static, then recovers; the note `Dirtier.` → a pink and teal spark cracks at the pointer; plus a custom glitch typeface on the headline.
- **Frontmatter `related` (companion slugs):** `stop-prompting-start-defining-outcomes`, `the-taste-transition`, `fable-made-me-start-using-codex`
- **Post date:** `2026-06-16`; **folder:** `workflows`; **type:** `long-read`; **status:** `published`
- **Skool draft path (frontmatter):** `(internal draft)`

## GIST (condensed)

A prompt is a memo fired once into the dark — a guess at an aesthetic you haven't seen yet. Directing inverts it: you stand inside a live loop, give one small note against a moving render, watch it land, and the screen hands you the next note. The author ran a CRT showreel page this way — twelve monitors, a cursor that tears signal, a glitch headline — none of it specified up front; every move emerged from reaction. The discipline is: one cause per round, every value a named dial, the agent proves its edit before calling done, and a locked look's dial values become the design system. The skill that runs the loop is open-source (`art-direct`). The human holds the loop; the model holds the hands.

## KEY LEARNINGS

1. **A feel cannot be written down — only reacted to.** A brief is a guess at an aesthetic you have not yet seen. The eye only knows once the live thing is moving in front of it. Stop specifying the feel; build a loop fast enough to react inside.

2. **One move per round is the causal-discipline rule.** If you change five things, your reaction maps to five causes and you cannot tell what landed. One note, one render, one reaction — then the next note.

3. **Named dials, not code edits.** Make every value a named dial you steer by feel. This is what lets a non-coder (or a coder staying in the director's chair) direct without reaching into the source.

4. **The agent must prove its own edit before it says done.** The build has to compile / render before the agent reports back. That keeps the human free to watch frames, not babysit errors.

5. **A locked look is a design system.** When the dial values settle, save them — those final values are the spec. Direction produces tokens, not just a one-off page.

6. **The taste is yours; the hands are not.** Nothing builds itself — an agent built each change, but every frame was reviewed and every move was called by the human. The loop scales authorship, it does not remove the author.

7. **Directing transfers from film to screens because the role is identical.** On a set you do not operate the camera — you watch the frame and call what it needs. The crew has the hands; you have the eye. The same seat exists in front of a live render.

## FILE INDEX

- **Post body:** `content/posts/workflows/direct-the-screen.mdx`
- **Co-located pack (this file):** `content/posts/workflows/direct-the-screen.context-pack.md`
- **Hero / loop diagram asset:** `/posts/workflows/direct-the-screen/the-live-loop.png` (on-disk under the aris-space public/posts tree)
- **Prompt-vs-direct diagram asset:** `/posts/workflows/direct-the-screen/prompt-vs-direct.png`
- **MDX block components source:** `@/components/blocks` (exports `Diagram`, `CrtKnockFidget`, `DialsToTokensFidget`)
- **Referenced skill repo:** `https://github.com/Pushing-Squares/art-direct`
- **Companion posts (same `workflows` neighbourhood + related):** `stop-prompting-start-defining-outcomes`, `the-taste-transition`, `fable-made-me-start-using-codex` (the last has its own `.context-pack.md` in this folder)
- **Skool mirror draft:** `(internal draft)`

> Backfilled 2026-07-18 from the published body; not needle-extracted at thought-time.