design-jina-anne

Structure design tokens into primitives, semantic aliases, and component-scoped layers.

Updated May 6, 2025
One-click install
npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill design-jina-anne
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-jina-anne
Source: https://github.com/rodrigo-altissimo/qiartificial/tree/main/.claude/skills/design/jina-anne
Command: npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill design-jina-anne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the challenge of building maintainable, multi-platform design token systems by turning scattered design decisions into a governed, layered architecture with consistent naming and delivery.

Core Features & Use Cases

  • Token architecture and layering: Design global (primitive) → alias (semantic) → component tokens to prevent brittle systems and enable safe evolution.
  • Taxonomy, naming, and governance: Establish taxonomy structure and naming conventions, then document how tokens are created, reviewed, and deprecated.
  • Multi-platform delivery and migration: Plan how one source of token truth propagates to web, iOS, Android, and tooling, including incremental migration from legacy variables.

Quick Start

Activate the design-jina-anne skill to define your token taxonomy, naming rules, and a multi-platform delivery strategy for your design system.

Frequently Asked Questions about design-jina-anne

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

FAQPage Schema
What is design token taxonomy and how does multi-platform delivery work?▼

Design token taxonomy structures design decisions into global primitives, semantic aliases, and component-scoped tokens, enabling multi-platform delivery by propagating one source of truth to web, iOS, Android, and tooling.

How do I structure a design token architecture to prevent brittle systems?▼

To structure design token architecture, you layer global primitives, semantic aliases, and component-scoped tokens, creating a governed taxonomy that prevents brittle systems and enables safe multi-platform evolution.

What's the best way to migrate from hard-coded values to a design token system?▼

The best way to migrate from hard-coded values is planning an incremental migration strategy that maps legacy variables to a governed, layered token architecture aligned with the W3C Design Tokens approach.

Does this approach support design system governance and naming conventions?▼

Yes, this approach supports design system governance by establishing taxonomy structure and naming conventions, then documenting governed workflows for how tokens are created, reviewed, and deprecated.

Can I use W3C Design Tokens format for multi-platform delivery planning?▼

Yes, you can use the W3C Design Tokens format for multi-platform delivery planning by producing platform delivery mappings that propagate a single source of token truth across web, iOS, and Android environments.

When do I need to audit design token naming conventions?▼

You need to audit design token naming conventions when refining a token system for multi-platform delivery, ensuring semantic aliases and component-scoped tokens align with your established taxonomy and governance workflows.