Section Title
...
--- name: design-minimal description: Use when the user explicitly asks for a standalone HTML page in a restrained minimal style, especially reading-first dashboards, briefs, handouts, maps, or internal reports. User-invoked only; do not auto-trigger. --- # Design Minimal Generate one standalone HTML page with a restrained minimal visual system: clear hierarchy, strong spacing, explicit structure, limited palette, and no decorative effects. ## Language - Match the visible interface language to the user's language and artifact context. - For Russian pages, write visible UI labels, headings, section names, status explanations, and footer copy in Russian. - Keep English only for file paths, commands, code identifiers, schema fields, API names, model/tool names, and literal values that must remain copyable. - If an English technical term is useful for teaching, pair it with a plain-language local label once, then use the local label in the interface. ## Hard Contract 1. Use one self-contained HTML file. 2. Use Tailwind CDN only for layout and component styling. 3. Do not write custom CSS rules for components, layout, typography, states, cards, grids, buttons, headers, or sections. 4. The only allowed CSS is design tokens as CSS variables in `:root`. 5. Do not add mobile adaptation: no responsive Tailwind prefixes (`sm:`, `md:`, `lg:`, `xl:`, `2xl:`), no media queries, no alternate mobile layout. 6. Do not use external fonts, JavaScript frameworks, icon libraries, SVG icons, gradients, shadows, rounded corners, or accent colors. 7. Use typography, color, spacing, and layout through Tailwind classes plus token variables. Allowed ` ``` Forbidden CSS shape: ```css .card { ... } @media (...) { ... } body { ... } button:hover { ... } ``` ## Tailwind Usage Use Tailwind classes directly on elements. Reference tokens through arbitrary values: ```html
BRIEF 042 · INTERNAL
BRIEF 042 · INTERNAL
Short one-line description.
...
...