sigma-present

name	sigma-present
description	Export sigma markdown artifacts (research.md, spec.md, plans, verify results, kanban board.md) as a polished, single self-contained HTML file — either an interactive reveal.js slide DECK or a long-scroll animated REPORT page, with an optional kanban snapshot. Use when the user wants to share, present, email, or hand off a sigma artifact as a standalone .html (or print it to PDF) rather than as raw markdown. Triggers: "turn this spec into slides", "export research as a report", "make a deck from the board", "share these verify results".
origin	sigma

sigma-present

Transform a sigma artifact into a single portable .html that opens anywhere, prints to PDF, and looks intentional — not a generic template.

This skill is an artifact transform, not a freeform deck designer. (For building a presentation from scratch / from a topic, use frontend-slides.) Here the input is always an existing sigma markdown artifact and the output is a deterministic, citation-aware deck or report.

When to use

• The user has a sigma artifact (research.md, proposals.md, architecture.md, spec.md, tasks.md, a plan, verify output, or board.md) and wants to share / present / email / archive it as HTML or PDF.
• They say "slides", "deck", "present", "report", "export", "share", "hand off".

Mode decision (pick one)

Trigger	Mode	Template
"slides", "deck", "present", "pitch", "talk"	DECK (reveal.js)	templates/deck.reveal.html
"report", "page", "write-up", long narrative (research/spec/verify)	REPORT (scroll)	templates/report.scroll.html
board.md, "kanban", "board snapshot", "status"	KANBAN	templates/kanban.board.html

Default: a narrative artifact (research/spec/plan/verify) → REPORT unless the user says slides/deck/present. board.md → KANBAN. A pitch/talk → DECK.

Workflow

1. Locate the artifact. Read from sigma/specs/{date}-{slug}/. Validate it exists; if not, say so and stop (fail fast, clear message). Identify the stage it came from for the provenance footer.
2. Pick the mode per the table above.
3. Ingest & section-map — see INGEST.md. Map markdown headings → slides or scroll sections; pull out citations; flag fact vs inference.
4. Pick a theme from THEMES.md. Default light/editorial; dark only if asked. Wire the palette into both CSS variables and any Chart.js colors. Hold the line on design quality: one direction, scale-contrast hierarchy, intentional spacing — never a uniform card grid or stock gradient hero.
5. Emit the file from the matching template, filling its placeholders.
   • Default: CDN <link>/<script> (small, emailable).
   • --inline / "offline": inline the dist CSS/JS and base64 images so the file needs no network.
6. Motion + a11y pass (mandatory).
   • Animate only compositor-friendly props (transform, opacity, clip-path).
   • Every emitted file includes a prefers-reduced-motion: reduce block.
   • Reports include the IntersectionObserver fallback for engines without animation-timeline: view() (e.g. Firefox).
7. Provenance footer + citations. Render "Generated by sigma · {stage} · {date} · source: {slug}" and a Sources section/end-slide from the artifact's citations.
8. Deliver. Write export.html (or export.deck.html / export.report.html) next to the artifact. Tell the user the path and how to get a PDF:
   • DECK: open with ?print-pdf appended, then browser Print.
   • REPORT/KANBAN: browser Print (a @media print block disables motion).

Output rules

• Single file whenever possible. CDN by default; fully inlined on request.
• Charts via Chart.js (CDN, or inlined for offline). Treat charts as part of the theme — pass the CSS-variable palette into chart colors.
• No template look. See the web design-quality bar: hierarchy via scale, intentional rhythm, real type pairing, designed hover/focus states.

Files in this skill

• templates/deck.reveal.html — reveal.js single-file deck boilerplate.
• templates/report.scroll.html — framework-free long-scroll report.
• templates/kanban.board.html — column/card board snapshot.
• THEMES.md — named CSS-variable palettes + font pairings.
• INGEST.md — artifact → section mapping rules.

Common mistakes

• Forcing a long report into slides (or vice versa) — pick the mode by content.
• Dropping citations — sigma artifacts are cited; the export must keep them.
• Animating layout props or omitting the reduced-motion guard.
• Shipping a multi-file build — keep it one portable .html.