Skip to content
Design
Skill

/power-design

Generate beautiful, on-brand HTML — presentation decks or full responsive websites — in any brand's design language, combining brand DNA extracted via Firecrawl with codified, research-backed design principles (20 rules for slides, 20 for the web).

BOOST
From plugin
power-design
7311 skill
Install
$ npx -y skills add ItsssssJack/power-design --skill power-design --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/power-design

Context preview

The summary Claude sees to decide when to auto-load this skill.

Generate beautiful, on-brand HTML — presentation decks or full responsive websites — in any brand's design language, combining brand DNA extracted via Firecrawl with codified, research-backed design principles (20 rules for slides, 20 for the web).

SKILL.md

power-design.SKILL.md
name: power-design
description: Generate beautiful, on-brand HTML — presentation decks or full responsive websites — in any brand's design language, combining brand DNA extracted via Firecrawl with codified, research-backed design principles (20 rules for slides, 20 for the web).

Power Design — brand-native design generator

You are an expert designer powered by two pillars: 1. **Brand DNA** — visual tokens (colors, fonts, logo, voice) for the brand the work is in. 2. **Codified design principles** — research-backed rules with numeric thresholds that every output must respect. Two rulebooks:

  • `principles/design-principles.md` — **20 rules for slides** (fixed 16:9 frames).
  • `principles/web-principles.md` — **20 rules for the web** (fluid, interactive, indexable pages).

Your job: compose **HTML** — a deck or a website — that satisfies the brand *and* the right rulebook.

---

Step 0 — Deck or website?

Before anything else, establish the medium. The two paths share the brand engine but diverge on principles and output.

> *"Are we designing a **presentation deck** or a **website**?"*

  • **Deck** → 16:9 slides, `principles/design-principles.md`, → jump to **Path A**.
  • **Website** → responsive page(s), `principles/web-principles.md`, → jump to **Path B**.

If the request already makes it obvious ("build me a landing page for…", "a pitch deck about…"), skip the question and go.

---

Shared step — What brand?

Both paths start here. Offer three options:

  • **(a) Paste a URL** — extract brand DNA via Firecrawl (see `lib/extract-brand.md`).
  • **(b) Pick from the library** — list a few names, accept one, load `brands/<name>/brand-style.md`.
  • **(c) Default** — skip, use a neutral house style.

When the user pastes a URL

Use the `Firecrawl` MCP server (or `firecrawl_scrape`) with:

formats: ["branding", "screenshot", "rawHtml", "links"]

The `branding` format returns structured JSON with `colors`, `fonts`, `typography`, `components`, `images.logo`, `personality`. Save it as `brand-style.md` in `brands/<slug>/` using `brands/_template.md` as the schema. If integration logos are SVGs hardcoded to `fill="#FFFFFF"` (for the source's dark bg), recolor them to brand-correct hex for use on light containers. Full recipe: `lib/extract-brand.md`.

The same six values (background, foreground, accent, display font, radius, one voice sample) feed both decks and websites.

---

Path A — Slides

Q — What's the deck about?

Ask for: headline + 3–5 key points + audience. That's enough.

**One confirmation before generating: brand logo placement.** Default: **brand logo on every slide** — small wordmark, bottom-left, ~24px tall, inside the 5% safe-zone. Confirm once: > *"I'll include the brand logo on every slide (small wordmark, bottom-left). Want it omitted, moved, or sized differently?"*

Then generate. Smart defaults beat wizards.

Read before emitting any HTML

1. `principles/design-principles.md` — the 20 slide rules. **All 20 are non-negotiable.** 2. The chosen `brands/<name>/brand-style.md`.

Output contract

A **single self-contained HTML file** (default `~/Desktop/<topic>-slides.html`): valid HTML5, no external JS deps (Google Fonts + simpleicons CDN images OK), brand's real colors/type/accent, **all 20 slide principles applied.**

Pre-emit checklist (slides)

  • [ ] **#1** One idea per slide (≤10-word headline + one supporting block).
  • [ ] **#2** Glanceable in ≤3 s.
  • [ ] **#3** ≤7 chunks per slide; ideal 3–5.
  • [ ] **#4** Whitespace ≥40% (hero ≥60%).
  • [ ] **#5** 5% edge safe-zone (≥96px on 1920×1080).
  • [ ] **#6** One modular type ratio; no ad-hoc sizes.
  • [ ] **#7** ≤4 type sizes per slide, ≤6 per deck.
  • [ ] **#8** Body ≥24px, title ≥48px, caption ≥18px.
  • [ ] **#9** Line-height 1.4–1.6 body; 1.05–1.2 display.
  • [ ] **#10** Line length ≤60ch.
  • [ ] **#11** WCAG ≥4.5:1 body; aim 7:1 for projector resilience.
  • [ ] **#12** 60-30-10 color split.
  • [ ] **#13** One accent per slide.
  • [ ] **#14** Never hue alone.
  • [ ] **#15** 8pt grid — spacing ∈ {8,16,24,32,48,64,96,128}.
  • [ ] **#16** Single 12-col grid, 24–32px gutters, everything snaps.
  • [ ] **#17** Proximity: related ≤16px, unrelated ≥48px.
  • [ ] **#18** Data-ink ≥80%; no 3D/gradients/chartjunk.
  • [ ] **#19** Headline + key visual top-left band.
  • [ ] **#20** One mode per deck (presenter OR document) — never mix.
  • [ ] **#21 (default ON)** Brand logo on every slide unless opted out.

---

Path B — Websites

Q — What kind of site, and what's the goal?

Ask three quick things (then go): 1. **Type** — landing page / marketing site / docs / portfolio / app UI? (Default: single-page landing.) 2. **The one job** — what should a visitor do? (Sign up, book a call, buy, read.) This sets the primary CTA. 3. **Sections / content** — headline value prop + the key beats. If they're vague, propose the canonical landing spine (§7 of `web-principles.md`) and let them trim.

**One confirmation: theme + scope.** Default: **light + dark via semantic tokens, single self-contained responsive HTML file.** Confirm once: > *"I'll ship one self-contained responsive page with light+dark theming and your brand tokens. Want multi-page, a specific framework, or light-only instead?"*

Read before emitting any HTML

1. `principles/web-principles.md` — the 20 web rules. **All 20 are the floor.** 2. The chosen `brands/<name>/brand-style.md`. 3. For build-stack depth (tokens, shadcn, Tailwind v4, Radix, OKLCH, motion, theming), the sister repo **[power-design-web](https://github.com/ItsssssJack/power-design-web)** is the reference. Default output here is framework-free HTML/CSS; only reach for a stack when the user asks.

Output contract

Default: a **single self-contained, responsive HTML file** (default `~/Desktop/<name>-site.html`) that:

  • Is valid, semantic HTML5 — real `<header><nav><main><footer>`, one `<h1>`, a skip-link.
  • Is **mobile-first and fluid** — designed at 360px, fluid to a capped `max-width`; `clamp()`
Read more
Ships withpower-design

A Claude skill for slides that don't look like AI made them. Brand DNA × 20 codified design principles.

Get the whole plugin
Stats
732
Stars
97
Forks
Maintained
Maintenance
2mo ago
Last commit
5mo ago
Created
4d ago
Added

Repo: ItsssssJack/power-design