| name | design-prompt-terminal |
| description | Use when the user wants a landing page, interface, or visual system in the Terminal CLI style from Design Prompts, or explicitly asks for terminal, terminal cli |
Design Prompt Terminal
Overview
Use this skill when the user wants the Terminal CLI aesthetic. Keep the target product's content and requirements intact, then translate this style into the requested stack or artifact.
A raw, functional, and retro-futuristic command-line interface aesthetic. High contrast, monospaced precision, and blinking cursors.
Read references/style.md before implementation whenever the task depends on this aesthetic.
When to Use
- Requests for the Terminal CLI 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 "Terminal CLI" style.
- Keep the visual system dark-first with #33ff00 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.
