nexu-io/open-design

huashu-bento-insight

Open Design vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.

80CollectingReads files
See how to use itView GitHub source
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/huashu-bento-insight"
Automated source guideDesignDeep source

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

Reorganized from the pinned upstream SKILL.md

Source-grounded design guide: huashu-bento-insight

Produce a single-file, Apple-keynote-school bento deck. You are a metrics curator working in HTML: every card holds exactly one insight, every number is tabular, and whitespace does the talking. The visual system, canvas contract, and navigation runtime are locked by example.htm…

npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/huashu-bento-insight"
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,205 source words · 8 usable sections

Design process

Read huashu-bento-insight 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, and which 3–6 metrics are the protagonists (plus the single most important one for the one-insight page). This style lives on its numbers — pick them before writing pages. 2. Copy example.html, retitle, then replace each section's co…

SKILL.md · Workflow
Clarify once: topic, audience, page count, and which 3–6 metrics areCopy example.html, retitle, then replace each section's contentFor ≥ 5 pages, showcase first: build the cover + the master bento
02

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

1. Unequal-height bento grid: CSS Grid (repeat(6, 1fr) columns × 1.18fr 1fr-style rows) with mixed span widths and one tall grid-row: span 2 hero card. Never a uniform equal-cell grid — unequal heights are the style. Gap 20–24px. 2. Card anatomy: --card surface + 1px solid var(-…

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, re-theme values only)

Fonts come from one Google Fonts @import (Inter + Geist + Geist Mono) —

SKILL.md · Design tokens (:root — keep the names, re-theme values only)
Fonts come from one Google Fonts @import (Inter + Geist + Geist Mono) —Brand may be re-themed to the user's primary color, but the triad stays:- Fonts come from one Google Fonts @import (Inter + Geist + Geist Mono) — the only allowed external reference. No other CDN, no icon fonts, no Chart.js/mermaid; charts are pure CSS/SVG. - Brand may be re-themed to the u…
05

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

1. Unequal-height bento grid: CSS Grid (repeat(6, 1fr) columns × 1.18fr 1fr-style rows) with mixed span widths and one tall grid-row: span 2 hero card. Never a uniform equal-cell grid — unequal heights are the style. Gap 20–24px. 2. Card anatomy: --card surface + 1px solid var(-…

SKILL.md · Signature devices (the visual DNA — every deck must show them)
Unequal-height bento grid: CSS Grid (repeat(6, 1fr) columns ×Card anatomy: --card surface + 1px solid var(--hairline) +Tabular KPI numerals: every number in --mono with

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 design task while explicitly checking the source sections.

Use huashu-bento-insight for this design 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, re-theme values only)”, “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].

Design 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, re-theme values only)” 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

prospecting

When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research,"

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

Open source detail

emails

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold out

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

Open source detail

free-tool-strategy

Plans free tools, calculators, generators, and interactive widgets that attract target audience through search and social sharing. Engineering as marketing — build something useful, capture leads. Use when someone wants to build a free tool for marketing, says 'free tool', 'calculator', 'generator', 'engineering as marketing', 'side project marketing', 'interactive widget', 'lead generation tool', 'SEO tool', 'growth hack', 'build something to attract users', or wants to attract users through ut

A separate implementation from MoizIbnYousaf/marketing-cli; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does the huashu-bento-insight source document cover?

Produce a single-file, Apple-keynote-school bento deck. You are a metrics curator working in HTML: every card holds exactly one insight, every number is tabular, and whitespace does the talking. The visual system, canvas contract, and navigation runtime are locked by example.htm…

How do I install huashu-bento-insight?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/huashu-bento-insight". 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.

prospecting by coreyhaines31

When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research,"

emails by coreyhaines31

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold out

free-tool-strategy by MoizIbnYousaf

