Atlaskit
Atlassian's design system, behind Jira and Confluence.
Atlaskit is the component layer of the Atlassian Design System, the one behind Jira, Confluence and Bitbucket. It is distributed as many small packages rather than one library, which is unusual and deliberate.
At a glance
| Install | per package, e.g. npm install @atlaskit/button |
| Tokens | @atlaskit/tokens, the single source of design decisions |
| Structure | components, tokens, primitives and tools as separate packages |
| Docs for agents | llms.txt plus a dedicated llms-tokens.txt |
| Licence | Apache-2.0 |
| MCP server | not published |
The token package is the interesting part
Atlassian split its design decisions into @atlaskit/tokens and treats that package as the source of truth, above the components. You can adopt the token layer without adopting a single component, which makes it viable as a foundation for a design system that does not look like Jira.
That separation is documented well enough that Atlassian publishes a llms-tokens.txt alongside its main llms.txt, one of very few libraries here to split its agent documentation by concern.
Per-package installation cuts both ways
You install only what you use, which keeps bundles honest on a large application. You also manage many version numbers instead of one, and cross-package compatibility becomes your problem during upgrades.
Choose it if
- You build Atlassian Forge or Connect apps and need to match the host product.
- You want a mature token architecture to build your own system on.
- Apache-2.0 suits your legal review.
Look elsewhere if
- You want one package and one version to track.
- You need a neutral look. The components carry Atlassian's visual language.
