MCPInstall

apply-mantel-styles

Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.

Installs
106
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/sammcj/agentic-coding --skill apply-mantel-styles
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads apply-mantel-styles automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Rules For Applying Mantel Brand Styles

When creating visual diagrams or frontend components, you can apply the following style guidelines to ensure consistency with the Mantel brand identity.

Colour Scheme

  • You should aim to use the following primary colours from the Mantel brand palette.
  • You may also use tints and shades of these colours as needed, but avoid introducing non-brand colours.

Palette

NameHexRGB
Ocean#1E5E82rgb(30, 94, 130)
Flamingo#D86E89rgb(216, 110, 137)
Deep Ocean#002A41rgb(0, 42, 65)
Sky Blue#81CCEArgb(129, 204, 234)
Cloud#EEF9FDrgb(238, 249, 253)

Extended Palette — Brand Ramps (50 lightest → 900 darkest)

Use these tokens for tints, shades, hover states, borders, and surfaces without introducing non-brand colours. Prefer the core step (bold) for each brand colour; reach for neighbouring steps when you need contrast adjustment.

Ocean — core 500

 50  #E8F2F8      500  #1E5E82   ← core
100  #C5DCEA      600  #174E6E
200  #9DC3D8      700  #103D57
300  #6AA5C3      800  #0A2D40
400  #3D89AF      900  #042031

Flamingo — core 500

 50  #FAEEF2      500  #D86E89   ← core
100  #F4D1DA      600  #C25079
200  #EDB0BE      700  #9E3456
300  #E690A2      800  #7A1E3D
400  #DE7F92      900  #550E28