Plans free tools, calculators, generators, and interactive widgets that attract target audience through search and social sharing. Engineering as marketing — build something useful, capture leads. Use when someone wants to build a free tool for marketing, says 'free tool', 'calculator', 'generator', 'engineering as marketing', 'side project marketing', 'interactive widget', 'lead generation tool', 'SEO tool', 'growth hack', 'build something to attract users', or wants to attract users through ut

sales-enablement by coreyhaines31

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. Fo

suede-signup by JasonColapietro

Cut friction out of registration: field-by-field audit, social versus email tradeoffs, progressive profiling, and recovering abandoned signups. Use when the user has a signup, registration, or trial-start flow that loses people partway through. Also use when the user mentions 'signup conversions,' 'registration friction,' 'signup form optimization,' 'free trial signup,' 'reduce signup dropoff,' 'account creation flow,' 'people aren't signing up,' 'signup abandonment,' 'trial conversion rate,' 'n

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

Bento Insight Grid · 便当格洞见

Produce a single-file, Apple-keynote-school bento deck. You are a metrics curator working in HTML: every card holds exactly one insight, every number is tabular, and whitespace does the talking. 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「Bento便当格模块网格 / Bento Grid」entry (neutral school, 95% fidelity) of references/design-styles.md in huashu-design by 花叔 (alchaincyf), MIT licensed. Reference lineage: Apple Keynote Bento-Grid era, new-generation MBB Bento/Big-Type decks (2024–2026), Stripe annual-report metric-card matrices, Pitch.com QBR templates. Distinct from the fixed 8-cell weekly-report KPI scenario: this is a general bento aesthetic theme — free-form unequal-height composition, weight contrast, sparklines.

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; cream pages add .cream.
  • 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; rounded 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, re-theme values only)

TokenValueRole
--bg#F5F5F7master page background (Apple light grey)
--cream#FBFAF7warm cream alternate page background
--card#FFFFFFdefault card surface
--card-dark#1D1D1Fhero inverse card (≤ 1–2 per deck spread)
--tint-blue#EAF2FEtinted card — brand
--tint-green#EAF8F0tinted card — positive
--tint-warm#FDF3E7tinted card — highlight
--ink#1D1D1Fprimary text
--ink-soft#424245body copy
--muted#6E6E73secondary labels
--faint#AEAEB2tertiary captions
--dark-ink / --dark-mut#F5F5F7 / #98989Dtext on dark card
--hairline#E8E8ED1px card border
--brand#0071E3brand blue — primary accent
--green#1FA958positive delta accent
--orange#F08A24highlight / caution accent
--shadow0 2px 6px rgba(0,0,0,.04), 0 12px 32px rgba(0,0,0,.05)micro shadow
--r-lg / --r-md / --r-sm32px / 24px / 14pxradius scale
--sans'Inter', 'Geist', -apple-system, 'PingFang SC', …body family
--display'Geist', 'Inter', …display headlines
--mono'Geist Mono', 'SF Mono', ui-monospace, …all KPI numerals
  • Fonts come from one Google Fonts @import (Inter + Geist + Geist Mono) — the only allowed external reference. No other CDN, no icon fonts, no Chart.js/mermaid; charts are pure CSS/SVG.
  • Brand may be re-themed to the user's primary color, but the triad stays: one brand + green (positive) + orange (caution). A fourth accent is the cardinal sin of this style. No gradients, no glassmorphism, no neon.

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

  1. Unequal-height bento grid: CSS Grid (repeat(6, 1fr) columns × 1.18fr 1fr-style rows) with mixed span widths and one tall grid-row: span 2 hero card. Never a uniform equal-cell grid — unequal heights are the style. Gap 20–24px.
  2. Card anatomy: --card surface + 1px solid var(--hairline) + var(--shadow) micro shadow + 24–32px radius. One insight per card: a card-label (14px/600 muted) on top, one protagonist below. Tinted and dark cards are seasoning — at most 1 dark + 2 tinted per bento page.
  3. Tabular KPI numerals: every number in --mono with font-variant-numeric: tabular-nums, weight 700–800, negative tracking; units in a .unit span at ~0.42em muted. Deltas are rounded .delta pills (↑ 42%) in green/orange tints.
  4. Sparklines & charts: inline <svg preserveAspectRatio="none"> polyline + optional 14%-opacity area fill for sparklines; bar charts are flex columns of rounded div bars with the current period in --brand and history in #E4E4E9, values printed in mono above each bar.
  5. Linear icons: inline SVG, stroke="currentColor", stroke-width="1.8", round caps, sitting in a 52px rounded tinted .icon chip. No emoji anywhere.
  6. Display weight contrast: headlines pair weight 800–900 spans with 300–400 .thin/.lite spans in the same line (e.g. 「稳健增长,全面提 效。」 with the verb heavy and the qualifier light). Kickers are 14px mono uppercase, 3px tracking, brand-colored.

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

