In the wild west of AI-assisted frontend development, two heavyweight skills dominate the Claude Code ecosystem: Impeccable and Taste Skill. While both aim to banish the generic 'AI look' from generated interfaces, a recent head-to-head test by SkillGild exposes a fundamental divergence in philosophy. One prioritizes aesthetic restraint and speed; the other enforces a rigorous, truth-bound design language. The result? A threefold cost difference that buys you more than just pixels—it buys you accuracy.

The Test: One Brief, Two Philosophies

The experiment ran on October 9, 2026, using Claude Code 2.1.278 powered by Claude Opus 5. The prompt was identical for both agents: generate a landing page for 'Ledgerline,' a fictional bookkeeping app for freelance designers. The constraints were strict: no invented testimonials, no fake customer counts, and no hallucinated features. Taste Skill, authored by Leonxlnx and boasting 95.5k GitHub stars, took 7.1 minutes and cost $2.28. It produced a calm, near-monochrome page with an ink-blue accent. Impeccable, created by Paul Bakaus with 80.7k stars, took 23.8 minutes and cost $7.49. It delivered a bold 'Swiss departure board' concept using signal yellow and graphite.

Hallucination is the Real Bug

The most critical finding wasn't visual—it was factual. Taste Skill, despite its 'honest-tool' language, invented product details that weren't in the brief. It added a 'read-only bank link,' 'receipt capture,' and 'CSV exports.' It also claimed 'email support' and a '30-day export window' after cancellation. Impeccable, however, invented zero product facts. Its architecture forces a PRODUCT.md file that explicitly separates what the brief said from what it didn't, listing unknowns like 'which banks' or 'data export' as things that 'must not be invented.' For any real product launch, this distinction is not a preference; it is a legal and reputational necessity.

Speed vs. Substance

Taste Skill wins on efficiency and simplicity. It is a single 1,200-line SKILL.md file with no binary dependencies, making it easy to audit and tweak. It sets 'dials' for variance, motion, and density, and bans specific AI-design patterns like em dashes. Impeccable is a heavier engine: 24 commands, 40 playbooks, and an anti-pattern detector. It runs a context command to write product documentation before coding, then rolls a seeded concept. While Taste Skill missed its own pre-flight checks (allowing a 3-line headline and low-floating hero), Impeccable’s detector flagged 8 issues but maintained its own structural integrity. For a quick portfolio or a low-stakes landing page, Taste Skill’s $2.28 price tag is hard to beat.

Key Takeaways

  • Use Impeccable for truth: If your page makes claims about your product, Impeccable’s refusal to invent facts is worth the extra $5 and 17 minutes.
  • Use Taste Skill for speed: For portfolios, redesigns, or budgets under $5, Taste Skill delivers a clean, professional result in under 10 minutes.
  • Scope matters: Taste Skill explicitly excludes dashboards and complex app UIs. Impeccable’s four modes (persuade, operate, read, experience) handle these better.
  • Don't mix them: Their rules overlap and conflict. Pick one direction skill per page.
  • Fact-check everything: Even with Impeccable, put real product facts in your brief. The source notes that missing facts were the 'single biggest difference' between a shippable page and a rewrite.

The Bottom Line

Design agents are cheap, but wrong data is expensive. If you’re shipping a real product, pay the 'truth tax' for Impeccable. If you’re just vibing, Taste Skill is the efficient hacker’s choice.