sworm-design

Codify Sworm design tokens and component recipes to prevent UI drift.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/TophC7/Sworm --skill sworm-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sworm-design
Source: https://github.com/TophC7/Sworm/tree/main/.claude/skills/sworm-design
Command: npx skills add https://github.com/TophC7/Sworm --skill sworm-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sworm Design System codifies tokens, surfaces, typography, shadows, motion, and iconography into a single source of truth to prevent UI drift across projects.

Core Features & Use Cases

  • Tokens, surfaces, and type scale are used to ensure visual consistency across components.
  • Encapsulated design rules govern shadows, motion, and iconography for coherent surfaces and interactions.
  • Use Case: when implementing or refactoring UI in Sworm, apply the design system tokens and primitives for cohesive visuals.

Quick Start

Review and align all UI work with the Sworm Design System tokens and primitives whenever editing UI code.

Frequently Asked Questions about sworm-design

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

FAQPage Schema
How do I prevent UI drift across multiple Tailwind projects?

To prevent UI drift, you need a single source of truth for design tokens. Codifying tokens, surfaces, and component recipes ensures visual consistency across projects by requiring components to consume shared UI primitives.

What are design tokens and how do they enforce visual consistency?

Design tokens are codified variables for typography, shadows, motion, and surfaces. They enforce visual consistency by acting as a single source of truth that components consume, preventing misaligned styling across different files.

How do I refactor UI components to use design system primitives?

Refactoring UI components involves aligning them with defined design tokens and primitives. You update component files to consume shared UI primitives and live tokens from your stylesheet, ensuring all visual outputs match the canonical design language.

Do I need a canonical design language defined before applying design tokens?

Yes, you need a canonical design language defined in your documentation and live tokens in your stylesheet. Without these foundational elements established, the design system cannot effectively enforce visual consistency across components.

What's the best way to manage UI tokens for a Tailwind design system?

The best way to manage UI tokens is codifying them into a single source of truth within your stylesheet. Encapsulating rules for shadows, motion, and iconography alongside tokens ensures coherent surfaces and consistent interactions.

Why does my UI look inconsistent after refactoring app.css?

Your UI looks inconsistent because components are likely not consuming the live tokens defined in your stylesheet. You must ensure all components use shared UI primitives and align with the canonical design language to prevent drift.