How impeccable.style sharpened the way I ship Assurcast

I run Assurcast, a curated news and jobs platform for internal audit professionals. For the past few weeks my design and front-end work has been guided by an unusual collaborator: an open-source Claude Code agent skill called impeccable.style, built by Paul Bakaus (pbakaus on GitHub).

The idea is simple. You teach the agent your product (PRODUCT.md) and your design system (DESIGN.md), and it gains opinionated views on craft. Color strategy, typography, spacing rhythm, anti-patterns to refuse. Then you can ask for a critique, a reshape, a polish pass, or hand it a brief and let it work. It runs locally in my Claude Code session against my actual repo. No SaaS, no dashboard, just your code and Claude.

What changed for me is how decisions get made. Before impeccable, I pushed features and tweaked chrome ad hoc (without a design background, yikes!). With it, every UI change starts with a documented decision in my kanban board: a trade-off table, a chosen direction, a rationale. We landed more than a dozen decisions in a few hours. A Restrained color strategy refresh on the subscribe widget. A dual-primary email-and-RSS pattern. Real "Curated" date stamps on every story. Typographic de-emphasis on the navbar. A mobile sticky bottom bar that finally surfaces subscribe to readers on phones. A 44pt touch-target floor across public, account, and admin surfaces. A source-byline emphasis that lifts the publisher domain above each story title, HN-style. Hacker News Style

The most useful moment, though, was when I pushed back. impeccable.style flagged "card monoculture" as a P1 finding (ten identical story cards on the homepage, no hierarchy, no hero). The recommended fix was to strip cards entirely and replace them with ruled separators and typographic hierarchy. I read the critique twice and disagreed. Assurcast is a wall of posts. Paradigm 2: Twitter, Hacker News, Substack, where uniformity is the social contract. The agent applied an editorial-front-page rule (NYT, Bloomberg, FT) to a social-feed product. I rejected the P1, documented why, and filed four softer enhancements that improve scanability without breaking the uniform-feed shape. The right answer wasn't more chrome. It was a closer reading of the product.

That's what makes the tool useful. It's not a stylebot generating mockups. It's a collaborator with strong views you can argue with. When it's right, you ship faster. When it's wrong, you sharpen your own thinking by explaining why. Either way, our kanban process accumulates a record of decisions you can defend a year from now. If you're shipping a product alone or in a small team, run impeccable.style on it. Bring something specific to argue about. See where it lands you.