You built it
with AI. Now
make it look
shipped.
You already build and launch web apps with AI. impeccable is the free tool that gives your agent a real designer's vocabulary, so what you ship stops looking like a language model made it.
Same brief. Two agents.
Neither screen below is hand-tuned. Both came straight out of an AI agent. The only variable is whether it had impeccable loaded.
Unlock Your Potential
Seamlessly leverage cutting-edge solutions to elevate your workflow.
The parts a rush leaves behind.
A quarterly for the people who actually finish the last ten percent, where the difference lives.
The curriculum ships the app. This ships the finish.
AI SaaS Mastery already hands you the stack: Claude Code, VS Code, Node.js, Git, and the workflow to launch without writing every line yourself. impeccable slots in right where the front end gets built. You tell your agent what good looks like in plain words, and it stops shipping the generic AI page every other launch is shipping.
A designer's vocabulary, handed to the machine.
Your agent can write the code. What it can't do by default is judge it. impeccable is a set of design commands and the taste behind them: shape, audit, polish, bolder, quieter, colorize, animate. You say what you want, and it knows the moves a good designer would make.
"Make this bolder." "This feels like AI made it." "Quiet it down." The tool carries the vocabulary, so you don't spell out every hex value and margin.
Not mockups or starting points. Production front end that is responsive, accessible, on-brand, and free of the tells that mark a page as machine-made.
Same tool, both ways you work.
There aren't two versions. The terminal and the VS Code way you already build in the course are the same install. Pick the line that matches your setup and paste it.
The one-line plugin install. Restart your session and the design commands are live.
/plugin marketplace add pbakaus/impeccableWorks the same in the VS Code terminal and in Codex. One command, every agent.
npx impeccable installKeep it current later with npx impeccable update. That's the whole cost of entry. It's free, and it stays free.
Installing it is step one. Running it like we do is the rest.
The tool is Paul's, and it's free. This is ours: the full playbook for running it on every build. No email wall for the Mastermind. It's all right here, so bookmark this page.
The before-and-after-build workflow
Most people run a design tool once, at the end, to clean up a mess. That's backwards. Run impeccable twice: once to point the build in the right direction, once to catch what slipped through.
Name the direction
Start with shape. Decide the aesthetic on purpose (the lane, the type, the color) before a line of code exists. A design point of view is a pre-decision, not something you stumble into after shipping.
Let it ship real code
Use craft for a full feature. It reads your existing brand and components, writes production code, and iterates against a real screenshot instead of a guess.
Audit, polish, then look
Run audit, then polish. Then screenshot it and actually look, desktop and mobile. A green build is not a look. Ask it straight: award gallery, or template?
The command map
Every command, and the plain thing you'd say out loud that should make you reach for it. You talk like a person; it makes the designer's move.
Build and discover
shape"I'm not sure what this should look like yet."craft"Build this feature, end to end."init"Set this project up for impeccable." (once)Review
audit"Check accessibility, performance, anti-patterns."critique"Give me a real design critique."Amplify and tune
bolder"This looks bland and too safe."quieter"Too loud. Calm it down."colorize"The color feels off or generic."typeset"Fix the type and the scale."layout"The spacing and composition are off."animate"Add purposeful motion."delight"Make it feel considered and alive."overdrive"Push something technically extraordinary."Adapt and clarify
adapt"Make it work on mobile, tablet, print."clarify"The copy or error messages are confusing."distill"Too much here. Simplify it."Harden and ship
polish"Final pass before this ships."harden"Handle the edge cases and empty states."optimize"It's slow. Tighten it."onboard"Improve the first-run and empty state."System
document"Capture the current design system as a spec."extract"Pull repeated patterns into reusable tokens."live"Let me try variants live in the browser."The Anti-Slop Copy Codex
impeccable fixes the design. This fixes the words on it. Paste this into your agent and hold every line of copy to it, because a beautiful page with robot copy still reads as robot.
The rules
No em dashes. Use a hyphen, a colon, a period, or parentheses. The long dash is the loudest tell in AI punctuation.
No question-then-punch. "The result? A transformation." "The best part? It's free." Real people don't write like that. Say it straight.
Contractions on. "It's," "you're," "don't." Write it the way you'd actually say it.
Be specific, not superlative. Name the market, say what actually happens, and prove it. Adjectives that prove nothing get cut.
The one test, every time: would a real person say this out loud? If no, rewrite it.
Delete on sight
Catch one, delete it, rewrite like a human. That's the whole discipline.
Your next build can look like you meant it.
Paste one line, restart your session, and tell your agent to make it impeccable.