design-systems

design-systems is a cursor rule for Cursor from madebyaris/advance-minimax-m3-cursor-rules. It costs 0 tokens per session (1,457 once invoked), scanned A, original, MIT.

A set of rules for building interfaces with shared design tokens, shadcn/ui components, Tailwind CSS version 4, themes, and reusable compositions.

In plain words
What is it for?
Defining semantic style variables, extending an existing design system, composing interface components, and supporting themes in web projects.
Why use it?
It reduces inconsistent colors, spacing, typography, and component behavior across an interface. It also encourages checking the existing project setup before changing it.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Defining semantic style variables, extending an existing design system, composing interface components, and supporting themes in web projects.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/madebyaris/advance-minimax-m3-cursor-rules/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.

Clone the repo
git clone --depth 1 https://github.com/madebyaris/advance-minimax-m3-cursor-rules

Made for: Cursor.

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/rules/madebyaris/advance-minimax-m3-cursor-rules/design-systems/github.svg)](https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/design-systems)
Your own site
<a href="https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/design-systems"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/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/rules/madebyaris/advance-minimax-m3-cursor-rules/design-systems"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/design-systems.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,457 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.00000 $0.01457
Opus 5 $0.00000 $0.00728
Sonnet 5 $0.00000 $0.00291
Haiku 4.5 $0.00000 $0.00146

Measured 11d ago against content hash 3eed6b3492d7, 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.

.cursor/rules/design-systems.mdc · 127 lines

How it starts

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

Design System Mechanics

Token structure, shadcn/ui usage, Tailwind v4 features, and component composition — not aesthetic direction.

For palettes, font pairings, category tone, layout direction, and the slop checklist, load the anti-slop-design skill (and its reference.md for full pages / responsive matrices). For general coding workflow, use core Code Discipline.

Inspect the project first: package.json, tailwind.config.*, globals.css, components.json, existing fonts and icon library. Extend what exists; do not replace the design system unprompted.


Token Shape (semantic, not hex soup)

Prefer semantic names mapped to CSS variables so themes and shadcn primitives stay aligned:

/* globals.css — Tailwind v4 @theme or :root */
@theme {
  --color-background: …;
  --color-foreground: …;
  --color-primary: …;
  --color-muted: …;
  --color-border: …;
  --radius-md: 8px;
  --font-body: …;
  --font-display: …;
}
  • Derive real values from the project brand or anti-slop-design Category Guide — placeholders above are structural only.
  • Prefer OKLCH for new token values (oklch(0.65 0.15 250)) — perceptually uniform lightness makes scales and dark-mode variants predictable. Tint neutrals toward the brand hue (chroma 0.005–0.01); never ship pure-gray scales or pure #000/#FFF.
  • Three token tiers when the system grows: primitive (--blue-600) → semantic (--color-primary) → component (--button-bg). Components consume semantic tokens; only semantic tokens reference primitives. Skip the component tier until a component actually needs an override.
  • Do not default to generic blue/indigo scales or Inter / Roboto unless the project already uses them.
  • Status colors: --destructive, --success, etc. — keep consistent with shadcn semantic tokens when present.

Typography Mechanics

  • Fluid display sizes with clamp(): font-size: clamp(2rem, 1.2rem + 3.5vw, 4rem) — no breakpoint jumps on headings.
  • Pair line-height inversely with size: body 1.6–1.8, headings 1.1–1.2. A 56px heading at line-height: 1.6 is broken.
  • Tighten tracking as display size grows (letter-spacing: -0.01em to -0.04em above ~32px); never negative-track body text.
  • Body measure: max-width: 65ch on prose containers, not pixel guesses.
  • Keep ≥1.25 ratio between adjacent type-scale steps; expose the scale as tokens, not ad-hoc text-[17px] values.
  • Load fonts with font-display: swap and preconnect; subset when the toolchain supports it.

Read the full file on GitHub · 127 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 · 127 lines · 0 tokens per session scan A 3eed6b3492d7

Subscribe to this mod's changes

design-systems is a cursor rule published in the GitHub repository madebyaris/advance-minimax-m3-cursor-rules (125 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,457 tokens. 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.