design-token

Identify canon gaps and generate justified design token proposals.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a formal process to propose a new design token when Flintmere's canon does not define a needed token, ensuring justification against existing tokens and alignment with Ledger or Glass canons.

Core Features & Use Cases

  • Evaluates surface needs and identifies gaps in the canon.
  • Presents a complete token proposal with name, value, canonical fit, usage rationale, migration plan, and council sign-off steps.
  • Documents and guides engineering handoff to update canonical files and design systems.

Quick Start

Describe the token need and run the proposal workflow to create a new design-token entry.

Frequently Asked Questions about design-token

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

FAQPage Schema
How do I propose a new design token when my design system canon lacks a definition?

To propose a new design token, you evaluate existing tokens for gaps, determine canonical fit for Ledger or Glass, perform contrast checks, and document a migration plan for Design Council sign-off.

What is the process for identifying design token gaps in a Tailwind token architecture?

Identifying design token gaps involves evaluating surface needs against the existing canon, determining whether the required token fits Ledger or Glass, and generating a justified token proposal with a formal migration plan.

How do I get Design Council sign-off for a token proposal?

You get Design Council sign-off by following a structured workflow that evaluates existing tokens, performs contrast checks, and produces a formal artifact at context/design/tokens with the recommended name, value, and migration steps.

Can I use this workflow to document an engineering handoff for new design tokens?

Yes, the workflow produces a formal artifact at context/design/tokens containing the recommended token name, value, category, and migration steps specifically to guide engineering handoff for updating canonical files.

When should I propose a new token instead of reusing an existing design system token?

You should propose a new token when a design surface requires a token not yet defined in the canon, which you determine by evaluating existing tokens and checking for canonical fit before justifying the gap.

What details are included in a formal design token proposal artifact?

A formal design token proposal artifact includes the recommended token name, value, category, canonical fit, usage rationale, documented migration plan, and required Design Council sign-off steps for engineering implementation.