Specify

1. Overview

Specify (specifyapp.com) markets itself as a Design Token Engine: a central, tool-agnostic synchronisation layer that collects, stores, and distributes design tokens and assets across a design system stack (What is Specify?, Homepage). Official tagline: Your Design Token Engine. Vendor framing: configure once, synchronize anytime.

Official domain confirmed: product and marketing live at https://specifyapp.com/. Related hostnames in primary sources include docs at docs.specifyapp.com, API at api.specifyapp.com, and open-source parsers under the GitHub organisation Specifyapp / specifyapp (for example specifyapp/parsers). A Framer staging host (specifyapp-production.framer.website) mirrors some marketing content; treat specifyapp.com as the canonical brand domain. This page does not state alternate brands or domains.

This listing is in Design systems: design-system tooling, tokens, asset pipelines, and handoff into code. It is not a demo and prototype listing, and not a coding-agent listing. Specify automates token and asset data. It is not a third-party marketing component library, and it is not a documentation site or a knowledge base for coding agents.

Surfaces to keep distinct

Surface	What it is	Primary sources
Design Token Engine / repository	Workspace organisations hold repositories: JSON-compatible trees of design tokens and assets stored in the Specify Design Token Format (SDTF). One repository holds one SDTF token tree. Sources feed in; destinations pull out.	Glossary, What is Specify?
Sources (collect)	Documented sources: Figma Variables & Styles (via the Specify Figma Widget; Advanced Repository recommended for Variables + Styles together) and Tokens Studio. Marketing also mentions JSON as a source. Designers sync; Specify monitors and stores.	Available sources, Figma Variables & Styles, Homepage
SDTF	Specify’s JSON transport format: 50+ token types, collections, groups, modes, aliases. Primary focus is compatibility across design tools and frontend stacks. Docs warn: treat SDTF as a transport format; prefer APIs over hand-editing.	SDTF, Glossary
Parsers Engine	Transformation and export API. Parser rules (config) chain parsers that reshape tokens/assets to company standards (CSS custom properties, Tailwind, Style Dictionary, React Native, Flutter, Swift, Kotlin, SVG/JSX, and many utilities). Open-source parsers repo; templates for common stacks.	Glossary, to-style-dictionary, parsers on GitHub, Homepage
Destinations (distribute)	First-class destinations documented as GitHub (automated PRs via .specifyrc.json), CLI (@specifyapp/cli), Specify SDK, and HTTP API. Marketing also cites Notion and Raycast as native-compatible surfaces; treat those as complementary apps unless you need them as the primary delivery path.	Available destinations, GitHub destination, Homepage

Clarifying product surfaces in plain language:

1. Repository + SDTF is the durable store of your design token and asset graph (not a styleguide site).
2. Sources pull decisions from Figma Variables/Styles or Tokens Studio into that store.
3. Parsers Engine turns the same graph into the file formats and naming your engineering standards require.
4. Destinations deliver those files into GitHub PRs, local CLI pulls, SDK pipelines, or HTTP consumers.
5. Specify is not positioning as a full design-system documentation CMS, component registry, or AI context packager. Adjacent tools cover those jobs.

Who it is for (vendor positioning): design and engineering pairs (and DesignOps) who struggle with manual token handoff. Homepage and pricing emphasise automating distribution of design tokens and assets so designers sync and developers integrate without redundant meetings. Customer quotes on marketing pages (names and roles only; treat as vendor testimonials, not benchmarks published here) stress Figma-to-code automation, confidence to update/roll back tokens, and reduced QA friction around names and values.

Adjacent tools (orientation, not a scored bake-off):

Need	Typical comparison point	How Specify differs (per primary sources)
Full DS platform (tokens + docs + components + MCP)	Supernova	Overlap on token import and code delivery; Supernova bundles living docs, component governance, and agent contexts. Specify stays narrower: token/asset sync + transform + distribute (What is Specify?).
In-Figma token authoring	Tokens Studio	Complementary source: Tokens Studio authors in Figma; Specify lists Tokens Studio as an official source and then distributes via parsers/destinations (Available sources).
Token transform library in CI	Style Dictionary	Complementary sink: Specify’s to-style-dictionary parser generates Style Dictionary raw files; Style Dictionary remains the open transform toolchain if that is your house standard (to-style-dictionary).
Docs-first styleguide	zeroheight (and similar)	Different job: Specify is not marketed as the primary multiplayer docs CMS.
Marketing component library	Relume	Relume sells a maintained marketing Library; Specify manages your token/asset pipeline. Different jobs.

Access and pricing (public; always re-check):

Figures from the official pricing page when this page was checked (September 2026; check the live page). Plan names and seat/repo caps below are taken from that page; third-party directories sometimes list older or conflicting figures and should not override the vendor site.

