nexu-io/open-design

huashu-keynote-black

Open Design's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.

80CollectingReads files
See how to use itView GitHub source
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/huashu-keynote-black"
Automated source guideReview and auditDeep source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded review guide: huashu-keynote-black

Produce a single-file, black-stage keynote deck. You are directing a launch event, not writing a document: the screen is a stage, every page is one beat, and the audience must be able to read it from the last row. The visual system, canvas contract, and navigation runtime are lo…

npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/huashu-keynote-black"
Check the pinned source

The pinned source contains enough sections and task detail for a source-grounded deep guide; automated content is still not an independent test.

1,140 source words · 8 usable sections

Review workflow

Read huashu-keynote-black through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

Workflow

1. Clarify once: topic, audience, page count, the ONE accent, and which 2–3 numbers are the protagonists (plus the price, if there is one). This style lives and dies by its hero numerals — pick them before any page. 2. Copy example.html, retitle, then replace each section's cont…

SKILL.md · Workflow
Clarify once: topic, audience, page count, the ONE accent, and whichCopy example.html, retitle, then replace each section's contentFor ≥ 5 pages, showcase first: build the cover + one big-number page,
02

Hard spec (locked — violating any line is a regression)

1. One idea per screen: each page centers one element with flex — one word, one number, one sentence, or one comparison. If a page needs a paragraph, it needs to become two pages. 2. Giant numeral theater: hero numbers are 320–460px, weight 900, tracking ≈ −0.04em, font-variant-…

SKILL.md · Hard spec (locked — violating any line is a regression)
One fixed at 1920 × 1080 px, centered withEach page is one inside stage with aNavigation (keep the script verbatim): ←/↑/PageUp previous,
03

Canvas & runtime

One fixed at 1920 × 1080 px, centered with

SKILL.md · Canvas & runtime
One fixed at 1920 × 1080 px, centered withEach page is one inside stage with aNavigation (keep the script verbatim): ←/↑/PageUp previous,
04

Design tokens (:root — keep the names; only --accent may change)

--accent is a single choice per deck from exactly three values:

SKILL.md · Design tokens (:root — keep the names; only --accent may change)
--accent is a single choice per deck from exactly three values:Fonts load via one Google Fonts @import (Inter + Noto Sans SC); no other- --accent is a single choice per deck from exactly three values: Mi orange FF6900, Spotify green 1ED760, Apple blue 2997FF. Mixing two of them in one deck is the cardinal sin of this style. - Fonts load via one Google…
05

Signature devices (the visual DNA — every deck must show them)

1. One idea per screen: each page centers one element with flex — one word, one number, one sentence, or one comparison. If a page needs a paragraph, it needs to become two pages. 2. Giant numeral theater: hero numbers are 320–460px, weight 900, tracking ≈ −0.04em, font-variant-…

SKILL.md · Signature devices (the visual DNA — every deck must show them)
One idea per screen: each page centers one element with flex — oneGiant numeral theater: hero numbers are 320–460px, weight 900,One-word manifesto: 240–300px weight-900 word ending in an accent

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Source-grounded prompt

Use for a review or audit task while explicitly checking the source sections.

Use huashu-keynote-black for this review or audit task: [task]. Inputs and constraints: [details]. Work through these pinned SKILL.md sections: “Workflow”, “Hard spec (locked — violating any line is a regression)”, “Canvas & runtime”, “Design tokens (:root — keep the names; only --accent may change)”, “Signature devices (the visual DNA — every deck must show them)”. Cite the concrete requirements that shape each step, do not invent capabilities absent from the source, and verify the result against: [acceptance criteria].

Review checklist

Verify each item before delivery

The source section “Workflow” has been checked.

The source section “Hard spec (locked — violating any line is a regression)” has been checked.

The source section “Canvas & runtime” has been checked.

The source section “Design tokens (:root — keep the names; only --accent may change)” has been checked.

Static permission evidence

Inspect the exact source lines that triggered a signal

These are source excerpts matched by deterministic rules, not findings of malicious behavior, safety, or actual execution.

Choose a different workflow

When another Skill is the better fit

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

