agentsclimarketplace

Tailwind design tokens

Skill TheGoat395/Codex-Skills/skills/tailwind-design-tokens

Codex-first Agent Skills library for premium frontend, website, motion, accessibility, QA, and handoff workflows.

Install
npx -y skills add TheGoat395/Codex-Skills --skill tailwind-design-tokens

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.0 KB, as published. Nobody here has run it

Tailwind Design Tokens

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.
  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.

Reference

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.