What is design-systems?

A shared set of interface building blocks, visual rules, and usage guidance for creating consistent digital products. It can include design tokens—named values for things such as color, spacing, and typography—and reusable components.

Use it to inventory components, define tokens and guidelines, create low-detail wireframes, plan a component library, document usage, and set up governance and adoption across teams.

Without shared rules, different teams often create inconsistent screens and duplicate work. A design system gives people common foundations while providing guidance for contributions, updates, and customization.

design-systems — Skill for Claude Code and Codex by liqiongyu

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 liqiongyu/lenny_skills_plus --skill design-systems

Clone the repo

git clone --depth 1 https://github.com/liqiongyu/lenny_skills_plus

Made for: Claude Code, Codex.

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/liqiongyu/lenny_skills_plus/design-systems/github.svg)](https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/design-systems)

Your own site

<a href="https://agentmods.dev/skills/liqiongyu/lenny_skills_plus/design-systems"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/design-systems/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/liqiongyu/lenny_skills_plus/design-systems"><img src="https://agentmods.dev/badge/skills/liqiongyu/lenny_skills_plus/design-systems.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,997 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.00022	$0.01997
Opus 5.5	$0.00009	$0.00799
Sonnet 5.5	$0.00004	$0.00399
Haiku 4.5	$0.00002	$0.00200

Measured 2mo ago against content hash 4616e49d774e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-systems 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 2mo ago.

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.

skills/design-systems/SKILL.md · 129 lines

How it starts

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

Design Systems

Scope

Covers

Creating or upgrading a design system (tokens + components + guidelines)
Using blockframes (lo-fi, system-aware wireframes) to lock logic before hi-fi execution
Designing a future-ready visual foundation (depth/elevation, motion, texture) without breaking consistency
Making the system easy for non-experts to use (guardrails, examples, starter templates)
Driving adoption + governance (contribution model, champions, release cadence)

When to use

“We need a design system / component library and a plan to build it.”
“Our UI is inconsistent—define tokens + components + documentation to standardize.”
“We want to refresh our UI style (more depth/texture/motion) without chaos.”
“We need to scale design across teams or support enterprise customers with customization.”
“We want faster hi-fi output by locking flows in lo-fi first.”

When NOT to use

You’re defining a brand identity or logo system (different process).
You need user research/discovery to decide what to build.
You only need to ship one isolated UI change (just implement it).
You’re doing pure front-end architecture unrelated to UI consistency.
You want to stand up a design engineering function or define the hybrid role (use design-engineering).
You need to run a one-off design review or critique session (use running-design-reviews).
You want to improve engineering team culture, rituals, or hiring (use engineering-culture).
You need a detailed feature spec or UX flow document (use writing-specs-designs).

Inputs

Minimum required

Product + surfaces: web/iOS/Android; key flows
Current state: existing UI kit/design system (if any), design tool (e.g., Figma), code stack (if relevant)
Goals: speed, consistency, accessibility, scalability, customization, enterprise adoption
Constraints: timeline, team ownership, level of engineering support, compliance/a11y needs

Missing-info strategy

Ask up to 5 questions from references/INTAKE.md, then proceed with explicit assumptions.
If platform/stack is unknown, assume a modern web product with a component library and design tokens.
Do not request secrets or credentials.

Read the full file on GitHub · 129 lines

Files

What ships with it

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

2mo ago First seen · 129 lines · 22 tokens per session scan A 4616e49d774e

Subscribe to this mod's changes

design-systems is a skill published in the GitHub repository liqiongyu/lenny_skills_plus (53 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 1,997 once invoked, about $0.0001 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-08-30.

Design and UX agent-skills ai-agents automation claude codex prompt-engineering

design-systems next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
design-systemsliqiongyu/lenny_skills_plus	Skill	53	5mo ago	Apache-2.0	A	22	Claude Code, Codex
planjeremylongshore/tons-of-skills-marketplace	Skill	2.9k	yesterday	MIT	A	144	Claude Code
prototypevinvcn/mattpocock-skills-zh-CN	Skill	5.6k	9d ago	MIT	A	39	Claude Code, Codex
ui-designAnastasiyaW/codex-claude-code-config	Skill	214	yesterday	MIT	A	97	Claude Code, Codex
frontend-designAnastasiyaW/codex-claude-code-config	Skill	214	yesterday	MIT	A	264	Claude Code
higroedyrustam/vibes-plug	Skill	121	yesterday	MIT	A	57	Cursor
ui-ux-pro-maxroedyrustam/vibes-plug	Skill	121	yesterday	MIT	A	43	Cursor