dcyfr-design-tokens

Enforce DCYFR design token usage via ESLint rules and PR reviews.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dcyfr/dcyfr-labs --skill dcyfr-design-tokens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dcyfr-design-tokens
Source: https://github.com/dcyfr/dcyfr-labs/tree/main/.opencode/skill/dcyfr-design-tokens
Command: npx skills add https://github.com/dcyfr/dcyfr-labs --skill dcyfr-design-tokens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In DCYFR projects, design consistency is often compromised by hardcoded Tailwind values, leading to visual drift and maintenance overhead.

Core Features & Use Cases

  • Detect and flag hardcoded values (gap-8, text-3xl, max-w-4xl, etc.)
  • Replace with tokens from @/lib/design-tokens
  • Validate color, spacing, typography, and container widths
  • Provide ESLint auto-fix guidance for common violations
  • Use cases include fixing token violations, converting legacy code, and reviewing PRs for token compliance

Quick Start

Install dependencies and run npm run lint to start enforcing design-token usage across the codebase.

Frequently Asked Questions about dcyfr-design-tokens

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

FAQPage Schema
How do I prevent hardcoded Tailwind values in my design system?

To prevent hardcoded Tailwind values, use this Skill to enforce design token usage. It detects and flags values like gap-8 or text-3xl during linting, replacing them with tokens from your design-tokens library to maintain visual consistency.

Can ESLint automatically fix design token violations in PR reviews?

Yes, ESLint can automatically fix design token violations. This Skill provides ESLint auto-fix guidance for common violations, validating color, spacing, typography, and container widths during PR reviews and component development.

What are design tokens and when do I need them for component development?

Design tokens are centralized variables for spacing, typography, containers, and colors. You need them during component development to prevent visual drift and reduce maintenance overhead caused by hardcoded values in your codebase.

Does this design token linter work with OpenCode workflows?

Yes, this design token linter integrates with OpenCode workflows. It satisfies token import validation and consistent naming conventions through automated ESLint checks specifically tailored for OpenCode-specific development environments.

What's the best way to convert legacy code to use a design-tokens library?

The best way to convert legacy code is running npm run lint to enforce design-tokens library usage. This automatically identifies hardcoded values and provides replacement guidance to ensure token compliance across the codebase.