Skills

Retro Arcade Story Deck

Builds a story deck about building a retro-arcade collection in a pixel style.

Install

npx skills add nexu-io/open-design --skill html-ppt-zhangzara-8-bit-orbit -g -a claude-code -y
Repository
nexu-io/open-design105k
Category
Documents
Updated
3d ago
License
Apache-2.0
Context cost
Lightabout 666 tokens
Runs scripts
No, instructions only

What it does

A gamer's journey building a retro-arcade collection, the obsession, the hunt, and what the machines came to mean. Built as a decision-grade story deck for friends, hobby community.

8-Bit Orbit

Pixel-art neon arcade aesthetic on a deep navy void.

A single self-contained HTML deck, typography, palette, decorative system, and slide vocabulary are all tuned together. Mixing layouts across templates breaks the system; stay inside this one.

At a glance

  • Scheme: dark
  • Formality: low
  • Density: medium
  • Slides in demo: 10

Best for

Anything that should feel like a CRT screen at 2am: cyberpunk, gaming, web3, indie dev tools, hackathon demos. Just as good for a tech talk that wants to lean into nostalgic-digital craft, a synthwave brand deck, or a creative review that wants to feel like a console.

Avoid for

Contexts where the dark neon palette would actively work against the message, quiet institutional finance disclosures, healthcare patient-facing materials, traditional luxury.

Workflow

  1. Clone example.html into the user's workspace as the working file.
  2. Replace placeholder content with the user's real headlines, body copy, numbers, names, dates, and section labels. Match existing dimensions when swapping image placeholders.
  3. Preserve the design system. Never substitute fonts, recolor the palette, restructure the layout grid, or strip decorative elements (corner brackets, paper grain, geometric shapes, illustrated SVGs). They are part of the identity.
  4. Adjust deck length by duplicating layouts. If the user has more content than the demo holds, duplicate an existing slide of the most appropriate layout. If less, drop slides from the bottom. Update page-number labels.
  5. Designing missing layouts: if a slide needs a layout the template doesn't have, design it from scratch using the same fonts, palette, decorative vocabulary, spacing rhythm, and component grammar, never bail to a different template.
  6. Keep the navigation runtime as shipped. If the deck ships an assets/deck-stage.js or inline keyboard handler, leave it intact.
Read the whole SKILL.md on GitHub

More in Documents