A design operating system for coding agents working on frontend interfaces such as websites, dashboards, SaaS products, and mobile screens. It provides commands and separate files for business requirements, visual rules, planning, critique, refinement, and quality checks.

Use it to design, redesign, critique, audit, polish, animate, or harden an interface. It helps create and maintain PRODUCT.md and DESIGN.md while applying the defined surface and visual rules.

It gives interface work a shared vocabulary and separates what a product must do from how it should look. Its craft checks target repetitive generated patterns such as generic fonts, gradients, cards, and icon tiles.

impeccable — Skill for Claude Code by oyi77/1ai-skills

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add oyi77/1ai-skills --skill impeccable

Clone the repo

git clone --depth 1 https://github.com/oyi77/1ai-skills

Made for: Claude Code.

Or install 1ai-skills, the plugin that ships this one along with the rest of its 216 skills, 4 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/oyi77/1ai-skills/impeccable/github.svg)](https://agentmods.dev/skills/oyi77/1ai-skills/impeccable)

Your own site

<a href="https://agentmods.dev/skills/oyi77/1ai-skills/impeccable"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/impeccable/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/oyi77/1ai-skills/impeccable"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/impeccable.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,151 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00083	$0.04151
Opus 5.5	$0.00033	$0.01660
Sonnet 5.5	$0.00017	$0.00830
Haiku 4.5	$0.00008	$0.00415

Measured today against content hash 15d1337ccd8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

impeccable scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

content/impeccable/SKILL.md · 298 lines

How it starts

The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Impeccable

A comprehensive design operating system and language for AI coding agents based on pbakaus/impeccable. Provides a structured 24-verb design vocabulary, dual-truth artifact separation (PRODUCT.md for business truth, DESIGN.md for visual truth), 4 surface archetypes (Persuade, Operate, Read, Experience), and a deterministic Craft Floor that eliminates generic AI slop, cards-inside-cards, unearned gradients, and un-tinted grays.

Overview

Most AI models were trained on the same corporate SaaS templates, resulting in repetitive failure modes: Inter for every font, saturated purple-to-cyan gradients, centered three-card hero sections, gray text on colored backgrounds, and rounded-square icon tiles above every heading.

impeccable breaks this convergence by introducing:

Durable Context Separation: Captures durable audience, purpose, and constraints in PRODUCT.md, while isolating visual rules, tokens, and font pairings in DESIGN.md.
24 Actionable Commands: Structured verbs covering planning (shape, init), creation (document, extract), evaluation (critique, audit), refinement (polish, bolder, quieter, distill, harden), and enhancement (animate, colorize, typeset, layout, delight).
4 Surface Modes: Tailors visual ambition to the user's intent—Persuade (marketing/landing), Operate (dense web apps/dashboards), Read (documentation/articles), and Experience (portfolios/showcases).
The Craft Floor: Strict mechanical invariants enforced before any code is committed.

[Phase 1: Init / Context] ──────► [Phase 2: Surface Mode & Shape]
   │ (PRODUCT.md)                         │ (Persuade / Operate / Read / Experience)
   ▼                                      ▼
[Phase 4: Floor & Polish] ◄───── [Phase 3: Code & Tokens (DESIGN.md)]
   │ (Contrast, Spacing, States)
   ▼
[Shipped Production Interface]

When to Use

When building or redesigning websites, web applications, landing pages, dashboards, or mobile interfaces.
When shaping UX/UI requirements before writing frontend implementation code (/impeccable shape).
When conducting UX critique reviews on hierarchy, cognitive load, and emotional resonance (/impeccable critique).
When executing technical quality audits for accessibility, performance, and responsive behavior (/impeccable audit).
When performing a final polish pass to eliminate visual bugs and establish shipping readiness (/impeccable polish).
When toning down aggressive designs (/impeccable quieter) or amplifying bland, timid layouts (/impeccable bolder).
When hardening error states, empty states, input validations, and overflow edge cases (/impeccable harden).
When establishing or reverse-engineering design tokens and CSS custom properties into a canonical DESIGN.md.

Read the full file on GitHub · 298 lines

Files

What ships with it

35 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today First seen · 298 lines · 83 tokens per session scan A 15d1337ccd8a

Subscribe to this mod's changes

impeccable is a skill published in the GitHub repository oyi77/1ai-skills (17 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 4,151 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-26.

CSS and styling Design and UX Frontend agent anti-slop audit content critique design-system impeccable polish ui ux

taste

Anti-slop frontend engineering directive and design taste system. Enforces brief inference, dynamic design dials, absolute prohibition of AI visual tells, and 100% full-output completion.

jxoesneon/Ciel · 38 tokens

design-system

Document and define UI design system tokens, components, and guidelines.

furkangonel/cowrangler · 16 tokens

impeccable

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…

martineserios/thebrana · 189 tokens

design

Use when the user wants the visual/experiential design of a product done systematically — a design system, a screen, a landing page, or a visual identity — grounded in researched real-world prior art and free of AI slop. Establishes/extends the design system, invokes the matching local taste skill, dispatches the…

jeremylongshore/tons-of-skills-marketplace · 126 tokens

design

Use when designing, redesigning, restyling or reviewing a web page or app screen (landing, product site, portfolio, dashboard, docs) or when a UI looks generic or AI-made. Deals a researched direction, takes the idea from the subject, uses real pictures, proves it in a browser. NOT the words (landing-copy), NOT…

ericrisco/rsc-harness · 79 tokens

vois-tokens

Rules and patterns for building UI with shadcn/ui, Tailwind v4 or StyleX, and Motion against a Vois design token set. Use when building components, pages, or any UI that should conform to the workspace design system. Covers spacing, typography, color tokens, component architecture, animation, accessibility, and modern…

ommakes/Skills · 77 tokens

impeccable

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Impeccable

Overview

When to Use

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

taste

design-system

impeccable

design

design

vois-tokens