# AI use cases for Impeccable (pbakaus/impeccable) Repo: [pbakaus/impeccable](https://github.com/pbakaus/impeccable) | Use cases: 3 | Page: https://dedupedai.com/use-cases/pbakaus-impeccable/ Impeccable is design guidance for AI coding agents: one skill, 24 commands such as polish, audit, critique, distill, animate, bolder and quieter, live browser iteration, and 62 deterministic detector rules for AI-generated frontend design. It starts with /impeccable init, which records product truth in PRODUCT.md, and it targets the usual AI tells: Inter everywhere, purple-to-blue gradients, cards nested in cards and gray text on colored backgrounds. The detector rules run in the CLI and a browser extension with no LLM and no API key. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Stop your AI-built UI looking like every other SaaS template: https://dedupedai.com/use-cases/pbakaus-impeccable/stop-your-ai-ui-looking-generic/ - Audit a page for AI design tells and fix them: https://dedupedai.com/use-cases/pbakaus-impeccable/audit-a-page-for-ai-design-tells/ - Share one Impeccable setup across your team with Git: https://dedupedai.com/use-cases/pbakaus-impeccable/share-impeccable-across-a-team-with-git/ ## How to stop your AI-built UI looking like every other SaaS template with Impeccable Repo: [pbakaus/impeccable](https://github.com/pbakaus/impeccable) | Difficulty: Beginner | Time: 20 minutes | Basis: From the README Install Impeccable, record what the product is, and let the agent design against that instead of defaults. **Who it is for:** A founder whose agent keeps shipping purple gradients and nested cards. **The problem:** AI coding agents fall back to the same handful of design tells on every project. **The outcome:** A PRODUCT.md with audience, purpose and voice, and design work that follows it. ### Steps 1. From your project root run `npx impeccable install` 2. Inside your AI coding tool run `/impeccable init` to write PRODUCT.md 3. Ask for a redesign, for example `/impeccable redo this hero section` ### Prompt to paste into your agent ```text Install pbakaus/impeccable in this project, run /impeccable init with me (ask me about audience and voice), then redo the hero section and list which generic AI tells you removed. ``` ### Caveat Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/pbakaus-impeccable/stop-your-ai-ui-looking-generic/ ## How to audit a page for AI design tells and fix them with Impeccable Repo: [pbakaus/impeccable](https://github.com/pbakaus/impeccable) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README Run audit or critique on a section, then polish before shipping. **Who it is for:** Someone about to launch a landing page built with an agent. **The problem:** It is hard to see what makes a page look machine-made. **The outcome:** A list of design problems on the page and a polished version. ### Steps 1. Run `/impeccable audit blog` or `/impeccable critique landing` on the area you care about 2. Read the findings from the detector rules and the critique 3. Run `/impeccable polish settings` (or your page) as the final pass 4. Use `/impeccable harden checkout` to add error handling and edge cases ### Prompt to paste into your agent ```text Run pbakaus/impeccable's audit and critique on my , fix the top five findings, then run polish and show me before and after screenshots. ``` ### Caveat Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/pbakaus-impeccable/audit-a-page-for-ai-design-tells/ ## How to share one Impeccable setup across your team with Git with Impeccable Repo: [pbakaus/impeccable](https://github.com/pbakaus/impeccable) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Add Impeccable as a submodule and link it to each teammate's tools so everyone gets the same design rules. **Who it is for:** A team where several people build UI with different agents. **The problem:** Each developer's agent follows different design habits. **The outcome:** One versioned copy of the design skill linked into Claude and Cursor for the whole repo. ### Steps 1. Run `git submodule add https://github.com/pbakaus/impeccable .impeccable` 2. Link it: `npx impeccable link --source=.impeccable --providers=claude,cursor` 3. Commit the .gitmodules, .impeccable, .claude and .cursor changes 4. Update later with `git submodule update --remote .impeccable` and link again ### Prompt to paste into your agent ```text Add pbakaus/impeccable to this repo as a Git submodule, link it for Claude and Cursor, commit it, and write a short CONTRIBUTING note telling teammates how to update it. ``` ### Caveat Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/pbakaus-impeccable/share-impeccable-across-a-team-with-git/