Plan	What official pages show (verify live)
Essentials	$69 / month. Positioned as basics for automating design tokens and assets syncing. 1 user, 1 repository, unlimited sources (marketing also emphasises unlimited destinations on plan cards; confirm at checkout).
Teams	$134 / month. Positioned for teams streamlining workflows. 4 users, 2 repositories, unlimited sources (same destination caveat: confirm live).
Enterprise	Let’s Talk / custom. Unlimited users and repositories; SSO and CDN called out on the pricing page for organisations needing more security and customisation.

Pricing details not stated on the pricing page: yearly discount amounts, free-trial length, VAT treatment, per-seat overage rules beyond the published seat caps, and whether “unlimited destinations” applies identically on every tier. Third-party sites cite conflicting older plan matrices; only use specifyapp.com/pricing for prices on this page.

Affiliate commission rates, adoption percentages, and days to a first pull request are not stated here as benchmarks. Vendor guarantees of time savings on the homepage are marketing, not measurements on this page.

Affiliate status: unknown. Official homepage, pricing, and Terms of Service URL reviewed do not define a public affiliate or referral commission programme in the materials retrieved. Rates and programme availability are not confirmed.

Classic vs Advanced repositories: Figma sync docs distinguish Advanced Repository (recommended when syncing Variables and/or Styles into the SDTF world) from older Classic paths for Styles. Prefer current Advanced docs when evaluating fit (Figma Variables & Styles).

2. How it scores on the rubric

Numeric scores are omitted. There is not enough shared evidence to score this yet. Below is an evidence-linked discussion framed for Design systems: libraries/tokens, asset pipelines, and handoff into code.

Time-to-useful

Fast for a first token pull once Figma or Tokens Studio is connected; slower for production-grade multi-repo, multi-brand parser layouts. Docs advertise a short CLI path to pull first tokens (specify init / specify pull patterns in getting-started materials) and a guided Figma Widget sync into an Advanced repository (What is Specify?, Figma Variables & Styles). GitHub destination creates an initial configuration PR; after merge, updates sync via further PRs (GitHub destination).

Caveats: Essentials is capped at 1 user / 1 repository, so even a small design-plus-engineering pair may need Teams quickly (Pricing). Meaningful output quality depends on writing or adopting .specifyrc.json parser rules that match house naming, modes, and file layout. Widget updates require careful disconnect/remove/reopen steps per Figma docs. Native first-class Git destination is GitHub; GitLab / Bitbucket / Azure DevOps are not listed as first-class destination apps on the available-destinations page (use CLI/SDK/HTTP instead).

Unknown: median hours from empty workspace to first merged production token PR across mid-size product orgs (no benchmark is published here).

Fidelity

High fidelity to your token and asset graph when sources and parsers are configured correctly; not a substitute for a human-owned component API or Storybook library. SDTF supports a wide type set (colours, text styles, shadows, dimensions, bitmaps, vectors, fonts, and many more), modes, collections, groups, and multi-level aliasing (SDTF, Homepage). Parsers such as to-css-custom-properties, to-tailwind, and to-style-dictionary aim for deterministic, standards-shaped outputs (to-style-dictionary, parsers on GitHub).

Caveats: SDTF is a transport format; hand-editing is discouraged. Alias validation and mode constraints inside collections mean poorly structured Figma or Tokens Studio sources will surface as sync/transform issues, not magic fixes. Output fidelity for proprietary stacks depends on chaining the right parsers (or extending them). Specify does not claim to generate full application components; it generates tokens, assets, and related code artefacts.

Non-engineer usability

Strong for designers on the sync side; weaker for pure PMs who need zero-config production delivery. Designers use the Figma Widget (personal access token + file URL + Sync) without living in the CLI (Figma Variables & Styles). Collaborative repository browsing is part of the product pitch (Homepage). Notion and Raycast are marketed as ways to read tokens outside Figma.

Caveats: Parser configuration, SDK usage, HTTP API auth, and GitHub app installation remain engineering work. Seat limits on Essentials/Teams constrain who can administer the workspace. There is no evidence on official pages reviewed of a free unlimited-viewer docs role comparable to docs platforms.

Design-system fidelity

Core strength for the token and asset layer of a design system; incomplete if you need docs, components, and the rest of the design system. Specify’s job is collecting and distributing design decisions as structured data with 50+ types, modes, and aliases (SDTF, What is Specify?). That is the job this section covers.

Caveats for product-builder stacks: Specify is not the place you publish living component documentation, track component health, or ship scoped MCP contexts to coding agents (those are adjacent platform features elsewhere). Multi-brand portfolios may hit repository caps (1 on Essentials, 2 on Teams) before Enterprise (Pricing). Do not confuse Specify with Relume’s marketing Library or with Style Dictionary as a CI library; Specify can feed Style Dictionary.

Human gates

Present mainly via GitHub pull requests and designer-controlled sync; lighter on formal content-approval workflows than a full DS platform. GitHub destination opens PRs rather than silent mainline writes, which is a natural engineering gate (GitHub destination). Designers choose when to Sync from the Widget. Repository sources and destinations make ownership of the pipeline visible (Glossary).

