Style Blueprint logo

Style Blueprint

Organization
pnp
style-blueprint

Blueprint engineering-drawing style tokens and row template for the list-styling skill. Monochromatic blue palette, double-ring rubber-stamp status badges, ultra-compact spec-sheet card with a blue left edge. The most compact card in the library — no sidebar, no banner. Overdue is the only element that turns red. Use when the user says "blueprint," "technical drawing," "engineering," "schematic," "spec sheet," or similar.

Overview

Publisherpnp
Repositorysharepoint-skills
Skill namestyle-blueprint
Stars
141
Forks
60
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by pnp on GitHub. Read the source before you install it.

Installation

Install the Style Blueprint AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-blueprint/style-blueprint
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/pnp/sharepoint-skills.git /tmp/sharepoint-skills
mkdir -p .claude/skills
cp -r /tmp/sharepoint-skills/Skills/style-blueprint/style-blueprint .claude/skills/style-blueprint
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Style Blueprint in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Style Blueprint on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Style Blueprint is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Blueprint — Style Tokens + Row Template

Monochromatic blue. Technical. Precise. Every card is a spec-sheet entry on an engineering drawing. Status badges are rubber stamps with double-ring borders. This is the most compact card in the library.

Layout philosophy: Ultra-compact spec sheet with a blue left edge. No sidebar, no banner — just a clean two-line card with a 4px blue left border. Line one is the document name. Line two is the stamp, progress bar, percentage, and due date — all on one row. The only color break in the entire list is overdue red. Everything else is blue, from the darkest ink to the palest wash.


Color Palette

SwatchHexSemantic Role
1#1e3a8aink — primary text, left edge, darkest blue
2#1e40afstamp — rubber stamp borders and text
3#2563ebdate — date text, secondary info
4#3b82f6fill — progress bar fill
5#60a5falabel — subtle labels like "DUE"
6#93c5fdrule — card border, grid lines
7#dbeafewash — progress track, lightest blue
8#ffffffpaper — card background
9#dc2626alert — overdue ONLY, the single non-blue

CRITICAL: Swatches 1–8 are ALL BLUE. Swatch 9 (red) is used ONLY for overdue states. There are no per-status color variations — every status looks the same monochromatic blue. The stamp text itself differentiates statuses. Overdue is the one dramatic break from the blueprint palette.


Badge Tokens (Rubber Stamp)

The stamp uses a double-ring border: an outer div with a 2px border and 1px padding, wrapping an inner span with a 1px border. This creates the classic certification/rubber-stamp impression.

  • outer_border: 2px solid #1e40af
  • outer_padding: 1px (gap between rings)
  • inner_border: 1px solid #1e40af
  • inner_padding: 2px 8px
  • font-size: 10px
  • font-weight: 700
  • text-transform: uppercase
  • color: #1e40af
  • background: transparent (stamps are outlines, not fills)
  • border-radius: 0px (sharp corners — technical, angular)

status_colors

Valuestamp_borderstamp_textbackground
Draft#1e40af#1e40aftransparent
In Review#1e40af#1e40aftransparent
Revising#1e40af#1e40aftransparent
Approved#1e40af#1e40aftransparent
Published#1e40af#1e40aftransparent
_fallback#1e40af#1e40aftransparent
OVERDUE (any)#dc2626#dc2626transparent

CRITICAL: Every status uses the SAME blue. The stamp text is the only differentiator. Overdue overrides ANY status — when a deadline has passed, the stamp turns red regardless of status value. This is intentionally monochromatic.


Progress Bar Tokens

  • progress_track_height: 4px (ultra-thin — compact)
  • progress_track_bg: #dbeafe (wash)
  • progress_track_border: none
  • progress_track_radius: 1px
  • progress_fill_color: #3b82f6 (single blue — NO color changes by percentage)
  • progress_fill_radius: 1px
  • progress_label_font_size: 13px
  • progress_label_font_weight: 700
  • progress_label_color: #1e3a8a (ink)

CRITICAL: Progress fill is ALWAYS #3b82f6 regardless of percentage. No low/mid/high color shifts. Blueprint is monochromatic.


Deadline Tokens

  • deadline_icon: none (no emoji — use text label "DUE" instead)
  • due_label: DUE
  • due_label_font_size: 10px
  • due_label_color_normal: #60a5fa (label)
  • due_label_color_overdue: #dc2626 (alert)
  • date_font_size: 12px
  • date_normal_color: #2563eb (date)
  • date_normal_weight: 500
  • date_overdue_color: #dc2626 (alert)
  • date_overdue_weight: 700
  • overdue_label: OVERDUE (text only — no emoji, no fire, no icons)
  • overdue_label_font_size: 10px
  • overdue_label_color: #dc2626

