Paul Bakaus is the founder of Renaissance Geek, Inc., and the creator of Impeccable, a design toolkit that helps people steer AI coding agents toward deliberate, distinctive interfaces. His career spans web interaction libraries, browser development tools, and products for creators. Across that work, he asks how software can make creative production more accessible while helping people develop the judgment to do it well.
From jQuery UI to creator tools
Bakaus created jQuery UI in 2007, giving web developers reusable interactions and widgets such as drag-and-drop, sortable lists, and date pickers. In 2008, Liferay hired him to develop the library full time. The partnership connected open-source development with enterprise use: Liferay would 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. His career history describes joining Google in 2013, leading product and developer relations for Chrome DevTools, and later leading developer relations for AMP and Web Stories. His introduction to mobile-first Device Mode explained how a streamlined browser interface could make responsive design part of developers’ everyday workflow.
As Google’s head of creator relations, Bakaus founded Google for Creators. His work on visual publishing also included a clear position on the reader’s experience: Web Stories should deliver a complete story, rather than act as teasers that send readers elsewhere to finish it. He later became head of creators at Koji, working across community, partnerships, marketing, and business development. In March 2023, Spotter appointed him executive vice president of product and creator tools. There he led product, engineering, and design and built Spotter Studio, an AI-powered tool for YouTube creators.
Founding Renaissance Geek
After Spotter, Bakaus worked independently as a fractional chief product officer and startup advisor while developing open-source tools. Impeccable grew out of that period. In 2026, he announced Renaissance Geek with backing from a16z, making Impeccable the company’s first product.
How Impeccable helps people steer design
Shared design vocabulary: Impeccable addresses a problem Bakaus sees as designers move into code and engineers take on more design work: people need a shared design vocabulary to communicate intent. Adjusting every margin and padding value can demand too much low-level control, while asking an agent to design everything leaves important decisions unspecified. His Design at the Speed of Adjectives talk explores the space between those approaches. Before changing an interface, he wants people to establish its audience, desired feeling, references, and what it should never resemble.
Actionable commands: Commands such as “bolder,” “quieter,” and “distill” then turn that context into actionable direction. “Bolder” means strengthening hierarchy, scale, and typography within the project’s visual language; an unconstrained model might instead invent colors, gradients, or effects. “Harden” addresses whether the design works across devices, including responsiveness and performance. Impeccable combines this vocabulary with persistent project context, quality checks, and browser-based inspection of changes in the actual codebase. The words are useful because the tool explains what they should cause the agent to do.
Deliberate iteration: Bakaus maps those interventions onto the design workflow: shaping an initial direction, crafting and iterating, hardening and polishing, and bringing the result back into the design system. He argues that effective design requires repeated choices informed by users and collaborators. Removing familiar AI styling habits is only a starting point; a competent page can still feel empty when nobody has decided what it should communicate. He explicitly rejects automatic operation as Impeccable’s purpose. The tool is meant to help people steer and refine their work.
Creative tools that develop judgment
That position extends to his critique of “Cursor for X” products. Creative tools should develop judgment, he argues. A novice may be able to request a dramatic film shot without understanding framing, pacing, or 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 gives that argument a concrete test. It began with a need for lightweight effects on his own website, packaged as standalone, dependency-free HTML files that people or coding agents could adapt. His account of building a black-hole shader describes repeated work on physics, appearance, performance, and interaction. Screenshots cannot fully convey how a complex effect feels over time, and perceptual tricks that work for human viewers can confuse automated visual assessment. In his talk, he describes using Impeccable’s experimental “overdrive” command to push the effect further, while making clear that the shader required sustained iteration.
Bakaus calls his approach amplified craft: tools can sharpen a person’s taste and help express it. He treats taste as contextual, cultural, and shaped by experience; as a visual recipe spreads, a distinctive choice can become a default. Renaissance Geek’s creative-work philosophy puts human judgment at the center of refinement, particularly the final stretch from a workable draft 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 ↗