skills.rest
artosetrov
artosetrovCOMMUNITY
Explore all skills by this author →
GitHub

ds-ecosystem

Create a 10-stage Figma design system plan aligned with implementation code.

Updated Mar 5, 2026
Search Tags:#workflow#components#figma#tokens#design-system#design-ops#parity
One-click install
npx skills add https://github.com/artosetrov/iron-fist-arena-backend --skill ds-ecosystem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ds-ecosystem
Source: https://github.com/artosetrov/iron-fist-arena-backend/tree/main/.claude/skills/ds-ecosystem
Command: npx skills add https://github.com/artosetrov/iron-fist-arena-backend --skill ds-ecosystem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This plan provides a master, repeatable blueprint to construct and orchestrate a complete Figma ecosystem for Hexbound, ensuring all stages from audit to QA are covered and aligned with code.

Core Features & Use Cases

  • 10-stage pipeline covering UI audit, Foundations, Tokens, Components, Screens, Consistency, File Structure, Naming, Prototype, and QA.
  • Acts as a master orchestrator to guarantee parity with implementation code and full screen/token coverage.

Quick Start

Follow the 10-stage master plan to assemble the complete Figma ecosystem for Hexbound.

Frequently Asked Questions about ds-ecosystem

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

FAQPage Schema
How do I build a Figma design system that stays aligned with implementation code?▼

Building a Figma design system aligned with implementation code requires a structured workflow covering UI audit, foundations, tokens, components, screens, consistency, file structure, naming, prototype, and QA to guarantee parity.

What is the workflow for establishing design tokens and component parity in Figma?▼

Design tokens and component parity are established through a 10-stage pipeline that systematically processes UI audit, foundations, tokens, components, screens, consistency, file structure, naming, prototype, and QA stages.

What's the best way to audit existing UI components before structuring a design system?▼

The best way to audit existing UI components is applying the first stage of the 10-stage DS ecosystem workflow, which evaluates current components before establishing foundations, tokens, and subsequent system architecture.

How do I ensure naming consistency and file structure across a Figma design system?▼

Naming consistency and file structure are ensured by executing dedicated stages within the 10-stage DS ecosystem workflow, which standardizes naming conventions and file organization to maintain design system parity.

Can I create a testable Figma prototype with full token coverage using a single workflow?▼

Yes, you can create a testable Figma prototype with full token coverage by following the master orchestration workflow, which delivers a wired prototype and guarantees full screen and token coverage through QA.

Related Skills

Explore More Design & Creative Skills→
HellKaiser45HellKaiser45

figma-generate-library

Automate Figma design system creation and synchronization from codebase tokens.

Community
Advanced
CharitablebusinessroninCharitablebusinessronin

figma-implement-design

Translate Figma designs into project UI components with design tokens.

Community
Advanced
jg-chalk-iojg-chalk-io

moai-design-systems

Automate design system creation and validation with tokens, components, and WCAG 2.2 checks.

Community
Advanced
ImL1sImL1s
6

figma-implement-design

Translate Figma designs into production-ready UI code using design tokens.

Community
Advanced