playbook/antigravity-awesome-skills/skills/pptx-deck-creation/references/design-profiles.md

PPTX Design Profile Catalog

This is the bundled reference for design profiles. Use it for all new decks. Design context is built-in and always available.

Quick-Select Guide

Profile ID	Best for
fluent-ui-design-tokens	Microsoft, M365, Teams, Power Platform, enterprise — default for new decks
getdesign-md-design-systems	Live fetch — brand-accurate DESIGN.md analyses (Apple, Stripe, Linear, Notion, …) from getdesign.md when matching a real product's look
corazzon-pptx-design-styles	30 modern style catalog; use when visual variety or multiple direction options are needed
primer-primitives	GitHub-style, developer products, token-driven UI reviews, engineering docs

Profiles

fluent-ui-design-tokens

Name: Fluent UI Design Token Guidance Kind: design-system-context License: MIT — Copyright (c) Microsoft Corporation Source: microsoft/fluentui Token categories: color, spacing, border radius, font, line height, stroke, shadow, duration, easing Themes: webLightTheme, webDarkTheme, teamsLightTheme, teamsDarkTheme, teamsHighContrastTheme Agent rule: Use design tokens instead of hardcoded colors, spacing, or typography values. Best for: Microsoft-aligned decks, Teams, M365, Power Platform governance, enterprise product reviews

---

getdesign-md-design-systems

Name: getdesign.md — Production-grade DESIGN.md Brand Analyses (Live Fetch) Kind: live-design-reference-context License: Per-entry; independent analyses published by VoltAgent. Reference/inspiration only — not official, not affiliated with or endorsed by the brands, and not redistributable assets. All trademarks belong to their owners. Source: getdesign.md · catalog: getdesign.md/design-md · spec basis: Google Stitch's DESIGN.md · awesome list: VoltAgent/awesome-design-md Catalog size: 300+ brand/product DESIGN.md analyses (e.g., Apple, Stripe, Linear, Notion, Vercel, Figma, Airbnb, Spotify, Tesla, IBM/Carbon, NVIDIA)

What getdesign.md is: A browsable frontend for the open-source awesome-design-md collection. Each catalog entry is a single DESIGN.md file — a structured Markdown document (the format introduced by Google Stitch) that captures the publicly observable design language of a real website so a coding agent can use it as reference while building original UI. They are analyses of patterns, not pixel-exact reproductions of the source sites.

Anatomy of a DESIGN.md entry (consistent section taxonomy across the catalog):

