| name | design-prompt-retro |
| description | Use when the user wants a landing page, interface, or visual system in the Retro style from Design Prompts, or explicitly asks for retro |
Design Prompt Retro
Overview
Use this skill when the user wants the Retro aesthetic. Keep the target product's content and requirements intact, then translate this style into the requested stack or artifact.
Ugly-cool 90s nostalgia aesthetic with Windows 95 beveled UI, system fonts, bright primary colors, marquee scrolling text, and maximum visual chaos.
Read references/style.md before implementation whenever the task depends on this aesthetic.
When to Use
- Requests for the Retro style or close synonyms tied to this aesthetic
- New landing pages, marketing sites, dashboards, or polished visual explorations
- Re-skinning an existing page while preserving the user's IA and content
Working Rules
- Treat the style as direction, not as a literal Acme clone.
- Preserve accessibility, responsive behavior, and existing product constraints.
- If the task lives inside an existing design system, adapt this style without breaking local patterns.
Prompt Starter
- Design a [surface] for [brand or product] in the "Retro" style.
- Keep the visual system light-first with #9333EA as the anchor accent.
- Use a clean sans-led hierarchy with confident sizing.
- Start from these section archetypes when relevant: hero, stats, features, how-it-works, benefits, pricing, testimonials, faq, blog, footer.
- Translate the style to the user's domain and copy; do not recreate the Acme demo literally.
- Preserve any existing product constraints, content model, and accessibility requirements.