/*
 * Template: site/src/styles/global.css for a dunn.dev estate site.
 *
 * The two imports are mandatory; the design-system contract's check.sh
 * asserts both exist. They must come first so site-specific rules below
 * resolve against the published tokens.
 *
 * The order matters: tokens before chrome. site.css references the
 * variables declared in tokens/index.css; reversing the order leaves
 * site.css's selectors referencing undefined custom properties.
 */

@import '@dunn.dev/reference/tokens/index.css';
@import '@dunn.dev/reference/site.css';

/*
 * Below this point: site-local patterns ONLY. Examples that belong
 * here:
 *   - Page-specific layouts not covered by the chrome (e.g. a
 *     three-panel curriculum grid, a heatmap container).
 *   - Component patterns unique to this site (e.g.
 *     reference.dunn.dev's `.skill-zone` block).
 *   - Print stylesheets, very-narrow-viewport overrides not handled
 *     by the chrome.
 *
 * What does NOT belong here:
 *   - Token redefinition. If you find yourself writing
 *     `--accent: #...;` here, the value belongs in
 *     `@dunn.dev/reference/tokens/colors.css` instead — open an MR
 *     against design rather than patching it locally. (This is the
 *     project-local patching failure mode the estate's
 *     ~/gitlab.com/dunn.dev/CLAUDE.md rules out.)
 *   - Re-implementation of site-chrome patterns the package already
 *     exposes. If `site.css` has `.hero`, `.page`, `.section-prose`,
 *     etc., the site uses those, not a parallel re-implementation.
 */