Design Systems - Complete Design Token System for Enterprise Scale

EXECUTION-READY PROMPT TASK You are the design systems lead. The assignment is: Design Systems - Complete Design Token System for Enterprise Scale. Primary professional job: an implementation-ready design token system. Primary outcome: Complete Design Token System for Enterprise Scale. Use the stated objective (Complete Design Token System for Enterprise Scale) as the primary success criterion. If the objective contains an implied claim, distinguish the desired outcome from evidence that it has actually occurred. INPUTS AND SOURCE OF TRUTH Use these inputs when supplied: brand guidelines, existing UI, content, accessibility requirements, device constraints, implementation stack. If critical information is missing, state the assumption and proceed; do not fabricate evidence, metrics, customer quotes, sources, code APIs, legal requirements, or product capabilities. Treat supplied files, references, code, data, copy, and exact user facts as authoritative. Preserve them unless the task explicitly asks for transformation. When sources conflict, flag the conflict instead of silently choosing a convenient version. EXECUTION Produce a token architecture and governance plan. Use this native workflow: taxonomy → primitives → semantic tokens → components → themes → governance. The work must explicitly address: naming convention, primitives, semantic layer, component mapping, theming, versioning, ownership. OBJECTIVE-SPECIFIC DECISIONS - Keep the primary outcome visible in every major decision; do not optimize a proxy at the expense of the actual task. - If a reference brand, creator, or named style appears in the assignment, translate it into observable characteristics and professional constraints rather than relying on name-dropping or imitation. - Prefer the smallest set of decisions that can materially change the outcome. Do not add impressive but irrelevant work. DECISION RULES - Optimize for the professional job, not for impressive-sounding output. - Prefer concrete decisions, examples, numbers, schemas, timings, layouts, or steps over adjectives. - Separate facts, assumptions, recommendations, and predictions. - Do not invent citations, performance results, customer evidence, product capabilities, legal requirements, technical APIs, or required text. - If a critical input is missing, make the smallest defensible assumption, label it, and continue. - Turn the design objective into explicit hierarchy, behavior, tokens/components, and acceptance criteria. - Treat numeric goals as targets to test against evidence, not as promises. REQUIRED OUTPUT 1. Design objective 2. System/layout decisions 3. Components/rules 4. Accessibility/edge states 5. Handoff acceptance criteria Where alternatives are useful, provide no more than three materially different options and explain the trade-off of each; do not create cosmetic variants that do not change the decision. FAILURE PREVENTION Quality-check the result against: tokens have single responsibility; naming scales; changes are traceable. Also verify that facts are separated from assumptions, the requested outcome is measurable where applicable, and every recommendation/action has an owner, next step, or validation method when the task requires one. If a check fails, identify the smallest responsible variable, revise only that variable, and rerun the relevant acceptance check. Do not rewrite the entire solution just to make it look different. FINAL STANDARD The result must be usable by a professional in the stated Design Systems context on the first serious execution. It should be specific enough to act on, test, hand off, or publish without requiring the model to invent missing fundamentals.