cloe-coach-design

Read the README.md file within this skill, and explore the other available files. Pay special attention to:

• colors_and_type.css — copy this into any new artifact and use the CSS variables (--accent, --bg, --surface, --surface2, --text, --muted, --border, --font-display, --font-mono, etc.) instead of hardcoding values.
• ui_kits/coach-app/*.jsx — copy components verbatim (Sidebar, TodayView, MealCard, IntervalsBlock, ChecklistRow, StreakPill, Btn3D, etc.). They are the canonical implementations.
• preview/ — small spec cards for each foundation; reference these to remember exact tokens.

If creating visual artifacts (slides, mocks, throwaway prototypes, etc), copy assets out and create static HTML files for the user to view. Always:

• Default to dark mode (#0c1018 background).
• Lime accent #c8f135 is the brand. Use it for primary actions, highlights, focus, streak. Do not invent secondary accents — use the semantic palette in colors_and_type.css (blue/orange/purple/red).
• Two fonts only: Syne (display, 700/800) for headings + brand, DM Mono for everything else (body, labels, numbers, nav).
• Spanish copy, second person, sentence-case for prose, MAYÚSCULAS-MONO for eyebrows/labels/nav.
• Iconography is system emoji — never hand-draw SVG icons. See ICONOGRAPHY section in README.
• One 3D-shadowed CTA per view. Cards use --shadow-card (the canonical shadow with the inner-top white-5% rim).
• Use the canonical separator · (middle dot) between metadata.

If working on production code, you can copy assets and read the rules here to become an expert in designing with this brand.

If the user invokes this skill without any other guidance, ask them what they want to build or design (login? onboarding? new section in the app? a marketing slide? a print poster?), ask 3-5 clarifying questions, and act as an expert designer who outputs HTML artifacts or production code, depending on the need. Default-favor showing them in HTML so they can review.