design-system

A design guide for applying consistent colors, themes, borders, shadows, spacing, and component states to interface work. It defines reusable visual rules for the docs.plus application.

In plain words
What is it for?
It guides visual changes in apps/webapp, including dark and light themes, surface elevation, component states, and shared design tokens.
Why use it?
It prevents new interface changes from looking inconsistent with the rest of the application or behaving differently across themes.

Skill for Claude CodeCodex

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/docs-plus/docs.plus/design-system
Any agent
npx skills add docs-plus/docs.plus --skill design-system
Clone the repo
git clone --depth 1 https://github.com/docs-plus/docs.plus

Made for: Claude Code, Codex.

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 760 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.

ModelPer sessionOnce invoked
Fable 5 $0.00066 $0.00760
Opus 5 $0.00033 $0.00380
Sonnet 5 $0.00013 $0.00152
Haiku 4.5 $0.00007 $0.00076

Measured yesterday against content hash 6c98399dfe68, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

design-system 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 yesterday.

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.

.agents/skills/design-system/SKILL.md · 45 lines

How it starts

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

Design System

Working protocol for visual changes in apps/webapp. The source of truth is .cursor/docs/design-system.md — tokens, themes, elevation species, state language, and the per-component catalog. AGENTS.md owns §UI And Theme. apps/webapp/AGENTS.md owns the rest of the behavioral invariants (§Pad Workspace Surfaces, §Floating Surfaces And Modal Scrims, §Motion System). That file loads automatically when you work under apps/webapp/.

Protocol

  1. Read the relevant doc sections first: tokens/themes for color work; elevation species for any new or moved surface. Read the component's catalog row before editing its frame or states.
  2. Classify before styling. Every surface is one species: docked (L0), anchored (L1), modal (L2), tooltip, card, control, sheet — reuse its canonical export or recipe verbatim. If no species fits, extend the doc's elevation table first, then implement.
  3. Change color at the token layer. New colors/effects become :root vars (+ both dark overrides) in globals.scss, exposed via @theme aliases when Tailwind utilities are needed. Components never carry hex or raw palette classes (brand allowlist and media-anchored black/white overlays excepted — see the doc's Color policy).
  4. States are recipes, not improvisation: hover base-200, active is-active (primary-10% + primary ink), context-menu-active primary-15%/8%, focus focus-visible:ring-2 ring-primary, unread error badge, disabled /40 ink. Cover both layers — desktop and mobile variants of the same component share tokens, not necessarily geometry.
  5. Keep lockstep surfaces in sync in the same change: skeleton mirrors, _document.tsx theme-color meta, third-party CSS-var themings (em-emoji-picker, .documentKeywordInput), and the JS motion mirror (utils/motion.ts). The skeleton mirrors are SlugPageLoader and ChatroomComposerSkeleton, which copy the real frame classes verbatim.
  6. Verify in the browser — light + dark (+ dark-HC for pad/TOC), desktop ≥1280px and mobile. Never typecheck alone. Confirm the webapp dev port before driving it (not always 3000).
  7. Close the loop: update the doc's affected rows (and AGENTS.md when doctrine moved) in the same change; after substantive design-system work, run the memory updater.

Read the full file on GitHub · 45 lines

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.

  1. yesterday First seen · 45 lines · 66 tokens per session scan A 6c98399dfe68

Subscribe to this mod's changes

design-system is a skill published in the GitHub repository docs-plus/docs.plus (88 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 760 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

docx

Read, create, and convert Microsoft Word (.docx) documents — extract text and tables, build reports from markdown/JSON, and export to PDF.

zhixuli0406/DuDuClaw · 34 tokens

document-converter

Convert Office documents (PPTX, DOCX, XLSX, PDF, HTML, CSV, JSON, XML, images) to Markdown using Microsoft MarkItDown. Provides the agent with conversion strategies for academic and research workflows.

wentorai/Research-Claw · 50 tokens

docx-manipulation

Create, edit, and manipulate Word documents programmatically using python-docx.

claude-office-skills/skills · 20 tokens

add-format

End-to-end checklist for adding a new input or output format to AILANG Parse (docparse). Use when the user says 'add support for X format', 'wire up a new parser', 'add .foo format', 'add a parser for .bar', 'support .baz files', 'ship format X', 'can we parse .qux', 'new format rollout', or mentions a file extension…

sunholo-data/ailang-parse · 183 tokens

landing-page

Create a new AILANG Parse documentation/landing page targeting a specific keyword or topic. Use when user says 'new landing page', 'new page for X', 'create a page about X', 'landing page for keyword X', or wants to add a documentation page to the docs/ site. Also use when the user references long-tail keywords, SEO…

sunholo-data/ailang-parse · 81 tokens

benchmark

Run OfficeDocBench evaluation and refresh benchmark scores across the AILANG Parse website. Use when the user says 'run benchmarks', 'rerun the benchmark', 'refresh benchmark numbers', 'update bench scores', 'regenerate summary.json', mentions OfficeDocBench, asks to evaluate parsers, asks why scores are out of sync…

sunholo-data/ailang-parse · 115 tokens