Starlit Deck

Give a reflective talk room to breathe against a dark night sky. Starlit Deck combines procedural CSS stars or horizon glow, warm serif headlines and sparse statements, with process dots, an arc timeline and optional painterly backgrounds. It suits founder letters, retrospectives and personal/company narratives, with a current shared browser editor and requested PowerPoint/PDF export.

What you get

  • Eight documented composition archetypes: cover, statement, split, dot-flow process, arc timeline, point list, stat row and warm-horizon close. The installation’s style kit has ten populated astronomy-example recipes that can be adapted or repeated; those ten examples are not the required count. Eight to fourteen slides is a planning guide, with the actual count agreed from the story.
  • Three coordinated night palettes: Midnight Gold for narrative/retrospective, Aurora Teal for technical/product and Dawn Rose for personal talks. There is no light variant; stars, glow and accent shift together. The Latin headline subset of Noto Serif SC is embedded, with system-serif fallbacks for Chinese and system sans body.
  • A complete no-image visual route using procedural starfields, plain navy and horizon glow, requiring no image-generation key or paid picture task. Two local library backgrounds and two example cover/closing slots offer optional atmospheric imagery; keep text regions quiet and avoid generating a picture for every slide.
  • A standalone HTML deck with current shared viewing/editing/presentation modes, notes, thumbnails and Save. All final media is embedded rather than delivered as a required companion images folder. The current editor replaces the older custom paging engine: its documented controls must not be equated with the old Esc-overview/N-notes/wheel-paging promises.
  • Python composition/build/check scripts and Node optional media helpers, with requested PPTX text/notes editable, pictures separate and backgrounds/SVG/decoration rendered. PDF provides one fixed 16:9 page per slide. The package supports PPTX even though an older exclusion says HTML/PDF only; it does not promise a native Google Slides document.

Before you choose

Read the talk without its stars: each statement should still advance the narrative and every quoted or numeric claim should have an approved source. Then restore the atmosphere and check that the sky leaves room for reading rather than replacing a missing argument.

Good fit

  • A founder letter, year-in-review or company narrative needs a reflective literary mood rather than dense sales information.
  • A personal/intimate talk benefits from sparse statements, with Dawn Rose as a coherent night-palette option.
  • A presenter starts with a plain outline and approved numbers, milestones or quotations and wants guided layout/rhythm choices reviewed for the actual content.

Not for

  • A dense sales deck, spreadsheet-like report or bright high-energy brand treatment that conflicts with dark sky and generous space.
  • Invented metrics, quotations or attributions to fill a stat row or make a statement feel authoritative.
  • A guarantee of the older bespoke navigation shortcuts, all-native PowerPoint artwork or a native Google Slides file.
  • Assuming the astronomy sample’s statements or generated sky imagery provide verified facts for a different talk.

How to use

You say/starlit-deck Create a night-sky presentation from my topic and outline as one self-contained HTML file, with full 16:9 slides, deep-navy procedural starfields and warm gold serif headlines. Include page navigation, a thumbnail overview, speaker notes and print-to-PDF export.
  1. Provide the outline, audience, narrative arc and approved numbers/milestones/quotes. Specify slide language explicitly when it should differ from English. Propose and confirm a count from the material when absent; eight to fourteen is typical guidance, not a required length or proof of pacing.

  2. Choose Midnight Gold, Aurora Teal or Dawn Rose during generation and keep one palette throughout. Update the coordinated sky/accent/glow tokens together rather than recolor a single heading. Keep the serif display/system-sans pairing, with Chinese relying on available serif fallbacks; no remote font service is needed.

  3. Plan one archetype per page, skipping stats/timeline when there is no real data or relevant sequence. Dot-flow works with three to five nodes, arc timeline with three to six points, point list with two to five entries and stat row with up to four supplied measures. If a number is missing, ask for it or omit the stat page instead of fabricating it.

  4. Keep most text slides on procedural void/horizon or plain navy. Avoid three or more visible-star pages in a row when the deck can vary, and reserve horizon glow for the close or one other emphasis. Keep paragraphs to one or two short sentences and notes to added talking points. When arc points change, update SVG positions and corresponding label percentages together.

  5. Use the CSS route without paid generation, or choose suitable reuse of the two local backgrounds, generate only needed gaps or regenerate selected pictures, with approved supplied assets first. Leave the text-side third calm, match the selected palette and use 16:9 sources. Optional built-in generation needs no FAL key; paid FAL uses FAL_KEY and recorded submit/status/fetch tasks without automatic failure resubmission. Charges/account limits apply. List unfilled picture frames honestly.

  6. Populate recipes and replace astronomy-example claims, labels, counts and notes with approved content. Compose/build/check with Python 3 and the expected count/style kit; Node is for optional image helpers. Embed all final assets in the HTML, preserve font notices and keep the shared runtime unchanged. The old companion-folder workflow is not the current delivery contract.

  7. Open over local HTTP and inspect each 1280×720 page for background rhythm, negative space, headline contrast, arc-label alignment, actual count and bounds. Use Edit/E for content and notes, Save and reopen the file. In current presentation mode, arrows/space and horizontal swipe navigate, and Escape exits presentation; use the editor’s thumbnail/notes interface rather than promise old Esc/N shortcuts or wheel paging.

  8. Test actual view/edit/present, text/images/order/notes, undo/redo and portable saving. Export requested PPTX/PDF, run check-pptx.py and inspect text/notes, rendered backgrounds/diagram layers and font substitution in PowerPoint, Keynote or WPS. A static check and documented controls do not constitute a completed browser verification.

Requirements and costs

You bring
Deck outline or content brief
Dependencies
FAL API key — optional (AI-painted night-sky backgrounds) · Chrome, Chromium or Edge plus Node.js 20 or newer — required only for PowerPoint export
Outside costs
FAL GPT-Image usage charges apply when generating AI background art.
Publisher testing
v1.0.4 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT

FAQ

User reviews

—0 reviews

Select a star to share your experience.

No reviews yet. Ratings appear once readers share real experiences.

Similar Skills

View all skills