LayoutRole
covercream page, giant 130–150px display statement + mini bento strip of 3–4 KPI cards
agenda4 equal cards, oversized hairline-grey mono numbers, first number brand-colored
bentothe master: 6-col × 2-row unequal grid, dark hero card with sparkline + 5 satellite cards
one-insightcream page, one 300–380px mono numeral protagonist + label + chip row
chartbig bar-chart card (2 rows tall) + 2 side insight cards
feature-bento3-col grid with wide cards, linear icon chips + meta footer rows
quoteoversized quote card (brand SVG quote marks, key phrase in brand color) + 2 stat cards
stats-2x22×2 grid of 80–90px numerals, one dark + one tinted card
roadmap3 track cards: mono Q-tag, dot-bulleted list, hairline-topped target footer
closingcream page, giant display farewell (one brand-colored word) + summary card strip

Typography & scale (read from 10 meters)

  • Display headlines 120–170px weight 900 on cover/closing, tracking −6 to −8px; page titles 62px weight 800, tracking −2px. Hero KPI 84–96px; the one-insight numeral 300–380px weight 800 with its %/unit glyph in --brand.
  • Body 15–19px --muted/--ink-soft, line-height 1.6–1.7. Labels 14px/600. Mono meta rows 14px with 1–2px tracking.
  • Chinese copy is idiomatic and uses 「」 quotes and full-width punctuation; zh/en mixing is welcome (mono English kickers over Chinese headlines is the house voice).

Rhythm & discipline

  • Default 10 pages (8–11 allowed). Page backgrounds alternate --bg and --cream for breathing rhythm; cards stay white/tinted/dark.
  • Whitespace is a feature: card padding ≥ 36px, page padding ≈ 84–110px; never cram more than 7 cards on one bento page.
  • One insight per card — if a card needs two numbers, it is two cards.
  • Honest data only — the user's actual numbers; missing data gets an <!-- 待用户提供 --> placeholder, never invented statistics. (The seed deck's 「澄流 ClearFlow」data is fictional demo content and must be fully replaced.) Negative metrics keep the orange caution treatment — bento decks that hide bad news read as marketing, not review.

Workflow

  1. Clarify once: topic, audience, page count, and which 3–6 metrics are the protagonists (plus the single most important one for the one-insight page). This style lives on its numbers — pick them before writing pages.
  2. Copy example.html, retitle, then replace each section's content following the layout enumeration. Keep the grid skeletons, token names, card anatomy, and the script intact. Re-theme by changing token values only — and only --brand plus tints, if the user's brand demands it.
  3. For ≥ 5 pages, showcase first: build the cover + the master bento 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; bar heights match their printed values proportionally; every bento page has unequal card heights and ≤ 1 dark card; no emoji; no fourth accent color; no leftover demo (「澄流」/"ClearFlow") text; grep for TODO.
Skill path
plugins/_official/examples/huashu-bento-insight/SKILL.md
Commit SHA
89d6d4ef21ba
Repository license
Apache-2.0
Data collected