atlassian-mcp-server

Atlassian Design System (ADS) for artifacts

Use this skill to make an artifact look and read like an Atlassian app (Jira, Confluence, Loom, Atlas style): pages, dashboards, prototypes, mockups, trackers and reports.

This skill is distilled from the official ADS MCP server (https://mcp.atlassian.com/v1/ads/public/mcp) and the @atlaskit/tokens, @atlaskit/button, @atlaskit/lozenge, @atlaskit/smart-card and @atlaskit/icon packages. Token values match @atlaskit/tokens 20.x.

How this fits with other skills

Non-negotiables

  1. Never hard-code a color, space, radius, shadow or font value. Use the --ds-* custom properties in render_kit/tokens.css. If you need a value it doesn’t have, pull it from the npm package (see “Getting any other token” in references/hand-built.md).
  2. Choose tokens by role, not by how they look. Brand is for primary actions and selection. Danger, warning, success, information and discovery carry meaning. Accents (blue, teal, green, lime, yellow, orange, red, magenta, purple, gray) are for categories and user-chosen colors only.
  3. Support light and dark. Every token has a dark value. Ship both.
  4. Use sentence case everywhere: titles, headings, buttons, tabs, labels and menu items. Use all caps only for acronyms and the legacy lozenge.
  5. Meet WCAG AA. Text under 24px needs 4.5:1 contrast. Large text and essential UI need 3:1. Never use color alone to carry meaning.
  6. Every link to a page, work item or other object is an inline smart link. Never show a bare URL, a plain blue text link or “click here”. A renderer builds them from the link data in references/data-format.md. By hand, follow “Smart links” in references/hand-built.md.

Content (voice and writing)

Where to go next