git:20260621.2caaecc to git:20260905.f7824ba

10 added, 14 removed. Audit A to A.

---

name: "tailwind-design-tokens"

- description: "Create token-driven Tailwind and CSS variable systems for premium websites. Use for color tokens, typography tokens, spacing rhythm, radius, shadows, gradients, surfaces, responsive constraints, dark/light modes, and avoiding random utility-class styling."

+ description: "Map semantic tokens into Tailwind utilities."

---

# Tailwind Design Tokens

+ For substantial web work, reuse the [scoped web contract](../website-operating-rules/references/scoped-web-contract.md) when available; it replaces duplicated policy here. Match the requested scope and existing decisions; a missing optional sibling does not block this local procedure.

## Overview

Make Tailwind feel like a design system, not utility confetti. Tailwind is fast, but the taste comes from tokens, constraints, and repeated decisions.

- ## Website Nonnegotiables

- - Inspect before coding: structure, framework, homepage or main entry file, styling system, JavaScript or interaction system, assets, and build commands.

- - Before major changes, explain planned files and wait unless the user clearly says proceed, build, create, implement, or fix.

- - Use existing project conventions first. Explain major new dependencies before adding them.

- - Never ship generic visual work: no default card grids, placeholder copy, weak type, random gradients, stock-like media, or template heroes.

- - Build version 1, inspect the rendered result, improve spacing, type, hierarchy, motion, media, hover states, and responsiveness, then run checks again.

- - Run available lint, build, and test commands when possible. Report commands, changed files, and any untested areas honestly.

- - Check desktop and mobile. Respect accessibility, semantic markup, focus states, and reduced-motion preferences.

## Workflow

- 1. Read the user's brief and identify the website category, audience, content reality, visual references, and asset availability.

+ 1. Identify the requested component or architecture outcome, affected files and existing decisions; reuse established content and visual direction.

2. Inspect the project before editing when code exists.

3. Apply this skill's specific rules from `references/tailwind-design-tokens-guide.md`.

- 4. Explain planned files before major changes unless the user has clearly said to proceed.

- 5. Build, inspect, polish, and verify before final delivery.

+ 4. Explain material implementation choices while continuing authorized work.

+ 5. Implement when requested, inspect affected output, fix observed defects, and run the smallest decisive relevant checks.

## Reference

Read `references/tailwind-design-tokens-guide.md` when this skill triggers for a concrete website build, redesign, visual review, or implementation plan.

+ ## Ownership

+ Own token consumption by the installed Tailwind version and mapping to utilities/aliases. Use `design-token-production-pipeline` only when generation, validation or multiple output consumers require a compiler contract.