Agent skill

Style Blueprint

Blueprint engineering-drawing style tokens and row template for the list-styling skill.

Install Style Blueprint

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-blueprint -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-blueprint --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Skills/style-blueprint/style-blueprint .claude/skills/style-blueprint && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "style-blueprint" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-blueprint/style-blueprint into .claude/skills/style-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-blueprint", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-blueprint/style-blueprint

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-blueprint -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-blueprint --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Skills/style-blueprint/style-blueprint .agents/skills/style-blueprint && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "style-blueprint" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-blueprint/style-blueprint into .agents/skills/style-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-blueprint", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-blueprint -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-blueprint --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Skills/style-blueprint/style-blueprint .cursor/skills/style-blueprint && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "style-blueprint" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-blueprint/style-blueprint into .cursor/skills/style-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-blueprint", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/pnp/sharepoint-skills.git --path Skills/style-blueprint/style-blueprint

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-blueprint -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-blueprint --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Skills/style-blueprint/style-blueprint .gemini/skills/style-blueprint && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "style-blueprint" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-blueprint/style-blueprint into .gemini/skills/style-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-blueprint", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-blueprint

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-blueprint -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Skills/style-blueprint/style-blueprint .github/skills/style-blueprint && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "style-blueprint" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-blueprint/style-blueprint into .github/skills/style-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-blueprint", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-blueprint -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-blueprint --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Skills/style-blueprint/style-blueprint .opencode/skills/style-blueprint && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "style-blueprint" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-blueprint/style-blueprint into .opencode/skills/style-blueprint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-blueprint", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: style-blueprint
GitHub stars: 133
Token cost: ~3.3k tokens
SKILL.md length: 1,069 words
Files: 1
Skills in repo: 52
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Blueprint engineering-drawing style tokens and row template for the list-styling skill.

The user says blueprint
SKILL.md covers Color Palette, Badge Tokens (Rubber Stamp), Progress Bar Tokens and Deadline Tokens, plus 6 more sections
Reaches developer.microsoft.com
Technical drawing

What it does

Style Blueprint is an agent skill from pnp/sharepoint-skills. 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.

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Design tokens. The repository describes itself as: Skills for Copilot in SharePoint. The licence is MIT.

When your agent uses it

The user says blueprint
Technical drawing

Example prompts

“blueprint,”
“technical drawing,”
“engineering,”
“/style-blueprint”

What it can do on your machine

Read from SKILL.md and the folder at commit 69712d2. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- developer.microsoft.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Style Blueprint loads about 3.3k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 1,069 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~110
When it runs · the whole SKILL.md, loaded when a task matches: ~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pnp/sharepoint-skills at commit 69712d2, republished under its MIT licence (© pnp). 1,069 words, ~3,321 tokens.

Download SKILL.mdSave it as .claude/skills/style-blueprint/SKILL.md (or your agent's skills folder).

name: style-blueprint
description: 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.

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

Swatch	Hex	Semantic Role
1	`#1e3a8a`	ink — primary text, left edge, darkest blue
2	`#1e40af`	stamp — rubber stamp borders and text
3	`#2563eb`	date — date text, secondary info
4	`#3b82f6`	fill — progress bar fill
5	`#60a5fa`	label — subtle labels like "DUE"
6	`#93c5fd`	rule — card border, grid lines
7	`#dbeafe`	wash — progress track, lightest blue
8	`#ffffff`	paper — card background
9	`#dc2626`	alert — 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

Value	stamp_border	stamp_text	background
Draft	`#1e40af`	`#1e40af`	transparent
In Review	`#1e40af`	`#1e40af`	transparent
Revising	`#1e40af`	`#1e40af`	transparent
Approved	`#1e40af`	`#1e40af`	transparent
Published	`#1e40af`	`#1e40af`	transparent
_fallback	`#1e40af`	`#1e40af`	transparent
OVERDUE (any)	`#dc2626`	`#dc2626`	transparent

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

Show full SKILL.md (447 more words)Show less

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.

Files

Just SKILL.md in Skills/style-blueprint/style-blueprint of pnp/sharepoint-skills.

Open the folder on GitHubat commit 69712d2

Compare with similar skills

Style Blueprint next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Style Blueprint compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Style Blueprint this skillpnp/sharepoint-skills	133	—	~3.3k	Automated safety check: Pass	MIT	today
Figma Design System Builderwarpdotdev/warp	65k	2 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
Figma use_figma Plugin API Ruleswarpdotdev/warp	65k	4 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
MCP Developmentcoollabsio/coolify	63k	1 repos	~949	Automated safety check: Pass	MIT	today
Design SystemOhh-889/skyroc	795	11 repos	~1.7k	Automated safety check: Pass	MIT	1 mo ago
Design Dnazanwei/design-dna	1.9k	1 repos	~2.1k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
65k GitHub starsUsed in 2 repos~4.4k tokens
Frontend & DesignAuto-check passed
Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
65k GitHub starsUsed in 4 repos~4.4k tokens
Frontend & DesignAuto-check passed
MCP Development
coollabsio/coolify
A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.
63k GitHub starsUsed in 1 repo~949 tokens
Frontend & DesignAuto-check passed
Design System
Ohh-889/skyroc
Token architecture, component specifications, and slide generation.
795 GitHub starsUsed in 11 repos~1.7k tokens
Frontend & DesignAuto-check passed
Design Dna
zanwei/design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects…
1.9k GitHub starsUsed in 1 repo~2.1k tokens
Frontend & DesignAuto-check passed
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
65k GitHub starsUsed in 4 repos~2.9k tokens
Frontend & DesignAuto-check passed

More from pnp/sharepoint-skills

All 52 skills in this repo

Scorecard Matrix
pnp/sharepoint-skills
Generates a polished, self-contained HTML heatmap scorecard — a weighted comparison matrix where entities (rows) are scored across dimensions (columns), with computed totals, rank badges, and a…
133 GitHub stars~1.9k tokensUpdated today
Auto-check passed
Analyze Document Library
pnp/sharepoint-skills
Analyze the current SharePoint document library in read-only mode and produce a structured summary of files, folders, file types, recent activity, naming issues, and organization recommendations.
133 GitHub stars~899 tokensUpdated today
Auto-check passed
Broken Link Auditor
pnp/sharepoint-skills
Audits SharePoint pages, news posts, and hyperlink fields for broken or risky links and saves a self-contained HTML link-health report to the site.
133 GitHub stars~2.5k tokensUpdated today
Auto-check passed
Custom Image Tagger
pnp/sharepoint-skills
Analyze selected construction images, create missing object metadata columns, and write concise visual metadata back to SharePoint columns using explicit image-analysis, list-schema, list-update…
133 GitHub stars~1.2k tokensUpdated today
Auto-check passed
Dossier
pnp/sharepoint-skills
Renders a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal description.
133 GitHub stars~1.9k tokensUpdated today
Auto-check passed
Exec Report
pnp/sharepoint-skills
Generates a polished, self-contained HTML executive report or dashboard from any data source — SharePoint lists, CSV exports, or a user description.
133 GitHub stars~2k tokensUpdated today
Auto-check passed

Questions about Style Blueprint

What does Style Blueprint do?

Blueprint engineering-drawing style tokens and row template for the list-styling skill. Style Blueprint is an agent skill from pnp/sharepoint-skills. Blueprint engineering-drawing style tokens and row template for the list-styling skill.

When should I use Style Blueprint?

Style Blueprint fits situations like: the user says blueprint; technical drawing.

How do I install Style Blueprint in Claude Code?

Run `npx skills add pnp/sharepoint-skills --skill style-blueprint -a claude-code`. Or copy the skill folder (Skills/style-blueprint/style-blueprint in pnp/sharepoint-skills) into .claude/skills/style-blueprint in your project. Claude Code loads it when a task matches its description.

How do I install Style Blueprint in Codex?

Run `npx skills add pnp/sharepoint-skills --skill style-blueprint -a codex`. Or copy the skill folder (Skills/style-blueprint/style-blueprint in pnp/sharepoint-skills) into .agents/skills/style-blueprint in your project. Codex loads it when a task matches its description.

Can I use Style Blueprint in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pnp/sharepoint-skills --skill style-blueprint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/style-blueprint, .gemini/skills/style-blueprint, .github/skills/style-blueprint and .opencode/skills/style-blueprint in your project.

What does Style Blueprint need to run?

SKILL.md names no scripts, command-line tools or credentials: Style Blueprint is instructions for the agent only.

Does Style Blueprint access the network?

SKILL.md names 1 domain. In commands or code: developer.microsoft.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Style Blueprint safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Style Blueprint use?

Style Blueprint is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Style Blueprint use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Style Blueprint?

Skills that share tags, products or a category with Style Blueprint: Figma Design System Builder (warpdotdev/warp, 65k stars), Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars), MCP Development (coollabsio/coolify, 63k stars) and Design System (Ohh-889/skyroc, 795 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Style Blueprint?

pnp (a GitHub organization) maintains it in pnp/sharepoint-skills, which has 133 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 9, 2026.

Source: pnp/sharepoint-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Style Blueprint

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Blueprint — Style Tokens + Row Template

Color Palette

Badge Tokens (Rubber Stamp)

status_colors

Progress Bar Tokens

Deadline Tokens

Row Card Tokens

Row Template Layout

rowFormatter JSON

Checklist — "Is This Actually a Blueprint?"

Responsive / mobile

Implementation notes

Palette trim

Rubber-stamp double-ring fallback

Files

Compare with similar skills

Similar skills

More from pnp/sharepoint-skills

Related

Questions about Style Blueprint