CRITICAL: No emoji anywhere in the blueprint style. No 🔥, no 🗓️, no ✨. Text labels only. This is a technical drawing, not a party.


Row Card Tokens

  • card_border: 1px solid #93c5fd (rule)
  • card_border_left: 4px solid #1e3a8a (ink — the blue left edge)
  • card_border_radius: 2px (barely rounded — sharp, technical)
  • card_background: #ffffff (paper)
  • card_margin_bottom: 4px (tight stacking)
  • card_padding: 8px 14px (compact)
  • card_shadow: none (clean, flat — no shadows on a blueprint)
  • gap_between_lines: 4px
  • overdue_border: 1px solid #dc2626
  • overdue_border_left: 4px solid #dc2626

CRITICAL: No shadows. Blueprints are flat technical drawings. The 4px left edge is the ONLY structural accent — it's a thin spec-sheet margin line, not a sidebar.


Row Template Layout

Ultra-compact two-line spec sheet with blue left edge.

┌──────────────────────────────────────────────────────┐
▌ API Guide.docx                                       │
▌ ╔═APPROVED═╗  ━━━━━━━━━━━░░░░  75%   DUE 5/15/26   │
└──────────────────────────────────────────────────────┘

Overdue variant:
┌──────────────────────────────────────────────────────┐  ← red border
▌ API Guide.docx                                       │
▌ ╔═APPROVED═╗  ━━━━━━━━━━━░░░░  75%   DUE 5/15 OVERDUE│
└──────────────────────────────────────────────────────┘