• 01 — Colors: Core palette as named tokens with hex + role (e.g., Primary #533afd, Ink #0d253d, Canvas #ffffff, Canvas Alt, Hairline, Muted, Accent), plus an extended brand/accent and gradient-stop set.
• 02 — Typography: A type scale split into display and body tiers; each token lists size / weight / line-height / letter-spacing and its role (e.g., display-xxl 56px/300/1.12/-1.4px, body-md 16/400/1.55, micro-cap 12/700 eyebrow).
• 03–05 — Components: Button variants (primary/secondary/outline/on-dark), card examples (incl. inverted/featured tiers), and form-element conventions (input borders, focus treatment).
• 06–08 — Foundations: Spacing scale (typically an 8px base with sub-units), border-radius scale (input → pill 9999px), and elevation/shadow stacks (L0 flat → L3 toast).
• 09 — Responsive: Breakpoint stair (mobile/tablet/desktop/wide), touch-target minimums (≥44×44px), and collapsing strategy.
• Plus a short prose intro describing the brand's "signature" (mood, motifs, hero treatment) and an Additional Links/preview block.

How users consume it (outside this skill): The getdesign package offers an add {slug} action that drops the file into a project, or users can choose "Download DESIGN.md"; some entries also offer a full website starter kit at …/design-md/kit. Inside this skill, treat the page as a read-only reference — fetch and extract signals; do not run the installer.

Fetch contract: Each entry is reachable at https://getdesign.md/{slug}/design-md (e.g., https://getdesign.md/stripe/design-md, https://getdesign.md/linear.app/design-md). Some slugs include the TLD (linear.app, mistral.ai, x.ai, opencode.ai). Browse https://getdesign.md/design-md to resolve the correct {slug}. Agent rule: Use this profile only when the user asks for a deck that should match a specific real-world brand or product aesthetic. Fetch the matching DESIGN.md entry, extract the color tokens, type scale, spacing/radius/elevation foundations, and signature motifs, then lock them in summary.design_context. Translate signals into explicit layout_tree primitives — do not embed scraped images, screenshots, or copy proprietary brand assets/logos. Record the entry URL and the "independent analysis, not affiliated" disclaimer as the design source. If the fetch fails or no slug matches, fall back to a bundled profile and note the fallback. Best for: Decks that must visually echo a known product or company; brand-accurate palette/typography/foundation sourcing without maintaining a local copy

---

corazzon-pptx-design-styles

Name: corazzon/pptx-design-styles — 30 Modern PPTX Style Templates Kind: pptx-style-template-context License: MIT — Copyright TodayCode / corazzon contributors Source: corazzon/pptx-design-styles 30 styles: Glassmorphism, Neo-Brutalism, Bento Grid, Dark Academia, Gradient Mesh, Claymorphism, Swiss International, Aurora Neon Glow, Retro Y2K, Nordic Minimalism, Typographic Bold, Duotone Color Split, Monochrome Minimal, Cyberpunk Outline, Editorial Magazine, Pastel Soft UI, Dark Neon Miami, Hand-crafted Organic, Isometric 3D Flat, Vaporwave, Art Deco Luxe, Brutalist Newspaper, Stained Glass Mosaic, Liquid Blob Morphing, Memphis Pop Pattern, Dark Forest Nature, Architectural Blueprint, Maximalist Collage, SciFi Holographic Data, Risograph Print Style families: modern-ui, editorial, retro, technical, luxury, organic, experimental Source inputs per style: hex colors, font pairings, layout rules, signature elements, avoid lists Agent rule: Pick one style, lock its palette and typography, then translate visual effects into explicit editable layout_tree primitives. Use raster assets only as supporting visuals. Do not mix styles accidentally. Best for: Choosing a predefined modern style from a broad catalog; generating multiple visual direction options before deck production

---

primer-primitives

Name: Primer Primitives Design Tokens Kind: design-system-context License: MIT — Copyright (c) 2018 GitHub Inc. Source: primer/primitives Token categories: color, spacing, typography, motion, z-index Spacing scale: xxs, xs, sm, md, lg, xl Typography roles: display, title, subtitle, body, caption, codeBlock, codeInline Color examples: #ffffff, #1f2328, #F6F8FA, #0969da, #1a7f37, #cf222e Best for: GitHub-style decks, developer products, token-driven UI reviews, engineering documentation

Use the entries above to:

1. Select the profile ID that best matches the user's audience, topic, and delivery context.
2. Lock the palette, typography, and signature element conventions described in the profile's source_signals.
3. Record the selected profile ID, source URL, and license in summary.design_context before building the deck spec.
4. Translate the style signals directly into explicit layout_tree primitives — colors, fills, rules, card shells, accent bands, and bboxes.

Fetching Live References from getdesign.md

When the user wants a deck that mirrors a specific real brand or product, use the getdesign-md-design-systems profile to pull a live analysis:

1. Browse the catalog at https://getdesign.md/design-md to find the brand and its {slug} (some slugs carry a TLD, e.g. linear.app, mistral.ai).
2. Fetch the entry at https://getdesign.md/{slug}/design-md (e.g., https://getdesign.md/apple/design-md).
3. Read the DESIGN.md sections and map them onto deck decisions:
   • Colors (01) → deck palette: Primary/Accent for emphasis and CTAs, Ink/Muted for text, Canvas/Canvas Alt for backgrounds and bands, Hairline for rules and dividers.
   • Typography (02) → title vs. body type roles, weights, and relative size hierarchy (display tier for slide titles/kickers, body tier for content).
   • Foundations (06–08) → spacing rhythm, corner radii for card shells/buttons, and elevation cues for layered cards.
   • Components (03–05) + signature motifs (intro prose) → card/pill/divider styling and the brand's hallmark accents (e.g., gradient bands).
4. Record the entry URL, the "independent analysis / not affiliated" disclaimer, and the extracted tokens in summary.design_context, then translate the signals into explicit layout_tree primitives.
5. Never embed scraped imagery, screenshots, logos, or other proprietary brand assets; use the signals as design guidance only. If the fetch fails or no slug matches, fall back to a bundled profile and flag the fallback in summary.design_context.