







This document describes the technical specification for a file format to exchange design tokens between different tools.
Inside Design Tokens: Token Specification
Design tokens become scalable when they are replicable. A token specification is a formula for achieving design tokens scalability and tools interoperability.
Inside Design Tokens: Definitions & Traits
Over the past three years, I’ve researched design tokens for usage in Theemo and I’m sharing my discoveries in this article series.
Design system doc spec 0.15.2
A machine-readable format for design system documentation. DSDS structures components, tokens, themes, foundations, patterns, and guides as a single source of truth for humans, parsers, and agents.

Inside Design Tokens: Modeling & Communication
Design system architecture with focus on design tokens, that form the vocabulary of your visual design language, helping to streamline the communication amongst stakeholders. Modeling the system with boundaries to ensure clear purpose and predictability for design tokens and stability guarantees wit
Inside Design Tokens: The Three Class Token Society
Design tokens are often grouped based on their phenomenal reference sequence. From basic, over semantic to component tokens. This article compares this organization with a model based architecture and figures out the advantages and disadvantages.
Procedural Tokens — encoding design decisions
Most design tokens hold a value. The interesting ones hold a rule. A live walk from static refs to procedural tokens.
Inside Design Tokens: Put your Tokens on a Scale
Ever worked with a set of design tokens that are super inconsistent and hardly distinguishable? Perhaps a wrong scale? This article explains the available scales, their problems and what to use them for.
Inside Design Tokens: Features
Features encode user preferences, inherit behavior(s) and are communicated by several principals through agents. Design tokens may or may not support features.
Inside Design Tokens: Naming
Naming design tokens can sometimes be considered its own discipline. Naming is surprisingly straight forward, and if it isn't then it solves the wrong problem.
LLMs as Collaborators in Language Specification and Design (PLSS 2026) - SPLASH/ISSTA 2026
Workshop on Programming Language Standardization and Specification This workshop aims to foster cross-pollination between researchers and industry professionals with experience in programming language specification and standardization. It provides a forum where participants can share insights, case studies, and best practices, and collaboratively explore solutions to current challenges. The goal of the workshop is to improve the collective understanding of how programming languages are specified, standardized, and evolved in practice. The workshop examines specifications as the foundation ...

Inside Design Tokens: Internals
Tokens not only have a name and a value, they carry on a lot more data, which when given proper meaning is a knowledgeable resource.
steve.prophet on Twitter / X
so get smart about how you generate code... example token analysis of compilation output.model generates DSL / intermediate format, compiler turns it into actual runtime code.need to only generate 796 tokens to deploy 8,265 tokens.10x+ token difference (!!) https://t.co/LAAPjFX9Sc pic.twitter.com/zMoOrWb6yf— steve.prophet (@nilslice) March 18, 2026
Friendly Forge Format (F3) — F3 v4.0 documentation
The Friendly Forge Format (abbreviated F3) is an Open File Format for storing the information from a forge such as issues, pull/merge requests, milestones, release assets, etc. as well as the associated VCS (Git, Mercurial, etc.).
Concise Binary Object Representation (CBOR)
The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack. This document obsoletes RFC 7049, providing editorial improvements, new details, and errata fixes while keeping full compatibility with the interchange format of RFC 7049. It does not create a new version of the format.
Inside Design Tokens: The Hidden Knowledge
Tokens contain a lot of information and even more the relationship between tokens. Making sense of this information is the hidden knowledge living within tokens. Unlocking this knowledge is the next evolution step for design tokens.