Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

nothing-design

Guides intentional Nothing-inspired UI and design-system work with typography, spacing, hierarchy, components, and platform-specific execution. Use when the user explicitly asks for Nothing style, Nothing design, or `/nothing-design`, not for generic UI or design tasks.

dallay · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add dallay/agentsync --skill nothing-design

About this skill


name: nothing-design description: >- Guides intentional Nothing-inspired UI and design-system work with typography, spacing, hierarchy, components, and platform-specific execution. Use when the user explicitly asks for Nothing style, Nothing design, or /nothing-design, not for generic UI or design tasks. license: MIT metadata: version: "3.0.0"

Nothing-Inspired UI/UX Design System

A senior product designer's toolkit trained in Swiss typography, industrial design (Braun, Teenage Engineering), and modern interface craft. Monochromatic, typographically driven, information-dense without clutter. Dark and light mode with equal rigor.

Before starting any design work, declare which Google Fonts are required and how to load them ( see references/tokens.md Section 1). Never assume fonts are already available.

This skill is for intentional Nothing-inspired execution, not loose minimalism. Apply it when the user explicitly asks for Nothing design language or invokes /nothing-design.


1. DESIGN PHILOSOPHY

  • Subtract, don't add. Every element must earn its pixel. Default to removal.
  • Structure is ornament. Expose the grid, the data, the hierarchy itself.
  • Monochrome is the canvas. Color is an event, not a default — except when encoding data status (see Section 3).
  • Type does the heavy lifting. Scale, weight, and spacing create hierarchy — not color, not icons, not borders.
  • Both modes are first-class. Dark mode: OLED black. Light mode: warm off-white. Neither is " derived" — both get full design attention. Ask the user which mode to start with.
  • Industrial warmth. Technical and precise, but never cold. A human hand should be felt.

2. CRAFT RULES — HOW TO COMPOSE

2.1 Visual Hierarchy: The Three-Layer Rule

Every screen has exactly three layers of importance. Not two, not five. Three.

LayerWhatHow
PrimaryThe ONE thing the user sees first. A number, a headline, a state.Doto or Space Grotesk at display size. --text-display. 48–96px breathing room.
SecondarySupporting context. Labels, descriptions, related data.Space Grotesk at body/subheading. --text-primary. Grouped tight (8–16px) to the primary.
TertiaryMetadata, navigation, system info. Visible but never competing.Space Mono at caption/label. --text-secondary or --text-disabled. ALL CAPS. Pushed to edges or bottom.

The test: Squint at the screen. Can you still tell what's most important? If two things compete, one needs to shrink, fade, or move.

Common mistake: Making everything "secondary." Evenly-sized elements with even spacing = visual flatness. Be brave — make the primary absurdly large and the tertiary absurdly small. The contrast IS the hierarchy.

2.2 Font Discipline

Per screen, use maximum:

  • 2 font families (Space Grotesk + Space Mono. Doto only for hero moments.)
  • 3 font sizes (one large, one medium, one small)
  • 2 font weights (Regular + one other — usually Light or Medium, rarely Bold)

Think of it as a budget. Every additional size/weight costs visual coherence. Before adding a new size, ask: can I create this distinction with spacing or color instead?

DecisionSizeWeightColor
Heading vs. bodyYesNoNo
Label vs. valueNoNoYes
Active vs. inactive navNoNoYes
Hero number vs. unitYesNoNo
Section title vs. contentYesOptionalNo

Rule of thumb: If reaching for a new font-size, it's probably a spacing problem. Add distance instead.

2.3 Spacing as Meaning

Spacing is the primary tool for communicating relationships.

Tight (4–8px)   = "These belong together" (icon + label, number + unit)
Medium (16px)    = "Same group, different items" (list items, form fields)
Wide (32–48px)   = "New group starts here" (section breaks)
Vast (64–96px)   = "This is a new context" (hero to content, major divisions)

If a divider line is needed, the spacing is probably wrong. Dividers are a symptom of insufficient spacing contrast. Use them only in data-dense lists where items are structurally identical.

2.4 Container Strategy (prefer top)

  1. Spacing alone (proximity groups items)
  2. A single divider line
  3. A subtle border outline
  4. A surface card with background change

Each step down adds visual weight. Use the lightest tool that works. Never box the most important element — let it float on the background.

2.5 Color as Hierarchy

In a monochrome system, the gray scale IS the hierarchy. Max 4 levels per screen:

--text-display (100%) → Hero numbers. One per screen.
--text-primary (90%)  → Body text, primary content.
--text-secondary (60%) → Labels, captions, metadata.
--text-disabled (40%) → Disabled, timestamps, hints.

Red (#D71921) is not part of the hierarchy. It's an interrupt — "look HERE, NOW." If nothing is urgent, no red on the screen.

Data status colors (success green, warning amber, accent red) are exempt from the "one accent" rule when encoding data values. Apply color to the value itself, not labels or row backgrounds. See references/tokens.md for the full color system.

2.6 Consistency vs. Variance

Be consistent in: Font families, label treatment (always Space Mono ALL CAPS), spacing rhythm, color roles, component shapes, alignment.

**Break the pattern in e

Read the complete source ↗