# Design at the Speed of Adjectives — Paul Bakaus, Renaissance Geek, Inc.

Paul Bakaus, Renaissance Geek, Inc.

[Talk page](https://ai.engineer/talks/v42opQpCy60-design-at-speed-adjectives) · [Video](https://www.youtube.com/watch?v=v42opQpCy60)

## Design at the Speed of Adjectives

Paul Bakaus explains why Impeccable gives coding agents a context-specific design vocabulary instead of trying to automate taste—and why words such as “bolder,” “quieter,” and “harden” work only when they encode real decisions.

### The same prompt, with and without design guidance

[0:12](https://www.youtube.com/watch?v=v42opQpCy60&t=12s)

Paul Bakaus, founder of Renaissance Geek, opens with an intentionally bland website and one small request: make its workflow section bolder. **Impeccable** is a design skill that runs inside coding harnesses including Claude Code, GitHub Copilot, Cursor, and Codex. With the skill installed, the section gains a more forceful visual hierarchy. The result still carries an unwanted generated-design tell—decorative section numbers—so the claim is improvement, not perfection.

![Captures the output from the same project and prompt without Impeccable, completing the opening visual comparison.](https://ai.engineer/api/talk-essay-media/b1bc38e393d1df9b401740d09dc6fa0a2db689d560d1203942602fdb12423fd3)

Captures the output from the same project and prompt without Impeccable, completing the opening visual comparison.

The comparison then repeats the same prompt on the same project without Impeccable. The visible difference motivates the rest of the talk: a vague adjective leaves a general model to choose its own interpretation, while a loaded design command constrains what the adjective should mean. This is a qualitative demonstration judged from two outputs; the recording supplies no measured evaluation establishing the size or consistency of the improvement.

### Finding the control level between pixels and autonomy

[2:50](https://www.youtube.com/watch?v=v42opQpCy60&t=170s)

The old product handoff is already collapsing. Designers increasingly work in code, engineers make design decisions, and design engineers span both. That weakens the familiar waterfall in which product defines the work, design produces an artifact, critique follows, and engineering eventually implements it. Impeccable’s shared vocabulary matters in this environment because design intent must survive continuous cross-functional iteration rather than one formal handoff.

![Shows the newer beige, serif, and italic visual convergence that Bakaus labels “Claude Beige” and “Algorithmic Uniqlo.”](https://ai.engineer/api/talk-essay-media/e4afc5afd6e2a3f9a038df0db02bd78fd013c39bbaf7c986c925ec11f0be0d4d)

Shows the newer beige, serif, and italic visual convergence that Bakaus labels “Claude Beige” and “Algorithmic Uniqlo.”

Current tools often pull people toward one of two extremes. **Direct manipulation** in Figma, Webflow, or another visual editor gives precise control over margins, padding, and the final appearance, but keeps the user at a low level of abstraction. **Fully agentic delegation** raises the level too far: “design this for me” leaves the agent responsible for choices the user never made. Using a powerful model merely to center a diff is comically excessive, yet handing it the whole design problem creates a different failure. The missing layer is steering at the level of intent.

Generated-design clichés also move. Purple gradients once made AI-produced pages easy to identify. Newer outputs may instead converge on beige palettes, serif display type, and italics—what Bakaus calls “Claude Beige” and “Algorithmic Uniqlo.” Any single page may be competent. The problem is sameness: when a model repeatedly draws from its median design reference, the output contains style without a project-specific reason for that style.

Where should human control enter AI-assisted design?
Pixel editing supplies precise but low-level control; full delegation supplies speed but leaves the model to invent design decisions. Impeccable targets the middle layer: human intent expressed through project-specific design language.
- Direct manipulation — Humans adjust margins, padding, and visual output directly.
- Intent-level steering — Humans choose direction while the agent translates it into design changes.
- Full delegation — The agent is asked to design or build without enough human decisions.
- Direct manipulation → Intent-level steering (Raise the abstraction level)
- Full delegation → Intent-level steering (Restore human decisions)

### Design cannot be one-shotted without decisions

[5:56](https://www.youtube.com/watch?v=v42opQpCy60&t=356s)

Effective design is context-rich and iterative. It depends on what the product is trying to accomplish, who will use it, and how several interested people respond to successive versions. Even a solo builder must inspect and revise the result; within a team, users and stakeholders add more opinions. A single agent call cannot wish that process away.

![Shows the competent-looking but intentionally empty one-shot page used to argue that nobody made project-specific decisions.](https://ai.engineer/api/talk-essay-media/47696dd7ba965f657a76a4a63ef5bed821ac15e7ef98a53128fb4c6b21914ba3)

Shows the competent-looking but intentionally empty one-shot page used to argue that nobody made project-specific decisions.

The first useful questions define the design territory: What emotional response should the product create? What must it never feel like? Which references are relevant? Who is the audience? A human design director could not responsibly accept “design my brand” and walk away without these answers. An agent needs the same missing context, even if it can produce a plausible page without asking for it.

This explains why a polished one-shot page can still feel empty. The model has rendered an image, but nobody chose what the hierarchy should communicate, what emotion belongs to the product, or why this visual language fits the audience. Competence is not the same as intention.

### Turning light words into project-specific commands

[8:11](https://www.youtube.com/watch?v=v42opQpCy60&t=491s)

Impeccable places control in adjectives and verbs used during real design work. Each command names a direction rather than a pixel operation: **bolder** raises emphasis, **quieter** reduces it, **distill** simplifies, **polish** prepares the work for finishing, **denser** changes information density, and **harden** checks whether the design works across devices and conditions. Hardening may expose weak responsiveness or poor performance rather than merely changing appearance.

![Highlights the memorable quality check: if someone believes AI made it bolder, the agent failed.](https://ai.engineer/api/talk-essay-media/f69a54c151d24e9dd5ad7f3b713a94107ce7764f45e87afa2d68675703262aed)

Highlights the memorable quality check: if someone believes AI made it bolder, the agent failed.

Designers and engineers can use the same model yet receive different results because their language carries different distinctions. Impeccable compresses some of that design vocabulary into a reusable skill, giving a less design-fluent user a way to express a direction the agent can translate into concrete work. The command does not replace the user’s decision; it makes the decision legible to the agent.

The “bolder” example shows the causal chain. Without added guidance, the model can interpret boldness as new colors, gradients, glass effects, or neon. Impeccable instead defines it through hierarchy, scale, and decisive typography. The observable change should be stronger attention and clearer emphasis without breaking the existing design system. The adjective remains easy to say, but its implementation is no longer unconstrained.

The command also carries a quality check: show the result to someone, say AI made it bolder, and “if they believe you, you failed.” The memorable phrasing pushes the agent away from conspicuous AI decoration and toward changes that look like a deliberate extension of the project. In practice, this asks the model to critique whether its own additions have become generic tells.

Borrowing a framing he credits to Matt Pocock, Bakaus describes an adjective as a light word that can be infused with domain meaning. A model already has many associations for “bolder”; the skill narrows those associations for this design task and project. That level of abstraction still has limits. It can help between the first exploration and the finishing pass, but Bakaus does not expect AI to replace human work in the final five, ten, or perhaps twenty percent needed to move from good to great.

How “bolder” becomes a bounded design operation
The adjective works because project context and command guidance translate an ambiguous word into specific visual mechanisms, followed by human judgment and another iteration.
- Human direction: “bolder” — The user chooses the desired movement rather than individual pixel changes.
- Project context — Audience, purpose, references, emotional territory, and the existing design system constrain the change.
- Loaded command meaning — Boldness maps to hierarchy, scale, and decisive type—not gradients, glass, or neon.
- Design-system-aware change — The agent raises attention without inventing an unrelated visual language.
- Review and iterate — Check for conspicuous AI tells and continue refining rather than treating the result as final.
- Human direction: “bolder” → Loaded command meaning (Selects a direction)
- Project context → Loaded command meaning (Narrows interpretation)
- Loaded command meaning → Design-system-aware change (Translates language into mechanisms)
- Design-system-aware change → Review and iterate (Inspect the visible result)
- Review and iterate → Human direction: “bolder” (Choose the next adjustment)

### Place commands throughout the real workflow

[11:57](https://www.youtube.com/watch?v=v42opQpCy60&t=717s)

A useful tool starts with the target user’s actual workflow. Design does not move through one clean line, so Impeccable identifies intervention points across shaping, crafting, iterating, hardening, and polishing. The work eventually returns to the design system, where reusable decisions are extracted and technical or design debt is cleaned up. Commands belong at different stages rather than being treated as interchangeable prompt decorations.

![Supports the key caveat that an adjective with nothing behind it is merely a nicer prompt.](https://ai.engineer/api/talk-essay-media/7b4b805291c420ec52a5746151ea6eb10c1626d2f96773c8619756e98d6dae00)

Supports the key caveat that an adjective with nothing behind it is merely a nicer prompt.

The stages support distinct jobs: **shaping** determines what should be built; **crafting and iteration** use directional words to explore and revise; **hardening and polishing** address edge cases and finish; **design-system cleanup** folds useful choices back into shared components and removes debt. Mapping these jobs prevents one command from pretending to solve the whole process.

`overdrive` is the playful exception that proves the mechanism. The command deliberately pushes a design over the top. Bakaus used it on an already developed event-horizon shader from Radiant Shaders to make the effect even more extravagant; it did not generate the shader in one shot. Community enthusiasm persuaded him to keep a command he had initially treated as half a joke. This is command design by observed usefulness and joy, not by completing an abstract taxonomy.

The caveat is simple: an adjective with nothing behind it is only a nicer prompt. Because the model has encountered many meanings for the word, the skill must define which meaning applies, which changes fit the project, and which familiar shortcuts to avoid.

Where Impeccable enters the design workflow
Commands assist at several points in a messy process; no single adjective replaces shaping, iteration, finishing, and cleanup.
- Shape — Establish the product direction and initial design territory.
- Craft — Build the design within the chosen direction.
- Iterate — Use directional adjectives and verbs to revise the work.
- Harden and polish — Address responsiveness, performance, edge cases, and finish.
- Return to the design system — Extract reusable choices and clean up technical and design debt.
- Shape → Craft (Direction guides construction)
- Craft → Iterate (Visible work enables revision)
- Iterate → Harden and polish (Refined work moves toward shipping)
- Harden and polish → Return to the design system (Preserve reusable decisions)
- Return to the design system → Shape (Future work inherits the system)

### No auto mode, because steering is the product

[14:09](https://www.youtube.com/watch?v=v42opQpCy60&t=849s)

The most requested feature is also the one Impeccable will not add: automatic operation. An auto mode that chooses every command and completes the design alone would recreate the one-shot workflow the tool was built to avoid. Bakaus is explicit enough to close an open pull request proposing it: “There is no auto, and there will be no auto.”

![Supports the closing concept of amplified craft and the claim that tools can sharpen taste but cannot manufacture it.](https://ai.engineer/api/talk-essay-media/ac506e7d8f4a11379f72af30d85b4957fddfc6ede9b1d7611ec9c528052c81e7)

Supports the closing concept of amplified craft and the claim that tools can sharpen taste but cannot manufacture it.

The refusal protects a product decision, not a missing implementation. Impeccable exists to let people steer toward an intended result. Removing the need to choose a command would also remove the moment when a person decides whether the design should become bolder, quieter, simpler, denser, or more resilient.

That leads to “amplified craft.” Tools can sharpen and extend a person’s taste, but Bakaus does not believe taste can be manufactured in a lab. Taste is contextual, cultural, and scarce; once everyone reproduces the same visual choices, those choices stop functioning as taste and become another muddy default. Impeccable therefore aims to increase the user’s ability to express judgment, not to solve judgment on the user’s behalf.

## Key takeaways

- The useful control layer for AI-assisted design sits above pixel manipulation and below full delegation: humans choose direction, while agents translate that direction into implementation.
- A design adjective works only when it carries project-specific meaning. In Impeccable, “bolder” means hierarchy, scale, and decisive typography rather than generic gradients, glass, or neon.
- Good design remains context-rich and iterative. Audience, emotional territory, references, stakeholder opinions, and visible review cannot be replaced by a single competent-looking generation.
- Commands should enter at specific workflow stages—shaping, crafting, iteration, hardening, polishing, and design-system cleanup—rather than pretending to automate the entire process.
- Impeccable deliberately rejects auto mode because choosing how to steer is the human contribution the tool is designed to preserve.

## Resources

- [Impeccable on GitHub](https://github.com/pbakaus/impeccable) — The open-source design skill discussed in the talk. Its documentation lists the available commands, installation paths, project-context files, detector rules, and supported coding harnesses.
- [Impeccable by Design](https://www.paulbakaus.com/impeccable-by-design/) — Bakaus’s longer written account of Impeccable and the design problem it addresses, useful for readers who want the product rationale beyond the short presentation.
- [Carving Shaders Out of Claude Code](https://www.paulbakaus.com/carving-shaders-out-of-claude-code/) — A detailed account of the iterative shader work referenced by the `overdrive` example, including the event-horizon shader and why ambitious visual work required dozens or hundreds of passes rather than one-shot generation.
- [Radiant Shaders](https://radiant-shaders.com/) — The shader collection containing the event-horizon work that Bakaus used as the already-developed foundation for an `overdrive` pass.

## Related talks

- [Don't Build Agents, Build Skills Instead](https://ai.engineer/talks/CEvIs9y1uog-agent-skills) — Explains the broader skill architecture behind packaging reusable procedural expertise on top of a general-purpose agent runtime.
- [The Missing Layer: Design Taste in AI Agents](https://ai.engineer/talks/7GMKdpLsxwU-missing-layer-design-taste-in-ai-agents) — Presents another design skill built around anti-slop guidance, visual references, persistent preferences, and iterative refinement.
- [Ending AI Slop](https://ai.engineer/talks/lCBf9slCanI-ending-ai-slop) — Explores a complementary approach to generic generated design: decomposing subjective qualities into context-specific signals while preserving legitimate differences in taste.

## Slides

### Impeccable

Paul introduces Impeccable as a design skill for coding harnesses. The talk focuses on his approach to building it.

[0:19](https://www.youtube.com/watch?v=v42opQpCy60&t=19s) [Impeccable logo and website address.](https://assets.ai.engineer/sites/aiecode2025/sha256/57ccb8e11dc21ef07707554167e71fa0cf334d921eddb5677f21a44133560bf0.webp)

IMPECCABLE

impeccable.style

Interface text:
EXIT - F
DARK - D
01 / 32

### Lumina sample product page

Bakaus introduces a deliberately basic Lumina page as a baseline. Its dark testimonial sits above a light call-to-action card inviting teams to run one release through Lumina.

[1:10](https://www.youtube.com/watch?v=v42opQpCy60&t=70s) [A Lumina product page with a clipped testimonial and a call to run a release through Lumina.](https://assets.ai.engineer/sites/aiecode2025/sha256/152e6a1471f33b26af51139a767e6ed0acf5c9128ebcc055ef4d07d88ccb595d.webp)

LUMINA · A SAMPLE PRODUCT PAGE

the argument, the owner, and the
final decision in the same place."

Priya Shah, VP Product at Orbit Labs

Run one release
through Lumina.

Bring a real spec, two active tickets, and the design file your team is already debating. We will map the decision trail in one working session.

Start a pilot

© 2026 Lumina, Inc.
Specs, tickets, design review, and release decisions in one planning surface.

Interface text:
EXIT · F
DARK · D
02 / 32

### Without and with Impeccable

For the same project and prompt, the model-only page stacks dark, color-coded sections; the Impeccable version places three light workflow stages beside a dark introduction.

[2:25](https://www.youtube.com/watch?v=v42opQpCy60&t=145s) [Two versions of a workflow page compare the model alone with Impeccable.](https://assets.ai.engineer/sites/aiecode2025/sha256/817b0fd172361e8cff043d2931ed97e2f1e847d90f60148e18e84a087c5ce1a6.webp)

NO SKILL · JUST THE MODEL

Lumina
Product  Workflow  Customers  Pilot  Book walkthrough

What stops slipping between tools.

The useful part of planning is not the card. It is the decision that usually gets lost between a doc, a ticket, and a meeting.

Evidence trail
Every phase keeps the source artifact, owner, and unresolved question attached.

Before kickoff
Ambiguity is named while scope is still cheap.
Lumina finds unresolved questions in the spec and turns them into owner-tagged decision items before sprint planning.
Spec  Figma review  Owner note

During build
Changes keep their source instead of becoming folklore.
Ticket edits, design deltas, and Slack decisions stay connected to the release object the team is actually shipping.
Ticket  Design delta  Blocked state

After release
The feature leaves behind a record people can read.
Support, growth, and engineering can see what changed, who approved it, and what follow-up moved out of scope.

WITH IMPECCABLE

Lumina
Product  Workflow  Customers  Pilot  Book walkthrough

What stops slipping between tools.

The useful part of planning is not the card. It is the decision that usually gets lost between a doc, a ticket, and a meeting.

Evidence trail
Every phase keeps the source artifact, owner, and unresolved question attached.

01
Before kickoff
Ambiguity is named while scope is still cheap.
Lumina finds unresolved questions in the spec and turns them into owner-tagged decision items before sprint planning.
Spec  Figma review  Owner note

02
During build
Changes keep their source instead of becoming folklore.
Ticket edits, design deltas, and Slack decisions stay connected to the release object the team is actually shipping.
Ticket  Design delta  Blocked state

03
After release
The feature leaves behind a record people can read.
Support, growth, and engineering can see what changed, who approved it, and what follow-up moved out of scope.
Release note  Decision log  Follow-up

Interface text:
EXIT · F
DARK · D
05 / 32

### Design at the speed of adjectives

Paul Bakaus introduces the talk, noting that the words are not all adjectives: some are verbs.

[2:35](https://www.youtube.com/watch?v=v42opQpCy60&t=155s) [Talk title beside a diagonal gold and teal textured graphic.](https://assets.ai.engineer/sites/aiecode2025/sha256/def9910b86b6c5189c9fe8cb4865695f7dd100a706e7a465d0c8c8dbf9f12223.webp)

Design at the speed
of adjectives.

SPEAKER
Paul Bakaus · Renaissance Geek

SESSION
Day 3 · 1:30pm · Room 2014

Interface text:
EXIT · F
DARK · D
06 / 32

### Design engineer

Paul Bakaus sees design and engineering roles blurring: designers move into code, engineers move into design, and the traditional handoff is breaking down.

[2:47](https://www.youtube.com/watch?v=v42opQpCy60&t=167s) [The words designer and engineer fade above the prominent phrase design engineer.](https://assets.ai.engineer/sites/aiecode2025/sha256/56c2c794d5739889a291c1e0120367fdb96db19f26b9e3cd274e9fc62d72484b.webp)

designer    engineer
design engineer

IMPECCABLE

DESIGN AT THE SPEED OF ADJECTIVES
07 / 32

Interface text:
EXIT - F
DARK - D

### Using Claude Opus to center a div

A meme pairs centering a div with a man lighting a cigar using a torch. Bakaus uses it to ask which tool is adequate for a task.

[4:31](https://www.youtube.com/watch?v=v42opQpCy60&t=271s) [A social post jokes about using Claude Opus to center a div, above a video of a man lighting a cigar with a torch.](https://assets.ai.engineer/sites/aiecode2025/sha256/d12e405ad8713320280e883403bd06b99273d7c97a99bbab3f2f4f268ce2af90.webp)

Itamar Golan
@ItakGol

Me using Claude Opus 4.7 to center a div.

Interface text:
IMPECCABLE
EXIT — F
DARK — D
DESIGN AT THE SPEED OF ADJECTIVES
09 / 32

### Too low

Bakaus argues that directly adjusting padding, margins and spacing operates at too low a level for most work. The inspector illustrates these fine-grained controls.

[4:54](https://www.youtube.com/watch?v=v42opQpCy60&t=294s) [“Too low” beside an inspector with spacing, radius, tracking and color controls.](https://assets.ai.engineer/sites/aiecode2025/sha256/7479862b236610ddc693e4fc94609a60c74d4a0db7fa94cd28d2f6b74c1c7d7a.webp)

Too low.

INSPECTOR
PADDING 24
RADIUS 8
GAP 16
TRACKING -.01
FILL

Interface text:
IMPECCABLE
EXIT - F
DARK - D
DESIGN AT THE SPEED OF ADJECTIVES
10 / 32

### Lumina website example

Bakaus uses Lumina’s purple gradients as an example of an older AI-generated web design pattern, which he says most frontier models have moved beyond.

[5:09](https://www.youtube.com/watch?v=v42opQpCy60&t=309s) [Dark workflow website with a purple gradient headline and feature cards.](https://assets.ai.engineer/sites/aiecode2025/sha256/1c5fc90119a746626f5aa6bef997a6e468098df47b785b2b5d2a4b38ef97ec61.webp)

POWERED BY AI

Build faster with intelligent workflows

The all-in-one platform that helps modern teams ship better products in record time. Powered by AI, designed for humans.

Join the waitlist →
Watch demo

Backed by top-tier investors

Northwind
Halcyon
Meridian
Fieldnote
Atlas & Co.
Verity

Everything you need to ship faster

One platform. Endless possibilities. Built for the future.

Lightning Fast
Enterprise Secure
Built to Scale

Interface text:
Lumina
Product
Solutions
Pricing
Customers
Docs
Sign in
Get started →
IMPECCABLE
EXIT · F
DARK · D
DESIGN AT THE SPEED OF ADJECTIVES
11 / 32

### Cadence website example

Bakaus calls this warm beige, serif-and-italic look “Claude beige.” He argues that even appealing designs become a problem when they all look alike.

[5:28](https://www.youtube.com/watch?v=v42opQpCy60&t=328s) [Beige workflow website with a serif headline and warm gradient background.](https://assets.ai.engineer/sites/aiecode2025/sha256/cd9f4171241f7df74dc417b72aa392bb6a8c602178eca980c617a0a9540c509e.webp)

AI-NATIVE WORKFLOWS

Build faster with intelligent workflows for modern teams

The all-in-one platform that helps product teams ship better software in record time. Powered by AI, designed for humans.

Start free trial →
Watch demo

Trusted by 10,000+ forward-thinking teams worldwide

Northwind
Halcyon
Quillstone
Fieldnote
Atlas & Co.
Verity

Everything you need to ship great products

One platform. Endless possibilities. Built for teams who care about craft.

Interface text:
Cadence
Product
Solutions
Pricing
Customers
Docs
Sign in
Get started
IMPECCABLE
EXIT - F
DARK - D
DESIGN AT THE SPEED OF ADJECTIVES
12 / 32

### Make it pop

Three overlapping memes capture the frustration of being asked to “make it pop” when designers and stakeholders lack a shared design language.

[7:10](https://www.youtube.com/watch?v=v42opQpCy60&t=430s) [Three overlapping memes joke about the frustrating design request to make it pop.](https://assets.ai.engineer/sites/aiecode2025/sha256/ec9978a4e4c406eb3d9b6add930e76e5e4ec63d31bd14168464997156d924d43.webp)

IMPECCABLE

If you guys could just make it pop
That'd be great

ONE DOES NOT SIMPLY
MAKE THE DESIGN "POP"

TELL ME TO "MAKE IT POP" AGAIN
I DARE YOU

DESIGN AT THE SPEED OF ADJECTIVES
15 / 32

Interface text:
EXIT · F
DARK · D

### Questions for design direction

Paul Bakaus starts with the intended emotional territory, feelings to avoid, and references. He also asks who the audience is: a designer needs to understand what the client is trying to build before choosing a direction.

[7:14](https://www.youtube.com/watch?v=v42opQpCy60&t=434s) [Three questions ask about emotional territory, what the design should never feel like, and references.](https://assets.ai.engineer/sites/aiecode2025/sha256/0a30ca12248c782b94208730bf7f5998e7cfcc09d9c5248cd383dc295341603f.webp)

IMPECCABLE

What's the emotional territory?
What should this never feel like?
What's the reference?

DESIGN AT THE SPEED OF ADJECTIVES
16 / 32

Interface text:
EXIT · F
DARK · D

### Nobody decided anything here

Bakaus uses a workflow landing page to critique one-shot design: the result may be competent, but he sees it as empty because nobody made design decisions.

[7:48](https://www.youtube.com/watch?v=v42opQpCy60&t=468s) [A generic workflow landing page appears above the critique, “Nobody decided anything here.”](https://assets.ai.engineer/sites/aiecode2025/sha256/1cd166c26427fb5e7708c15e7531a8f17031e5c7dddc0adc0d30a96a27d78917.webp)

Nobody decided anything here.

AI-NATIVE WORKFLOWS

Build faster with intelligent workflows for modern teams

The all-in-one platform that helps product teams ship better software in record time. Powered by AI, designed for humans.

Start free trial →
Watch demo

Trusted by 10,000+ forward-thinking teams worldwide

Northwind   Halcyon   Quillstone   Fieldnote   Atlas & Co.   Verity

Everything you need to ship great products
[illegible]

Interface text:
IMPECCABLE
Cadence
Product   Solutions   Pricing   Customers   Docs
Sign in   Get started
EXIT - F   DARK - D
DESIGN AT THE SPEED OF ADJECTIVES
— 17 / 32

## Full transcript

[0:01](https://www.youtube.com/watch?v=v42opQpCy60&t=1s) [music]

[0:12](https://www.youtube.com/watch?v=v42opQpCy60&t=12s) Cool. Uh, let's get this going. Welcome

[0:15](https://www.youtube.com/watch?v=v42opQpCy60&t=15s) everyone. Thanks for coming. Um, my name

[0:18](https://www.youtube.com/watch?v=v42opQpCy60&t=18s) is Paul and, uh, I'm going to try to

[0:21](https://www.youtube.com/watch?v=v42opQpCy60&t=21s) save you from the midday slump. So,

[0:24](https://www.youtube.com/watch?v=v42opQpCy60&t=24s) let's, uh, let's see if we can do that.

[0:26](https://www.youtube.com/watch?v=v42opQpCy60&t=26s) Um, okay. So this talk, this cold open

[0:29](https://www.youtube.com/watch?v=v42opQpCy60&t=29s) of this talk will make a lot more sense

[0:31](https://www.youtube.com/watch?v=v42opQpCy60&t=31s) if you know uh what impeccable is. Uh

[0:34](https://www.youtube.com/watch?v=v42opQpCy60&t=34s) but if you don't know what it is, it's a

[0:35](https://www.youtube.com/watch?v=v42opQpCy60&t=35s) design, it's a design skill that turns

[0:37](https://www.youtube.com/watch?v=v42opQpCy60&t=37s) your coding harness into a better

[0:39](https://www.youtube.com/watch?v=v42opQpCy60&t=39s) designer and hopefully you into a better

[0:40](https://www.youtube.com/watch?v=v42opQpCy60&t=40s) designer. Um and you can try it out. It

[0:43](https://www.youtube.com/watch?v=v42opQpCy60&t=43s) works across all harnesses, cloth code,

[0:45](https://www.youtube.com/watch?v=v42opQpCy60&t=45s) github, copilot, cursor, codex, etc. Um,

[0:50](https://www.youtube.com/watch?v=v42opQpCy60&t=50s) and this talk is really about uh my

[0:53](https://www.youtube.com/watch?v=v42opQpCy60&t=53s) approach to how to building this tool as

[0:56](https://www.youtube.com/watch?v=v42opQpCy60&t=56s) opposed to the tool itself. Um, but

[0:58](https://www.youtube.com/watch?v=v42opQpCy60&t=58s) let's get started with a pretty typical

[1:00](https://www.youtube.com/watch?v=v42opQpCy60&t=60s) website. So, this is a intentionally

[1:04](https://www.youtube.com/watch?v=v42opQpCy60&t=64s) very basic website and I want to give

[1:06](https://www.youtube.com/watch?v=v42opQpCy60&t=66s) you that one as context to what I'm

[1:08](https://www.youtube.com/watch?v=v42opQpCy60&t=68s) going to show you next. So, you know,

[1:10](https://www.youtube.com/watch?v=v42opQpCy60&t=70s) it's it's a it's it's an okay website.

[1:12](https://www.youtube.com/watch?v=v42opQpCy60&t=72s) It's not great. It's pretty bland. Um

[1:15](https://www.youtube.com/watch?v=v42opQpCy60&t=75s) but it at least it has some color some

[1:17](https://www.youtube.com/watch?v=v42opQpCy60&t=77s) something. Um so now here is um the

[1:22](https://www.youtube.com/watch?v=v42opQpCy60&t=82s) command make it bolder make the workflow

[1:25](https://www.youtube.com/watch?v=v42opQpCy60&t=85s) section bolder with impeccable.

[1:28](https://www.youtube.com/watch?v=v42opQpCy60&t=88s) Um so this is with impeccable installed.

[1:31](https://www.youtube.com/watch?v=v42opQpCy60&t=91s) So now there are it's not perfect. There

[1:35](https://www.youtube.com/watch?v=v42opQpCy60&t=95s) are some problems with this. for

[1:36](https://www.youtube.com/watch?v=v42opQpCy60&t=96s) example, the um the section numbers that

[1:39](https://www.youtube.com/watch?v=v42opQpCy60&t=99s) you have there, that's a very typical AI

[1:41](https://www.youtube.com/watch?v=v42opQpCy60&t=101s) slop tail uh that uh that GPT loves to

[1:44](https://www.youtube.com/watch?v=v42opQpCy60&t=104s) do and I mean Claude actually loves to

[1:46](https://www.youtube.com/watch?v=v42opQpCy60&t=106s) do as well and

[1:48](https://www.youtube.com/watch?v=v42opQpCy60&t=108s) it sometimes creeps in. So I wouldn't

[1:50](https://www.youtube.com/watch?v=v42opQpCy60&t=110s) say this is perfect by any means but I

[1:52](https://www.youtube.com/watch?v=v42opQpCy60&t=112s) think it's I would say bolder than

[1:54](https://www.youtube.com/watch?v=v42opQpCy60&t=114s) before. Um

[1:56](https://www.youtube.com/watch?v=v42opQpCy60&t=116s) now a lot of people install impeccable

[1:59](https://www.youtube.com/watch?v=v42opQpCy60&t=119s) try it out uh and then they ask me well

[2:02](https://www.youtube.com/watch?v=v42opQpCy60&t=122s) I don't know like maybe it could be

[2:03](https://www.youtube.com/watch?v=v42opQpCy60&t=123s) placebo maybe the model is good enough

[2:04](https://www.youtube.com/watch?v=v42opQpCy60&t=124s) in itself right uh not sure if it

[2:06](https://www.youtube.com/watch?v=v42opQpCy60&t=126s) actually works well let's compare it to

[2:10](https://www.youtube.com/watch?v=v42opQpCy60&t=130s) this is exactly the same project GPD55

[2:12](https://www.youtube.com/watch?v=v42opQpCy60&t=132s) on extra high um same exact prompt

[2:16](https://www.youtube.com/watch?v=v42opQpCy60&t=136s) without impeccable

[2:20](https://www.youtube.com/watch?v=v42opQpCy60&t=140s) so there is a slight difference I would

[2:22](https://www.youtube.com/watch?v=v42opQpCy60&t=142s) say but you be the judge of

[2:25](https://www.youtube.com/watch?v=v42opQpCy60&t=145s) Um, so the before and after is pretty

[2:28](https://www.youtube.com/watch?v=v42opQpCy60&t=148s) different and I'm going to talk about

[2:31](https://www.youtube.com/watch?v=v42opQpCy60&t=151s) why that is and um and and what the

[2:34](https://www.youtube.com/watch?v=v42opQpCy60&t=154s) approach is.

[2:36](https://www.youtube.com/watch?v=v42opQpCy60&t=156s) So designing at the speed of adjectives

[2:39](https://www.youtube.com/watch?v=v42opQpCy60&t=159s) and um to get the elephant out of the

[2:41](https://www.youtube.com/watch?v=v42opQpCy60&t=161s) room, they are not just adjectives,

[2:43](https://www.youtube.com/watch?v=v42opQpCy60&t=163s) they're also verbs. Uh but some of them

[2:46](https://www.youtube.com/watch?v=v42opQpCy60&t=166s) are adjectives.

[2:50](https://www.youtube.com/watch?v=v42opQpCy60&t=170s) First off, the role of the engineer and

[2:52](https://www.youtube.com/watch?v=v42opQpCy60&t=172s) the design are blurring. Um, I've seen

[2:54](https://www.youtube.com/watch?v=v42opQpCy60&t=174s) more people become design engineers than

[2:57](https://www.youtube.com/watch?v=v42opQpCy60&t=177s) ever. Designers are moving into code,

[2:59](https://www.youtube.com/watch?v=v42opQpCy60&t=179s) engineers are moving into design and

[3:01](https://www.youtube.com/watch?v=v42opQpCy60&t=181s) vice versa. Some of the best comments I

[3:03](https://www.youtube.com/watch?v=v42opQpCy60&t=183s) get from people who walk up to me and

[3:05](https://www.youtube.com/watch?v=v42opQpCy60&t=185s) say like, well, impeccable gives me this

[3:07](https://www.youtube.com/watch?v=v42opQpCy60&t=187s) shared language of design that everybody

[3:09](https://www.youtube.com/watch?v=v42opQpCy60&t=189s) can communicate now in. But really,

[3:12](https://www.youtube.com/watch?v=v42opQpCy60&t=192s) these worlds are all colliding in my

[3:14](https://www.youtube.com/watch?v=v42opQpCy60&t=194s) opinion and the typical handoff is kind

[3:17](https://www.youtube.com/watch?v=v42opQpCy60&t=197s) of broken. like the the waterfall

[3:19](https://www.youtube.com/watch?v=v42opQpCy60&t=199s) process of I start with design, maybe I

[3:22](https://www.youtube.com/watch?v=v42opQpCy60&t=202s) start with like the what on the PM side,

[3:24](https://www.youtube.com/watch?v=v42opQpCy60&t=204s) then it goes into design and then

[3:25](https://www.youtube.com/watch?v=v42opQpCy60&t=205s) there's like this handoff and this

[3:27](https://www.youtube.com/watch?v=v42opQpCy60&t=207s) critique process and then ultimately the

[3:29](https://www.youtube.com/watch?v=v42opQpCy60&t=209s) engineer builds it. That thing is just

[3:31](https://www.youtube.com/watch?v=v42opQpCy60&t=211s) not real anymore. I don't know about

[3:32](https://www.youtube.com/watch?v=v42opQpCy60&t=212s) you, but um I think that's starting to

[3:35](https://www.youtube.com/watch?v=v42opQpCy60&t=215s) collapse very quickly in small and large

[3:38](https://www.youtube.com/watch?v=v42opQpCy60&t=218s) companies.

[3:41](https://www.youtube.com/watch?v=v42opQpCy60&t=221s) And when it comes to the actual work of

[3:43](https://www.youtube.com/watch?v=v42opQpCy60&t=223s) design,

[3:45](https://www.youtube.com/watch?v=v42opQpCy60&t=225s) I feel like there's right now kind of

[3:46](https://www.youtube.com/watch?v=v42opQpCy60&t=226s) like two worlds that you can play in.

[3:48](https://www.youtube.com/watch?v=v42opQpCy60&t=228s) Either it's direct manipulation sort of

[3:51](https://www.youtube.com/watch?v=v42opQpCy60&t=231s) like in the pixel space, right? So

[3:53](https://www.youtube.com/watch?v=v42opQpCy60&t=233s) you're in Figma and you're manipulating

[3:55](https://www.youtube.com/watch?v=v42opQpCy60&t=235s) margins, paddings, whatever it is. Um or

[3:58](https://www.youtube.com/watch?v=v42opQpCy60&t=238s) you're in web flow or you're in some

[3:59](https://www.youtube.com/watch?v=v42opQpCy60&t=239s) other tool where you directly

[4:01](https://www.youtube.com/watch?v=v42opQpCy60&t=241s) manipulating the final output uh or the

[4:04](https://www.youtube.com/watch?v=v42opQpCy60&t=244s) design. Now that's fine, but then you

[4:07](https://www.youtube.com/watch?v=v42opQpCy60&t=247s) feel like you're getting behind because

[4:08](https://www.youtube.com/watch?v=v42opQpCy60&t=248s) everybody else is like agentic and going

[4:11](https://www.youtube.com/watch?v=v42opQpCy60&t=251s) crazy with loops and loop maxing, right?

[4:13](https://www.youtube.com/watch?v=v42opQpCy60&t=253s) And now you're going on the other

[4:14](https://www.youtube.com/watch?v=v42opQpCy60&t=254s) extreme, which is simply telling your

[4:16](https://www.youtube.com/watch?v=v42opQpCy60&t=256s) agent, please design this for me or

[4:18](https://www.youtube.com/watch?v=v42opQpCy60&t=258s) please build this. But it feels like to

[4:20](https://www.youtube.com/watch?v=v42opQpCy60&t=260s) me at least there's this there's this

[4:22](https://www.youtube.com/watch?v=v42opQpCy60&t=262s) middle ground that we haven't explored

[4:24](https://www.youtube.com/watch?v=v42opQpCy60&t=264s) enough like what is the exact level of

[4:26](https://www.youtube.com/watch?v=v42opQpCy60&t=266s) control? How can we insert the human in

[4:28](https://www.youtube.com/watch?v=v42opQpCy60&t=268s) the loop at the exact right time?

[4:32](https://www.youtube.com/watch?v=v42opQpCy60&t=272s) Uh and so this this came to mind then

[4:35](https://www.youtube.com/watch?v=v42opQpCy60&t=275s) it's pretty popular tweet a while ago.

[4:37](https://www.youtube.com/watch?v=v42opQpCy60&t=277s) Um so centering a diff with opus. Yes.

[4:42](https://www.youtube.com/watch?v=v42opQpCy60&t=282s) Uh not a great use of opus. Uh but you

[4:46](https://www.youtube.com/watch?v=v42opQpCy60&t=286s) know it kind of speaks to that problem.

[4:48](https://www.youtube.com/watch?v=v42opQpCy60&t=288s) It's like okay well when do we use which

[4:51](https://www.youtube.com/watch?v=v42opQpCy60&t=291s) tool? When is which tool adequate to do

[4:53](https://www.youtube.com/watch?v=v42opQpCy60&t=293s) what job?

[4:56](https://www.youtube.com/watch?v=v42opQpCy60&t=296s) In my opinion right now for most work

[5:00](https://www.youtube.com/watch?v=v42opQpCy60&t=300s) the direct manipulation of padding,

[5:02](https://www.youtube.com/watch?v=v42opQpCy60&t=302s) margins, spacing and so on is actually

[5:04](https://www.youtube.com/watch?v=v42opQpCy60&t=304s) at a elevation that's too low.

[5:08](https://www.youtube.com/watch?v=v42opQpCy60&t=308s) And on the other hand um if you go fully

[5:12](https://www.youtube.com/watch?v=v42opQpCy60&t=312s) agentic you get web pages like this now

[5:15](https://www.youtube.com/watch?v=v42opQpCy60&t=315s) that you would you would get this in

[5:16](https://www.youtube.com/watch?v=v42opQpCy60&t=316s) like 2022 I would say. So everybody here

[5:19](https://www.youtube.com/watch?v=v42opQpCy60&t=319s) can point out the typical AI slot

[5:20](https://www.youtube.com/watch?v=v42opQpCy60&t=320s) patterns. Um but the purple gradients

[5:23](https://www.youtube.com/watch?v=v42opQpCy60&t=323s) were actually way beyond that. there are

[5:25](https://www.youtube.com/watch?v=v42opQpCy60&t=325s) no purple gradients anymore uh in most

[5:27](https://www.youtube.com/watch?v=v42opQpCy60&t=327s) frontier models. Um now we just get this

[5:31](https://www.youtube.com/watch?v=v42opQpCy60&t=331s) and it's kind of wears a different suit

[5:32](https://www.youtube.com/watch?v=v42opQpCy60&t=332s) as Claude would say. Um but uh but it

[5:36](https://www.youtube.com/watch?v=v42opQpCy60&t=336s) really is slop as well. It's just a

[5:38](https://www.youtube.com/watch?v=v42opQpCy60&t=338s) moving target. So now we have I call

[5:40](https://www.youtube.com/watch?v=v42opQpCy60&t=340s) this claude beige. We have these

[5:42](https://www.youtube.com/watch?v=v42opQpCy60&t=342s) instrument serif fonts. We have italics.

[5:44](https://www.youtube.com/watch?v=v42opQpCy60&t=344s) And it's not necessarily a bad design.

[5:46](https://www.youtube.com/watch?v=v42opQpCy60&t=346s) It's just everything that comes out of

[5:48](https://www.youtube.com/watch?v=v42opQpCy60&t=348s) claw design looks that way. And when

[5:51](https://www.youtube.com/watch?v=v42opQpCy60&t=351s) everything looks the same, you kind of

[5:52](https://www.youtube.com/watch?v=v42opQpCy60&t=352s) get algorithmic unilo as I call it. Uh

[5:56](https://www.youtube.com/watch?v=v42opQpCy60&t=356s) so also not great.

[5:58](https://www.youtube.com/watch?v=v42opQpCy60&t=358s) Now here's my first hot take of today's

[6:01](https://www.youtube.com/watch?v=v42opQpCy60&t=361s) session. You cannot oneshot design.

[6:05](https://www.youtube.com/watch?v=v42opQpCy60&t=365s) Um now many people want to and maybe

[6:07](https://www.youtube.com/watch?v=v42opQpCy60&t=367s) we'll get there eventually. I just don't

[6:09](https://www.youtube.com/watch?v=v42opQpCy60&t=369s) think it's possible at the current

[6:11](https://www.youtube.com/watch?v=v42opQpCy60&t=371s) moment. Uh maybe not ever. Um, I think

[6:14](https://www.youtube.com/watch?v=v42opQpCy60&t=374s) in order to build something that really

[6:17](https://www.youtube.com/watch?v=v42opQpCy60&t=377s) looks and feels great and is effective

[6:19](https://www.youtube.com/watch?v=v42opQpCy60&t=379s) design, you need to have something

[6:22](https://www.youtube.com/watch?v=v42opQpCy60&t=382s) that's context context rich which has

[6:24](https://www.youtube.com/watch?v=v42opQpCy60&t=384s) been informed by what you're trying to

[6:26](https://www.youtube.com/watch?v=v42opQpCy60&t=386s) do, what your audience is, what you're

[6:28](https://www.youtube.com/watch?v=v42opQpCy60&t=388s) trying to build. And also it will have

[6:30](https://www.youtube.com/watch?v=v42opQpCy60&t=390s) to be multi-shot. You will have to

[6:32](https://www.youtube.com/watch?v=v42opQpCy60&t=392s) iterate on your design. Uh, and you I

[6:35](https://www.youtube.com/watch?v=v42opQpCy60&t=395s) mean even if you're a soloreneur, but if

[6:37](https://www.youtube.com/watch?v=v42opQpCy60&t=397s) you're not a soloreneur, you might have

[6:39](https://www.youtube.com/watch?v=v42opQpCy60&t=399s) different people who have different

[6:40](https://www.youtube.com/watch?v=v42opQpCy60&t=400s) opinions. Users have opinions. I mean

[6:42](https://www.youtube.com/watch?v=v42opQpCy60&t=402s) design is messy. it's process and

[6:45](https://www.youtube.com/watch?v=v42opQpCy60&t=405s) wishing it away and just saying like

[6:47](https://www.youtube.com/watch?v=v42opQpCy60&t=407s) solve this problem for me agent will not

[6:49](https://www.youtube.com/watch?v=v42opQpCy60&t=409s) unfortunately solve your problem. Um

[6:54](https://www.youtube.com/watch?v=v42opQpCy60&t=414s) now the other problem is if you don't

[6:56](https://www.youtube.com/watch?v=v42opQpCy60&t=416s) know the language of design or if your

[6:58](https://www.youtube.com/watch?v=v42opQpCy60&t=418s) stakeholders don't know the language of

[7:00](https://www.youtube.com/watch?v=v42opQpCy60&t=420s) design gets really frustrating really

[7:01](https://www.youtube.com/watch?v=v42opQpCy60&t=421s) quickly too. So if you've ever designed

[7:03](https://www.youtube.com/watch?v=v42opQpCy60&t=423s) something um you kind of know like this

[7:05](https://www.youtube.com/watch?v=v42opQpCy60&t=425s) kind of experience um and then you know

[7:08](https://www.youtube.com/watch?v=v42opQpCy60&t=428s) the inner feeling builds up of like

[7:11](https://www.youtube.com/watch?v=v42opQpCy60&t=431s) and at some point you're like

[7:15](https://www.youtube.com/watch?v=v42opQpCy60&t=435s) uh

[7:16](https://www.youtube.com/watch?v=v42opQpCy60&t=436s) so really what you have to ask first is

[7:18](https://www.youtube.com/watch?v=v42opQpCy60&t=438s) what's the emotional territory? What

[7:20](https://www.youtube.com/watch?v=v42opQpCy60&t=440s) should this never feel like? What's

[7:22](https://www.youtube.com/watch?v=v42opQpCy60&t=442s) what's the reference? What's the

[7:24](https://www.youtube.com/watch?v=v42opQpCy60&t=444s) audience? These are all really important

[7:26](https://www.youtube.com/watch?v=v42opQpCy60&t=446s) questions to figure out. Like you can't

[7:27](https://www.youtube.com/watch?v=v42opQpCy60&t=447s) go to a human design studio even if it's

[7:31](https://www.youtube.com/watch?v=v42opQpCy60&t=451s) the best design studio in the world. You

[7:33](https://www.youtube.com/watch?v=v42opQpCy60&t=453s) go to design director and you say like

[7:35](https://www.youtube.com/watch?v=v42opQpCy60&t=455s) you know what I want to design for my

[7:37](https://www.youtube.com/watch?v=v42opQpCy60&t=457s) brand and a design dire not nods. It's

[7:40](https://www.youtube.com/watch?v=v42opQpCy60&t=460s) like got it and then walks away. That

[7:43](https://www.youtube.com/watch?v=v42opQpCy60&t=463s) doesn't make any sense. Like they

[7:45](https://www.youtube.com/watch?v=v42opQpCy60&t=465s) obviously have to figure out what it is

[7:46](https://www.youtube.com/watch?v=v42opQpCy60&t=466s) that you're trying to build and what

[7:47](https://www.youtube.com/watch?v=v42opQpCy60&t=467s) you're trying to get out of it.

[7:50](https://www.youtube.com/watch?v=v42opQpCy60&t=470s) Importantly on this example even sort of

[7:52](https://www.youtube.com/watch?v=v42opQpCy60&t=472s) like the 2026 version of AI slop you

[7:55](https://www.youtube.com/watch?v=v42opQpCy60&t=475s) know quickly vibe coded page nobody

[7:58](https://www.youtube.com/watch?v=v42opQpCy60&t=478s) decided anything here

[8:01](https://www.youtube.com/watch?v=v42opQpCy60&t=481s) like you just oneshotted this nobody

[8:03](https://www.youtube.com/watch?v=v42opQpCy60&t=483s) decided anything on this page this was

[8:05](https://www.youtube.com/watch?v=v42opQpCy60&t=485s) just I mean it's maybe competent but

[8:08](https://www.youtube.com/watch?v=v42opQpCy60&t=488s) completely empty

[8:10](https://www.youtube.com/watch?v=v42opQpCy60&t=490s) so my uh thesis that I make here and

[8:15](https://www.youtube.com/watch?v=v42opQpCy60&t=495s) what I've been trying to build over the

[8:16](https://www.youtube.com/watch?v=v42opQpCy60&t=496s) last couple months is a tool that gives

[8:19](https://www.youtube.com/watch?v=v42opQpCy60&t=499s) you just the amount of control needed to

[8:22](https://www.youtube.com/watch?v=v42opQpCy60&t=502s) steer your agent in the right direction

[8:24](https://www.youtube.com/watch?v=v42opQpCy60&t=504s) with adjectives and verbs.

[8:26](https://www.youtube.com/watch?v=v42opQpCy60&t=506s) And these are the types of words I'm

[8:28](https://www.youtube.com/watch?v=v42opQpCy60&t=508s) talking about. Talking about words like

[8:30](https://www.youtube.com/watch?v=v42opQpCy60&t=510s) make this bolder, make this quieter, uh

[8:33](https://www.youtube.com/watch?v=v42opQpCy60&t=513s) distill this. So basically

[8:34](https://www.youtube.com/watch?v=v42opQpCy60&t=514s) simplification, um polish this, um make

[8:37](https://www.youtube.com/watch?v=v42opQpCy60&t=517s) it denser or harden this. Um harden for

[8:41](https://www.youtube.com/watch?v=v42opQpCy60&t=521s) instance would mean uh make sure that

[8:43](https://www.youtube.com/watch?v=v42opQpCy60&t=523s) this design works across the board.

[8:44](https://www.youtube.com/watch?v=v42opQpCy60&t=524s) Maybe the performance is bad on certain

[8:46](https://www.youtube.com/watch?v=v42opQpCy60&t=526s) devices. Maybe it's not responsive. Um,

[8:49](https://www.youtube.com/watch?v=v42opQpCy60&t=529s) and so these are these are words

[8:51](https://www.youtube.com/watch?v=v42opQpCy60&t=531s) that we use in the world of design. And

[8:55](https://www.youtube.com/watch?v=v42opQpCy60&t=535s) I noticed when seeing two people attempt

[8:57](https://www.youtube.com/watch?v=v42opQpCy60&t=537s) the exact same task and one is an

[8:59](https://www.youtube.com/watch?v=v42opQpCy60&t=539s) engineer who's never really touched

[9:00](https://www.youtube.com/watch?v=v42opQpCy60&t=540s) design at all and the other one is a

[9:02](https://www.youtube.com/watch?v=v42opQpCy60&t=542s) designer um there's a stark difference

[9:06](https://www.youtube.com/watch?v=v42opQpCy60&t=546s) even when they use the same model and

[9:07](https://www.youtube.com/watch?v=v42opQpCy60&t=547s) same harness everything in the output

[9:09](https://www.youtube.com/watch?v=v42opQpCy60&t=549s) that they're getting based on the

[9:10](https://www.youtube.com/watch?v=v42opQpCy60&t=550s) language that they use. So, I've been

[9:14](https://www.youtube.com/watch?v=v42opQpCy60&t=554s) trying to put that language basically

[9:17](https://www.youtube.com/watch?v=v42opQpCy60&t=557s) compress it into a skill uh and into a

[9:19](https://www.youtube.com/watch?v=v42opQpCy60&t=559s) system to be able to express yourselves

[9:21](https://www.youtube.com/watch?v=v42opQpCy60&t=561s) better. And so, for example, you could

[9:24](https://www.youtube.com/watch?v=v42opQpCy60&t=564s) have like a baseline um over here, but

[9:27](https://www.youtube.com/watch?v=v42opQpCy60&t=567s) then you make it bolder and the agent

[9:30](https://www.youtube.com/watch?v=v42opQpCy60&t=570s) actually knows what bolder in your

[9:31](https://www.youtube.com/watch?v=v42opQpCy60&t=571s) context means. You make it quieter, it

[9:33](https://www.youtube.com/watch?v=v42opQpCy60&t=573s) knows what it means. You distill and it

[9:36](https://www.youtube.com/watch?v=v42opQpCy60&t=576s) knows what it means.

[9:40](https://www.youtube.com/watch?v=v42opQpCy60&t=580s) Um, but then bolder how what does bolder

[9:44](https://www.youtube.com/watch?v=v42opQpCy60&t=584s) mean in the context of your project?

[9:45](https://www.youtube.com/watch?v=v42opQpCy60&t=585s) That's a really important question

[9:47](https://www.youtube.com/watch?v=v42opQpCy60&t=587s) because as you could tell at the

[9:48](https://www.youtube.com/watch?v=v42opQpCy60&t=588s) beginning of the demo uh in the cold

[9:51](https://www.youtube.com/watch?v=v42opQpCy60&t=591s) open uh when you just ask GPT or claude

[9:55](https://www.youtube.com/watch?v=v42opQpCy60&t=595s) whatever make this bolder it doesn't

[9:56](https://www.youtube.com/watch?v=v42opQpCy60&t=596s) know anything about what you mean. Uh

[9:58](https://www.youtube.com/watch?v=v42opQpCy60&t=598s) now it has its own sense of reference of

[10:01](https://www.youtube.com/watch?v=v42opQpCy60&t=601s) like what boulder could mean but it will

[10:03](https://www.youtube.com/watch?v=v42opQpCy60&t=603s) do whatever it wants right it will

[10:05](https://www.youtube.com/watch?v=v42opQpCy60&t=605s) invent new colors it will invent new

[10:07](https://www.youtube.com/watch?v=v42opQpCy60&t=607s) gradients. it will I mean it doesn't

[10:09](https://www.youtube.com/watch?v=v42opQpCy60&t=609s) matter um what it actually means in

[10:12](https://www.youtube.com/watch?v=v42opQpCy60&t=612s) impeccable

[10:14](https://www.youtube.com/watch?v=v42opQpCy60&t=614s) not gradients not glass not neon but

[10:17](https://www.youtube.com/watch?v=v42opQpCy60&t=617s) actually hierarchy scale decisive type

[10:20](https://www.youtube.com/watch?v=v42opQpCy60&t=620s) so uh things that uh don't break your

[10:23](https://www.youtube.com/watch?v=v42opQpCy60&t=623s) design system and adequately raise the

[10:27](https://www.youtube.com/watch?v=v42opQpCy60&t=627s) attention that the user would put on it

[10:31](https://www.youtube.com/watch?v=v42opQpCy60&t=631s) uh and this is an actual sentence from

[10:33](https://www.youtube.com/watch?v=v42opQpCy60&t=633s) the the file that is loaded when you say

[10:37](https://www.youtube.com/watch?v=v42opQpCy60&t=637s) bolder impeccable um show someone your

[10:39](https://www.youtube.com/watch?v=v42opQpCy60&t=639s) work and say AI make this bolder made

[10:42](https://www.youtube.com/watch?v=v42opQpCy60&t=642s) this bolder if they believe you you

[10:44](https://www.youtube.com/watch?v=v42opQpCy60&t=644s) failed this is something that we

[10:47](https://www.youtube.com/watch?v=v42opQpCy60&t=647s) actually instruct the agent to do for

[10:49](https://www.youtube.com/watch?v=v42opQpCy60&t=649s) themselves and then the agent oftent

[10:50](https://www.youtube.com/watch?v=v42opQpCy60&t=650s) times reflects and like I don't know

[10:54](https://www.youtube.com/watch?v=v42opQpCy60&t=654s) think I did some bad work here

[10:57](https://www.youtube.com/watch?v=v42opQpCy60&t=657s) an adjective is a light wart and a light

[11:01](https://www.youtube.com/watch?v=v42opQpCy60&t=661s) wart such a German term and Matt Puk

[11:05](https://www.youtube.com/watch?v=v42opQpCy60&t=665s) actually talked about this recently uh

[11:06](https://www.youtube.com/watch?v=v42opQpCy60&t=666s) who also makes some really excellent

[11:08](https://www.youtube.com/watch?v=v42opQpCy60&t=668s) skills. And so this is uh stolen by one

[11:10](https://www.youtube.com/watch?v=v42opQpCy60&t=670s) of his tweets, but I really think uh um

[11:14](https://www.youtube.com/watch?v=v42opQpCy60&t=674s) it makes a lot of sense. Um these are

[11:16](https://www.youtube.com/watch?v=v42opQpCy60&t=676s) words that h that you basically imbue

[11:19](https://www.youtube.com/watch?v=v42opQpCy60&t=679s) with meaning that you infuse with

[11:21](https://www.youtube.com/watch?v=v42opQpCy60&t=681s) meaning and they mean something. They

[11:23](https://www.youtube.com/watch?v=v42opQpCy60&t=683s) already mean something to the model, but

[11:24](https://www.youtube.com/watch?v=v42opQpCy60&t=684s) then you translate this into the area

[11:28](https://www.youtube.com/watch?v=v42opQpCy60&t=688s) that you're interested in

[11:30](https://www.youtube.com/watch?v=v42opQpCy60&t=690s) and the right altitude really shifts.

[11:34](https://www.youtube.com/watch?v=v42opQpCy60&t=694s) Um, now I don't think you can solve any

[11:38](https://www.youtube.com/watch?v=v42opQpCy60&t=698s) problems at that altitude. That's super

[11:40](https://www.youtube.com/watch?v=v42opQpCy60&t=700s) important too. Uh, there is still room

[11:42](https://www.youtube.com/watch?v=v42opQpCy60&t=702s) for the very beginning. For instance, if

[11:44](https://www.youtube.com/watch?v=v42opQpCy60&t=704s) you just want exploratory work and you

[11:46](https://www.youtube.com/watch?v=v42opQpCy60&t=706s) just want to get something on the screen

[11:47](https://www.youtube.com/watch?v=v42opQpCy60&t=707s) or you just want the last amount of

[11:50](https://www.youtube.com/watch?v=v42opQpCy60&t=710s) polish. I don't think right now uh AI is

[11:53](https://www.youtube.com/watch?v=v42opQpCy60&t=713s) good enough to replace humans for the

[11:55](https://www.youtube.com/watch?v=v42opQpCy60&t=715s) last 5, 10, maybe even 20% of the work

[11:57](https://www.youtube.com/watch?v=v42opQpCy60&t=717s) to get it from good to great. Uh but it

[12:02](https://www.youtube.com/watch?v=v42opQpCy60&t=722s) does actually make it better. Now I've

[12:05](https://www.youtube.com/watch?v=v42opQpCy60&t=725s) built tools for more than 20 years. I

[12:07](https://www.youtube.com/watch?v=v42opQpCy60&t=727s) guess I'm dating myself here. Uh but

[12:10](https://www.youtube.com/watch?v=v42opQpCy60&t=730s) whenever I build a tool, I actually map

[12:11](https://www.youtube.com/watch?v=v42opQpCy60&t=731s) the workflow first. I think about what

[12:14](https://www.youtube.com/watch?v=v42opQpCy60&t=734s) is the actual workflow of the target

[12:15](https://www.youtube.com/watch?v=v42opQpCy60&t=735s) user that I'm trying to help. And the

[12:18](https://www.youtube.com/watch?v=v42opQpCy60&t=738s) workflow of design is not linear. It's

[12:20](https://www.youtube.com/watch?v=v42opQpCy60&t=740s) messy. Has many different stages. Uh

[12:23](https://www.youtube.com/watch?v=v42opQpCy60&t=743s) there are different people involved. And

[12:25](https://www.youtube.com/watch?v=v42opQpCy60&t=745s) so I kind of mapped every part of the

[12:27](https://www.youtube.com/watch?v=v42opQpCy60&t=747s) process and thought about well what are

[12:29](https://www.youtube.com/watch?v=v42opQpCy60&t=749s) the injection points along that route

[12:32](https://www.youtube.com/watch?v=v42opQpCy60&t=752s) and how can we help along that route.

[12:35](https://www.youtube.com/watch?v=v42opQpCy60&t=755s) And so you start with initialization

[12:36](https://www.youtube.com/watch?v=v42opQpCy60&t=756s) with the shaping process of design uh

[12:39](https://www.youtube.com/watch?v=v42opQpCy60&t=759s) you go over to uh crafting to iterating

[12:42](https://www.youtube.com/watch?v=v42opQpCy60&t=762s) uh with all these verbs and adjectives

[12:44](https://www.youtube.com/watch?v=v42opQpCy60&t=764s) and then to the actual harden and polish

[12:46](https://www.youtube.com/watch?v=v42opQpCy60&t=766s) phase and finally you kind of bring it

[12:48](https://www.youtube.com/watch?v=v42opQpCy60&t=768s) back to your design system. You do some

[12:49](https://www.youtube.com/watch?v=v42opQpCy60&t=769s) tech debt cleanup design deck cleanup.

[12:53](https://www.youtube.com/watch?v=v42opQpCy60&t=773s) Um, now here's one example of a command

[12:56](https://www.youtube.com/watch?v=v42opQpCy60&t=776s) that I wasn't actually sure about

[12:57](https://www.youtube.com/watch?v=v42opQpCy60&t=777s) shipping and it's called overdrive. Um,

[13:01](https://www.youtube.com/watch?v=v42opQpCy60&t=781s) I basically built this uh built this

[13:03](https://www.youtube.com/watch?v=v42opQpCy60&t=783s) command in Impeccable that uh tries to

[13:06](https://www.youtube.com/watch?v=v42opQpCy60&t=786s) create something completely over the top

[13:08](https://www.youtube.com/watch?v=v42opQpCy60&t=788s) and it was kind of like a a half of a

[13:10](https://www.youtube.com/watch?v=v42opQpCy60&t=790s) joke maybe. Um, but people absolutely

[13:14](https://www.youtube.com/watch?v=v42opQpCy60&t=794s) are rabbit about this about this thing.

[13:15](https://www.youtube.com/watch?v=v42opQpCy60&t=795s) Um, and they love it. Um, and so this is

[13:18](https://www.youtube.com/watch?v=v42opQpCy60&t=798s) just one example of I mean this is not

[13:20](https://www.youtube.com/watch?v=v42opQpCy60&t=800s) oneshotted. Uh this is a um sort of

[13:22](https://www.youtube.com/watch?v=v42opQpCy60&t=802s) realistic event horizon shader um that

[13:25](https://www.youtube.com/watch?v=v42opQpCy60&t=805s) I've built for my shader library radiant

[13:27](https://www.youtube.com/watch?v=v42opQpCy60&t=807s) shaders. But I did actually use the

[13:29](https://www.youtube.com/watch?v=v42opQpCy60&t=809s) overdrive command for this to uh

[13:32](https://www.youtube.com/watch?v=v42opQpCy60&t=812s) overdrive it even more uh and make it

[13:34](https://www.youtube.com/watch?v=v42opQpCy60&t=814s) more ridiculous. So sometimes I come up

[13:36](https://www.youtube.com/watch?v=v42opQpCy60&t=816s) with these uh commands I'm actually not

[13:38](https://www.youtube.com/watch?v=v42opQpCy60&t=818s) sure about and I test them with the

[13:39](https://www.youtube.com/watch?v=v42opQpCy60&t=819s) community and once it sticks uh I

[13:42](https://www.youtube.com/watch?v=v42opQpCy60&t=822s) realize okay well there are more people

[13:44](https://www.youtube.com/watch?v=v42opQpCy60&t=824s) who are getting joy out of this.

[13:46](https://www.youtube.com/watch?v=v42opQpCy60&t=826s) Um

[13:49](https://www.youtube.com/watch?v=v42opQpCy60&t=829s) oh here we go. Here we go. Okay. Um, an

[13:52](https://www.youtube.com/watch?v=v42opQpCy60&t=832s) adjective with nothing behind is just a

[13:54](https://www.youtube.com/watch?v=v42opQpCy60&t=834s) nicer prompt. So, you really have to

[13:56](https://www.youtube.com/watch?v=v42opQpCy60&t=836s) tell the agent what you mean by the word

[13:59](https://www.youtube.com/watch?v=v42opQpCy60&t=839s) that you're using. Uh, it it has so many

[14:01](https://www.youtube.com/watch?v=v42opQpCy60&t=841s) different meanings uh within its

[14:04](https://www.youtube.com/watch?v=v42opQpCy60&t=844s) training materials that you really have

[14:05](https://www.youtube.com/watch?v=v42opQpCy60&t=845s) to tell it. Um, now here's another

[14:07](https://www.youtube.com/watch?v=v42opQpCy60&t=847s) thing.

[14:09](https://www.youtube.com/watch?v=v42opQpCy60&t=849s) I've gotten so many requests

[14:12](https://www.youtube.com/watch?v=v42opQpCy60&t=852s) for an automatic way of using

[14:13](https://www.youtube.com/watch?v=v42opQpCy60&t=853s) Impeccable. So many. It's so

[14:17](https://www.youtube.com/watch?v=v42opQpCy60&t=857s) frustrating. Like so at least once a

[14:19](https://www.youtube.com/watch?v=v42opQpCy60&t=859s) week somebody tweets at me say like you

[14:21](https://www.youtube.com/watch?v=v42opQpCy60&t=861s) know what would be cool just let

[14:22](https://www.youtube.com/watch?v=v42opQpCy60&t=862s) impeccable do all the work by itself. I

[14:24](https://www.youtube.com/watch?v=v42opQpCy60&t=864s) don't have to decide on any command

[14:25](https://www.youtube.com/watch?v=v42opQpCy60&t=865s) anymore. That's not the point. The point

[14:27](https://www.youtube.com/watch?v=v42opQpCy60&t=867s) is to give you a way to steer what you

[14:30](https://www.youtube.com/watch?v=v42opQpCy60&t=870s) want to end up with. It's never going to

[14:33](https://www.youtube.com/watch?v=v42opQpCy60&t=873s) be a tool to oneshot design. That's not

[14:35](https://www.youtube.com/watch?v=v42opQpCy60&t=875s) the intent. And I'll never I mean

[14:37](https://www.youtube.com/watch?v=v42opQpCy60&t=877s) there's a pull request standing uh

[14:39](https://www.youtube.com/watch?v=v42opQpCy60&t=879s) standing out right now that I'm going to

[14:40](https://www.youtube.com/watch?v=v42opQpCy60&t=880s) close because of that.

[14:43](https://www.youtube.com/watch?v=v42opQpCy60&t=883s) There is no auto and there will be no

[14:45](https://www.youtube.com/watch?v=v42opQpCy60&t=885s) auto

[14:47](https://www.youtube.com/watch?v=v42opQpCy60&t=887s) in my opinion and uh this is a bit

[14:49](https://www.youtube.com/watch?v=v42opQpCy60&t=889s) awkward maybe for some of the next

[14:51](https://www.youtube.com/watch?v=v42opQpCy60&t=891s) speakers but I think taste cannot be

[14:54](https://www.youtube.com/watch?v=v42opQpCy60&t=894s) amplified uh sorry I think taste can be

[14:56](https://www.youtube.com/watch?v=v42opQpCy60&t=896s) amplified I think I call this amplified

[14:58](https://www.youtube.com/watch?v=v42opQpCy60&t=898s) craft uh and I think you can work with

[15:01](https://www.youtube.com/watch?v=v42opQpCy60&t=901s) tools to sharpen your taste and bring

[15:04](https://www.youtube.com/watch?v=v42opQpCy60&t=904s) out more of your taste I really do not

[15:05](https://www.youtube.com/watch?v=v42opQpCy60&t=905s) think it can be lab ground lab grown I

[15:07](https://www.youtube.com/watch?v=v42opQpCy60&t=907s) think it is uh taste by definition sort

[15:11](https://www.youtube.com/watch?v=v42opQpCy60&t=911s) of is uh contextual It's cultural. It's

[15:15](https://www.youtube.com/watch?v=v42opQpCy60&t=915s) scars. And once everybody replicates the

[15:17](https://www.youtube.com/watch?v=v42opQpCy60&t=917s) same thing, it starts to become really

[15:20](https://www.youtube.com/watch?v=v42opQpCy60&t=920s) muddy and we don't think of it as taste

[15:23](https://www.youtube.com/watch?v=v42opQpCy60&t=923s) anymore. That's my opinion. And I know

[15:24](https://www.youtube.com/watch?v=v42opQpCy60&t=924s) this is like a hotly contested topic.

[15:26](https://www.youtube.com/watch?v=v42opQpCy60&t=926s) Uh, but I'm not trying to solve taste

[15:28](https://www.youtube.com/watch?v=v42opQpCy60&t=928s) with my tools.

[15:30](https://www.youtube.com/watch?v=v42opQpCy60&t=930s) Um,

[15:32](https://www.youtube.com/watch?v=v42opQpCy60&t=932s) that's what I got. Uh, this was about

[15:34](https://www.youtube.com/watch?v=v42opQpCy60&t=934s) finding the right level of control for

[15:36](https://www.youtube.com/watch?v=v42opQpCy60&t=936s) design. Thank you very much. And, uh, I

[15:38](https://www.youtube.com/watch?v=v42opQpCy60&t=938s) think I have time for a few questions if

[15:40](https://www.youtube.com/watch?v=v42opQpCy60&t=940s) you have any. Thank you.

[15:56](https://www.youtube.com/watch?v=v42opQpCy60&t=956s) >> [music]