design-intelligence

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does the huashu-keynote-black source document cover?

Produce a single-file, black-stage keynote deck. You are directing a launch event, not writing a document: the screen is a stage, every page is one beat, and the audience must be able to read it from the last row. The visual system, canvas contract, and navigation runtime are lo…

How do I install huashu-keynote-black?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/huashu-keynote-black". Inspect the command and pinned source before running it.

Which permission-related actions were detected?

Static rules flagged read-files in the source; the page lists the matching lines and excerpts.

Repository stars
82,073
Repository forks
9,485
Quality
80/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

80/100
Documentation24/30
Specificity16/25
Maintenance20/20
Trust signals20/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

ab-testing by coreyhaines31

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

churn-prevention by coreyhaines31

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

design-intelligence by event4u-app

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

design-system-capture by event4u-app

Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.

existing-ui-audit by event4u-app

Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 6 min

Keynote Black · 黑场大数字

Produce a single-file, black-stage keynote deck. You are directing a launch event, not writing a document: the screen is a stage, every page is one beat, and the audience must be able to read it from the last row. The visual system, canvas contract, and navigation runtime are locked by example.html. Start from example.html, replace content only — do not rewrite the design or the script. Do not introduce any color or font outside this spec.

Generated from the「黑底巨型数字剧场 / Black Big-Number Stage」entry (大胆派, 还原 97%) of references/design-styles.md in huashu-design by 花叔 (alchaincyf), MIT licensed — references: Steve Jobs' 2007 iPhone keynote, Lei Jun's Xiaomi SU7 Ultra launch, Spotify Wrapped, Presentation Zen. The upstream entry is a written spec; this plugin realizes it as a full multi-section deck while preserving its DNA.

Not to be confused with siblings: dir-key-nav-minimal rotates 8 colored monochrome pages (indigo/cream/crimson/jade…) — this deck is constant pure black with one accent and no color rotation; studio is a black + electric-yellow design-studio text style with no big numbers; ppt-keynote is a light generic Keynote card deck.

Hard spec (locked — violating any line is a regression)

Canvas & runtime

  • One <div id="stage"> fixed at 1920 × 1080 px, centered with position: fixed; top: 50%; left: 50%; a fit() function applies translate(-50%, -50%) scale(min(innerWidth/1920, innerHeight/1080)) on load and resize. All inner layout in px — the scaler owns responsiveness.
  • Each page is one <section class="slide"> inside #stage with a data-screen-label="01 封面"-style label; exactly one slide carries .active. There are no light pages — every page is the black stage.
  • Navigation (keep the script verbatim): //PageUp previous, //Space/PageDown next, Home/End first/last; #/N hash routing (1-indexed) read on load + hashchange, written via history.replaceState; click left third = back, rest = forward; fixed counter pill bottom-right, key-hint bottom-left. No external JS, no build step — the file must open inside a sandboxed iframe via file://.

Design tokens (:root — keep the names; only --accent may change)

TokenValueRole
--stage#000000the stage — every page background
--ink#FFFFFFprimary type, pure white only
--accent#FF6900the one accent — deck-wide single choice
--muted#9B9B9Bcaptions / secondary lines
--faint#5F5F5Fwhisper labels, footnotes
--line#2A2A2Ahairlines, capsule borders
--bar-base#3A3A3Alosing / baseline comparison bar
--sans'Inter', 'Geist', 'Noto Sans SC', 'PingFang SC', 'Hiragino Sans GB', 'Microsoft YaHei', sans-serifthe only family
  • --accent is a single choice per deck from exactly three values: Mi orange #FF6900, Spotify green #1ED760, Apple blue #2997FF. Mixing two of them in one deck is the cardinal sin of this style.
  • Fonts load via one Google Fonts @import (Inter + Noto Sans SC); no other external resource of any kind.

