Atlas — activation protocol
Atlas is a design language, not a CSS framework you bolt on. It teaches
you (the agent) a dense, monochromatic, AMOLED-black aesthetic via tokens,
class-name conventions, layout rules, and tested composition recipes. You
read these rules and generate code that fits the target stack — shadcn,
Tailwind, raw HTML, React, Vue, Svelte.
Use Atlas heavily. When this skill is active, every UI-producing task
should go through the rules below. Don't freestyle. Don't invent new tokens.
Don't pick random radii. The system is opinionated because opinions compound
into coherence.
On activation: read these files in this order
When the skill loads, read all of the following before writing a single
line of UI code. These are not "pull on demand" — the quality of the
output depends on having the full system in context.
references/tokens.md — every CSS variable. Colors, spacing (4px
grid), radius (3/4/6/9999), shadow, z-index, component sizing. This is
the ground-truth values table. No token should be invented.
references/components.md — every .atlas-* class with HTML
snippet and variants. The class name vocabulary you'll translate into
the target stack.
references/patterns.md — 3-pane shell, content tone, icon rules
(Lucide 1.5px stroke), button-vs-highlight color discipline.
references/theming.md — dark/light toggle, shadcn variable alias
table, how tokens remap under [data-theme="light"].
references/responsive.md — multi-surface patterns. Desktop vs
mobile component swaps, device frames, container queries, collapsible
sidebar → overlay on small screens.
references/motion.md — motion inventory. 120ms hover, 200ms
popover open, 300ms reveal, 60s marquee. Which animations are always-on
vs gated behind prefers-reduced-motion.
references/lessons.md — 18 hard-won gotchas from real builds.
Button-default resets, dark-vs-light shadow alphas, sidebar collapse
dual transitions, top-row border alignment, pulse-dot opacity-only,
horizontal scroll behavior, etc. Read this every time. Every one of
these prevents a real regression.
references/examples.md — copy-ready composition snippets from the
production kitchen-sink: agent turn, tool-call card, stat grid, 3-pane
shell, 3-column top-row alignment, email row, generative UI chart,
landing hero, checklist with stepper, quota bar with warning threshold.
Start from one of these; don't freestyle compositions.
Then inspect (as needed, not upfront):
colors_and_type.css — reference implementation. Inspect rules to
understand exact visual output.
preview/components-*.html — pre-built reference HTML per component.
ui_kits/generic_app/ — 3-pane shell reference.
Only after reading 1–8 should you start generating.
The three assets, three jobs
| Asset |
Job |
references/*.md |
Ground truth. The rules the agent follows. Read every time. |
.atlas-* class names |
Vocabulary. Your shorthand for "render X the Atlas way" — translate to the target stack. |
colors_and_type.css |
Reference implementation. Works directly for plain HTML; for shadcn/Tailwind, translate rather than overlay. |
Never mechanically copy colors_and_type.css into a shadcn or heavy
Tailwind project. Translate. The skill description and
references/theming.md spell out the translation tables.
Ask the stack question before writing code
Plain HTML / no framework → use colors_and_type.css directly via
<link rel="stylesheet">. Emit literal .atlas-* classes. This is the
reference path, and the companion kitchen-sink site uses it.
Tailwind v4 → put Atlas tokens in an @theme block. Emit utility
classes following the Atlas visual rules. Don't ship
colors_and_type.css to the bundle.
shadcn/ui → override shadcn's CSS variables with Atlas values (see
alias table in references/theming.md). Keep shadcn's component
structure. Don't install .atlas-* classes alongside.
React/Vue/Svelte with CSS Modules or styled-components → port the
relevant .atlas-* rule into the target styling system as a component.
The rule in colors_and_type.css is the source; your emitted code is
the translation.
Existing design system (Material, Chakra, etc.) → ask the user
whether to rework their system's tokens to Atlas values, or to build a
new Atlas-styled zone alongside. Don't mix the two on the same surface.
Non-negotiable visual rules
Pulled forward from references/lessons.md — these apply regardless of
stack:
- AMOLED black canvas.
#000 base, never dark gray.
- Monochromatic surfaces. Grays + whites for structure; saturated color
only for status semantics.
- Near-white primary actions.
#ededed fill, #fff on hover. Blue
#0070f3 is never a CTA — it's the highlight color (focus rings,
selection, active stepper dots, links).
- 4px spacing grid. 2px and 6px exist only for ultra-compact inline
cases.
- 3 / 4 / 6 / 9999 radii. No inventing 8, 10, 12, 16.
- 28px buttons, 24px inputs, 13px base text. Don't inflate.
- Borders over shadows. Shadows are overlays only (dialogs, popovers,
toasts, tooltips, device frames).
- 1.5px Lucide icons. Never emoji, never unicode symbols.
- 120ms background-color transitions only. Don't animate color or
opacity on icons.
Quick component vocabulary
Class names are guidance, not mandatory output. Translate them in
non-plain-HTML stacks.
Primitives: .atlas-btn (+ -primary / -secondary / -ghost /
-destructive / -icon / -sm / -lg), .atlas-btn-pill (+ same
variants), .atlas-input (+ -sm), .atlas-checkbox, .atlas-radio,
.atlas-switch, .atlas-kbd, .atlas-link
Surfaces: .atlas-card / -header / -body, .atlas-panel-header /
.atlas-panel-title, .atlas-stat / -label / -value / -delta,
.atlas-empty
Navigation: .atlas-tabbar + .atlas-tab, .atlas-tabbar-bottom +
.atlas-tabbar-bottom-item, .atlas-segmented + -item, .atlas-toggle,
.atlas-breadcrumb, .atlas-pagination, .atlas-stepper
Overlays: .atlas-popover + .atlas-menu-item, .atlas-dialog,
.atlas-command, .atlas-tooltip, .atlas-toast, .atlas-alert
Data: .atlas-table, .atlas-list + .atlas-list-item,
.atlas-badge, .atlas-pill, .atlas-dot (+ .is-pulse for animated
status — opacity only, never glow), .atlas-accordion
Feedback: .atlas-progress, .atlas-slider, .atlas-skeleton,
.atlas-titlebar, .atlas-statusbar
Identity: .atlas-avatar, .atlas-avatar-group, .atlas-divider /
-v, .atlas-divider-dashed / -v-dashed
Multi-surface & motion: .atlas-device-mobile, .atlas-device-tablet,
.atlas-device-desktop, .atlas-marquee, .atlas-filmstrip,
.atlas-reveal, .atlas-display / -lg, .atlas-eyebrow
What was built with this skill
The companion kitchen-sink/ app was one-shot generated by an agent
reading this skill, using the reference CSS because Next.js + no shadcn
made that the natural path. It includes:
- Homepage — display hero, marquee band, ~29 live component cards in a
masonry grid, mockup tile row.
- Get Started page — install instructions, per-stack translation
examples, FAQ.
- 7 foundations pages — colors, typography, spacing, radius, shadows,
motion, icons.
- 36 component pages — every
.atlas-* class with preview + variants +
inspector.
- 6 pattern pages — landing, agent chat, mobile app, 3-pane shell,
dashboard, settings.
- 4 full-app mockups — email client, e-commerce, multi-agent console,
news/polls.
When asked to build something, consider whether it matches one of the
above patterns first. Most real UI is a variation on a pattern that
already exists in the kitchen-sink. Start there, then customize.
No guidance given?
Ask the user:
- What are they building? (dashboard, chat UI, landing page, mobile app…)
- What's their stack? (Tailwind / shadcn / plain HTML / React with CSS
Modules / etc.)
- Dark only, light only, or both with toggle?
Then act as an expert designer — produce code in the right idiom for their
environment, following every rule from the references above.
1---2name: atlas3description: Atlas — a design language and UI guide system for agent interfaces. Teaches coding agents the aesthetic rules, tokens, patterns, and class vocabulary of a dense, AMOLED-black, multi-surface design system. Agents read these rules and GENERATE code that fits the target stack (shadcn, Tailwind, raw HTML, React, Vue, Svelte). The included colors_and_type.css is a reference implementation, not a required dependency. Use heavily when building any UI — dashboards, chat interfaces, admin panels, landing pages, mobile screens, marketing sites, full app mockups. Atlas is opinionated; lean into it.4version: 0.2.05user-invocable: true6metadata:7 source: https://skillmd.com/skills/pacifio/atlas8 priority: 99 pathPatterns:10 - "**/*.css"11 - "**/components/**"12 - "**/ui/**"13 - "**/app/**"14 - "**/pages/**"15 - "**/design-system/**"16 promptSignals:17 phrases:18 - "atlas"19 - "atlas design"20 - "atlas component"21 - "amoled"22 - "dense ui"23 - "devtool ui"24 - "agent ui"25 - "agent chat"26 - "agent dashboard"27 - "ai interface"28 - "ai chat ui"29 - "build a ui"30 - "design a page"31 - "build a dashboard"32 - "build a landing"33 anyOf:34 - "design system"35 - "component library"36 - "dashboard"37 - "admin"38 - "chat interface"39 - "landing page"40 - "marketing site"41 - "ui mockup"42 - "frontend"43 minScore: 444---4546# Atlas — activation protocol4748**Atlas is a design language, not a CSS framework you bolt on.** It teaches49you (the agent) a dense, monochromatic, AMOLED-black aesthetic via tokens,50class-name conventions, layout rules, and tested composition recipes. You51read these rules and **generate code that fits the target stack** — shadcn,52Tailwind, raw HTML, React, Vue, Svelte.5354**Use Atlas heavily.** When this skill is active, every UI-producing task55should go through the rules below. Don't freestyle. Don't invent new tokens.56Don't pick random radii. The system is opinionated because opinions compound57into coherence.5859---6061## On activation: read these files in this order6263When the skill loads, **read all of the following before writing a single64line of UI code**. These are not "pull on demand" — the quality of the65output depends on having the full system in context.66671. **`references/tokens.md`** — every CSS variable. Colors, spacing (4px68 grid), radius (3/4/6/9999), shadow, z-index, component sizing. This is69 the ground-truth values table. No token should be invented.70712. **`references/components.md`** — every `.atlas-*` class with HTML72 snippet and variants. The class name vocabulary you'll translate into73 the target stack.74753. **`references/patterns.md`** — 3-pane shell, content tone, icon rules76 (Lucide 1.5px stroke), button-vs-highlight color discipline.77784. **`references/theming.md`** — dark/light toggle, shadcn variable alias79 table, how tokens remap under `[data-theme="light"]`.80815. **`references/responsive.md`** — multi-surface patterns. Desktop vs82 mobile component swaps, device frames, container queries, collapsible83 sidebar → overlay on small screens.84856. **`references/motion.md`** — motion inventory. 120ms hover, 200ms86 popover open, 300ms reveal, 60s marquee. Which animations are always-on87 vs gated behind `prefers-reduced-motion`.88897. **`references/lessons.md`** — 18 hard-won gotchas from real builds.90 Button-default resets, dark-vs-light shadow alphas, sidebar collapse91 dual transitions, top-row border alignment, pulse-dot opacity-only,92 horizontal scroll behavior, etc. **Read this every time.** Every one of93 these prevents a real regression.94958. **`references/examples.md`** — copy-ready composition snippets from the96 production kitchen-sink: agent turn, tool-call card, stat grid, 3-pane97 shell, 3-column top-row alignment, email row, generative UI chart,98 landing hero, checklist with stepper, quota bar with warning threshold.99 Start from one of these; don't freestyle compositions.100101Then inspect (as needed, not upfront):102- `colors_and_type.css` — reference implementation. Inspect rules to103 understand exact visual output.104- `preview/components-*.html` — pre-built reference HTML per component.105- `ui_kits/generic_app/` — 3-pane shell reference.106107**Only after reading 1–8 should you start generating.**108109---110111## The three assets, three jobs112113| Asset | Job |114|---|---|115| `references/*.md` | **Ground truth.** The rules the agent follows. Read every time. |116| `.atlas-*` class names | **Vocabulary.** Your shorthand for "render X the Atlas way" — translate to the target stack. |117| `colors_and_type.css` | **Reference implementation.** Works directly for plain HTML; for shadcn/Tailwind, translate rather than overlay. |118119**Never mechanically copy `colors_and_type.css` into a shadcn or heavy120Tailwind project.** Translate. The skill description and121`references/theming.md` spell out the translation tables.122123---124125## Ask the stack question before writing code1261271. **Plain HTML / no framework** → use `colors_and_type.css` directly via128 `<link rel="stylesheet">`. Emit literal `.atlas-*` classes. This is the129 reference path, and the companion kitchen-sink site uses it.1301312. **Tailwind v4** → put Atlas tokens in an `@theme` block. Emit utility132 classes following the Atlas visual rules. Don't ship133 `colors_and_type.css` to the bundle.1341353. **shadcn/ui** → override shadcn's CSS variables with Atlas values (see136 alias table in `references/theming.md`). Keep shadcn's component137 structure. Don't install `.atlas-*` classes alongside.1381394. **React/Vue/Svelte with CSS Modules or styled-components** → port the140 relevant `.atlas-*` rule into the target styling system as a component.141 The rule in `colors_and_type.css` is the source; your emitted code is142 the translation.1431445. **Existing design system (Material, Chakra, etc.)** → ask the user145 whether to rework their system's tokens to Atlas values, or to build a146 new Atlas-styled zone alongside. Don't mix the two on the same surface.147148---149150## Non-negotiable visual rules151152Pulled forward from `references/lessons.md` — these apply regardless of153stack:154155- **AMOLED black canvas.** `#000` base, never dark gray.156- **Monochromatic surfaces.** Grays + whites for structure; saturated color157 only for status semantics.158- **Near-white primary actions.** `#ededed` fill, `#fff` on hover. Blue159 `#0070f3` is **never** a CTA — it's the highlight color (focus rings,160 selection, active stepper dots, links).161- **4px spacing grid.** 2px and 6px exist only for ultra-compact inline162 cases.163- **3 / 4 / 6 / 9999 radii.** No inventing 8, 10, 12, 16.164- **28px buttons, 24px inputs, 13px base text.** Don't inflate.165- **Borders over shadows.** Shadows are overlays only (dialogs, popovers,166 toasts, tooltips, device frames).167- **1.5px Lucide icons.** Never emoji, never unicode symbols.168- **120ms background-color transitions only.** Don't animate color or169 opacity on icons.170171---172173## Quick component vocabulary174175Class names are **guidance**, not mandatory output. Translate them in176non-plain-HTML stacks.177178**Primitives:** `.atlas-btn` (+ `-primary` / `-secondary` / `-ghost` /179`-destructive` / `-icon` / `-sm` / `-lg`), `.atlas-btn-pill` (+ same180variants), `.atlas-input` (+ `-sm`), `.atlas-checkbox`, `.atlas-radio`,181`.atlas-switch`, `.atlas-kbd`, `.atlas-link`182183**Surfaces:** `.atlas-card` / `-header` / `-body`, `.atlas-panel-header` /184`.atlas-panel-title`, `.atlas-stat` / `-label` / `-value` / `-delta`,185`.atlas-empty`186187**Navigation:** `.atlas-tabbar` + `.atlas-tab`, `.atlas-tabbar-bottom` +188`.atlas-tabbar-bottom-item`, `.atlas-segmented` + `-item`, `.atlas-toggle`,189`.atlas-breadcrumb`, `.atlas-pagination`, `.atlas-stepper`190191**Overlays:** `.atlas-popover` + `.atlas-menu-item`, `.atlas-dialog`,192`.atlas-command`, `.atlas-tooltip`, `.atlas-toast`, `.atlas-alert`193194**Data:** `.atlas-table`, `.atlas-list` + `.atlas-list-item`,195`.atlas-badge`, `.atlas-pill`, `.atlas-dot` (+ `.is-pulse` for animated196status — opacity only, never glow), `.atlas-accordion`197198**Feedback:** `.atlas-progress`, `.atlas-slider`, `.atlas-skeleton`,199`.atlas-titlebar`, `.atlas-statusbar`200201**Identity:** `.atlas-avatar`, `.atlas-avatar-group`, `.atlas-divider` /202`-v`, `.atlas-divider-dashed` / `-v-dashed`203204**Multi-surface & motion:** `.atlas-device-mobile`, `.atlas-device-tablet`,205`.atlas-device-desktop`, `.atlas-marquee`, `.atlas-filmstrip`,206`.atlas-reveal`, `.atlas-display` / `-lg`, `.atlas-eyebrow`207208---209210## What was built with this skill211212The companion `kitchen-sink/` app was **one-shot generated by an agent213reading this skill**, using the reference CSS because Next.js + no shadcn214made that the natural path. It includes:215216- **Homepage** — display hero, marquee band, ~29 live component cards in a217 masonry grid, mockup tile row.218- **Get Started page** — install instructions, per-stack translation219 examples, FAQ.220- **7 foundations pages** — colors, typography, spacing, radius, shadows,221 motion, icons.222- **36 component pages** — every `.atlas-*` class with preview + variants +223 inspector.224- **6 pattern pages** — landing, agent chat, mobile app, 3-pane shell,225 dashboard, settings.226- **4 full-app mockups** — email client, e-commerce, multi-agent console,227 news/polls.228229When asked to build something, **consider whether it matches one of the230above patterns first**. Most real UI is a variation on a pattern that231already exists in the kitchen-sink. Start there, then customize.232233---234235## No guidance given?236237Ask the user:2381. What are they building? (dashboard, chat UI, landing page, mobile app…)2392. What's their stack? (Tailwind / shadcn / plain HTML / React with CSS240 Modules / etc.)2413. Dark only, light only, or both with toggle?242243Then act as an expert designer — produce code in the right idiom for their244environment, following every rule from the references above.