Key differences from every other style:

  • NO banner (unlike Retro's colored top banner)
  • NO sidebar (unlike Neobrutalism's left panel)
  • NO shadows (unlike both Retro and Neobrutalism)
  • NO emoji (unlike every other style)
  • NO per-status colors (unlike every other style)
  • Two lines total — the most compact card in the library
  • Double-ring stamp border — unique to Blueprint

rowFormatter JSON

Adapt before applying. The column names below ([$Status], [$Progress], [$Deadline]) are example placeholders — replace them with the actual internal column names from the user's list. Note: Blueprint has no per-status color expressions, so there are no status value strings to remap. Follow list-styling Step 3.

json
{
  "$schema": "https://developer.microsoft.com/json-schemas/sp/v2/view-formatting.schema.json",
  "hideSelection": false,
  "hideColumnHeaders": true,
  "rowFormatter": {
    "elmType": "div",
    "style": {
      "display": "flex",
      "flex-direction": "column",
      "border": "=if([$Deadline] < @now, '1px solid #dc2626', '1px solid #93c5fd')",
      "border-left": "=if([$Deadline] < @now, '4px solid #dc2626', '4px solid #1e3a8a')",
      "border-radius": "2px",
      "background-color": "#ffffff",
      "margin-bottom": "4px",
      "padding": "8px 14px",
      "gap": "4px"
    },
    "children": [
      {
        "elmType": "div",
        "style": {
          "font-size": "13px",
          "font-weight": "700",
          "color": "#1e3a8a",
          "line-height": "1.2"
        },
        "txtContent": "=if([$FileLeafRef] == '', [$Title], [$FileLeafRef])"
      },
      {
        "elmType": "div",
        "style": {
          "display": "flex",
          "align-items": "center",
          "gap": "12px"
        },
        "children": [
          {
            "elmType": "div",
            "style": {
              "display": "inline-flex",
              "padding": "1px",
              "border": "=if([$Deadline] < @now, '2px solid #dc2626', '2px solid #1e40af')"
            },
            "children": [
              {
                "elmType": "span",
                "txtContent": "[$Status]",
                "style": {
                  "display": "inline-block",
                  "padding": "2px 8px",
                  "border": "=if([$Deadline] < @now, '1px solid #dc2626', '1px solid #1e40af')",
                  "font-size": "10px",
                  "font-weight": "700",
                  "text-transform": "uppercase",
                  "color": "=if([$Deadline] < @now, '#dc2626', '#1e40af')",
                  "white-space": "nowrap",
                  "background-color": "transparent"
                }
              }
            ]
          },
          {
            "elmType": "div",
            "style": {
              "flex": "1",
              "height": "4px",
              "background-color": "#dbeafe",
              "border-radius": "1px",
              "overflow": "hidden",
              "min-width": "60px"
            },
            "children": [
              {
                "elmType": "div",
                "style": {
                  "width": "=toString([$Progress]) + '%'",
                  "height": "100%",
                  "background-color": "#3b82f6",
                  "border-radius": "1px"
                }
              }
            ]
          },
          {
            "elmType": "span",
            "txtContent": "=toString([$Progress]) + '%'",
            "style": {
              "font-size": "13px",
              "font-weight": "700",
              "color": "#1e3a8a",
              "min-width": "32px"
            }
          },
          {
            "elmType": "div",
            "style": {
              "display": "flex",
              "align-items": "center",
              "gap": "4px"
            },
            "children": [
              {
                "elmType": "span",
                "txtContent": "DUE",
                "style": {
                  "font-size": "10px",
                  "font-weight": "600",
                  "color": "=if([$Deadline] < @now, '#dc2626', '#60a5fa')",
                  "text-transform": "uppercase"
                }
              },
              {
                "elmType": "span",
                "txtContent": "=toLocaleDateString([$Deadline])",
                "style": {
                  "font-size": "12px",
                  "font-weight": "=if([$Deadline] < @now, '700', '500')",
                  "color": "=if([$Deadline] < @now, '#dc2626', '#2563eb')"
                }
              },
              {
                "elmType": "span",
                "txtContent": "=if([$Deadline] < @now, 'OVERDUE', '')",
                "style": {
                  "font-size": "10px",
                  "font-weight": "700",
                  "color": "#dc2626",
                  "text-transform": "uppercase"
                }
              }
            ]
          }
        ]
      }
    ]
  }
}

Checklist — "Is This Actually a Blueprint?"

  • ✅ Full rowFormatter — NOT default column grid
  • ✅ Ultra-compact TWO-LINE layout — the shortest card in the library
  • ✅ NO banner, NO sidebar, NO panel — just a clean spec sheet
  • ✅ 4px blue left edge (#1e3a8a) — a margin line, NOT a sidebar
  • ✅ Double-ring rubber stamp badges (outer 2px + inner 1px border)
  • ✅ ALL stamps are the same monochromatic blue — no per-status color variation
  • ✅ Stamp background is TRANSPARENT — outlines only, like a real ink stamp
  • ✅ Progress bar is 4px thin (half the height of other styles)
  • ✅ Progress fill is ALWAYS #3b82f6 — no color changes by percentage
  • ✅ NO emoji anywhere — no 🔥, no 🗓️, no ✨, no 🎯
  • ✅ Text labels only: "DUE" and "OVERDUE"
  • ✅ NO shadows — flat, clean, technical
  • ✅ Border-radius 2px — barely rounded, sharp and precise
  • ✅ 4px margin between cards — tight stacking
  • ✅ Entire palette is swatches 1–8 (all blue) from the blueprint palette
  • ✅ Overdue is the ONLY red (#dc2626) — left edge, stamp, date, and label all flip to red
  • ✅ Overdue card border turns red on ALL sides — impossible to miss
  • ✅ Silhouette test: two flat lines with a left edge looks NOTHING like a banner card or sidebar card

Responsive / mobile

  • ≤ 720 px: the high-density inline metadata wraps to a second line under the title. Keep the blue left-edge accent at full height.
  • ≤ 480 px: drop the swatch ramp from 8 swatches to ~3 in practice — primary, accent, overdue red. Hide tertiary chips entirely; never shrink chip text below 12 px on mobile.
  • Hero text step-down: 16 px → 14 px on mobile. The style relies on tight stacking, not large text.

Implementation notes

Palette trim

The shipped palette ships nine blue swatches (1–9). In practice, swatches 4–6 are largely interchangeable to the eye and can be collapsed when re-skinning. A safe minimum set is swatch 1 (primary), swatch 7 (accent), and the overdue red #dc2626. Anything beyond that is connoisseur territory — use only when the list has 5+ distinct status values that genuinely need separation.

Rubber-stamp double-ring fallback

The double-ring rubber-stamp badge depends on a nested element pattern (inner ring + outer ring). If the second ring's offset or clip-path is dropped by a SharePoint theme or modern view renderer:

  • Fall back to a single solid ring at the outer color, with the inner space filled by a lighter tint of the same swatch.
  • Keep the uppercase status text inside — the ring is decoration; the label carries the meaning.
  • Never substitute a pill — it breaks the silhouette test.

Frequently asked questions

What does the Style Blueprint AI skill do?

Blueprint engineering-drawing style tokens and row template for the list-styling skill. Monochromatic blue palette, double-ring rubber-stamp status badges, ultra-compact spec-sheet card with a blue left edge. The most compact card in the library — no sidebar, no banner. Overdue is the only element that turns red. Use when the user says "blueprint," "technical drawing," "engineering," "schematic," "spec sheet," or similar.

Why use Style Blueprint on TypingMind?

Because you install it once and use it with any model. Style Blueprint is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Style Blueprint in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-blueprint/style-blueprint. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Style Blueprint?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Style Blueprint?

As many as you like. As long as a model supports skills, you can use Style Blueprint with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Style Blueprint AI skill free?

Yes. It is published on GitHub by pnp under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