What is design-systems-architecture?

A guide to designing and governing a design system: a shared set of visual rules, reusable interface components, interaction patterns, documentation, and team decisions. It covers how these parts are organized and maintained as a product grows.

Planning design-system foundations, design tokens, component architecture, documentation, governance, versioning, deprecation, and collaboration across teams.

It helps prevent each team or screen from inventing its own buttons, colors, spacing, and usage rules. It also addresses ownership, versioning, and retiring outdated parts.

How plugin87/full-stack-design-skills configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to plugin87/full-stack-design-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/plugin87/full-stack-design-skills/main/.claude/skills/design-systems-architecture/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/plugin87/full-stack-design-skills

Made for: Claude Code.

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/plugin87/full-stack-design-skills/design-systems-architecture/github.svg)](https://agentmods.dev/skills/plugin87/full-stack-design-skills/design-systems-architecture)

Your own site

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

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

When invoked 3,748 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.00108	$0.03748
Opus 5.5	$0.00043	$0.01499
Sonnet 5.5	$0.00022	$0.00750
Haiku 4.5	$0.00011	$0.00375

Measured 2mo ago against content hash 91cd1cecf0fd, 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-architecture 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.

.claude/skills/design-systems-architecture/SKILL.md · 518 lines

How it starts

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

Design Systems Architecture

A practical guide to building, scaling, and maintaining design systems that serve teams and products long-term.

A design system is more than a component library—it's a shared language, a source of truth, and a scalable architecture for consistent digital experiences. This skill covers the principles, organization, and governance that make systems sustainable.

What Is a Design System?

A design system comprises:

Foundation — Design tokens (colors, typography, spacing, etc.) that define the visual language

Components — Reusable UI building blocks (buttons, cards, modals) paired with guidelines

Patterns — Common interaction and layout patterns (forms, navigation, error handling)

Documentation — Clear guidance on when/how to use each piece

Governance — Decision-making framework, versioning, deprecation policy

Tools — Platforms that host, maintain, and distribute the system (Figma, Storybook, npm, etc.)

Design System Principles

1. Atomic Design Methodology

Atomic Design (by Brad Frost) organizes components by complexity:

Atoms (smallest)

Buttons, labels, inputs, icons
Standalone; can't be broken down further
Example: <button>, <label>, <input />

Molecules (combination of atoms)

Form field (label + input + error message)
Card header (icon + title + subtitle)
Search box (input + icon + button)
Example: <FormField>, <CardHeader>

Organisms (combination of molecules + atoms)

Contact form (multiple form fields + button)
Header (logo + nav + search box)
Product card (image + title + description + button)
Example: <ContactForm>, <Header>

Templates (layout + organisms, no content)

Product listing page layout (header + sidebar + product grid)
Article template (nav + hero + content + footer)
Example: <ProductListingTemplate>

Pages (templates + real content)

Actual product listing page with real products
Actual article with real text
Example: <ProductListingPage>

Read the full file on GitHub · 518 lines

Files

What ships with it

5 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 · 518 lines · 0 tokens per session scan A 91cd1cecf0fd

Subscribe to this mod's changes

design-systems-architecture is a skill published in the GitHub repository plugin87/full-stack-design-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 108 tokens to every session and 3,748 once invoked, about $0.0004 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-31.

Design and UX

design-systems-architecture next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
design-systems-architectureplugin87/full-stack-design-skills	Skill	11	3mo ago	MIT	A	108	Claude Code
webgl-holographic-foilnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	41	Claude Code, Codex
html-ppt-hermes-cyber-terminalnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	53	Claude Code, Codex
html-ppt-taste-brutalistnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	78	Claude Code, Codex
visual-ralphYeachan-Heo/oh-my-codex	Skill	34k	3d ago	MIT	A	52	Codex
glance-canonical-layoutsandroid/skills	Skill	10k	yesterday	Apache-2.0	A	56	Claude Code
accessibilitymicrosoft/hve-core	Skill	1.6k	yesterday	MIT	A	47	Claude Code

full-stack-design-skills: Skill for Claude Code