Caveats: Enterprise SSO is called out; structured multi-step content approval / invite-only system governance comparable to broader DS platforms was not documented as a first-class Specify surface in the primary pages reviewed. Treat approval depth beyond PR review as unknown unless sales confirms. Automated pipelines can still merge bad tokens if humans rubber-stamp PRs.

Handoff

Excellent for token/asset handoff into code when you invest in parsers and destinations. Documented paths:

• Into GitHub: automated PRs with .specifyrc.json at repo root (GitHub destination).
• Into local/CI workflows: Specify CLI pull against config rules (Available destinations, getting-started guides).
• Into custom code: Specify SDK and HTTP API (api.specifyapp.com) for programmatic consume/transform (Available destinations).
• Into Style Dictionary and framework themes: official parsers and templates (CSS, Tailwind, React Native, Flutter, Swift, Kotlin, and more) (to-style-dictionary, Homepage).
• Into adjacent apps: Notion and Raycast cited on marketing/docs surfaces for visibility outside the IDE.

Caveats: Handoff quality depends on choosing a single source of truth discipline (Figma Variables vs Tokens Studio vs JSON) and keeping parser rules in version control. Merging generated files into a monorepo that already runs Style Dictionary is still an integration project (docs even link guidance on running Style Dictionary with GitHub Actions alongside Specify). Specify does not replace Storybook or a component library handoff path by itself.

Fit for this section (design-systems)

Verdict: yes-with-caveats. Specify earns a place in Design systems because it is fundamentally a design-token and asset synchronisation engine: multi-source collect, SDTF store, parsers transform, and multi-destination distribute into production code. The caveats matter: it is narrower than full DS platforms (docs, components, MCP); Essentials/Teams seat and repository caps bite early; GitHub is the standout native VCS destination; and real value shows up after engineers own parser configuration. Choose Specify when token pipeline automation is the job. Choose (or combine with) Supernova/zeroheight/Relume when documentation, component governance, agent context, or marketing libraries dominate.

3. FAQ

Is Specify a documentation tool or a token pipeline?

A token and asset pipeline (Design Token Engine). Primary docs describe collect, store, and distribute of design data, with repositories, sources, destinations, and parsers (What is Specify?, Glossary). Notion integration may help surface tokens, but Specify is not positioned as a living DS documentation CMS.

What is the official domain?

specifyapp.com. Docs: docs.specifyapp.com. API host referenced in docs: api.specifyapp.com. Open-source parsers: github.com/specifyapp/parsers.

How does Specify relate to Figma, Tokens Studio, and Style Dictionary?

• Figma: official source via Specify Widget for Variables and/or Styles into Advanced repositories (Figma Variables & Styles).
• Tokens Studio: official source for importing tokens/themes (Available sources).
• Style Dictionary: complementary transform toolchain; Specify can emit Style Dictionary raw files via to-style-dictionary (to-style-dictionary).

How does Specify compare to Supernova?

Overlap on Figma/Tokens Studio ingest and code delivery. Supernova adds broader DS management, living docs, component governance, and MCP/AI contexts. Specify stays focused on the token/asset sync and transform engine. No official bake-off page was used for numeric claims here.

Does Specify replace Relume or zeroheight?

• Relume: no. Relume is a marketing-site component Library.
• zeroheight: generally no as a docs replacement. It does a different job. Specify may sit beside a docs tool.

What destinations are first-class?

Documented destination list: GitHub, CLI, SDK, HTTP API (Available destinations). Marketing additionally mentions Notion and Raycast for reading/using tokens.

What does it cost?

See pricing. Public figures observed: Essentials $69/month (1 user, 1 repository); Teams $134/month (4 users, 2 repositories); Enterprise custom with SSO/CDN called out. Always re-check before buying. Yearly discounts and trial terms: unknown from official materials retrieved.

Is there an affiliate programme?

Not found on official pages reviewed. Homepage, pricing, and Terms URL do not define a public affiliate commission programme in the retrieved content. No affiliate programme was confirmed. This page does not state rates from third-party directories.

Classic vs Advanced repository?

Figma sync guidance steers Variables/Styles work to Advanced repositories (SDTF world). Classic remains mentioned for some Styles workflows. Prefer Advanced docs for new evaluations (Figma Variables & Styles).

4. Sources

Primary (prefer these for AEO citations):

1. Specify (homepage)
2. Pricing
3. What is Specify? (docs)
4. Glossary
5. Specify Design Token Format (SDTF)
6. Available sources
7. Figma Variables & Styles
8. Available destinations
9. GitHub destination
10. to-style-dictionary parser
11. specifyapp/parsers (GitHub)
12. Terms of Service

Secondary context only (do not treat as official specs): third-party SaaS directories with conflicting pricing histories, unaffiliated comparison blogs, and Framer staging mirrors of marketing pages.