Paul Bakaus (@pbakaus) header
Paul Bakaus (@pbakaus) profile picture

Renaissance geek (creativity × culture × tech). Product engineer before it was cool. Made @impeccable_ai, @radiant_shaders, @jqueryui | x-@google, @zynga

San Francisco, CA
Joined February 2008
Photo by Paul Bakaus (@pbakaus)Photo by Paul Bakaus (@pbakaus)Photo by Paul Bakaus (@pbakaus)Photo by Paul Bakaus (@pbakaus)Photo by Paul Bakaus (@pbakaus)Photo by Paul Bakaus (@pbakaus)Photo by Paul Bakaus (@pbakaus)Photo by Paul Bakaus (@pbakaus)Photo by Paul Bakaus (@pbakaus)Photo by Paul Bakaus (@pbakaus)
Paul Bakaus retweeted
The cure to burnout is not rest, it's momentum. Solo Talk is back: Six solo founders touched on this in six different ways. I rewatched their episodes and pulled a clip from each that deserved more commentary. 00:47 Make things for the love of the game (@DhravyaShah) 03:55 Company-building is the closest thing to art (@FDavidsonT) 06:31 The ten-year test for picking a problem (@thaiscbranco_) 10:29 What two years of chewing glass taught him (@Altimor) 14:25 Do the work you avoid, first (@clairevo) 17:51 Don't hire yourself out of building (@pbakaus)
12
8
2
79
7,717
Paul Bakaus retweeted
You asked for better. Your AI added a border. You asked again. It added a shadow. We've all been there. Video by @Abdul_wahab_one 🫡
12
15
3
600
76,055
Paul Bakaus retweeted
deep in your craft, curious about everything, always making things happen? we’re hiring renaissance geeks to build impeccable + automated design reviews: • frontend • backend / ai & evals • community & advocacy • forward deployed renaissance-geek.ai/careers
9
5
1
37
6,967
Paul Bakaus retweeted
Running Impeccable in Codex / ChatGPT? Impeccable *won't* find slop reliably without hooks, so check your settings and make sure they're trusted for each project. We just updated our install steps with better info on this: impeccable.style/#downloads
2
2
26
3,926
Paul Bakaus retweeted
BREAKING: @OpenAI just dropped GPT-6 Sol. It’s my new daily driver in Codex: not quite Astra, but close enough for much of my everyday work, faster, and 50% cheaper than 5.6 Sol. We tested it across the work we actually do at @every and ran it head to head versus Opus 5.5. Here’s my vibe check: • Writing: On a paragraph-writing task drawn from my real work, Sol scored close to Astra, which is still my top model for writing. It writes clean, minimal prose and puts the important idea first. Opus 5.5 is pleasant to work with, but its drafts still tend to bury the point. • Computer use: If you love Astra’s computer use, you’ll like Sol. An earlier Sol preview matched Astra on 17 of 18 attempts across six of our simpler Hands tasks, at a much lower token price. • Coding: Sol improves on GPT-5.6—including better Ruby code in @kieranklaassen tests—but Opus 5.5 has the higher ceiling for long, autonomous builds. One frustration: Codex’s new security classifier repeatedly stopped work we’d already authorized to ask for approval. That’s friction from the classifier, not necessarily a limitation of Sol, but it made long runs harder to leave alone. Overall: Sol feels like an S-class iPhone release: It will give you much of Astra’s power at about a fifth of Astra’s price. Opus 5.5 is the bigger surprise. In some of our tests, it matches or even beats Fable 5.1 on many tasks while also being cheaper than Opus 5. A few people on our team who were Codex converts have started to wobble with Opus 5.5. If you’re already in the Claude ecosystem you’re going to love this model. If you’re a Codex user, it’s worth a look especially for your top-end coding tasks. You’ll like Sol 6 if you spend your day in Codex reading, writing, and getting things done. It’s fast, much cheaper than Astra, and it’s the model I keep reaching for. You’ll like Opus 5.5 if you want to hand an agent a hard coding or visual project and see how far it can take it. Its best work went further than Sol’s in our tests—enough to pull some of our team back toward Claude. You can go deeper on all of our evals including each real-world task and how they're scored at the links below: Writing: checks.every.to/p/dans-edito… Knowledge work: checks.every.to/p/mikes-chec… Reading: checks.every.to/p/dans-readi… Full vibe checks on @every coming soon!
Please welcome GPT-6 Sol and GPT-6 Luna to the GPT-6 universe. GPT-6 Sol and Luna build on the advances behind GPT-6 Astra, bringing much of its strengths into faster and more affordable models to support work at scale. We’ve also made caching and inference more efficient, and we’re passing the savings directly to you: 50% lower API prices for Sol and Luna compared with GPT‑5.6 promotional pricing.
46
30
11
628
141,172
Paul Bakaus retweeted
Make this bolder means something different depending on who's typing it, even with the same model and the same harness. @pbakaus built "Design at the Speed of Adjectives" around that gap, and it's on @aiDotEngineer's YouTube. Paul is Founder at Renaissance Geek, Inc. The talk works through a vocabulary of adjectives and verbs, bolder, quieter, distill, polish, harden, meant to give a coding agent enough context to steer design work instead of guessing. - You cannot one-shot design. Paul's first hot take: good design needs context and multiple passes, not a single prompt, even for a solo founder. - An adjective with nothing behind it is just a nicer prompt. In Impeccable, bolder doesn't mean new gradients or glass, it means hierarchy, scale, and decisive type that don't break the existing design system. - The test for whether it worked. He holds the tool to a plain standard: show someone your work and say you made it bolder. If they believe you, you failed. - Harden covers the boring failure modes. It's the command for making sure a design holds up across devices and performance, not another layer of polish. - No auto mode, on purpose. People keep asking for Impeccable to just decide the commands itself. Paul is closing the pull request for that. The tool exists to give a human a lever, not to remove them from the loop. - Design's workflow isn't linear. He mapped it in stages, initialization, shaping, crafting and iterating, hardening and polishing, then back into the design system. - Taste can be amplified, not lab-grown. His closing distinction: tools can sharpen taste, but taste itself stays contextual and scarce, not something a model can manufacture. I'm working through the published talks from AI Engineer World's Fair sharing summaries and takeaways. Follow for more!
1
1
3
450
Paul Bakaus retweeted
Replying to @pbakaus
@pbakaus keeps delivering and expanding @impeccable_ai's reach (and value). This time to PRs.
engineering is moving 10x faster. design review hasn't caught up. introducing Impeccable ..for PRs! a design review agent that simulates your users, uses your app, finds friction & slop. Impeccable’s design judgment in every PR. reply if you want in on the closed beta 👀
1
1
1
876
Paul Bakaus retweeted
Product people of SF! On Sep 22 we're hosting an event with the incredible @pbakaus (Founder of @impeccable_ai) and @moeamaya (Founder of @operatecrm). If you care about creativity and craft and want to hang out with some of the best design talent in the Bay Area, don’t miss this one! luma.com/ys9d7lpl
4
3
13
4,727
Paul Bakaus retweeted
oh hi @NousResearch! if you missed it in the long 4.1 changelog: Impeccable is now officially supported in Hermes Agent (and thx to @Teknium for helping update our docs via a PR!)
2
2
33
4,833
Paul Bakaus retweeted
Welcoming Paul Bakaus @pbakaus, founder of Renaissance Geek @impeccable_ai, and a product engineer before it was cool. Speaking at Abstract Conference. Sept 2nd abstract.convex.dev
2
18
2,769
Paul Bakaus retweeted
In Defense of Writing. A disturbing trend I see emerging is people lazily generating longer form content from bullet points or dictation they give to an LLM, and then passing it off as their own. Beyond the obvious breach of trust and social expectation when doing this, there are several more nuanced but equally insidious problems with doing this. First, writing is thinking. If you aren't taking the time to write, edit, rework, reshape, and play with your words, you're shortcutting a key aspect of refining an thought. You rob yourself of this opportunity if you just skip to the end. I have yet to read anything generated that even comes close to the clarity and impact of a well-written piece. Second, respect. Very few people will tell you this to your face, but as soon as they read something 'from you' that has all the tell-tale signs of AI slop, their respect (and trust) for you drops. What you are communicating is that you don't take the time and effort to do things properly, or at least entirely honestly. This is damaging in way many don't realize. I instantly discount anything I read as soon as I recognize it as AI slop. Third, and I think most important, you are training yourself to take the easy way out. I think this is different than 'working smart'. It's intellectual laziness, effectively choosing cheap calories rather than a nourishing meal, even if it takes longer to prepare. That effort is where good things, as well as your own growth, come from. Many days on here I feel like the last man alive who wants to actually read what you wrote. It's entirely possible that this is a losing battle and the nature of media and medium is trending in an irreversible way. But I really hope it's not. I'll leave you with a philosophical question: every social media platform is going to great lengths to label AI-generated images and video. Why not writing, as well?
69
104
32
956
78,824
Paul Bakaus retweeted
Small follow-up for Codex users: If your design hooks aren't firing in Codex, grab v3.9.1 (just published): it fixes the plugin hook manifest Codex's parser was rejecting (the prev fix was only partially complete). Install / update: npx impeccable install github.com/pbakaus/impeccabl…
Impeccable v3.9.0 + CLI v3.2.0 are out. Skill: • Now avoids and corrects GPT-style 'grid/mesh' backgrounds • /impeccable bolder stays inside your design system • /impeccable critique uses sub-agents effectively to debias on more harnesses • Bundled helpers run under strict-permission harnesses • Codex hook manifest fix CLI (--gpt): • New slop detector rule: grid-line backgrounds • First install preserves external skills symlinks install: npx impeccable install update: npx impeccable update
1
24
8,281
one of the reasons to get into cinema (or the history of any art form) is to marvel at the physical lengths people used to go to to realize a vision. I think this will get harder and harder to understand in an AI “art-on-demand” culture. It won’t be intuitive how they did this
They showed us this sequence in my first year of film school and it was one of the first things I remember truly blowing my mind back then
22
3,299
14
29,637
491,723
Paul Bakaus retweeted
Using the /impeccable skill built into the GitHub Copilot app, @cassidoo gave her PocketCal app a design refresh! ✨ Enable in Settings > Experimental to try it out. gh.io/app?utm_source=social-…
24
33
3
372
79,130
Paul Bakaus retweeted
/impeccable is now available via experimental settings in the GitHub Copilot App! It breathes fresh life into design that would otherwise feel AI generated. Give it a try!
.@impeccable_ai earned its way to 40k+ stars on GitHub by delivering exceptional value. Today, we are making design and quality a built-in layer for all creators: Impeccable is now a built-in skill in the GitHub Copilot app. AI raised the floor. We’re here to help raise the ceiling.
8
23
3
188
27,984
Impeccable immediately leveled up my UIs. Its approach to skills has become my general template for custom skills in other domains. Strongly recommend you give it a try! Very excited for what @pbakaus is building.
2
2
11
2,416
RT @MTSlive: SITUATION EXPLAINED: What separates the people who get great output from AI from the people who get average output? We asked…
This quoted post is unavailable.
1
1,249
Paul Bakaus retweeted
Impeccable creator Paul Bakaus says AI should be cognitive delegation, not cognitive surrender: "Cognitive delegation is, I'm using Google Maps, and Google Maps tells me where I can go as quickly as possible." "But what if I let Google Maps decide where I want to go to? Now I kind of cognitive surrender to the application, and I think that's very true for LLMs if you're not careful." "You prompt something, and then it creates a beautiful plan, and then it's eight pages long. You're not going to read through that plan. You're going to scroll through that plan and skim it, and it's like, 'I guess the model knows what it's doing.'" "I think delegating to the model is great, but preserving that point of view, making sure that you're still the one driving is also really important." @pbakaus
28
40
13
339
80,260