New to Claude Skills? Learn how to install them →

nexu-io on GitHub

Narrative Sparkline

Free

Create engaging data-driven presentations with ease.

by nexu-io84.9k stars on nexu-io/open-design
5 views
Updated Aug 10, 2026
Get this skill

Free · Opens the source repo

What Narrative Sparkline does

Narrative Sparkline is designed for professionals who need to craft compelling presentations that effectively communicate data-driven narratives. This skill allows you to produce a single-file Duarte-style narrative deck that visually represents the journey from 'what is' to 'what could be'. The presentation format is grounded in a unique oscillating waveform that serves as the backbone of your story, providing a clear and engaging way to present key metrics and forecasts. Each page is meticulously structured to ensure that the visual elements align with the narrative flow, making it easy for your audience to follow along.

The skill is built around a specific HTML structure, requiring users to start from the provided example.html file. This approach ensures consistency in design and functionality, as you replace the content without altering the established layout or script. The design is intentionally minimalistic, featuring a fixed canvas size of 1920x1080 pixels and a strict color palette that emphasizes the brand's orange accent. This focus on uniformity helps maintain a professional appearance across all slides, making it suitable for high-stakes environments such as board meetings or financial presentations.

By adhering to the hard specifications outlined in the skill, users can create visually appealing and informative slides that highlight key performance indicators (KPIs) and other critical data points. The skill is particularly useful for finance and business professionals who need to present complex information in a digestible format. With its emphasis on storytelling through data, Narrative Sparkline is an excellent tool for anyone looking to enhance their presentation skills and drive informed decision-making.

In summary, Narrative Sparkline is a specialized tool for creating narrative-driven presentations that leverage data effectively. Its structured approach and focus on visual storytelling make it ideal for professionals in finance and analytics who seek to communicate insights clearly and persuasively.

When to use it

Use this skill when you need to present complex data in a visually appealing and narrative format, particularly in business or finance contexts.

When not to use it

This skill may not be suitable for casual presentations or when flexibility in design and layout is required.

What you can build with it

Board Meeting Presentations

Use Narrative Sparkline to create impactful presentations that clearly communicate financial forecasts and performance metrics to board members.

KPI Reporting

Generate visually engaging reports that effectively highlight key performance indicators for stakeholders, making data easier to digest.

Data Storytelling Workshops

Leverage this skill in workshops focused on data storytelling to teach participants how to present data in a narrative format.

How to install Narrative Sparkline

View source

1. Install with the skills CLI

npx skills add nexu-io/open-design/huashu-sparkline-arc --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by nexu-io

Narrative Sparkline · 叙事波形

Produce a single-file, Duarte-style narrative deck. You are a story cartographer working in HTML: every page is built on one oscillating waveform that travels between "what is" and "what could be", and orange appears only where the story turns. 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 Sparkline叙事波形 / Narrative Sparkline (Duarte式) spec (中性派, 还原91%) in references/design-styles.md of huashu-design by 花叔 (alchaincyf), MIT licensed. Lineage: Nancy Duarte《Resonate》sparkline structure, Al Gore An Inconvenient Truth, Duarte Inc. data storytelling.

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#0E0E0Cdark pages (solo-line, closing)
--ink#1A1814primary text on light
--night-ink#F5F3EEprimary text on dark
--accent#FF6B2Cthe brand orange — the only accent
--accent-dimrgba(255,107,44,.14)annotation halos / soft fills
--ghost#C9C7C2greyed comparison waveform
--grid#ECEAE6hairline rules
--muted#9A958Csecondary labels
--muted-2#5F5A52body copy on light
--night-line#26241Fhairlines on dark pages
--night-mut#8A857Csecondary text on dark
--sans'Inter', 'PingFang SC', …, sans-serifheadlines + body
--mono'Geist Mono', 'SFMono-Regular', 'Menlo', monospacelabels, annotations, numerals

