Paul Bakaus is the founder and CEO of Renaissance Geek and the creator of Impeccable, a toolkit for directing AI coding agents toward deliberate, distinctive interface design. His career spans jQuery UI, browser development tools, and software for creators. Across that work, he has pursued a recurring question: how can tools make creative production more accessible while helping people develop the judgment to do it well?
Making the web easier to build
Bakaus created jQuery UI in 2007, supplying reusable interactions and widgets such as drag-and-drop, sortable lists, and date pickers. Developers could assemble richer interfaces without implementing each behavior themselves. In January 2008, Liferay hired him to develop the library full time. The partnership connected open-source development with enterprise use: Liferay planned to integrate the library into its products and offer business-critical support.
He subsequently built Aves, an early browser game engine, and co-founded the company around it, which Zynga acquired in 2010. He joined Google in 2013, leading product and developer relations for Chrome DevTools, and later developer relations for AMP and Web Stories. His introduction to mobile-first Device Mode explained how a streamlined interface and resizable viewport could make responsive design part of developers’ everyday workflow: inspect the real page at different widths and adjust it without continually rearranging the development environment.
Building tools for creators
As Google’s head of creator relations, Bakaus founded Google for Creators, extending his work on tools and education to people publishing on the web. He also took a clear position on the reader’s experience: Web Stories should deliver a complete story, rather than interrupt a list or recipe and send readers elsewhere for what the headline promised. Publishers could link to deeper material while still making the immediate experience useful.
Impeccable addresses a gap between specifying every margin and padding value and asking an agent to make all the design decisions. Bakaus’s Design at the Speed of Adjectives describes how people can communicate intent at a more useful level while retaining control over the result.
Shared design vocabulary: Before changing an interface, Bakaus wants people to establish its audience, purpose, desired feeling, references, and constraints. Commands such as “bolder,” “quieter,” and “distill” then give the agent specific interventions. “Bolder,” for example, means strengthening hierarchy, scale, and typography within the project’s visual language; an unconstrained model might instead invent colors, gradients, or effects. The vocabulary matters because the toolkit explains what each direction should cause the agent to do.
Checks in the working product:Impeccable builds on Anthropic’s frontend-design skill with persistent project context, critique, technical checks, and live browser iteration. Critique examines hierarchy and clarity; audits address accessibility, performance, and responsive behavior. Browser inspection lets people assess changes in the actual interface, where a plausible design still has to work across devices.
Deliberate iteration: Bakaus connects these interventions to shaping a direction, crafting and revising it, hardening and polishing it, and incorporating the result into the design system. Removing predictable AI styling establishes a starting point. A competent page can still feel empty if nobody has decided what it should communicate. He rejects automatic operation as Impeccable’s purpose: users and collaborators must keep making choices and refining the work.
Creative tools that develop judgment
His critique of “Cursor for X” products extends that argument beyond interface design. Creative tools should develop judgment, he argues. A novice may be able to request a dramatic film shot without understanding how framing, timing, or depth of field changes its emotional effect. Vocabulary and feedback can expose those relationships, helping the person understand why a choice works and make better decisions over time.
His open-source Radiant shader collection provides a concrete example of this approach. It began with a need for lightweight effects on his own website. He packaged the effects as standalone, dependency-free HTML files that people or coding agents could adapt.
Building a black-hole shader required sustained work on physics, appearance, performance, and interaction. Screenshots gave agents an incomplete understanding of an effect experienced over time, while perceptual shortcuts that worked for human viewers could confuse automated visual assessment. Repeated human inspection and adjustment remained essential.
Bakaus calls his approach amplified craft: tools can expand what a person can attempt, sharpen their taste, and help them express it. He treats taste as contextual, cultural, and shaped by experience. As a visual recipe spreads, a distinctive choice can become a thoughtless default. Renaissance Geek’s creative-work philosophy centers on the human judgment needed to carry a promising draft through the final stretch to something worth shipping.
Paul Bakaus explains how Impeccable grew from a design prompt into a harness extension, using independent critics, creative seeds, selective instructions, persistent context, scripts, hooks, and browser feedback. Making those mechanisms work across models requires more than portable prose—and some design judgments still need human eyes.
Separate visual judgment from deterministic defect detection. Independent reviewers prevent a linter’s issue count from becoming the whole assessment of a design.
Unexpected seeds change generation’s starting point. Discarding safe choices, generating a broad pool with independent ranking, and script-selected colors push beyond repeated defaults in different ways.
Scripts can return environment-specific next steps, while hooks validate edits automatically. Pre-tool hooks can block a write; post-tool feedback depends on the model repairing it. Ignore rules accommodate false positives.
Portability requires adapting execution behavior as well as text. Delegation permissions, question tools, task completion, hooks, and model tendencies affect whether the workflow works.
Evaluate software behavior, agent procedures, and individual rules separately. Aesthetic judges can reward the wrong preferences, so Bakaus uses them for a first pass and retains human evaluation.
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 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.
▶ Watch ↗