A guide and toolkit for designing, reviewing, and improving frontend interfaces such as websites, dashboards, forms, and app screens. Frontend means the part of software people see and use.

Gathering product and design context, then building or refining layouts, components, interactions, colors, typography, and empty states.

It helps turn an existing or rough interface into a clearer, more consistent, accessible, and polished product design.

impeccable — Skill by waynesutton

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.

agentmods

npx agentmods add skills/waynesutton/markdown-site/impeccable

Any agent

npx skills add waynesutton/markdown-site --skill impeccable

Clone the repo

git clone --depth 1 https://github.com/waynesutton/markdown-site

Made for: Claude Code, Codex.

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00189	$0.02586
Opus 5	$0.00095	$0.01293
Sonnet 5	$0.00038	$0.00517
Haiku 4.5	$0.00019	$0.00259

Measured 3d ago against content hash 383a0988b45c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d ago.

The scan reads SKILL.md. This mod also ships 14 executable files (scripts/cleanup-deprecated.mjs, scripts/design-parser.mjs, scripts/detect-csp.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

Copies of this mod

6 near-identical copies found in the catalogue:

impeccable — 88% identical, 63 lines differ
impeccable — 86% identical, 75 lines differ
impeccable — 81% identical, 34 lines differ
impeccable — 81% identical, 77 lines differ
impeccable — 81% identical, 87 lines differ
impeccable — 78% identical, 77 lines differ

.agents/skills/impeccable/SKILL.md · 152 lines

How it starts

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

Designs and iterates production-grade frontend interfaces. Real working code, committed design choices, exceptional craft.

Setup (non-optional)

Two steps before any design work. Both are required. Skipping either produces generic output that ignores the project.

1. Context gathering

Two files at the project root, case-insensitive:

PRODUCT.md — required. Users, brand, tone, anti-references, strategic principles.
DESIGN.md — optional, strongly recommended. Colors, typography, elevation, components.

Load both in one call:

node .agents/skills/impeccable/scripts/load-context.mjs

Consume the full JSON output. Never pipe through head, tail, grep, or jq.

If the output is already in this session's conversation history, don't re-run. Exceptions requiring a fresh load: you just ran $impeccable teach or $impeccable document (they rewrite the files), or the user manually edited one.

$impeccable live already warms context via live.mjs — if you've run live.mjs, don't also run load-context.mjs this session.

If PRODUCT.md is missing, empty, or placeholder ([TODO] markers, <200 chars): run $impeccable teach, then resume the user's original task with the fresh context.

If DESIGN.md is missing: nudge once per session ("Run $impeccable document for more on-brand output"), then proceed.

2. Register

Every design task is brand (marketing, landing, campaign, long-form content, portfolio — design IS the product) or product (app UI, admin, dashboard, tool — design SERVES the product).

Identify before designing. Priority: (1) cue in the task itself ("landing page" vs "dashboard"); (2) the surface in focus (the page, file, or route being worked on); (3) register field in PRODUCT.md. First match wins.

If PRODUCT.md lacks the register field (legacy), infer it once from its "Users" and "Product Purpose" sections, then cache the inferred value for the session. Suggest the user run $impeccable teach to add the field explicitly.

Read the full file on GitHub · 152 lines

Files

What ships with it

51 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.

3d ago First seen · 152 lines · 189 tokens per session scan A 383a0988b45c

Subscribe to this mod's changes

impeccable is a skill published in the GitHub repository waynesutton/markdown-site (631 stars, last pushed 3mo ago), licensed MIT. It adds 189 tokens to every session and 2,586 once invoked, about $0.0009 per session on Opus 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-08-30.

CSS and styling Design and UX Frontend cms convex markdown open-source sync

Shade tokens, not hex

Use Shade semantic tokens (bg-background, text-foreground, border-border-default, bg-surface-elevated) — never hex, hsl(), or bg-gray-200-style raw palette utilities for UI chrome. Trigger when editing TSX/CSS in Shade-consuming apps.

TryGhost/Ghost · 61 tokens

Shade dropdown surface contract

DropdownMenu, Select, and Popover share one visual recipe (bg-surface-elevated-2 + border-border/60 dark:border-border/30 + shadow-md). Change them together. Trigger when editing any of those three Shade files.

TryGhost/Ghost · 54 tokens

Shade inputSurface recipe

Use the inputSurface() recipe for form-control chrome (border, background, radius, focus ring, invalid state) — don't roll your own. Trigger when editing form-control-shaped files in Shade.

TryGhost/Ghost · 44 tokens

Shade ShadCN install

Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.

TryGhost/Ghost · 72 tokens

Shade use primitives

Replace bare divs that only carry flex/grid/gap utilities with Shade primitives (Stack, Inline, Box, Grid, Container, Text). Use semantic gap="md" instead of gap-4. Trigger when editing TSX in Shade-consuming apps.