Fonts: one Google Fonts @import (Inter 400–900 + Geist Mono 400–600) and nothing else. No CDN scripts, no chart libraries, no images — every chart is a hand-written inline SVG path. A second accent color is the cardinal sin of this style; grey is the only other voice.

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

  1. The waveform spine: every page carries at least one full-bleed .spark SVG with a smooth cubic-bézier oscillating path. Line layer uses preserveAspectRatio="none" so the path stretches; annotation dots/text live in a second, non-stretched SVG layer with the same viewBox so circles stay round and type stays true. Line weights: .arc 5px orange hero line, .arc-thin 3.5px, .ghost-line 3px grey, .ghost-dash stroke-dasharray: 2 10 grey baseline/industry reference.
  2. Orange turning-point annotations: .pt group = soft halo circle (--accent-dim), solid orange dot (r≈6–7), optional 2px orange ring for THE inflection point, plus Geist Mono uppercase .lab (12px, 2px tracking) and .val (20px, 600) value text. Grey .pt-ghost dots mark pain points on comparison lines. Orange marks turning points only — if every dot is orange, nothing turns.
  3. Progressive reveal: paths carry pathLength="1" + class draw (stroke-dasharray: 1; stroke-dashoffset: 1); .slide.active .draw animates stroke-dashoffset to 0 (spark-draw, ~1.8s, ease-out-ish cubic-bezier). Segment stagger via d1/d2/d3, dot fade-ins via p1…p5 (animation-delay ladder). Because .active toggles display, the reveal replays every time a slide is entered — keep it that way.
  4. Mono hairline chrome: 56px .chrome-top / .chrome-bottom strips on every page — Geist Mono 11px uppercase, 2px tracking, --grid hairline border (--night-line on dark), org name left with an orange / separator, orange uppercase tag right, orange P.NN page marker bottom right. No solid bars, no logos — type and one hairline only.
  5. Greyed contrast: every claim gets a comparison — dashed industry baseline, the old process line above the new one, or a flat ghost line under the rising arc. The grey line is the "what is"; the orange line is the "what could be".
  6. Mono numerals: giant numbers (.giant, 160–220px Geist Mono 600, negative tracking, font-variant-numeric: tabular-nums) with one orange glyph (%, ×, unit); stat strips (.stat-strip) with a --grid top hairline, 44px mono numbers and 11px uppercase captions.

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

LayoutRole
covergiant statement headline (orange full stop) + waveform below with what-is / turn / new-bliss dots
contentschapters hung directly on the waveform as numbered annotation points
what-isleft action-title column + low, flat grey waveform with dashed industry ghost + stat strip
turning-pointgiant mono numeral + V-shaped inflection waveform, THE ringed orange dot, dated annotation
before-afterstacked contrast: grey jagged line top half, orange rising line bottom half, hairline divider
solo-linedark page, one orange line crossing the void, one annotation, one big number
evidencerising waveform with 4 labelled value dots + summary strip of mini inline-SVG sparklines
roadmapthree waveform segments revealed in sequence (d1/d2/d3) + three phase columns below
quoteorange SVG quote marks + 56px/800 quote with orange key phrase + ghost waveline footer
closingdark page, 6px orange curve climbing out of the top-right edge + giant CTA

Typography & narrative discipline

  • Headlines: Inter 800–900, 54–108px, tracking −1.5 to −4px; the closing glyph (。 or .) of a hero headline is orange — never the whole headline.
  • Body: 19px / 1.8 --muted-2, emphasized spans --ink 700, max-width ~620px. Labels/annotations/numerals: always Geist Mono, uppercase, 2–4px tracking. Chinese copy uses 「」 quotes and full-width punctuation.
  • Default 10 pages (8–11 allowed). White pages dominate; at most 2–3 dark pages (solo-line + closing). Orange budget: turning points, annotation dots, chrome tags and single glyphs — roughly ≤ 5 orange touches per page.
  • The deck must read as a Duarte sparkline: establish "what is" low, mark one explicit dated turning point, oscillate through evidence, end with the line climbing out of frame ("new bliss"). One story, one line.
  • No emoji, no gradients, no shadows, no images, no chart libraries. Real content only — the user's actual numbers and dates; missing data gets an honest <!-- 待用户提供 --> placeholder, never invented statistics. (The seed deck's 「澈流 / CHELIU」 data is fictional demo content and must be fully replaced.)

Workflow

  1. Clarify once: topic, audience, page count — and the story spine: what is the "what is", what is THE dated turning point, which 3–4 numbers prove the climb. This style dies without a real inflection moment.
  2. Copy example.html, retitle, then replace each section's content following the layout enumeration. Keep chrome strips, spark/reveal CSS, token names, and the script intact. Reshape the bézier paths to match the user's actual data direction (down-then-up, stepped, etc.) but keep the two-layer SVG pattern and pathLength="1" reveal mechanics.
  3. For ≥ 5 pages, showcase first: build the cover + the turning-point page, confirm the grammar, then batch the rest.
  4. Self-check before delivery: arrow through every page; counter and #/N hash stay in sync; reveal animation replays on each entry; no overflow beyond 1920×1080; annotation dots sit visually on their lines at 16:9; orange appears only at turning points; every page has the chrome strips and at least one waveform; no leftover demo (「澈流」/"CHELIU") text; grep for TODO.

Frequently asked questions about Narrative Sparkline

Similar skills