Source profileQuality 85/100

nexu-io/open-design/plugins/_official/examples/huashu-pentagram-grid/SKILL.md

huashu-pentagram-grid

Open Design's positioning & messaging system: the one-line promise, the pillars, and the proof — the source of truth for all copy. Built as a decision-grade marketing & GTM deck for brand & marketing team.

Source repository stars
82,073
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Produce a single-file, Swiss-grid data deck. You are an information architect working in HTML: every page is a measured grid, every number has a coordinate, and red appears exactly where the eye must land. The visual system, canvas contract, and navigation runtime are locked by…

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/huashu-pentagram-grid"
    Safe inspection promptEditorial

    Inspect the Agent Skill "huashu-pentagram-grid" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/plugins/_official/examples/huashu-pentagram-grid/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Workflow

      1. Clarify once: topic, audience, page count, and which 2–4 numbers are the protagonists. This style lives and dies by its hero numerals — pick them before writing any page. 2. Copy example.html, retitle, then replace each section's content following the layout enumeration. Keep…

      Clarify once: topic, audience, page count, and which 2–4 numbers areCopy example.html, retitle, then replace each section's contentFor ≥ 5 pages, showcase first: build the cover + one data-theater
    2. 02

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

      Zero external dependencies: no Google Fonts, no @import, no CDN. One font stack, one accent. A second accent color is the cardinal sin of this style.

      One fixed at 1920 × 1080 px, centered withEach page is one inside stage with aNavigation (keep the script verbatim): ←/↑/PageUp previous,
    3. 03

      Canvas & runtime

      One fixed at 1920 × 1080 px, centered with

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

      Design tokens (:root — keep the names, re-theme values only)

      Zero external dependencies: no Google Fonts, no @import, no CDN. One font stack, one accent. A second accent color is the cardinal sin of this style.

      Zero external dependencies: no Google Fonts, no @import, no CDN. One font stack, one accent. A second accent color is the cardinal sin of this style.
    5. 05

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

      1. 64px black chrome bars top and bottom of every light page: top bar = uppercase 12px/700/3px-tracking label left (with a red / separator) + red uppercase label right; bottom bar = 900-weight logotype + 1px 444 vertical divider + grey footnote left, red uppercase label right. D…

      64px black chrome bars top and bottom of every light page: top bar =Grid hairlines: absolutely-positioned 1px verticalsGiant numeral anchor: one 180–260px, weight-900,

    Permission review

    Static risk signals and limitations

    Reads files

    low · line 31

    The documentation asks the agent to read local files, directories, or repositories.

    step — the file must open inside a sandboxed iframe via `file://`.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score85/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars82,073SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    nexu-io/open-design
    Skill path
    plugins/_official/examples/huashu-pentagram-grid/SKILL.md
    Commit
    89d6d4ef21baf80f871595abdf6f7de6e941dd44
    License
    Apache-2.0
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    Pentagram Info-Architecture · 信息建筑·红

    Produce a single-file, Swiss-grid data deck. You are an information architect working in HTML: every page is a measured grid, every number has a coordinate, and red appears exactly where the eye must land. 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.

    Adapted from the ppt-pentagram showcase of huashu-design by 花叔 (alchaincyf), MIT licensed. The upstream file is a single data page; this plugin extends it into a full multi-section deck while preserving its DNA.

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

    TokenValueRole
    --paper#FFFFFFlight page background
    --night#111111dark pages + chrome bars
    --ink#111111primary text on light
    --night-ink#FFFFFFprimary text on dark
    --accent#E63946the only red — the only accent
    --grid#E8E8E8hairline rules / column rules
    --track#F5F5F5bar-chart track
    --bar-base#E0E0E0losing / baseline bar
    --muted#999999secondary labels
    --muted-2#666666body copy on light
    --faint#BBBBBBtertiary captions
    --night-line#333333hairlines on dark pages
    --night-mut#888888secondary text on dark
    --sans'Helvetica Neue', 'Helvetica', 'PingFang SC', 'Hiragino Sans GB', 'Microsoft YaHei', Arial, sans-serifthe only family

    Zero external dependencies: no Google Fonts, no @import, no CDN. One font stack, one accent. A second accent color is the cardinal sin of this style.

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

    1. 64px black chrome bars top and bottom of every light page: top bar = uppercase 12px/700/3px-tracking label left (with a red / separator) + red uppercase label right; bottom bar = 900-weight logotype + 1px #444 vertical divider + grey footnote left, red uppercase label right. Dark pages swap solid bars for 1px --night-line hairline strips with the same text.
    2. Grid hairlines: absolutely-positioned 1px verticals (top:64px; bottom:64px) and horizontals (left/right:80px) at opacity: 0.05 black (0.08 white on dark). 80px outer margins are the master gutter; columns land on them.
    3. Giant numeral anchor: one 180–260px, weight-900, negative-tracked (≈ −1px per 20px of size) number per hero page; its decimal point, slash, or unit glyph is red (<span class="decimal"> / .red). Hero numerals on dark divider pages may be fully red.
    4. Red/dark/grey bar charts: .bar-row = right-aligned 90px label + --track track + fill (winner red / dark black / base grey) with the value printed inside, right-aligned, white (grey on base). The subject of the page is always the red bar. Optional .delta red uppercase annotation underneath.
    5. Summary strip: border-top: 1px solid var(--grid) row of .summary-items — 32px/900 number with one red glyph + 11px uppercase spaced caption.
    6. Outlined red badge (.open-badge): 2px red border, red uppercase 11px text, optional inline-SVG dot glyph. Square corners — this style has zero border-radius anywhere except the runtime counter pill.

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

    LayoutRole
    covergiant statement headline (red full stop) + right-column hero numeral
    contentsnumbered red-kicker rows separated by --grid hairlines
    big-numberone 260px numeral protagonist + side stat rail
    data-theaterleft hero column + 2–3 .bench-col bar-chart columns + summary strip (the upstream master)
    dividerdark page, 260px red chapter number + oversized title
    two-columnbefore/after comparison: grey bars left, red bars right
    timelineequal columns, 96px year numerals graded grey→black→red
    quotewhitespace + red SVG quote marks + 54px/900 quote, key phrase red
    stats-grid2×2 grid of 128px numerals with red glyph accents
    closingdark page, giant CTA with red punctuation + key-hint capsule

    Typography & scale (read from 10 meters)

    • Headlines 64–120px weight 900, tracking −2 to −5px. Hero numerals 180–260px weight 900. Body 15–18px, --muted-2, line-height 1.7, emphasized spans in --ink 700.
    • Labels: 11–13px, weight 700, letter-spacing: 2–3px, text-transform: uppercase — this is the connective tissue of the style.
    • Chinese copy uses 「」 quotes and full-width punctuation; red is applied to single punctuation glyphs (。 , /) inside headlines, never whole headings.

    Rhythm & discipline

    • Default 10 pages (8–11 allowed). White pages dominate; at most 2–3 dark pages (divider + closing, optionally one dark hero) — this is a white style with black bookends, not a dark theme.
    • Red budget: ≤ 4 red touches per page (bars count as one device). If everything is red, nothing is.
    • No emoji, no icon fonts, no decorative illustrations, no gradients, no shadows, no rounded corners. Flat ink on paper. Icons, if truly needed, are minimal inline SVG strokes.
    • Real content only — the user's actual numbers; missing data gets an honest <!-- 待用户提供 --> placeholder, never invented statistics. (The seed deck's "析衡" data is fictional demo content and must be fully replaced.)

    Workflow

    1. Clarify once: topic, audience, page count, and which 2–4 numbers are the protagonists. This style lives and dies by its hero numerals — pick them before writing any page.
    2. Copy example.html, retitle, then replace each section's content following the layout enumeration. Keep chrome bars, grid hairlines, token names, and the script intact. Re-theme by changing token values only — and only if the user's brand genuinely demands it; the red/black/white triad is the identity.
    3. For ≥ 5 pages, showcase first: build the cover + one data-theater 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 widths match their printed values proportionally; every page shows the chrome bars and at least one grid hairline; red count per page ≤ 4; no leftover demo ("析衡"/"XIHENG") text; grep for TODO.

    Alternatives

    Compare before choosing

    Computed 1007

    event4u-app/agent-config

    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.

    Computed 9827

    MoizIbnYousaf/marketing-cli

    higgsfield-generate

    Use when the user wants to generate an image or video via Higgsfield AI. Covers 30+ models: Soul V2, Seedance 2.0, Kling 3.0, Veo 3.1, GPT Image 2, Nano Banana 2. Also covers Marketing Studio — branded ad video/image with avatars and products. Use whenever: "generate an image", "make a video", "animate this photo", "image-to-video", "img2vid", "edit this image with AI", "produce a clip", "create an ad", "make a UGC video", "marketing video", "brand video", "TV spot", "import product from URL", "

    Computed 9727

    MoizIbnYousaf/marketing-cli

    creative

    Generate visual asset briefs, ad copy variants, AI image prompts, video scripts, and storyboards. Full creative production system with 5 specialized modes: product photos, product video, social graphics, talking heads, and ad creative. Make sure to use this skill whenever the user mentions any visual or creative marketing need — ad creative, image prompts, video scripts, thumbnails, banners, social graphics, product photography, storyboards, or marketing visuals of any kind. Even if they just sa

    Computed 9542,015

    coreyhaines31/marketingskills

    site-architecture

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what page