sapphire-design

Included with Lifetime

$97 forever

Approximate the Danske Bank Sapphire design system using plain CSS and HTML, without installing @danske/sapphire-* packages. Use this skill whenever the user asks to build UI that should look like Sapphire, match Danske Bank's design system, create Sapphire-styled components, or wants banking/fintech UI with a Scandinavian design language. Also trigger when the user mentions 'sapphire tokens', 'sapphire components', or wants to create UI prototypes that follow the Sapphire visual style. This skill is framework-agnostic and works with any frontend stack.

Design

What this skill does


# Sapphire Design System (Lightweight Approximation)

This skill teaches you how to build UI that closely matches Danske Bank's Sapphire design system using only CSS custom properties and plain HTML/CSS patterns. No npm packages required.

The real Sapphire system uses `@danske/sapphire-react`, `@danske/sapphire-css`, `@danske/sapphire-design-tokens`, and `@danske/sapphire-icons`. This skill extracts the essential design tokens, component patterns, and icon catalog so you can replicate the look and feel in any framework (React, Vue, Svelte, plain HTML, etc.).

## Quick Start

Every Sapphire-styled page needs two things:

1. **A theme class on a root element** - Add `class="sapphire-theme-default"` to your `<body>` or root container
2. **The design tokens CSS** - Either link to the tokens stylesheet or inline the CSS custom properties

The tokens define everything: colors, spacing, typography, radii, shadows, and control sizes. Components are built by referencing these tokens, which means your entire UI stays consistent and theme-switchable.

```html
<body class="sapphire-theme-default">
  <!-- All Sapphire-styled content goes here -->
</body>
```

## How to Use This Skill

1. **Start with tokens**: Read `references/tokens.md` for the full set of CSS custom properties. Copy the `.sapphire-theme-default` block into your project's CSS.
2. **Build components**: Read only the component reference files you need (see table below). This keeps context lean — not every page needs every component.
3. **Add icons**: Read `references/icons.md` for the complete icon catalog (700+ icons). Icons are simple SVGs that you can inline or reference.

## Component References

Components are split into focused files. Read only what your task requires:

| File | Components | When to read |
|------|-----------|-------------|
| `references/core.md` | Surface, Text, Card, Separator, Layout (stack/row/container) | **Always** — needed for any Sapphire page |
| `references/buttons.md` | Button (7 variants × 3 sizes, states, icons) | When the UI has buttons or clickable actions |
| `references/forms.md` | Text Field, Checkbox, Radio, Switch, Select | When the UI has form inputs or settings |
| `references/feedback.md` | Badge, Alert, Tabs, Dialog/Modal, Avatar | When the UI shows status indicators, navigation tabs, modals, or user avatars |

For a typical page, start with `core.md` + `buttons.md`. Add `forms.md` if there are inputs, `feedback.md` if there are badges/alerts/tabs/dialogs.

## Design Principles

Sapphire follows these key principles that you should maintain:

- **Semantic color tokens**: Never hardcode colors. Use semantic tokens like `--sapphire-semantic-color-foreground-primary` instead of raw hex/hsl values. This ensures theme compatibility (light, dark, contrast modes).
- **Consistent spacing scale**: Use the spacing tokens (`--sapphire-semantic-size-spacing-*`) for all padding, margins, and gaps. The scale runs from `4xs` (0.125rem) to `6xl` (4.5rem).
- **Pill-shaped buttons**: Buttons use `border-radius` equal to their height, creating the signature pill shape.
- **Subtle interaction states**: Hover/active states use semi-transparent overlays via `color-mix()`, not distinct solid colors. This creates smooth, layered interactions.
- **Typography hierarchy**: Use the heading scale (`heading-2xl` down to `heading-xs`) and body scale (`body-lg` down to `body-xs`) with the Danske font family (falls back to system sans-serif).
- **Focus rings**: All interactive elements show a `2px solid blue-400` outline on keyboard focus, offset by 2px.
- **Disabled = 30% opacity**: Disabled elements use `opacity: 0.3` universally.

## Theme Variants

Sapphire has three surface levels plus a contrast (dark) mode. Each adjusts token values:

| Class | Background | Use Case |
|-------|-----------|----------|
| `.sapphire-theme-default` | White | Primary surface |
| `.sapphire-theme--secondary` | Sand-50 | Elevated sections |
| `.sapphire-theme--tertiary` | Sand-100 | Nested containers |
| `.sapphire-theme--contrast` | Gray-900 (dark) | Dark mode / hero sections |

Nest theme classes to create depth. A card on a secondary surface would have the secondary class on the section and the default class on the card itself.

## Font

Sapphire uses the proprietary "Danske" font. When approximating without the font files, use a system font stack that matches the geometric sans-serif style:

```css
font-family: 'Danske', -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif;
```

## Accessibility

- All interactive elements must have visible focus indicators (the focus ring tokens handle this)
- Color is never the sole indicator of state - always pair with icons, text, or shape
- Minimum touch target size: `--sapphire-semantic-size-height-control-sm` (2rem / 32px)
- Use semantic HTML elements (`<button>`, `<input>`, `<nav>`) - the CSS classes layer on top

Files: 7

Size: 97.5 KB

Complexity: 53/100

Category: Design

Source: https://github.com/thomasrohde/marketplace/tree/main/plugins/sapphire-design/skills/sapphire-design

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts