Style Retro logo

Style Retro

Organization
pnp
style-retro

Retro Memphis style tokens and row template for the list-styling skill. Bright contrasting colors, colored shadows, playful stacked card with a status-colored top banner and large progress number. Layout is a stacked vertical card with a bold colored header strip — NOT a sidebar layout. Use when the user says "retro," "memphis," "80s," "90s," "colorful," "playful," "fun style," or similar.

Overview

Publisherpnp
Repositorysharepoint-skills
Skill namestyle-retro
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 Retro 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-retro/style-retro
  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-retro/style-retro .claude/skills/style-retro
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Style Retro 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 Retro 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 Retro 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.

Retro Memphis — Style Tokens + Row Template

Bright, playful, LOUD. Every status is a different color. Colored shadows. Stacked vertical card with a bold colored banner. This is the fun one.

Layout philosophy: Stacked vertical card with colored banner. The top third of the card is a bold status-colored banner containing the document name in large white text. Below it, a white content area with the status badge, a large progress percentage, and deadline info. The banner color changes per status — the card's personality changes with every item. This is structurally different from Neobrutalism's horizontal sidebar split.

Badge Tokens

  • padding: 5px 14px
  • border-radius: 20px (full pill — playful, round, fun)
  • font-size: 12px
  • font-weight: 700
  • text-transform: uppercase

status_colors

Valuebgtextborderbanner_color
Draft#fbbf24#1f29372px solid #d97706#fbbf24
In Review#3b82f6#ffffff2px solid #7c3aed#3b82f6
Revising#f472b6#ffffff2px solid #db2777#f472b6
Approved#2dd4bf#1f29372px solid #0d9488#2dd4bf
Published#a78bfa#ffffff2px solid #7c3aed#a78bfa
_fallback#e5e7eb#3741512px solid #9ca3af#e5e7eb

CRITICAL: The banner_color IS the status bg color — the entire top of the card floods with the status hue. Draft cards have a yellow top. In Review cards have a blue top. Revising cards have a hot pink top. Every card in the list is a different color.

Progress Bar Tokens

  • progress_track_height: 10px
  • progress_track_bg: #fef3c7 (warm yellow tint)
  • progress_track_border: 2px solid #d97706
  • progress_track_radius: 5px
  • progress_fill_radius: 3px
  • progress_color_low: #f472b6 (HOT PINK — not red)
  • progress_color_mid: #3b82f6 (ELECTRIC BLUE — not amber)
  • progress_color_high: #2dd4bf (TEAL — not green)
  • progress_label_font_size: 28px (HUGE — the hero element)
  • progress_label_font_weight: 800
  • progress_label_color: #7c3aed (PURPLE)

Deadline Tokens

  • deadline_icon: 🗓️
  • date_font_size: 13px
  • date_normal_color: #374151
  • date_normal_weight: 600
  • date_overdue_color: #db2777 (HOT PINK — not red)
  • date_overdue_weight: 800
  • date_sublabel_color: #7c3aed (PURPLE)
  • overdue_label: 🔥 OVERDUE

Row Card Tokens

  • card_border: 3px solid (color matches status shadow_color)
  • card_border_radius: 12px (rounded — playful)
  • card_background: #ffffff
  • card_margin_bottom: 12px
  • card_shadow: 6px 6px 0px (large hard offset — COLORED per status)
  • banner_height: (auto — wraps content with padding)
  • banner_padding: 16px 20px
  • content_padding: 16px 20px
  • overdue_border_color: #db2777
  • overdue_shadow_color: #db2777

Row Template Layout

Stacked vertical card with a status-colored banner on top.

    ╭──────────────────────────────────────────────────╮
    │▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
    │▓▓  API Guide.docx                             ▓▓│ ← status-colored
    │▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│   banner
    │                                                  │
    │  [IN REVIEW]  🎯 ON TRACK     72%    🗓️ 5/15/26 │ ← white content
    │                                                  │
    │  ░░████████████████████████████████░░░░░░░░░░░   │ ← warm yellow
    │                                                  │   track + amber
    ╰──────────────────────────────────────────────────╯   border
       ▓▓▓▓▓▓ ← 6px colored offset shadow

Key difference from Neobrutalism: Neobrutalism is a HORIZONTAL split (sidebar left, content right). Retro is a VERTICAL split (banner top, content bottom). Even the silhouettes are different.

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. Also update every status value string ('Draft', 'In Review', 'Revising', etc.) to match the user's actual Choice values. 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, '3px solid #db2777', if([$Status] == 'Draft', '3px solid #d97706', if([$Status] == 'In Review', '3px solid #7c3aed', if([$Status] == 'Revising', '3px solid #db2777', if([$Status] == 'Approved', '3px solid #0d9488', if([$Status] == 'Published', '3px solid #7c3aed', '3px solid #9ca3af'))))))",
      "border-radius": "12px",
      "background-color": "#ffffff",
      "margin-bottom": "12px",
      "box-shadow": "=if([$Deadline] < @now, '6px 6px 0px #db2777', if([$Status] == 'Draft', '6px 6px 0px #d97706', if([$Status] == 'In Review', '6px 6px 0px #7c3aed', if([$Status] == 'Revising', '6px 6px 0px #db2777', if([$Status] == 'Approved', '6px 6px 0px #0d9488', if([$Status] == 'Published', '6px 6px 0px #7c3aed', '6px 6px 0px #9ca3af'))))))",
      "overflow": "hidden"
    },
    "children": [
      {
        "elmType": "div",
        "style": {
          "padding": "16px 20px",
          "background-color": "=if([$Deadline] < @now, '#db2777', if([$Status] == 'Draft', '#fbbf24', if([$Status] == 'In Review', '#3b82f6', if([$Status] == 'Revising', '#f472b6', if([$Status] == 'Approved', '#2dd4bf', if([$Status] == 'Published', '#a78bfa', '#e5e7eb'))))))",
          "display": "flex",
          "align-items": "center",
          "gap": "10px"
        },
        "children": [
          {
            "elmType": "div",
            "style": {
              "font-size": "16px",
              "font-weight": "800",
              "color": "=if([$Status] == 'Draft', '#1f2937', if([$Status] == 'Approved', '#1f2937', '#ffffff'))",
              "flex": "1",
              "line-height": "1.3"
            },
            "txtContent": "=if([$FileLeafRef] == '', [$Title], [$FileLeafRef])"
          },
          {
            "elmType": "span",
            "txtContent": "=if([$Deadline] < @now, '🔥', '✨')",
            "style": {
              "font-size": "20px"
            }
          }
        ]
      },
      {
        "elmType": "div",
        "style": {
          "padding": "16px 20px",
          "display": "flex",
          "flex-direction": "column",
          "gap": "12px"
        },
        "children": [
          {
            "elmType": "div",
            "style": {
              "display": "flex",
              "align-items": "center",
              "gap": "14px",
              "flex-wrap": "wrap"
            },
            "children": [
              {
                "elmType": "span",
                "txtContent": "[$Status]",
                "style": {
                  "display": "inline-block",
                  "padding": "5px 14px",
                  "border-radius": "20px",
                  "font-size": "12px",
                  "font-weight": "700",
                  "text-transform": "uppercase",
                  "white-space": "nowrap",
                  "border": "=if([$Status] == 'Draft', '2px solid #d97706', if([$Status] == 'In Review', '2px solid #7c3aed', if([$Status] == 'Revising', '2px solid #db2777', if([$Status] == 'Approved', '2px solid #0d9488', if([$Status] == 'Published', '2px solid #7c3aed', '2px solid #9ca3af')))))",
                  "color": "=if([$Status] == 'Draft', '#1f2937', if([$Status] == 'In Review', '#ffffff', if([$Status] == 'Revising', '#ffffff', if([$Status] == 'Approved', '#1f2937', if([$Status] == 'Published', '#ffffff', '#374151')))))",
                  "background-color": "=if([$Status] == 'Draft', '#fbbf24', if([$Status] == 'In Review', '#3b82f6', if([$Status] == 'Revising', '#f472b6', if([$Status] == 'Approved', '#2dd4bf', if([$Status] == 'Published', '#a78bfa', '#e5e7eb')))))"
                }
              },
              {
                "elmType": "span",
                "txtContent": "=if([$Deadline] < @now, '🔥 AT RISK', '🎯 ON TRACK')",
                "style": {
                  "font-size": "11px",
                  "font-weight": "700",
                  "color": "=if([$Deadline] < @now, '#db2777', '#0d9488')"
                }
              },
              {
                "elmType": "span",
                "txtContent": "=toString([$Progress]) + '%'",
                "style": {
                  "font-size": "28px",
                  "font-weight": "800",
                  "color": "#7c3aed",
                  "margin-left": "auto"
                }
              }
            ]
          },
          {
            "elmType": "div",
            "style": {
              "width": "100%",
              "height": "10px",
              "background-color": "#fef3c7",
              "border": "2px solid #d97706",
              "border-radius": "5px",
              "overflow": "hidden"
            },
            "children": [
              {
                "elmType": "div",
                "style": {
                  "width": "=toString([$Progress]) + '%'",
                  "height": "100%",
                  "border-radius": "3px",
                  "background-color": "=if([$Progress] < 30, '#f472b6', if([$Progress] < 66, '#3b82f6', '#2dd4bf'))"
                }
              }
            ]
          },
          {
            "elmType": "div",
            "style": {
              "display": "flex",
              "align-items": "center",
              "gap": "6px"
            },
            "children": [
              {
                "elmType": "span",
                "txtContent": "🗓️",
                "style": { "font-size": "13px" }
              },
              {
                "elmType": "span",
                "txtContent": "=toLocaleDateString([$Deadline])",
                "style": {
                  "font-size": "13px",
                  "font-weight": "=if([$Deadline] < @now, '800', '600')",
                  "color": "=if([$Deadline] < @now, '#db2777', '#374151')"
                }
              },
              {
                "elmType": "span",
                "txtContent": "=if([$Deadline] < @now, '🔥 OVERDUE', 'DEADLINE')",
                "style": {
                  "font-size": "10px",
                  "font-weight": "=if([$Deadline] < @now, '700', '500')",
                  "color": "=if([$Deadline] < @now, '#db2777', '#7c3aed')",
                  "text-transform": "uppercase"
                }
              }
            ]
          }
        ]
      }
    ]
  }
}

Checklist — "I Can't Believe That's SharePoint"

  • ✅ Full rowFormatter — NOT default column grid
  • ✅ VERTICAL STACKED layout with colored banner on top — NOT a sidebar (structurally different from Neobrutalism)
  • ✅ Banner background FLOODS with the status color — yellow, blue, pink, teal, or lavender
  • ✅ Document name is white-on-color in the banner — bold and prominent
  • ✅ ✨ sparkle emoji in banner (🔥 for overdue) — playful decorative element
  • ✅ Card border AND shadow color change per status — colored, NEVER black
  • ✅ 6px hard offset colored shadows (bigger than Neobrutalism's 4px)
  • ✅ Rounded corners (12px) — playful, not sharp
  • ✅ Pill-shaped status badges (20px radius) with colored borders
  • ✅ Progress percentage is HUGE (28px) and PURPLE — pushed to the right
  • ✅ Progress bar track is warm yellow (#fef3c7) with amber border
  • ✅ Progress fills are PINK → BLUE → TEAL (not red → amber → green)
  • ✅ Deadline sublabel is PURPLE, overdue is HOT PINK with 🔥
  • ✅ Every status gets its own distinct hue — no repeats
  • ✅ Overdue cards: banner turns hot pink, border/shadow turn hot pink, 🔥 replaces ✨
  • ✅ The list looks like a bag of candy exploded — in a good way
  • ✅ Silhouette test: banner-on-top looks NOTHING like sidebar-on-left (Neobrutalism)

Responsive / mobile

  • ≤ 600 px: drop the colored box-shadow offset from 4 px to 2 px so it doesn't clip the next card.
  • ≤ 480 px: the banner stays full-width — it carries the identity. Stack the metadata (progress + deadline) vertically below it.
  • Hero text: the large progress percentage below the banner steps 32 px → 24 px on mobile. Do not go below 24 px.
  • Touch targets: ≥ 44 × 44 px on the row card.

Implementation notes

Status-tinted shadows render inconsistently

The colored box-shadow (hot pink for overdue, banner color elsewhere) is not portable:

  • Chrome / Edge: render the offset and color correctly.
  • Safari: occasionally mutes saturation on box-shadow colors, so the pink reads more salmon than hot.
  • Older SharePoint themes: strip multi-layer or colored box-shadow entirely.

Provide a fallback that does not depend on the shadow: the colored top banner must always render — it is the primary identity element. The shadow is decoration. When QA shows the shadow is missing in a target environment, do not add a different decoration; let the banner do the work.

The pink/blue/teal progress palette is intentional — explain it once

Consumers used to traffic-light progress (red < 30% → amber → green ≥ 70%) will see a 95 % card filled in teal and assume the style is broken. It is not. Retro Memphis progress goes pink → blue → teal by design — each value gets its own distinct hue, the way 80s Memphis palettes worked.

When applying this style for the first time in a tenant, surface this fact in a single sentence to the user: "Progress in Retro Memphis uses pink → blue → teal instead of red → amber → green — that's intentional."

Frequently asked questions

What does the Style Retro AI skill do?

Retro Memphis style tokens and row template for the list-styling skill. Bright contrasting colors, colored shadows, playful stacked card with a status-colored top banner and large progress number. Layout is a stacked vertical card with a bold colored header strip — NOT a sidebar layout. Use when the user says "retro," "memphis," "80s," "90s," "colorful," "playful," "fun style," or similar.

Why use Style Retro on TypingMind?

Because you install it once and use it with any model. Style Retro 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 Retro in TypingMind?

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

Which AI models can use Style Retro?

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 Retro?

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

Is the Style Retro 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 👇