# legions.dev -- Design System Reference

## 1. Visual Theme & Atmosphere

Radical browser-default intentionalism. Times Roman at system defaults, no custom colours, no border radii. A conceptual statement that treats raw HTML semantics as the aesthetic. Anti-design as design.

The overall mode is **light**, with a editorial, serif-driven typographic identity. Depth is entirely absent -- the composition is rigorously flat.

---

## 2. Color Palette & Roles

No explicit colour tokens detected. The palette relies on browser defaults -- black text on transparent backgrounds -- making the content itself the sole visual differentiator.

**Key observations:** No token layer exists. Colours emerge from context and browser defaults. Light-mode-first palette.

---

## 3. Typography Rules

**h1** -- Times, 32px, weight 700

**Hierarchy principle:** A single typeface (Times) handles all levels. Size and weight alone establish rhythm.

**What is absent:** No monospace or system-UI fallback. The serif identity is deliberate -- do not substitute.

---

## 4. Component Styling

**Border radii:** No border radii detected -- corners are sharp throughout.

**Interactive states:**
Interactive states (hover, focus) are not strongly surfaced in extracted CSS. Assume minimal or JavaScript-driven state changes.

**Buttons & controls:** Match the typographic register -- serif labels, generous line-height, understated borders.

---

## 5. Layout Principles

Spacing is minimal and relies on default browser margins. No grid or flex gap patterns are strongly expressed.

No dominant padding pattern -- spacing is contextual.

Avoid introducing grid lines, dividers, or decorative rules unless absolutely necessary. Let whitespace do the structural work.

---

## 6. Depth & Elevation

No box shadows detected. Depth is achieved through colour contrast and spacing alone -- the design is intentionally flat.

Maintain the flat aesthetic throughout. If you must indicate overlapping layers (modals, tooltips), use border outlines or background tints rather than shadows.

---

## 7. Do's and Don'ts

**Do:**
- Respect the editorial, serif-driven typographic voice -- every element should speak the same typeface language.
- Use whitespace as a primary design tool. When in doubt, add space rather than elements.
- Stay within the established colour range -- no additional palette colours.
- Keep interactions subtle: micro-transitions at 150-200ms maximum.

**Don't:**
- Do not swap the serif for a sans-serif alternative. The editorial register depends on it.
- Do not add drop shadows, gradients, or decorative textures unless they are already present in the system.
- Do not use colour to communicate hierarchy -- spacing and scale do that work here.
- Avoid centring body text. The layout has a strong left-anchored reading rhythm.

---

## 8. Responsive Behavior

No explicit CSS breakpoints extracted. The layout relies on fluid units, CSS Grid auto-fit, or a single-column mobile-first approach.

Build mobile-first. Use fluid type and spacing where the existing CSS suggests it (clamp(), vw units). Avoid rigid pixel breakpoints if the system uses fluid scaling.

On small screens, collapse multi-column layouts to a single column without compromising the typographic scale. The type should remain readable -- never below 14px rendered size.

---

## 9. Agent Prompt Guide

When generating UI components, extensions, or page sections for **legions.dev**, instruct the agent as follows:

> "Build in the style of legions.dev: radical browser-default intentionalism. Use Times as the primary typeface. Light background, dark text. No shadows or elevation. Minimal palette, no custom tokens. No animations -- immediate state changes only. Generous whitespace, strong typographic scale. Sharp corners throughout."

---

*Generated by Sparkbites -- extracted from live CSS analysis*