SynthCSS features
Vote on proposals, fund the ones that matter, and follow builds through to shipped.
Add native <dialog> component (.dialog parts, sizes), SynthJS showModal/close on existing open/dismiss, confirm pattern
SynthCSS has no documented dialog component. This adds a small, predictable vocabulary for:
Fix Windows test portability (fileURLToPath in 6 tests, .gitattributes LF) and add test.yml CI on Ubuntu + Windows
On Windows, several tests build filesystem paths with new URL(...).pathname. That yields /C:/..., or C:\C:\... once resolved, instead of a native path. Separately, git's default core.autocrlf=true on Windows checks files out with CRLF line endings, which makes scripts/verify-ai-contract.mjs report…
Add SynthMCP workspace package (packages/synthmcp): stdio MCP server over synthcss.ai.json with 7 tools
Coding agents should be able to query and validate SynthCSS through MCP instead of having the full docs embedded in their prompts. Every answer comes from synthcss.ai.json, the single source of truth.
Add optional SynthJS runtime (dist/synth.js IIFE): data-synth-* open, dismiss, toggle, tabs, dropdown with ARIA, tests and AI contract
AI-generated interfaces built with SynthCSS currently need hand-written DOM event code for interactivity. SynthJS is an optional, dependency-free runtime in the same repo. Markup declares interaction intent with data-synth-* attributes and SynthJS implements it accessibly. CSS-only usage stays…
Add a zero-specificity base layer applying font, colour and type-scale tokens to html and h1–h4 in synthcss.css
SynthCSS defines --font-sans, --color-text, --color-background, --leading-normal and the --text-* scale, but no rule applies them to the document.
Contract 1.1.0: add data-ui/@layer synth.ext extension rule, app-shell example and 'Not covered yet' list
The AI contract (synthcss.llm.md / synthcss.ai.json, v1.0.0) forbids custom classes, custom flex/grid, restyling components and non-token inline styles. It offers no legal path when the vocabulary lacks a pattern, so generators break the rules inconsistently. The contract also has no full-page…
Add .switch toggle and .input-group (input with attached buttons/selects) form components
.field covers labelled controls, but there is no toggle switch and no input with an attached button. In a benchmark, agents fell back to plain checkboxes and hand-wrote flex CSS for attached buttons, which violates AI Generation Rule 2 (no custom CSS). Both patterns should be first-class components.
Add .nav/.nav-link and .tabs/.tabs-item components with ARIA-driven state and AI contract entries
In benchmark runs, every agent-generated page with navigation hand-wrote nav-link CSS. Every team-screen run also hand-wrote a segmented control. The selected-state attribute was inconsistent: aria-selected in some runs, aria-pressed in another. SynthCSS should provide both components and name one…
Add .avatar component (initials/image/icon, sizes, tone variants), --color-accent token, and .alert-icon part
Dashboards need small square or round chips for initials, photos and icons on a tinted background. SynthCSS has no component for these, and no non-status decorative hue. In a benchmark, agents hand-wrote 21–70 lines of custom CSS per page, invented --color-accent, and in one run added unsanctioned…
Add zero-specificity base layer applying font, colour and heading type tokens to html and h1–h4
SynthCSS defines font, colour and type tokens but never applies them to the document. Pages that follow the contract render in the browser's default serif font, and overriding --font-sans on :root has no visible effect. Benchmark evidence: 5 of 6 agent-built pages rendered in serif.
Add .sidebar-end modifier so sidebar layouts can put the narrow column on the right, with contract entries
.sidebar, .sidebar-sm and .sidebar-lg always make the first child the narrow column. Dashboards often need a wide main column with a narrow column on the right.
Add versioned AI contract (synthcss.llm.md + synthcss.ai.json) with sync verification and showcase section
AI agents should be able to learn SynthCSS's full public vocabulary from one compact file in a single context window. They should not need to crawl the docs or read the source.
Add core semantic components (button, field, card, badge, alert, panel, table, empty-state) with docs, showcase and tests
Give AI agents a small, semantic, predictable component vocabulary on top of the existing SynthCSS tokens and layout primitives, so they can build a common app UI without composing low-level utility classes.
Add a static SynthCSS showcase site (showcase/) with automated GitHub Pages deployment via Actions
Give visitors a single static page that shows what SynthCSS is, why it is AI-first, and live demos of its existing tokens and layout primitives. The page is published via GitHub Pages and built with SynthCSS itself.
Add semantic layout primitives (container, stack, cluster, grid, sidebar, split, center, cover) with docs and fixtures
Give SynthCSS a small, intent-named structural vocabulary so that AI agents can build responsive layouts without composing low-level flex/grid utilities.
Add core semantic CSS design tokens (:root), default light theme, token reference docs and check script
SynthCSS needs a small, semantic set of CSS custom properties that every future component and layout primitive consumes. AI agents should be able to restyle an interface by changing a handful of clearly named variables, e.g. "more compact, larger radius, different primary color".