Sky — core 400 (Sky's brand anchor sits at 400, not 500)

 50  #F0FAFD      400  #81CCEA   ← core
100  #D9F1F9      500  #59BAE2
200  #B8E5F5      600  #329DD3
300  #95D6EF      700  #1B7EAD
                  800  #0E5F85
                  900  #064260

Neutral — greys for text, borders, dividers on light surfaces

 50  #F5F7F9      500  #8A99AB
100  #DDE3EA      600  #5C6A7A
200  #C5CED9      700  #3E4F5E
300  #A8B5C4      800  #293C49
400  #B2BECC      900  #161C21

Anchor Tokens (fixed, not on a ramp)

TokenHexUse
Deep Ocean#002A41Primary dark background
Cloud#EEF9FDPrimary light / neutral background
Skywalker 950#001421Near-black dark surface
Skywalker 900#001E2FDeepest dark section
Skywalker 800#042D44Dark surface 2
Skywalker 700#073B58Dark surface 3
Skywalker 600#0C4F74Dark surface 4 (lightest dark)

Semantic Status Colours

Use these for success / warning / error / attention states. Do not substitute brand colours — overloading Flamingo for errors breaks the semantic contract users rely on.

TokenHexUse
Yoda 600#07883DSuccess / positive
BB8 600#E87400Warning
Kylo 600#D91544Error / danger
Pyre 300#FFD60AHighlight / attention

General Design Principles

Colour Hierarchy

  1. Primary Actions/Elements: Ocean (#1E5E82)
  2. Secondary/Supporting: Sky Blue (#81CCEA)
  3. Emphasis/Accent: Flamingo (#D86E89)
  4. Foundation/Authority: Deep Ocean (#002A41)
  5. Background/Neutral: Cloud (#EEF9FD)
  • Light backgrounds use Cloud (#EEF9FD) or white (#FFFFFF).
  • Dark backgrounds use Deep Ocean (#002A41). Never use pure black (#000000).
  • Primary text on light backgrounds is Deep Ocean. On dark backgrounds, use white.
  • Accent elements (borders, icons, highlights) use Ocean, Flamingo, or Sky Blue.

Semantic Usage

  • Use Ocean for primary actions, main navigation, and brand-level emphasis
  • Use Sky Blue for interactive elements, information, and secondary actions
  • Use Flamingo sparingly for CTAs and brand highlights (not for errors — use Kylo)
  • Use Deep Ocean for text, borders, authoritative elements
  • Use Cloud for backgrounds, subtle dividers, inactive states
  • Use the semantic status colours (Yoda / BB8 / Kylo / Pyre) for success / warning / error / attention — never substitute brand colours for these
  • Default to light / day mode colour schemes

Consistency Rules

  • Avoid mixing colour schemes from other brands
  • Maintain consistent colour meanings across all diagrams in a project
  • When transparency is needed, use rgba values of the brand colours
  • For hover/pressed states, step one rung on the brand ramp (e.g. ocean-500 → ocean-600 on hover, flamingo-500 → flamingo-600 on press). Only fall back to percentage darken/lighten if no ramp token fits

Frontend Component Styles

Component Guidelines

Buttons

Primary:

  • Background: Ocean (#1E5E82)
  • Text: Cloud (#EEF9FD)
  • Hover: Deep Ocean (#002A41)
  • Border: none or Ocean

Secondary:

  • Background: Sky Blue (#81CCEA)
  • Text: Deep Ocean (#002A41)
  • Hover: Ocean (#1E5E82) with Cloud text
  • Border: Ocean (#1E5E82)

Accent/CTA:

  • Background: Flamingo 500 (#D86E89)
  • Text: White (#FFFFFF)
  • Hover: Flamingo 600 (#C25079)
  • Border: none

Ghost/Outline:

  • Background: transparent
  • Text: Ocean (#1E5E82)
  • Hover: Cloud (#EEF9FD) background
  • Border: Ocean (#1E5E82)

Navigation

Header:

  • Background: Deep Ocean (#002A41)
  • Text: Cloud (#EEF9FD)
  • Active: Sky Blue (#81CCEA)
  • Hover: Ocean (#1E5E82) background

Sidebar:

  • Background: Cloud (#EEF9FD)
  • Text: Deep Ocean (#002A41)
  • Active: Ocean (#1E5E82) with Cloud text
  • Hover: Sky Blue (#81CCEA) background

Forms

Input Fields:

  • Background: White (#FFFFFF)
  • Border: Sky Blue (#81CCEA)
  • Focus Border: Ocean (#1E5E82)
  • Text: Deep Ocean (#002A41)
  • Placeholder: Sky Blue (#81CCEA)
  • Error Border: Kylo 600 (#D91544)

Labels:

  • Colour: Ocean (#1E5E82)
  • Required Indicator: Flamingo (#D86E89)

Cards and Surfaces

Standard Card:

  • Background: White (#FFFFFF)
  • Border: Cloud (#EEF9FD)
  • Shadow: rgba(0, 42, 65, 0.1)

Highlighted Card:

  • Background: Cloud (#EEF9FD)
  • Border: Sky Blue (#81CCEA)
  • Shadow: rgba(30, 94, 130, 0.15)

Alerts and Messages

Use the semantic status colours — do not overload Flamingo for errors/warnings or Ocean for success.

Error:

  • Background: Kylo 600 (#D91544) at 10% opacity
  • Border: Kylo 600 (#D91544)
  • Text: Deep Ocean (#002A41)
  • Icon: Kylo 600 (#D91544)

Warning:

  • Background: BB8 600 (#E87400) at 10% opacity
  • Border: BB8 600 (#E87400)
  • Text: Deep Ocean (#002A41)
  • Icon: BB8 600 (#E87400)

Success:

  • Background: Yoda 600 (#07883D) at 10% opacity
  • Border: Yoda 600 (#07883D)
  • Text: Deep Ocean (#002A41)
  • Icon: Yoda 600 (#07883D)

Info:

  • Background: Sky Blue (#81CCEA) at 10% opacity
  • Border: Sky Blue (#81CCEA)
  • Text: Deep Ocean (#002A41)
  • Icon: Sky Blue (#81CCEA)

Data Visualisation (Charts)

  • Primary Series: Ocean (#1E5E82)
  • Secondary Series: Sky Blue (#81CCEA)
  • Tertiary Series: Deep Ocean (#002A41)
  • Highlight/Accent: Flamingo (#D86E89)
  • Background: Cloud (#EEF9FD)
  • Grid Lines: Sky Blue (#81CCEA) at 20% opacity
  • Text: Deep Ocean (#002A41)

CSS Variables

:root {
   /* Core brand (anchor steps) */
   --brand-ocean: #1E5E82;        /* ocean-500 */
   --brand-flamingo: #D86E89;     /* flamingo-500 */
   --brand-sky-blue: #81CCEA;     /* sky-400 */
   --brand-deep-ocean: #002A41;
   --brand-cloud: #EEF9FD;

   /* Ocean ramp */
   --ocean-50:  #E8F2F8; --ocean-100: #C5DCEA; --ocean-200: #9DC3D8;
   --ocean-300: #6AA5C3; --ocean-400: #3D89AF; --ocean-500: #1E5E82;
   --ocean-600: #174E6E; --ocean-700: #103D57; --ocean-800: #0A2D40;
   --ocean-900: #042031;

   /* Flamingo ramp */
   --flamingo-50:  #FAEEF2; --flamingo-100: #F4D1DA; --flamingo-200: #EDB0BE;
   --flamingo-300: #E690A2; --flamingo-400: #DE7F92; --flamingo-500: #D86E89;
   --flamingo-600: #C25079; --flamingo-700: #9E3456; --flamingo-800: #7A1E3D;
   --flamingo-900: #550E28;

   /* Sky ramp */
   --sky-50:  #F0FAFD; --sky-100: #D9F1F9; --sky-200: #B8E5F5;
   --sky-300: #95D6EF; --sky-400: #81CCEA; --sky-500: #59BAE2;
   --sky-600: #329DD3; --sky-700: #1B7EAD; --sky-800: #0E5F85;
   --sky-900: #064260;

   /* Neutral greys */
   --neutral-50:  #F5F7F9; --neutral-100: #DDE3EA; --neutral-200: #C5CED9;
   --neutral-300: #A8B5C4; --neutral-400: #B2BECC; --neutral-500: #8A99AB;
   --neutral-600: #5C6A7A; --neutral-700: #3E4F5E; --neutral-800: #293C49;
   --neutral-900: #161C21;

   /* Dark surfaces */
   --skywalker-950: #001421; --skywalker-900: #001E2F; --skywalker-800: #042D44;
   --skywalker-700: #073B58; --skywalker-600: #0C4F74;

   /* Semantic status */
   --yoda-600: #07883D;  /* success */
   --bb8-600:  #E87400;  /* warning */
   --kylo-600: #D91544;  /* error */
   --pyre-300: #FFD60A;  /* highlight */

   /* Semantic mappings */
   --colour-primary: var(--brand-ocean);
   --colour-primary-dark: var(--brand-deep-ocean);
   --colour-secondary: var(--brand-sky-blue);
   --colour-accent: var(--brand-flamingo);
   --colour-background: var(--brand-cloud);
   --colour-surface: #FFFFFF;

   /* Text */
   --text-primary: var(--brand-deep-ocean);
   --text-secondary: var(--brand-ocean);
   --text-on-primary: var(--brand-cloud);
   --text-on-accent: #FFFFFF;

   /* State (semantic status — do not substitute brand colours) */
   --colour-error: var(--kylo-600);
   --colour-warning: var(--bb8-600);
   --colour-success: var(--yoda-600);
   --colour-info: var(--brand-sky-blue);
   --colour-highlight: var(--pyre-300);

   /* Shadows and overlays */
   --shadow-colour: rgba(0, 42, 65, 0.1);
   --overlay-light: rgba(238, 249, 253, 0.9);
   --overlay-dark: rgba(0, 42, 65, 0.8);
}

Tailwind Configuration

Tailwind's config key is colors (American spelling) — this is required by the framework regardless of project-wide spelling conventions.

module.exports = {
   theme: {
      extend: {
         colors: {
            brand: {
               ocean: '#1E5E82',
               flamingo: '#D86E89',
               'sky-blue': '#81CCEA',
               'deep-ocean': '#002A41',
               cloud: '#EEF9FD',
            },
            ocean: {
               50: '#E8F2F8', 100: '#C5DCEA', 200: '#9DC3D8',
               300: '#6AA5C3', 400: '#3D89AF', 500: '#1E5E82',
               600: '#174E6E', 700: '#103D57', 800: '#0A2D40',
               900: '#042031',
            },
            flamingo: {
               50: '#FAEEF2', 100: '#F4D1DA', 200: '#EDB0BE',
               300: '#E690A2', 400: '#DE7F92', 500: '#D86E89',
               600: '#C25079', 700: '#9E3456', 800: '#7A1E3D',
               900: '#550E28',
            },
            sky: {
               50: '#F0FAFD', 100: '#D9F1F9', 200: '#B8E5F5',
               300: '#95D6EF', 400: '#81CCEA', 500: '#59BAE2',
               600: '#329DD3', 700: '#1B7EAD', 800: '#0E5F85',
               900: '#064260',
            },
            neutral: {
               50: '#F5F7F9', 100: '#DDE3EA', 200: '#C5CED9',
               300: '#A8B5C4', 400: '#B2BECC', 500: '#8A99AB',
               600: '#5C6A7A', 700: '#3E4F5E', 800: '#293C49',
               900: '#161C21',
            },
            skywalker: {
               600: '#0C4F74', 700: '#073B58', 800: '#042D44',
               900: '#001E2F', 950: '#001421',
            },
            // Semantic status (single-step anchors)
            yoda: '#07883D',   // success
            bb8:  '#E87400',   // warning
            kylo: '#D91544',   // error
            pyre: '#FFD60A',   // highlight
         }
      }
   }
}

Fonts & Typography

  • Where applicable, the 'Inter' typeface is used for headlines, subheadings, and body copy.
  • Favour bundling the font for offline use over relying on CDNs.
RoleFontWeightCSS
HeadlinesInterSemiBoldfont-weight: 600
SubheadingsInterMediumfont-weight: 500
Body copyInterRegularfont-weight: 400

Inter CDN Fallback

If bundling is not possible, use this CDN:

<!-- HTML in your document's head -->
<link rel="preconnect" href="https://rsms.me/">
<link rel="stylesheet" href="https://rsms.me/inter/inter.css">
:root {
  font-family: Inter, sans-serif;
  font-feature-settings: 'liga' 1, 'calt' 1; /* fix for Chrome */
}
@supports (font-variation-settings: normal) {
  :root { font-family: InterVariable, sans-serif; }
}

Logo System

Logo Variants

The skill bundles all logo files in assets/. Selection guide:

FileUse when…
Mantel_Logo__Positive.svgFull-colour logo on light backgrounds
Mantel_Logo__Negative.svgFull-colour logo on dark backgrounds
Mantel_Logo__Navy.svgMono (Deep Ocean) logo on light backgrounds
Mantel_Logo__White.svgMono (white) logo on dark backgrounds
Mantel_Icon__Positive.svgFull-colour icon only, on light backgrounds
Mantel_Icon__Negative.svgFull-colour icon only, on dark backgrounds
Mantel_Icon__Navy.svgMono (Deep Ocean) icon, on light backgrounds
Mantel_Icon__White.svgMono (white) icon, on dark backgrounds

Logo Rules (critical — violations are immediately visible)

  1. Never stretch or distort. Logo aspect ratio is approximately 4.67:1. Icon is approximately 1.5:1. Always preserve proportions.
  2. Never change logo colours. Use only the provided variants — never recolour the icon or wordmark.
  3. Never crop the logo. All elements must be fully visible.
  4. Minimum clear space around the logo equals the height and width of the icon portion.
  5. Minimum sizes: Logo 80px / 21mm wide. Icon 44px / 12mm wide.
  6. Light logo on light background = wrong. Dark logo on dark background = wrong. Always use the variant that contrasts with the background.
  7. Preferred for client-facing materials: Use the full-colour Negative logo on Deep Ocean backgrounds. This is the most common and branded combination.
  8. Never add a coloured border around the logo — the brand guide explicitly prohibits this.

Resources

If you are creating diagrams you MUST also read in ./resources/diagrams.md


This information should help you maintain visual consistency with the Mantel brand across diagrams and frontend components.

FAQ

What does the apply-mantel-styles skill do?

Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.

How do I install apply-mantel-styles?

Run npx skills add https://github.com/sammcj/agentic-coding --skill apply-mantel-styles in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/apply-mantel-styles/ (personal) or .claude/skills/apply-mantel-styles/ (project).

Which AI agents can use apply-mantel-styles?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is apply-mantel-styles safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains apply-mantel-styles?

It is published by sammcj in sammcj/agentic-coding. It has 106 recorded installs.

More from sammcj/agentic-coding

View all →

Critically analyse the reasoning in written content (articles, blogs, transcripts, reports), not code. Use only when explicitly asked to critically analyse or critique an argument.

AI & Agents2.4K installs

Applies the Diataxis framework to create or improve technical documentation. Use when being asked to write high quality tutorials, how-to guides, reference docs, or explanations, when reviewing documentation quality, or when deciding what type of documentation to create. Helps identify documentation types using the action/cognition and acquisition/application dimensions.

Docs & Writing615 installs

creating-development-plans

sammcj/agentic-coding

Creates structured development plans with phased task breakdowns, requirements, and QA checklists. Use when the user explicitly asks to create a dev plan, development plan, or document development requirements.

ghostty-config

sammcj/agentic-coding

Use when creating, editing or debugging Ghostty terminal configuration - config.ghostty files, config option names and their valid values, keybinds and key sequences, themes, fonts, shell integration, or ghostty + CLI actions. Covers macOS and Linux/GTK differences.

AI & Agents221 installs

code-simplification

sammcj/agentic-coding

Use this skill when you need to review and refactor code to make it simpler, more maintainable, and easier to understand. Helps with identifying overly complex solutions, unnecessary abstractions.

prompt-enhancer

sammcj/agentic-coding

Transform poor or overly simple prompts with expert-level framing. Use when the user explicitly asks to improve, refine, or rewrite a prompt, or wants help framing a request for another AI system. Do NOT use for authoring, reviewing, or migrating system prompts or skills targeting a specific Claude model.

AI & Agents184 installs

Popular frontend & design skills

View category →

setup-matt-pocock-skills

mattpocock/skills

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Frontend & Design1.1M installs

frontend-design

anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

OfficialFrontend & Design1M installs

hyperframes-animation

heygen-com/hyperframes

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

prototype

mattpocock/skills

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Frontend & Design999.2K installs

hyperframes-core

heygen-com/hyperframes

The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

Frontend & Design930.5K installs

vercel-react-best-practices

vercel-labs/agent-skills

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

OfficialFrontend & Design843.1K installs