adi-design

Apply Adi's personal design language and CSS tokens to UI surfaces across his apps.

25|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/wisdom-in-a-nutshell/agents --skill adi-design-wisdom-in-a-nutshell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adi-design
Source: https://github.com/wisdom-in-a-nutshell/agents/tree/main/skills-source/owned/adi-design
Command: npx skills add https://github.com/wisdom-in-a-nutshell/agents --skill adi-design-wisdom-in-a-nutshell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Keeping multiple personal apps visually consistent is hard: colors drift, generic warm-cream AI defaults creep in, and each stack consumes design tokens differently. This Skill provides Adi's complete design identity — palette, typography, spacing, radius, and motion rules — as vendored CSS tokens plus a written design language, so every UI he builds or restyles looks like one cohesive product. ## Core Features & Use Cases - Vendored design tokens: assets/tokens.css ships oklch color tokens (sage accent, amber secondary, rose for rare alerts), Newsreader/Inter font stacks, spacing, radius, and motion variables with light and dark modes. - Written design language: references/design-language.md documents the aesthetic rationale, hard rules (no warm-cream backgrounds, one accent only, cards under ~16px radius), accessibility contrast requirements, and per-product notes. - Per-stack integration guidance: instructions for consuming tokens in plain CSS projects and Tailwind/shadcn setups, including mapping variables into a Tailwind theme. - Use Case: When restyling a page on adithyan.io, import the tokens, point the Tailwind theme at the CSS variables, swap body copy to Newsreader, and verify the result against the hard rules — no cream background, sage as the only accent. ## Quick Start Use the adi-design skill to restyle this page with Adi's design tokens, replacing the background with the off-white variable and setting sage as the single accent color.

Frequently Asked Questions about adi-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply a design token system to a Tailwind project?▼

Import the tokens.css file for the CSS variable definitions, then point the Tailwind theme at those variables, for example mapping colors like bg and accent to var(--bg) and var(--accent). Swap fonts to Newsreader for reading and Inter for UI chrome.

How do I keep multiple personal apps visually consistent?▼

Share one vendored tokens.css file across every app and reference variables instead of raw hex or oklch values. Keep app-specific colors like chart palettes in a small local tokens.local.css layered after the core tokens.

Does this design system support dark mode?▼

Yes, the tokens define dark overrides via prefers-color-scheme media queries. Dark mode uses a warm-neutral charcoal background rather than green or pure black, with adjusted accent, amber, and rose values.

Why does colored text fail contrast checks in my UI?▼

Base accent, amber, and rose fills do not clear the 4.5:1 ratio as small text. Use the -ink variants such as --accent-ink for links, labels, and white-on-color buttons, which are tuned to pass AA.

When should I not add colors to the shared design tokens?▼

Product-specific colors like chart series or map phase colors do not belong in the shared tokens file. Keep them in a per-product tokens.local.css layered after the core so the shared identity stays universal.