Impeccable gives coding agents design vocabulary such as "bolder," "quieter," and "distill," with each command defined for the project's context.
2
Paul Bakaus argues that design needs context, iteration, and human decisions, so it cannot be reliably produced in one prompt.
3
Impeccable will not get an automatic mode because its purpose is to let people steer the result rather than hand design decisions to an agent.
Summary
Paul Bakaus presents Impeccable, a design skill that runs on top of coding harnesses such as Claude Code, GitHub Copilot, Cursor, and Codex. He compares the same design task with and without the skill, then explains why current AI-generated pages often share the same visual patterns. Purple gradients have given way to what he calls "Claude beige," with Instrument Serif and italics. Bakaus argues that design is context-rich, iterative, and shaped by people with different opinions, so a single prompt cannot make the right decisions. Impeccable gives users a vocabulary for steering an agent, including commands such as "bolder," "quieter," "distill," "polish," "denser," and "harden." The words only work when the tool defines what they mean for a particular project. He maps these commands onto the messy design workflow and rejects requests for an automatic mode. The tool is meant to sharpen a person's taste and craft, not replace their decisions.
Impeccable adds a design skill to coding harnesses
Bakaus describes Impeccable as a design skill that turns a coding harness into a better designer and, ideally, makes the user better at design too. It works across tools including Claude Code, GitHub Copilot, Cursor, and Codex. He demonstrates the difference by asking the same project to make a workflow section "bolder" with and without Impeccable. The result is not perfect, since the generated page can still contain familiar AI patterns such as numbered sections, but he says the version using the skill is bolder.
Bakaus sees engineers moving into design and designers moving into code. He says Impeccable gives people a shared design language, while the older sequence of product work, design, handoff, critique, and engineering is becoming less real. He contrasts direct manipulation in tools such as Figma or Webflow with fully agentic instructions such as asking an agent to design or build a page. Direct manipulation can operate at too low a level, while fully agentic work removes too much control. He is looking for a middle ground that puts the human in the loop at the right point.
Bakaus says the obvious purple gradients associated with earlier AI-generated pages have largely disappeared from frontier models. Their replacement is what he calls "Claude beige": beige palettes, Instrument Serif fonts, and italics. He does not call these choices inherently bad. The problem is that pages produced by the same model begin to look alike. He calls this "algorithmic unilo" and treats it as another form of design slop. The visual signs keep changing, so avoiding one familiar pattern does not solve the underlying problem.
Bakaus's first major claim is that people cannot currently oneshot design, and perhaps never will. Effective design needs context about the goal, the audience, the product, and the emotional territory. It also needs iteration and room for different people to have different opinions. Before making a page, someone has to decide what it should feel like, what it should never feel like, and what it references. A quickly vibe-coded page can be competent while still being empty because nobody made those decisions.
Adjectives become controls when the project defines them
Impeccable lets users steer an agent with words such as "bolder," "quieter," "distill," "polish," "denser," and "harden." An adjective by itself is only a nicer prompt because it can mean many things in the model's training data. In Bakaus's example, "bolder" does not mean adding gradients, glass, or neon. It means using hierarchy, scale, and decisive type to raise attention without breaking the design system. The command is useful because it translates a familiar design word into decisions that fit the current project.
A useful command has to resist generic design habits
Bakaus says the file loaded by Impeccable gives each command a project-specific meaning. When someone asks a general model to make a page bolder, the model may invent colors or gradients based on its own reference points. Impeccable instead defines bolder as changes to hierarchy, scale, and type. It even tells the agent that if a user cannot tell the result was made by AI, the agent has done a better job. The goal is to increase emphasis without producing a familiar AI visual signature.
Bakaus maps the user's design workflow before deciding where the tool should intervene. He describes stages that include initialization, shaping, crafting, iteration, hardening, polishing, and returning changes to the design system. The workflow is not linear and can involve several people. He uses this map to place different commands along the process. One example is "overdrive," which pushes a design beyond normal limits. He was unsure about shipping it, but the community enjoyed using it to make an already elaborate shader more excessive.
Bakaus says people ask him at least once a week for an automatic mode that chooses commands and does all the work. He rejects that request because the tool's purpose is to let users decide what they want. He says there will be no automatic mode and plans to close a pull request that adds one. He believes tools can amplify craft and help people sharpen their taste, but taste cannot be lab-grown. It is contextual and cultural, shaped by experience and personal scars.
