opencoo-design

Read the README.md file within this skill, and explore the other available files. If creating visual artifacts (slides, mocks, throwaway prototypes, etc), copy assets out of `assets/` and create static HTML files for the user to view. 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, ask some questions, and act as an expert designer who outputs HTML artifacts _or_ production code, depending on the need. Key non-negotiables: - Product name is always lowercase `opencoo` — never `OpenCoo`, `OpenCOO`, or `Open Coo`. - Warm paper (`#F6F3EC`) + ink (`#121210`) base. Advisory Amber only on agent surfaces (<10% coverage). Wiki Teal only on citations. - Three type families, one job each: Instrument Serif italic (display only), Geist (UI), JetBrains Mono (paths/data/micro). - No gradients. No emoji. No drop shadows for elevation. Never pill-shaped buttons. - The logo's three glyphs (open arc / filled disc / ring-with-dot) are the entire iconography system.