Design knowledge as searchable local data: 79 styles, 192 palettes, 119 UX rules
Editor's takeIts sharpest self-description is that models can write CSS but lack a taste database. Ten rule categories are ordered by severity, with Accessibility and Touch & Interaction first as CRITICAL and Charts last — that ordering is the stance. The Design System Generator runs five parallel searches, and the repo states plainly: do not persist unverified output, so a generated design system has to be checked before it lands in your repo.
v2.13.0, MIT, 129k stars, site uupm.cc. Instead of lecturing the model it ships structured catalogues the agent queries before writing code: 79 UI styles, 192 palettes with reasoning, 74 type pairings, 119 UX rules, 105 icon suggestions, 17 GSAP presets, 25 chart types, 22 stacks and 34 landing-page patterns.
Taste Skill: 13 anti-slop frontend skills that turn AI tells into countable rules
Editor's takeThe lesson worth stealing is rules expressed as countable mechanical tests: eyebrow count ≤ ceil(sections/3), bento cells equal to content items, zero em-dashes on the page, palette families rotated across projects. Each one aims straight at the model repeating itself instead of stopping at an adjective. The repo is equally honest about its edges: v2 self-declares experimental and is still moving, §13 explicitly excludes dashboards, data tables, multi-step wizards, code editors and native mobile, and the only test in the repo guards the source-invocation semantics of the skill.sh shell helper rather than the design rules.
One MIT repo holding 13 skills: ten that output code and three that output reference images only, all installed into Claude Code / Codex / Cursor with a single npx skills add. The default design-taste-frontend v2 (experimental) is a 1,228-line SKILL.md: first the model must emit a one-line "design read", then it sets three dials (DESIGN_VARIANCE / MOTION_INTENSITY / VISUAL_DENSITY), then it implements against 14 chapters of hard rules - install the official package for corporate briefs, label aesthetic borrowings in comments, zero em-dashes anywhere on the page, eyebrow quota computed from section count, bento cells equal to content items, and finally a 50-plus box pre-flight check. The repo also ships research/laziness, a literature directory using controlled studies to explain why models cut output short.
anatomy: turn a technical concept into a real machine, a zero-dependency isometric figure skill with a 12-check geometry audit
Editor's takeWhat is most worth stealing is that it ships its own falsification tooling: twelve checks in kit/audit.mjs (clearances, solid clearances, terminals, loose ends, supports, folds, self-overlaps, crowding, stand-in shapes, wobble, seats, depth order) plus scripts/lines.mjs demanding 'line ends: 0', which turns 'looks fine' into countable failures. It also states outright that a stand-in shape that quiets the audit is itself a bug, and the coverage check exists to catch it. Aesthetics are numeric too: bevels 0.4-1.6, screw dots 0.4-0.55, the subject filling 55-65% of the card, a device ratio cap of 1.5, and a 3D bend bound of R ≥ 2r / sin²(e − θmax). CI rebuilds every example in both themes and requires an empty git diff, so kit compatibility is a machine guarantee. The limits are stated just as honestly: not a chart library (no axes or series), machines, instruments, tools and furniture only, 3D self-reported beta at roughly 20 fps for 380 parts, and one figure costs a long session.
A standard Agent Skill that makes Claude Code, OpenCode or Codex explain a technical idea by inventing a real machine (a pin-tumbler lock for a cache key, a gantry plotter for one shared GPU context) and drawing it as four-tone isometric SVG with a zero-dependency kit of about 16,200 lines, plus optional WebGL shaders and a beta 3D mode. Eight examples ship with their built pages committed, and CI on macOS with Node 22 rebuilds each one and requires byte-identical output.
Claude CodeOpenCodeCodex
$npx skills add wheresryan22/anatomy -g -a claude-code
