| name | entur-brand-design |
| description | Apply Entur's visual identity correctly in designs, presentations, data visualizations, and web UI. Use when the user asks about Entur colors, Entur branding, Entur typography, Entur data visualization, creating charts or graphs for Entur, making a presentation that looks like Entur, building a branded web page or document for Entur, or anything that should follow Entur's visual identity. Trigger even if the user doesn't say "design system" — if they mention Entur and are making something visual, this skill applies. |
Audience: AI coding agents. Entur employees should visit linje.entur.no/identitet.
Entur Brand Design
This skill helps you apply Entur's visual identity correctly across web design, presentations, data visualizations, and branded content.
The Entur identity is built around clarity and trust. Blue, white, and coral are the foundation. The design serves the content — it never competes with the information users need.
Identity documentation: https://linje.entur.no/identitet
Design tokens: https://linje.entur.no/tokens
Brand-led surfaces vs. product UI
The rules below differ by context. Apply the right set:
Brand-led surfaces — marketing pages, presentations, documents, splash screens, campaign material:
- All three core colors (Lavender 90, white, coral) must be present
- Blue and white are dominant; coral is a detail accent
- Nationale typeface (or Arial fallback)
Product UI — application screens, dashboards, forms, data tables, travel planning:
- Prefer semantic tokens and component defaults from
@entur/*
- Do not force brand colors manually — components are already on-brand
- Only reach for explicit brand colors when building a Contrast section or a branded hero area
Core rules
- In brand-led surfaces, include all three core colors — Lavender 90 (
#181c56), white (#ffffff), and coral (#ff5959) must be present. A design without any of them stops feeling like Entur.
- Never use coral as a large background fill — it is a detail color. Maximum one coral accent per view (accent line, logo mark, CTA highlight).
- Weight blue and white as dominant — blue for structure/headers, white for content. Secondary colors add depth but never overpower.
- Never use data visualization colors for UI elements (buttons, status indicators) — data colors are for charts only.
- Apply data colors in the specified order — Blue first, Coral second, then Jungle, Azure, Lavender, Peach, Spring, Lilac. Never rearrange arbitrarily.
- Use Arial when Nationale is unavailable (Office, email, external collaborators without a license).
- Never build presentations from scratch — always start from
template.pptx. It embeds the correct 7 Entur slide masters.
- In code, always use tokens — not hex values. Brand docs and design specs list canonical hex values as references; translate them to CSS tokens when writing code.
Core principles
- Three-color foundation: Lavender 90 (
#181c56), white, and coral (#ff5959) must always be present in brand-led work. Everything else supports them.
- Coral is punctuation: use it sparingly. One coral accent per view. It's a detail color — it appears in the logo and in focus points, not as a large fill.
- Content is the hero: blue structures the layout, white hosts the content. Design recedes so information leads.
- Restraint: two font weights, limited secondary colors, generous whitespace. Avoid busyness.
Reference files
Read these for specifics:
references/colors.md — full color system, primary/secondary palettes, CSS tokens, color weighting, status colors, contrast requirementsreferences/typography.md — Nationale typeface, two weights for digital, Arial fallback, hierarchy guidelines, font loadingreferences/data-visualization.md — data color palette (ordered), colorblind accessibility, light/dark variants, combining with transport colorsreferences/visual-identity.md — layout principles, Contrast component, animation, illustrations, presentation guidelinesreferences/presentations-pptx.md — step-by-step python-pptx workflow, layout index, 5 slide patterns, helper functions, QAreferences/catalog.json — machine-readable index of all 51 layouts + 7 masters in template.pptx with python-pptx references
By use case
Web design / UI development
Read references/colors.md for the token system. Use Contrast from @entur/layout for Lavender 90 sections. Use @entur/typography for correct type hierarchy. Semantic color tokens auto-adapt to dark mode. Do not hardcode hex values in CSS or JS — use tokens.
Data visualizations / charts
Read references/data-visualization.md. Use the 8-color palette in order. Start with Blue and Coral for 2 series. Always test for colorblind accessibility. Import from @entur/tokens/dist/data.css.
Presentations and documents
Read references/typography.md (use Arial if Nationale is unlicensed) and references/visual-identity.md. Lead with Lavender 90 sections, white for content, coral only as accents on key points. For programmatic generation with python-pptx, read references/presentations-pptx.md and references/catalog.json.
Branding questions
Read references/colors.md and references/visual-identity.md together. The identity section explains the brand positioning and what to avoid.
Quick reference
Primary colors: #181c56 (Lavender 90), #ffffff (white), #ff5959 (coral) — hex for reference; use tokens in code
Main typeface: Nationale (licensed) / Arial (fallback)
Digital weights: Medium (500) body, Demibold (600) headings
Color token import: @import '@entur/tokens/dist/base.css'
Data viz import: @import '@entur/tokens/dist/data.css'
Full docs: https://linje.entur.no/identitet
Beyond Entur
For general creative design beyond Entur brand guidelines, the community skill frontend-design covers free-form aesthetics — but Entur work should follow identity guidelines here first.
