How to Use Codex as a Designer

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: How to Use Codex as a Designer
- URL: https://www.youtube.com/watch?v=GOtHFZnagO0
- Topic: Codex + Claude Workflows
- My current learning frame: Use the transcript anchors for Codex as a design partner: it opens with full-time designer working for you. Then, I'll give you my honest take on Codex first Claude code for designer work because they are actually, then moves...
- Why this matters: New playlist item from Griffin Wooldridge; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:25 / Evidence 1: "full-time designer working for you. Then, I'll give you my honest take on Codex first Claude code for designer work because they are actually more different tools than you may think at first. Let's get into it. Quick..."
- 2:53 / Evidence 2: "inside it. Codex will read it automatically on every task, so you write it once instead of re-explaining yourself every prompt. This is basically your design system talking directly to the agent. Now, this is just a demo..."
- 4:33 / Evidence 3: "agent to design, for example. Now, there's a handful of useful plugins for designers inside Codex that are built by OpenAI themselves. The first one I want to install is this product design plugin. It's a collection of..."
- 7:59 / Evidence 4: "the guidelines in your agents.md file and your attached inspiration image don't conflict because, for example, if you say you want light mode in the .md file and then dark mode in the inspiration image, that's going to..."
- 9:41 / Evidence 5: "during the session and any sources that it's followed to build those outputs. You can also bring up a bottom panel. This is your terminal that you can use inside Codex and a right sidebar, which is basically..."
- 14:18 / Evidence 6: "that's making up this whole design and the in-app browser that we have running right now. One more thing worth knowing because it's brand new at the time of recording. Codex can now build interactive sites and apps..."
- 16:17 / Evidence 7: "Codex for designers. You saw how to give it context with an agents.md file, plugins, and skills, how to generate a UI that respects your design system, and how to iterate fast with annotations and the visual loop."

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A routing matrix for when to use Codex, Claude, browser checks, or manual review.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Inspect -> Plan -> Edit -> Verify -> Review -> Route
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "How to Use Codex as a Designer", not a generic Codex + Claude Workflows essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.