design-system

design-system is a command for Claude Code from Adityaraj0421/naksha-studio. It costs 20 tokens per session (2,029 once invoked), scanned A, original, MIT.

A tool for creating design tokens, theme settings, or a design system from code or Figma. Design tokens are shared names for values such as colors, typography, and spacing.

In plain words
What is it for?
Use it to generate CSS variables, Tailwind settings, Style Dictionary output, or a design system extracted from existing code or Figma files.
Why use it?
It helps keep visual values consistent across an application and produces settings compatible with the chosen token format.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the naksha-studio plugin — 47 commands, 7 agents shipped together

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 commands/adityaraj0421/naksha-studio/design-system
Clone the repo
git clone --depth 1 https://github.com/Adityaraj0421/naksha-studio

Made for: Claude Code.

Or install naksha-studio, the plugin that ships this one along with the rest of its 47 commands, 7 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-system

README.md
[![agentmods](https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-system.svg)](https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-system)
Your own site
<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-system"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-system.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,029 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.1 $0.00020 $0.02029
Opus 5 $0.00010 $0.01014
Sonnet 5 $0.00004 $0.00406
Haiku 4.5 $0.00002 $0.00203

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

commands/design-system.md · 170 lines

How it starts

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

/design-system

You are the Design System Lead. Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/design-system-lead.md for your full knowledge base.

Input: $ARGUMENTS

Determine Mode

Based on the user's input, run one of these workflows:

Context7 Documentation Lookup

Before running the selected mode, use Context7 to fetch current documentation for the target token format. This keeps generated token schemas compatible with the latest library versions.

When to look up what (call mcp__plugin_context7_context7__resolve-library-id then mcp__plugin_context7_context7__query-docs):

  • Generating Tailwind tokens (Mode A or C) → resolve "tailwindcss" → query "theme extend colors typography configuration"
  • Generating Style Dictionary output → resolve "style-dictionary" → query "token format transforms platforms"
  • Generating CSS custom properties → no lookup needed (CSS spec is stable)
  • Mode B (Figma extraction) → no lookup needed

If .naksha/project.json has a tokenFormat field, look up only that format's library. Otherwise look up all applicable formats and note any version differences in the output.

Context7 Fallback: If the tools are unavailable, proceed with built-in knowledge. The token generation will still produce correct output.

v5 Project Context

Before running any mode, read .naksha/project.json (search up to 3 directory levels) for v5 constraints that pre-shape the token system:

  • constraints.grid → set the base spacing unit to this value. If "4px", the spacing scale is 4, 8, 12, 16, 20, 24, 32, 40, 48, 64px. If "8px", scale is 8, 16, 24, 32, 40, 48, 64, 80, 96px. Note in output: "Base grid: {value} (from project constraints)."
  • constraints.dark_mode → if false, skip dark mode token variants entirely. If true, dark mode variants are required. If absent, include dark mode as an optional layer.
  • constraints.accessibility_target → if "WCAG AAA", generate semantic color tokens that achieve 7:1 contrast minimum. If "WCAG AA" (or absent), use 4.5:1.
  • constraints.breakpoints → use these as the responsive breakpoint values in the generated token set. Emit them as named breakpoint tokens (e.g., --breakpoint-md: 768px).
  • constraints.max_content_width → emit as a layout token: --layout-max-width: {value}px.
  • component_patterns → for each named pattern, ensure the generated component tokens match the recorded description. If a card-layout pattern exists with "16px padding, 8px radius", the generated --card-padding and --card-radius tokens must match.

Read the full file on GitHub · 170 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. 6d ago First seen · 170 lines · 20 tokens per session scan A f8a3865bb540

Subscribe to this mod's changes

design-system is a command published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 2,029 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.