skills.rest
deepeshBodh
deepeshBodhCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

authoring-design-system

Merge design-token extractions into a coherent design system with provenance.

35|2|Updated Dec 31, 2025
Search Tags:#screenshots#tokens#design-system#design-tokens#component-library#design-synthesis#token-consolidation
One-click install
npx skills add https://github.com/deepeshBodh/human-in-loop --skill authoring-design-system
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: authoring-design-system
Source: https://github.com/deepeshBodh/human-in-loop/tree/main/plugins/humaninloop/skills/authoring-design-system
Command: npx skills add https://github.com/deepeshBodh/human-in-loop --skill authoring-design-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrates multiple design-token extractions into a single, coherent design system with clear provenance, eliminating token drift and conflicting definitions across sources.

Core Features & Use Cases

  • Token consolidation across color, typography, spacing, and components from multiple extractions.
  • Conflict tracking and rationale documentation to preserve source decisions.
  • Output of implementation-ready artifacts and system documentation with complete source attribution for audits and handoff.

Quick Start

Run this skill after finishing all extractions to generate a unified design system with provenance and ready-to-code tokens.

Frequently Asked Questions about authoring-design-system

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

FAQPage Schema
How do I consolidate design tokens from multiple extractions into a unified design system?▼

To consolidate design tokens, merge multiple extractions by resolving token and component conflicts, documenting the rationale, and generating an implementation-ready library with source attribution.

What is design token drift and how does merging extractions prevent conflicting definitions?▼

Design token drift occurs when conflicting definitions exist across multiple sources. Merging extractions resolves these conflicts, tracks provenance, and eliminates drift by documenting source decisions and rationale.

How do I track provenance and document rationale when resolving design token conflicts?▼

Tracking provenance during design token conflict resolution involves preserving source attribution for each decision and documenting the rationale to maintain an auditable record of system changes.

Can I generate implementation-ready artifacts and a structured component library from merged design tokens?▼

Yes, merging design tokens generates platform-ready artifacts with complete source attribution and outputs a structured component library designed for direct code integration.

What's the best way to handle color, typography, and spacing token consolidation across different sources?▼

The best approach for consolidating color, typography, and spacing tokens is to merge multiple extractions into a single coherent system that resolves conflicts and documents the rationale for source decisions.

Do I need to finish all design token extractions before assembling a unified component library?▼

Yes, you must finish all extractions first. Running the assembly process after extraction completion generates a unified design system with provenance and ready-to-code tokens.

Related Skills

Explore More Design & Creative Skills→
Markson22Markson22

reversa-design-system

Extract design tokens and documentation from CSS, theme files, and screenshots.

Community
Intermediate
tech-leads-clubtech-leads-club
5.0k

figma-implement-design

Translate Figma designs into production-ready UI code via Figma MCP.

Official
Advanced
1479089714790897
7

kwp-design-design-system

Audit component libraries for naming inconsistencies and missing documentation.

Community
Intermediate
eivindebeivindeb

manual-merge-branches

Merge Git branches with explicit user approval for each conflict resolution.

Community
Advanced