Signature devices (the visual DNA — every deck must show them)

  1. One idea per screen: each page centers one element with flex — one word, one number, one sentence, or one comparison. If a page needs a paragraph, it needs to become two pages.
  2. Giant numeral theater: hero numbers are 320–460px, weight 900, tracking ≈ −0.04em, font-variant-numeric: tabular-nums, pure white, with a small uppercase unit beside or below — the unit (or one glyph) may take the accent. Exactly one quiet --muted caption line underneath.
  3. One-word manifesto: 240–300px weight-900 word ending in an accent full stop (<span class="a">。</span>), with one whisper line below.
  4. Stage spotlight: a single faint radial-gradient(closest-side, rgba(255,255,255,.05), transparent) ellipse behind the hero element (.spotlight). This is the only decoration allowed — no other gradients, no photos, no emoji, no icon fonts, no shadows, no border-radius (runtime counter pill excepted).
  5. Whisper top label: 12px / 600 / 4px-tracking uppercase --faint label centered at the top of every page (event name · chapter). It is chrome, not content — keep it nearly invisible.
  6. Accent-vs-grey comparison bars: .vs-row = white 20px label left, full-width --line-hairline-topped track, accent fill for the subject vs --bar-base fill for the baseline, values printed at the right end in tabular-nums (accent value white-hot, baseline value --muted). The page's subject is always the accent bar.
  7. Price reveal: small struck-through --muted expectation line above a giant white price whose currency glyph is the accent. The deck's climax.

Layout enumeration (use 5+ per deck, never one layout everywhere)

LayoutRole
coverwhisper event label + product name with accent full stop + one sub line
agenda"今晚,只讲三件事。" — 3 numbered rows, accent numerals, hairline-separated
one-word240–300px single word + accent 。 + whisper subtitle
big-number320–460px numeral + uppercase unit + one caption (the workhorse — use 2–3)
versussubject vs baseline spec bars, accent vs --bar-base, tabular values
quote64–88px white statement, one phrase in accent, attribution in --faint
pricestrikethrough expectation + giant price, accent currency glyph
one-more-thingthe classic teaser line + one whisper reveal
closing「谢谢。」-scale farewell + key-hint capsule

Typography & scale (read from the last row)

  • Geometric bold sans only, weights 700–900; headlines 96–180px, hero words 240–300px, hero numbers 320–460px, all with negative tracking (−0.02 to −0.05em). Captions 20–24px --muted; whisper labels 12–13px uppercase 4px-tracking --faint. Nothing between 24px and 64px — this style has no "medium" type; it whispers or it shouts.
  • Every digit everywhere sits in tabular-nums. Large numbers take thin comma grouping (1,024).
  • Chinese copy uses 「」 quotes; the accent is applied to a single glyph or a single phrase, never a whole headline.

Rhythm & discipline

  • Default 10 pages (8–11 allowed). Sequence builds like a launch event: cover → agenda → alternating word/number beats → versus → quote → price reveal → one more thing → closing. Place the biggest number and the price in the back half — the deck must escalate.
  • Accent budget: at most one accent device per page; pages with none are encouraged. Pure black + pure white carries the style; the accent is the laser pointer, not the lighting rig.
  • Real content only — the user's actual words and numbers; missing data gets an honest <!-- 待用户提供 --> placeholder, never invented statistics. (The seed deck's 「曜石 YAO」 launch is fictional demo content and must be fully replaced.)

Workflow

  1. Clarify once: topic, audience, page count, the ONE accent, and which 2–3 numbers are the protagonists (plus the price, if there is one). This style lives and dies by its hero numerals — pick them before any page.
  2. Copy example.html, retitle, then replace each section's content following the layout enumeration. Keep tokens, spotlight, whisper labels, and the script intact. Change --accent only to one of the three sanctioned values.
  3. For ≥ 5 pages, showcase first: build the cover + one big-number page, confirm the grammar, then batch the rest.
  4. Self-check before delivery: arrow through every page; counter and #/N hash stay in sync; no overflow beyond 1920×1080; one idea and ≤ 1 accent device per page; every digit tabular; versus bar widths match their printed values proportionally; no second accent anywhere; no leftover demo (「曜石」/「YAO」) text; grep for TODO.
Skill path
plugins/_official/examples/huashu-keynote-black/SKILL.md
Commit SHA
89d6d4ef21ba
Repository license
Apache-2.0
Data collected