design-systems

design-systems is a skill for Claude Code from MonumentalSystems/Atlas-Agent-Teams. It costs 22 tokens per session (1,778 once invoked), scanned A, original, MIT.

Guidance for creating a design system: a shared set of visual rules and reusable interface components. It covers colors, typography, spacing, icons, accessibility, documentation, and component libraries.

In plain words
What is it for?
Use it to define design foundations, reusable components, recurring interface patterns, page templates, usage rules, and implementation guidance.
Why use it?
It helps teams keep screens consistent and makes design and development easier to maintain as a product grows.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the design-ux plugin — 4 skills, 1 command, 5 agents shipped together

Good fit Use it to define design foundations, reusable components, recurring interface patterns, page templates, usage rules, and implementation guidance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/monumentalsystems/atlas-agent-teams/design-systems
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 MonumentalSystems/Atlas-Agent-Teams --skill design-systems
Clone the repo
git clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-Teams

Made for: Claude Code.

Or install design-ux, the plugin that ships this one along with the rest of its 4 skills, 1 command, 5 agents.

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.

agentmods badge for design-systems

README.md
[![agentmods](https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/design-systems/github.svg)](https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/design-systems)
Your own site
<a href="https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/design-systems"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/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.

agentmods 80×15 button for design-systems

Your own site · 80×15
<a href="https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/design-systems"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/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,778 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.01778
Opus 5 $0.00011 $0.00889
Sonnet 5 $0.00004 $0.00356
Haiku 4.5 $0.00002 $0.00178

Measured 11d ago against content hash 1c9b81f0665e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 11d 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.

teams/design-ux/skills/design-systems/SKILL.md · 177 lines

How it starts

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

Design Systems

Design System Principles

Core Principles

  • Consistency: Ensure consistent visual language and behavior across all products
  • Scalability: Design systems that grow with the product and team
  • Efficiency: Speed up design and development through reusable components
  • Accessibility: Build accessibility into every component from the start
  • Maintainability: Create systems that are easy to update and maintain
  • Documentation: Document everything thoroughly for clear adoption

Design System Structure

  • Foundations: Colors, typography, spacing, icons, elevation
  • Components: Reusable UI elements with documented variations
  • Patterns: Common solutions to recurring design problems
  • Templates: Page layouts and screen structures
  • Guidelines: Usage rules and best practices
  • Resources: Assets, downloads, and implementation guides

Component Libraries

Popular Component Libraries

  • Material Design: Google's design system with comprehensive components
  • Ant Design: Enterprise-class UI design language and React components
  • Tailwind CSS: Utility-first CSS framework with design tokens
  • shadcn/ui: Beautiful, accessible components built with Radix UI and Tailwind
  • Chakra UI: Simple, modular and accessible component library
  • MUI: React components that implement Google's Material Design

Component Design Principles

  • Single Responsibility: Each component should have one clear purpose
  • Composability: Components should be composable and flexible
  • Predictable Behavior: Components should behave consistently
  • Accessible: All components must meet WCAG AA standards
  • Responsive: Components must work across all device sizes
  • Documented: Each component has clear documentation and examples

Component States

  • Default: Normal state of the component
  • Hover: When user hovers over the component
  • Focus: When component has keyboard focus
  • Active: When component is being activated
  • Disabled: When component is not available
  • Loading: When component is in a loading state
  • Error: When component has an error state

Read the full file on GitHub · 177 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. 11d ago First seen · 177 lines · 22 tokens per session scan A 1c9b81f0665e

Subscribe to this mod's changes

design-systems is a skill published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,778 once invoked, about $0.0001 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

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 50 tokens

frontend-ui-dark-ts

Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.

microsoft/skills · 48 tokens

reveal-hover-effect

Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…

MengTo/Skills · 66 tokens

frontend-visual-qa

Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…

daymade/claude-code-skills · 145 tokens

prototype-web

A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.

nexu-io/html-anything · 24 tokens