Styles Overview

/assets/css/rare.min.css

v0.6.11 Beta | CDN | Download file_download

Rare Styles is a CSS library for clarity-first content and decision-grade interfaces. It is built for situations where attention is the scarcest resource: longreads, internal tools, dashboards, documentation, reporting. This is not a decoration kit and not a vehicle for visual fashion.

Visual decisions are not optional. They are the design.

Every screen makes choices for the reader: where to look, what to read first, what to ignore. General-purpose CSS frameworks defer those choices to the developer, who defers them to defaults. The result is interfaces that are technically clean and practically noisy.

Rare Styles takes the opposite stance. It encodes Rareism — the discipline of removing what does not drive a decision — directly in its tokens, components and defaults. The library does not stay neutral on what attention should serve. It serves the signal.

Rare Styles

Rare Styles is the technical instrument of Digital Rareism. Its tokens, components and defaults carry the same philosophy: signal over noise, certainty over feature count, function over ornament.

Built on 20 years of business-tooling expertise

Rare Styles is authored by Rare Digits Production, a team that has spent two decades building instruments for businesses and decision-makers.

Most CSS frameworks ship a box of primitives and let the frontend assemble the answer. Rare Styles ships the answer. Visual decisions — typography, spacing, contrast, density, hierarchy — are already made and encoded in the defaults. Dark text on light background. Calm typography. Sufficient contrast. Deliberate density. The page you are reading uses these defaults with no overrides.

This shifts where the design work happens. With Rare Styles, the design is largely done before the technical specification reaches the frontend developer. The developer composes structure; the library carries the visual language. There are no debates about font sizes, no rounds of “make it more breathable”, no theme variants to A/B.

Clarity is the default, not the goal.

There is no light/dark toggle either — see the stance on theme switching for why.

Where a page genuinely calls for a different frame — a longread that wants a slower reading rhythm, or a data view that needs the full canvas — Rare Styles provides two opt-in body-level layout modes: Story for prose-heavy pages, Dashboard for data-heavy pages. Most pages need neither. The defaults already render correctly.

The important part is not how many components ship. It is that each one has earned its place by serving a real reading or decision task.

Standard Architecture

The library is organized into layered modules: tokens, utilities, layout, typography, elements, components, navigation, decorations, layouts. You can ship the full bundle or import only the modules you need from the SCSS source.

Tokens

All design decisions live as CSS custom properties — colors, spacing, typography, shadows, motion, surfaces. Adapting Rare Styles to a constrained brand context is a matter of overriding tokens in :root, not forking the library. Brand identity (--brand-color) and decision-driving accents (--signal) are intentionally kept separate.

Components

Components split into two semantic families. Cards carry narrative content: article previews, persons, projects. Panels carry data and system content: KPIs, charts, status, settings. Both work in either layout mode. The choice is semantic, not stylistic.

Layouts

Story and Dashboard are opt-in body-level modes for pages whose content asks for a different frame. Story scales typography up and adjusts heading treatment for prose-heavy reading; Dashboard removes the sidebar and lifts text-width constraints for data-heavy composition. Most pages need neither — the defaults already render correctly. The visual language stays identical across all three states.

Professional Considerations

Rare Styles accounts for details that are often skipped in feature-driven frameworks: keyboard focus visibility, motion reduction, semantic markup, WCAG AA contrast, and a clear public API contract that distinguishes breaking from non-breaking change.

The following sections cover each module in depth: tokens, layout, typography, colors, elements, components, navigation, decorations, utilities, layouts, and integration with sibling libraries — Rare Scripts and Rare Charts.