@cube-dev/ui-kit 0.171.0 → 0.173.0

package/docs/components/other/CubeLogo.md

@@ -37,35 +37,35 @@ Every path is drawn with `currentColor`. Inheriting is the default and usually c
 <CubeFullLogo color="#dark" />
 ```
 
-There are **no baked-in brand hexes**, which is what lets the marks work on any surface and in any schema.
+There are **no baked-in brand hexes**, which is what lets the marks work on any surface and in any scheme.
 
-## Light and dark schemas
+## Light and dark schemes
 
 The mark is two different drawings rather than one drawing recoloured — the dark variant is filled differently so it holds its weight against a dark surface. Both are rendered, and the `@dark` state swaps them in CSS.
 
 That means the swap costs no re-render, is correct during SSR and before hydration, and needs no prop in the normal case. It also means a snapshot of the DOM always contains both paths; assert on `[data-element="LightMark"]` / `[data-element="DarkMark"]` rather than on a single `path`.
 
-### Pinning a schema
+### Pinning a scheme
 
-`@dark` is a _state_, and it is resolved against the **document**. Where the background is known but the document schema does not describe it, pass `schema` to pin one mark:
+`@dark` is a _state_, and it is resolved against the **document**. Where the background is known but the document scheme does not describe it, pass `scheme` to pin one mark:
 
 ```jsx
 {/* A fixed-dark panel inside a light app */}
 <Block fill="#surface-inverse">
-  <CubeFullLogo schema="dark" color="#white" />
+  <CubeFullLogo scheme="dark" color="#white" />
 </Block>
 
 {/* A themed region — `tokens` overrides token *values*, so it cannot reach a state */}
-<Block tokens={renderColorTokens({ schema: 'dark' })} fill="#surface">
-  <CubeFullLogo schema="dark" />
+<Block tokens={renderColorTokens({ scheme: 'dark' })} fill="#surface">
+  <CubeFullLogo scheme="dark" />
 </Block>
 ```
 
-Use it only when you know the surface. Omitting it is the right default: a pinned schema stops following the user's own light/dark preference.
+Use it only when you know the surface. Omitting it is the right default: a pinned scheme stops following the user's own light/dark preference.
 
 ## Properties
 
-- **`schema`** `'light' | 'dark'` — Pin one mark instead of letting the `@dark` state pick. Omit it unless you know the surface; see [Pinning a schema](#pinning-a-schema)
+- **`scheme`** `'light' | 'dark'` — Pin one mark instead of letting the `@dark` state pick. Omit it unless you know the surface; see [Pinning a scheme](#pinning-a-scheme)
 - **`size`** — Maps onto `font-size`. Both axes on `CubeLogo`, height only on `CubeFullLogo`
 - **`color`** — Any color token. Both marks are drawn with `currentColor`, so this is inherited by default
 

package/docs/components/overlays/Tooltip.md

@@ -42,7 +42,7 @@ Display container for tooltip content. Has a directional arrow dependent on its
 - **`showIcon`** `boolean` — Controls whether an icon should be displayed in the tooltip
 - **`placement`** `PlacementAxis` (default: `'top'`) — Position of the tooltip relative to its trigger. Options: `top`, `bottom`, `left`, `right`
 - **`isMaterial`** `boolean` — Enables material-style tooltip with auto pointer events
-- **`isLight`** `boolean` — Uses light color schema for the tooltip
+- **`isLight`** `boolean` — Uses light color scheme for the tooltip
 - **`isOpen`** `boolean` — Controlled open state of the tooltip
 - **`defaultOpen`** `boolean` — Whether the tooltip is open by default (uncontrolled)
 - **`onOpenChange`** `(isOpen: boolean) => void` — Callback when the tooltip open state changes
@@ -78,7 +78,7 @@ These properties allow direct style application without using the `styles` prop:
 The `mods` property on the tooltip accepts the following modifiers you can override:
 
 - **`material`** `boolean` — Enables material-style tooltip with pointer events
-- **`light`** `boolean` — Uses light color schema instead of dark
+- **`light`** `boolean` — Uses light color scheme instead of dark
 - **`open`** `boolean` — Indicates whether the tooltip is currently visible
 
 ## Usage Patterns
@@ -144,7 +144,7 @@ Control where the tooltip appears relative to its trigger:
 The tooltip is capped at `36x` wide (or the viewport minus `4x`, whichever is smaller) and wraps its content to stay inside that cap. Runs with no spaces — URLs, tokens, identifiers, error strings — are broken mid-word rather than allowed to overflow the bubble.
 
 ```jsx
-<TooltipProvider title="https://cubecloud.example.com/deployments/12345/schema/files/model/cubes/very_long_cube_name.yml">
+<TooltipProvider title="https://cubecloud.example.com/deployments/12345/scheme/files/model/cubes/very_long_cube_name.yml">
   <Button>Hover me</Button>
 </TooltipProvider>
 ```

package/docs/components/overlays/TooltipProvider.md

@@ -19,7 +19,7 @@ A convenience wrapper that combines `TooltipTrigger` and `Tooltip` into a single
 - **`delay`** `number` (default: `250`) — The delay time in ms for the tooltip to show up
 - **`closeDelay`** `number` (default: `500`) — The delay time in ms for the tooltip to close
 - **`isMaterial`** `boolean` — Enables material-style tooltip with auto pointer events
-- **`isLight`** `boolean` — Uses light color schema for the tooltip
+- **`isLight`** `boolean` — Uses light color scheme for the tooltip
 - **`isOpen`** `boolean` — Controlled open state of the tooltip
 - **`defaultOpen`** `boolean` — Whether the tooltip is open by default (uncontrolled)
 - **`onOpenChange`** `(isOpen: boolean) => void` — Callback when the tooltip open state changes

package/docs/tasty/README.md

@@ -1,25 +1,29 @@
 # Tasty Docs
 
-Tasty is a styling engine for design systems that turns component state into deterministic CSS by compiling state maps into mutually exclusive selectors. Use this hub to choose the right guide once you know whether you are evaluating the model, adopting it in a design system, or implementing reusable, stateful components day to day.
+Tasty is CSS-in-JS for React design systems. You describe hover, disabled, variants, themes, responsive behavior, and other conditions as state maps; Tasty compiles them so one branch wins without specificity fights or source-order surprises.
+
+Use this hub to move from the core idea to a working component, then into design-system patterns or API reference as needed.
 
 ## Start Here
 
-- **New to Tasty**: [Getting Started](getting-started.md) for installation, the first component, optional shared `configure()`, ESLint, editor tooling, and rendering mode selection.
-- **Learning the component model**: [Methodology](methodology.md) for root + sub-elements, `styleProps`, tokens, extension, and recommended boundaries between `styles`, `style`, and wrappers.
-- **Evaluating the selector model**: [Style rendering pipeline](pipeline.md) for how mutually exclusive selectors make stateful styling deterministic.
-- **Evaluating fit**: [Comparison](comparison.md) for tool-selection context, then [Adoption Guide](adoption.md) for audience fit and rollout strategy inside a design system.
+- **Understand why**: [Introduction](../README.md) for the problem, the state-map model, and the product overview.
+- **Try it**: [Getting Started](getting-started.md) to build a stateful component, add shared configuration, and choose a rendering mode.
+- **Build a component system**: [Methodology](methodology.md) for root + sub-elements, typed public APIs, tokens, and extension patterns; then [Building a Design System](design-system.md).
+- **Evaluate or adopt it**: [Comparison](comparison.md) for tool-selection context and [Adoption Guide](adoption.md) for an incremental rollout.
+- **Understand the compiler**: [Style rendering pipeline](pipeline.md) for how state maps become mutually exclusive selectors.
 
 ## By Role
 
 - **Application developer using an existing design system**: [Getting Started](getting-started.md), then [React API](react-api.md).
 - **Design-system author**: [Methodology](methodology.md), [Building a Design System](design-system.md), [Configuration](configuration.md), and [Adoption Guide](adoption.md).
-- **Platform or tooling engineer**: [Configuration](configuration.md), [Zero Runtime (tastyStatic)](tasty-static.md), [Server-Side Rendering](ssr.md), and [Debug Utilities](debug.md).
+- **Platform or tooling engineer**: [Configuration](configuration.md), [Build-Time Extraction (`tastyStatic`)](tasty-static.md), [Server-Side Rendering](ssr.md), and [Debug Utilities](debug.md).
 
 ## By Styling Approach
 
 - **React components**: [React API](react-api.md)
-- **Zero-runtime / build-time extraction**: [Zero Runtime (tastyStatic)](tasty-static.md)
-- **Runtime `tasty()` with server collection and hydration**: [Server-Side Rendering](ssr.md)
+- **Zero-client-runtime React with `tasty()`**: [Server-Side Rendering](ssr.md), especially the static Astro integration
+- **Build-time extraction with `tastyStatic()`**: [Build-Time Extraction](tasty-static.md)
+- **Hydrated `tasty()` with server collection**: [Server-Side Rendering](ssr.md)
 - **Upgrading from v2**: [Migration Guide (v2 → v3)](migration-v3.md)
 
 ## By Task
@@ -32,3 +36,4 @@ Tasty is a styling engine for design systems that turns component state into det
 - **Debug generated CSS or cache behavior**: [Debug Utilities](debug.md)
 - **Understand how selector generation works internally**: [Style rendering pipeline](pipeline.md)
 - **Understand runtime injection internals**: [Style Injector](injector.md)
+- **Reproduce and interpret performance measurements**: [Runtime Benchmarks](runtime-benchmarks.md)

package/docs/tasty/adoption.md

@@ -1,8 +1,10 @@
 # Adoption Guide
 
-Tasty is not a drop-in replacement for another styling library. It is a **substrate for building a design-system-defined styling language**: what the comparison guide calls a house styling language. That means adoption usually starts where styling for reusable, stateful components has already become a composition problem, not with an all-at-once rewrite.
+Tasty is most useful where reusable component styling has become a state-resolution problem: hover intersects with disabled, variants intersect with themes, and every extension makes selector behavior harder to predict.
 
-This guide is for design-system maintainers and platform engineers evaluating Tasty or introducing it into an existing codebase. Use this document for rollout strategy and adoption sequencing; use the [Comparison guide](comparison.md) when the open question is whether Tasty is the right tool in the first place.
+It normally sits underneath a design system’s existing components. You can preserve their public React APIs while moving their style logic into state maps that produce one declared winner. Adoption should start with a small, state-heavy component—not an all-at-once rewrite.
+
+This guide is for design-system maintainers and platform engineers evaluating Tasty or introducing it into an existing codebase. Use it for rollout strategy and adoption sequencing; use the [Comparison guide](comparison.md) when the open question is whether Tasty is the right tool.
 
 ---
 
@@ -18,12 +20,14 @@ Product code
 ```
 
 **What Tasty owns:**
+
 - The DSL and value parser (tokens, custom units, auto-calc, color opacity)
 - State compilation (mutually exclusive selectors from state maps)
 - Style injection and deduplication (runtime or build-time)
 - The `tasty()` component factory and hooks API
 
 **What the DS team owns:**
+
 - Token names and values (colors, spacing, typography)
 - Custom units and their semantics
 - State aliases (`@mobile`, `@dark`, `@compact`)
@@ -39,12 +43,14 @@ Two teams using Tasty can end up with very different authoring models. That is b
 ## Who should adopt Tasty
 
 **Strong fit:**
-- A design-system or platform team that wants to define a governed styling language
+
+- A design-system or platform team that owns shared component APIs
 - Components with complex, intersecting states (hover + disabled + theme + breakpoint)
 - Teams that need deterministic style resolution without cascade/specificity bugs
-- Organizations where styling decisions should be centralized, not distributed
+- Organizations that want tokens, states, and extension rules to stay consistent across products
 
 **Not the right fit:**
+
 - Solo developers building a one-off app with minimal UI structure
 - Teams that want a shared utility vocabulary and direct markup authoring (Tailwind is better here)
 - Projects where low ceremony matters more than central governance
@@ -58,16 +64,16 @@ For a detailed comparison with Tailwind, Panda CSS, vanilla-extract, StyleX, Sti
 
 Tasty provides the engine. The DS team defines the language that runs on it. Here is what that typically involves:
 
-| Layer | What you define | Where |
-|-------|----------------|-------|
-| **Tokens** | Color names, spacing scale, border widths, radii | `configure({ tokens })` |
-| **Units** | Custom multiplier units (`x`, `r`, `bw`, or your own) | `configure({ units })` |
-| **State aliases** | Responsive breakpoints, theme modes, feature flags | `configure({ states })` |
-| **Recipes** | Reusable style bundles (card, elevated, input-reset) | `configure({ recipes })` |
-| **Typography** | Preset definitions (h1-h6, t1-t4, etc.) | `configure({ presets: { ... } })` |
-| **Style props** | Which CSS properties each component exposes as React props | `styleProps` in each component |
-| **Sub-elements** | Inner parts of compound components (Title, Icon, Content) | `elements` + capitalized keys in `styles` |
-| **Override rules** | How product engineers extend or constrain components | Styled wrappers via `tasty(Base, { ... })` |
+| Layer              | What you define                                            | Where                                      |
+| ------------------ | ---------------------------------------------------------- | ------------------------------------------ |
+| **Tokens**         | Color names, spacing scale, border widths, radii           | `configure({ tokens })`                    |
+| **Units**          | Custom multiplier units (`x`, `r`, `bw`, or your own)      | `configure({ units })`                     |
+| **State aliases**  | Responsive breakpoints, theme modes, feature flags         | `configure({ states })`                    |
+| **Recipes**        | Reusable style bundles (card, elevated, input-reset)       | `configure({ recipes })`                   |
+| **Typography**     | Preset definitions (h1-h6, t1-t4, etc.)                    | `configure({ presets: { ... } })`          |
+| **Style props**    | Which CSS properties each component exposes as React props | `styleProps` in each component             |
+| **Sub-elements**   | Inner parts of compound components (Title, Icon, Content)  | `elements` + capitalized keys in `styles`  |
+| **Override rules** | How product engineers extend or constrain components       | Styled wrappers via `tasty(Base, { ... })` |
 
 The same engine can power a minimal design system with a handful of tokens:
 
@@ -85,9 +91,15 @@ Here is how the layers connect end-to-end. The DS team configures the engine, de
 ```tsx
 // ds/config.ts — DS team defines the language
 configure({
-  tokens: { '#primary': 'oklch(55% 0.25 265)', '#surface': '#fff', '#text': '#111' },
+  tokens: {
+    '#primary': 'oklch(55% 0.25 265)',
+    '#surface': '#fff',
+    '#text': '#111',
+  },
   states: { '@mobile': '@media(w < 768px)', '@dark': '@root(schema=dark)' },
-  recipes: { card: { padding: '4x', fill: '#surface', radius: '1r', border: true } },
+  recipes: {
+    card: { padding: '4x', fill: '#surface', radius: '1r', border: true },
+  },
 });
 
 // ds/components/Card.tsx — DS team builds components on top
@@ -105,7 +117,7 @@ const Card = tasty({
 <Card padding={{ '': '4x', '@mobile': '2x' }}>
   <Card.Title>Monthly Revenue</Card.Title>
   <Card.Body>$1.2M — up 12% from last month</Card.Body>
-</Card>
+</Card>;
 ```
 
 See [Configuration](configuration.md) for the full `configure()` API.
@@ -116,9 +128,21 @@ See [Configuration](configuration.md) for the full `configure()` API.
 
 You do not need to adopt everything at once. Tasty is designed to be introduced layer by layer.
 
-A practical way to start is with the components that already suffer from intersecting state and variant logic: buttons, inputs, menus, disclosures, dialogs, list items, interactive cards, and compound components. Those are the places where deterministic resolution pays off fastest.
+A practical first slice is one component that already suffers from intersecting state and variant logic: a button, input, menu item, disclosure, or interactive card. Keep its public API unchanged, move one or two properties into Tasty state maps, and verify that the declared priority matches the behavior your team expects.
+
+This proves the differentiator before you invest in a complete token vocabulary or migrate an entire component library.
+
+### Phase 1 -- Pilot one state-heavy component
+
+Choose a component with a known hover/disabled, focus/error, or variant/theme interaction. Preserve its external props and visual behavior. The pilot should answer three questions:
+
+1. Is the state map easier to review than the existing selectors or conditional class logic?
+2. Does extending the component keep the intended state priority?
+3. Can your current tokens and component API move over without product-code churn?
+
+If the answer is yes, establish the shared design-system vocabulary around the successful slice.
 
-### Phase 1 -- Tokens and units
+### Phase 2 -- Tokens and units
 
 Start by defining your design tokens and custom units. This is the lowest-risk step: it only configures the parser and does not require rewriting any components.
 
@@ -136,14 +160,14 @@ configure({
   // A DS typically redefines them to use CSS custom properties
   // so that the actual scale is controlled via CSS, not JS:
   units: {
-    x: 'var(--gap)',   // 2x → calc(var(--gap) * 2)
+    x: 'var(--gap)', // 2x → calc(var(--gap) * 2)
     r: 'var(--radius)',
     bw: 'var(--border-width)',
   },
 });
 ```
 
-### Phase 2 -- State aliases and recipes
+### Phase 3 -- State aliases and recipes
 
 Define the state vocabulary your components will share. This is where you start encoding your team's conventions.
 
@@ -152,7 +176,8 @@ configure({
   states: {
     '@mobile': '@media(w < 768px)',
     '@tablet': '@media(w < 1024px)',
-    '@dark': '@root(schema=dark) | (!@root(schema) & @media(prefers-color-scheme: dark))',
+    '@dark':
+      '@root(schema=dark) | (!@root(schema) & @media(prefers-color-scheme: dark))',
   },
   recipes: {
     card: { padding: '4x', fill: '#surface', radius: '1r', border: true },
@@ -161,7 +186,7 @@ configure({
 });
 ```
 
-### Phase 3 -- Migrate a few primitives
+### Phase 4 -- Migrate a few primitives
 
 Pick 2-3 widely used primitives (Box, Text, Button) and rewrite them with `tasty()`. Keep the public API identical so product code does not need to change.
 
@@ -179,7 +204,7 @@ const Box = tasty({
 
 At this point you can validate the DSL, token workflow, and component authoring experience before expanding the rollout.
 
-### Phase 4 -- Encode complex states
+### Phase 5 -- Expand state resolution
 
 Move the components with the most painful intersecting states (buttons with hover + disabled + theme variants, inputs with focus + error + readonly) to Tasty's state map syntax. This is where mutually exclusive selectors start paying off.
 
@@ -209,7 +234,7 @@ const Button = tasty({
 });
 ```
 
-### Phase 5 -- Standardize style props and sub-elements
+### Phase 6 -- Standardize style props and sub-elements
 
 Define which style props each component category exposes. Layout components get flow/gap/padding. Interactive components get positioning. Compound components declare sub-elements.
 
@@ -225,9 +250,9 @@ const Card = tasty({
 });
 ```
 
-### Phase 6 -- Expand to full DS coverage
+### Phase 7 -- Expand to full DS coverage
 
-Migrate the remaining components, add the [ESLint plugin](https://github.com/tenphi/eslint-plugin-tasty) to enforce style conventions at lint time, and consider [zero-runtime mode](tasty-static.md) for static or performance-critical pages.
+Migrate the remaining components, add the [ESLint plugin](https://github.com/tenphi/eslint-plugin-tasty) to enforce style conventions at lint time, and choose between [server-only `tasty()`](ssr.md) and [`tastyStatic()` build-time extraction](tasty-static.md) when a page should ship no Tasty styling runtime.
 
 ---
 
@@ -254,8 +279,8 @@ const DangerButton = tasty(Button, {
 const LoadingButton = tasty(Button, {
   styles: {
     fill: {
-      loading: '#yellow',       // new state appended
-      disabled: '#gray.20',     // existing state overridden in place
+      loading: '#yellow', // new state appended
+      disabled: '#gray.20', // existing state overridden in place
     },
   },
 });
@@ -270,7 +295,7 @@ const LoadingButton = tasty(Button, {
 </Space>
 ```
 
-**Components are server components by default.** All `tasty()` components and style functions are hook-free, so they work as React Server Components without `'use client'`. In server-only contexts (Next.js RSC, Astro without `client:*` directives), they produce zero client JavaScript. Product engineers only add `'use client'` when their component needs actual React interactivity (state, effects, event handlers), never because of styling.
+**Components are server components by default.** All `tasty()` components and style functions are hook-free, so they work as React Server Components without `'use client'`. In server-only contexts they ship no Tasty styling runtime. Astro without `client:*` directives ships no client JavaScript; server-only Next.js RSC follows the same Tasty architecture, while final output depends on the application deployment. Product engineers only add `'use client'` when their component needs actual React interactivity (state, effects, event handlers), never because of styling.
 
 **No cascade/specificity concerns.** Tasty's mutually exclusive selectors mean extending a component cannot accidentally break another. Import order, class name collisions, and specificity arithmetic are non-issues.
 
@@ -295,4 +320,4 @@ const LoadingButton = tasty(Button, {
 - [Configuration](configuration.md) -- tokens, recipes, custom units, style handlers, and TypeScript extensions
 - [Style Properties](styles.md) -- complete reference for all enhanced style properties
 - [Comparison](comparison.md) -- positioning and trade-offs vs. other styling systems
-- [Zero Runtime (tastyStatic)](tasty-static.md) -- build-time static styling with Babel plugin
+- [Build-Time Extraction (`tastyStatic`)](tasty-static.md) -- static styling with the Babel plugin

package/docs/tasty/ai-agents.md

@@ -16,7 +16,7 @@ Color tokens (`#name`), custom properties (`$name`), `preset` names, `recipe` na
 const Card = tasty({ as: 'div', styles: { … }, styleProps: ['padding'] }); // new component
 const Hero = tasty(Card, { styles: { … } });                              // extend a component
 const cls = useStyles({ … });                                             // ad-hoc class name
-tastyStatic('.card', { … });                                              // build-time, zero runtime
+tastyStatic('.card', { … });                                              // build-time extraction
 ```
 
 - Wrap, don't pass styles per instance: ❌ `<Box styles={{ padding: '2x' }} />` → ✅ `const Box = tasty({ styles: { padding: '2x' } })`.
@@ -29,26 +29,26 @@ Keys are camelCase — a Tasty property or a real CSS property. No kebab-case, n
 
 Prefer the Tasty shorthand over its CSS equivalents:
 
-| Use | Instead of |
-|-----|------------|
-| `fill` | `backgroundColor`, `background` |
-| `image` | `backgroundImage` |
-| `border` | `borderColor`, `borderWidth`, `borderStyle`, `borderTop`/`Right`/`Bottom`/`Left` |
-| `radius` | `borderRadius` |
-| `outline` | `outlineColor`, `outlineWidth`, `outlineStyle`, `outlineOffset` |
-| `shadow` | `boxShadow` |
-| `padding` | `paddingTop`/`Right`/`Bottom`/`Left` |
-| `margin` | `marginTop`/`Right`/`Bottom`/`Left` |
-| `inset` | `top`, `right`, `bottom`, `left` |
-| `width` / `height` | `minWidth`/`maxWidth`, `minHeight`/`maxHeight` |
-| `flow` | `flexDirection`, `flexWrap`, `flexFlow`, `gridAutoFlow` |
-| `preset` | `fontSize`, `lineHeight`, `letterSpacing`, `fontWeight`, `fontStyle`, `textTransform` |
-| `font` | `fontFamily` |
-| `scrollbar` | `scrollbarWidth`, `scrollbarColor`, `scrollbarGutter` |
-| `gridColumns` / `gridRows` / `gridAreas` | `gridTemplateColumns` / `Rows` / `Areas` |
-| `textOverflow: 'ellipsis / 3'` | `lineClamp` |
-| `hide: true` | `display: 'none'` |
-| `flexGrow` / `flexShrink` / `flexBasis` | `flex` |
+| Use                                      | Instead of                                                                            |
+| ---------------------------------------- | ------------------------------------------------------------------------------------- |
+| `fill`                                   | `backgroundColor`, `background`                                                       |
+| `image`                                  | `backgroundImage`                                                                     |
+| `border`                                 | `borderColor`, `borderWidth`, `borderStyle`, `borderTop`/`Right`/`Bottom`/`Left`      |
+| `radius`                                 | `borderRadius`                                                                        |
+| `outline`                                | `outlineColor`, `outlineWidth`, `outlineStyle`, `outlineOffset`                       |
+| `shadow`                                 | `boxShadow`                                                                           |
+| `padding`                                | `paddingTop`/`Right`/`Bottom`/`Left`                                                  |
+| `margin`                                 | `marginTop`/`Right`/`Bottom`/`Left`                                                   |
+| `inset`                                  | `top`, `right`, `bottom`, `left`                                                      |
+| `width` / `height`                       | `minWidth`/`maxWidth`, `minHeight`/`maxHeight`                                        |
+| `flow`                                   | `flexDirection`, `flexWrap`, `flexFlow`, `gridAutoFlow`                               |
+| `preset`                                 | `fontSize`, `lineHeight`, `letterSpacing`, `fontWeight`, `fontStyle`, `textTransform` |
+| `font`                                   | `fontFamily`                                                                          |
+| `scrollbar`                              | `scrollbarWidth`, `scrollbarColor`, `scrollbarGutter`                                 |
+| `gridColumns` / `gridRows` / `gridAreas` | `gridTemplateColumns` / `Rows` / `Areas`                                              |
+| `textOverflow: 'ellipsis / 3'`           | `lineClamp`                                                                           |
+| `hide: true`                             | `display: 'none'`                                                                     |
+| `flexGrow` / `flexShrink` / `flexBasis`  | `flex`                                                                                |
 
 The last row goes the other way — longhands over the shorthand — because `flex` is lossy: it resets the components you omit to non-initial values (`flex: '0'` silently sets `flex-basis: 0%`) and cannot express `flexShrink: 0` at all. The longhands also carry separate state maps.
 
@@ -56,23 +56,23 @@ The last row goes the other way — longhands over the shorthand — because `fl
 
 ### Tokens
 
-| Syntax | Meaning |
-|--------|---------|
-| `#name` | color token → `var(--name-color)` |
-| `#name.50` | token at 50% opacity (`0`–`100`) |
-| `#name.$opacity` | opacity from a custom property |
-| `#clear` / `#current` | `transparent` / `currentcolor` |
-| `$name` | custom property → `var(--name)` |
-| `(#a, #b)` | fallback chain |
-| `$$name` / `##name` | the custom property *name* (not its value) — inside `transition` |
-| `$$name(…)` | call a CSS `@function` declared via `@function`, `useFunction`, or config |
+| Syntax                | Meaning                                                                   |
+| --------------------- | ------------------------------------------------------------------------- |
+| `#name`               | color token → `var(--name-color)`                                         |
+| `#name.50`            | token at 50% opacity (`0`–`100`)                                          |
+| `#name.$opacity`      | opacity from a custom property                                            |
+| `#clear` / `#current` | `transparent` / `currentcolor`                                            |
+| `$name`               | custom property → `var(--name)`                                           |
+| `(#a, #b)`            | fallback chain                                                            |
+| `$$name` / `##name`   | the custom property _name_ (not its value) — inside `transition`          |
+| `$$name(…)`           | call a CSS `@function` declared via `@function`, `useFunction`, or config |
 
 - ❌ `#f5f5f5`, `rgb(0 0 0)`, `oklch(…)`, `okhsl(…)`, `red` → ✅ `#surface` (add the token to the config if it doesn't exist).
 - ❌ `var(--gap)` → ✅ `$gap` · ❌ `$accent-color` → ✅ `#accent` · ❌ `transparent` → ✅ `#clear` · ❌ `currentColor` → ✅ `#current`.
 - A `$name` must be declared as a `'$name': value` key in the same styles object, or in the config.
 - Names are case-sensitive and start lowercase — `$myVar` → `--myVar`; a leading capital folds (`$Foo` → `--foo`). Prefer kebab-case.
 - A `$name` reference is untyped: it fills the first free slot in a shorthand (`border: '1bw $my-style'` → the line style). Write colors as `#name`; `$name-color` is a fallback for pointing at a raw CSS custom property that holds a color.
-- `preset` and `transition` take token *names*, not values, so a `$name` cannot stand in for one (it warns in dev and is ignored).
+- `preset` and `transition` take token _names_, not values, so a `$name` cannot stand in for one (it warns in dev and is ignored).
 
 ### Units
 
@@ -96,25 +96,25 @@ Never use it. Tasty owns specificity through doubled selectors and state orderin
 
 A value is `[values…] [modifiers…]`, and several groups can be comma-separated (later groups override earlier ones). A group that names **direction** modifiers takes a **single** value, applied to every direction it names — per-side values come from comma groups. A group naming no direction keeps plain CSS shorthand order (1–4 values). (`inset` + `dock` is the one exception: a second value insets the spanned sides.) Only the modifiers a property knows are valid:
 
-| Property | Modifiers |
-|----------|-----------|
-| `padding`, `margin`, `inset`, `fade` | `top` `right` `bottom` `left` |
-| `border` | the four directions + `solid` `dashed` `dotted` `double` `groove` `ridge` `inset` `outset` `none` `hidden` |
-| `outline` | the style keywords above |
-| `radius` | `top` `right` `bottom` `left` + shapes `round` `ellipse` `leaf` `backleaf` |
-| `width`, `height` | `min` `max` `fixed` |
-| `flow` | `row` `column` `row-reverse` `column-reverse` `wrap` `nowrap` `dense` |
-| `overflow` | `visible` `hidden` `scroll` `clip` `auto` `overlay` |
-| `position` | `static` `relative` `absolute` `fixed` `sticky` |
-| `shadow` | `inset` |
-| `preset` | `name / strong` (or `bold`) `italic` `icon` `tight` |
-| box properties | `longhand` — emit CSS longhands instead of the shorthand |
+| Property                             | Modifiers                                                                                                  |
+| ------------------------------------ | ---------------------------------------------------------------------------------------------------------- |
+| `padding`, `margin`, `inset`, `fade` | `top` `right` `bottom` `left`                                                                              |
+| `border`                             | the four directions + `solid` `dashed` `dotted` `double` `groove` `ridge` `inset` `outset` `none` `hidden` |
+| `outline`                            | the style keywords above                                                                                   |
+| `radius`                             | `top` `right` `bottom` `left` + shapes `round` `ellipse` `leaf` `backleaf`                                 |
+| `width`, `height`                    | `min` `max` `fixed`                                                                                        |
+| `flow`                               | `row` `column` `row-reverse` `column-reverse` `wrap` `nowrap` `dense`                                      |
+| `overflow`                           | `visible` `hidden` `scroll` `clip` `auto` `overlay`                                                        |
+| `position`                           | `static` `relative` `absolute` `fixed` `sticky`                                                            |
+| `shadow`                             | `inset`                                                                                                    |
+| `preset`                             | `name / strong` (or `bold`) `italic` `icon` `tight`                                                        |
+| box properties                       | `longhand` — emit CSS longhands instead of the shorthand                                                   |
 
 Directional modifiers beat placeholder zeros:
 
 - ❌ `padding: '0 0 2x 0'` → ✅ `padding: '2x bottom'`
 - ❌ `padding: '1x 1x 2x 1x'` → ✅ `padding: '1x, 2x bottom'`
-- ❌ `border: '0 0 1bw 0'` — four tokens parse as *one* border value, so this renders no border at all → ✅ `border: '1bw bottom'`
+- ❌ `border: '0 0 1bw 0'` — four tokens parse as _one_ border value, so this renders no border at all → ✅ `border: '1bw bottom'`
 - ❌ `padding: '2x 4x top right'` — a directional group takes one value, so `4x` is dropped → ✅ `padding: '2x top, 4x right'`
 - ❌ `fade: '3x 1x top bottom'` → ✅ `fade: '3x top, 1x bottom'`
 
@@ -130,17 +130,17 @@ Use semantic names, not CSS property names: `fade` `fill` `color` `theme` `borde
 
 A property value can be an object of `state: value`. Key order is priority — later keys win.
 
-| Key | Generated selector |
-|-----|--------------------|
-| `hovered` | `[data-hovered]` (boolean modifier from `mods`) |
-| `theme=danger` | `[data-theme="danger"]` (value modifier) |
-| `:hover` | pseudo-class |
-| `.active` | class selector |
-| `[aria-expanded="true"]` | attribute selector |
-| `hovered & .active` | AND |
-| `hovered \| focused` | OR (`,` also means OR) |
-| `!disabled` | NOT |
-| `hovered ^ focused` | XOR — exactly one (keep chains ≤ 4 operands) |
+| Key                      | Generated selector                              |
+| ------------------------ | ----------------------------------------------- |
+| `hovered`                | `[data-hovered]` (boolean modifier from `mods`) |
+| `theme=danger`           | `[data-theme="danger"]` (value modifier)        |
+| `:hover`                 | pseudo-class                                    |
+| `.active`                | class selector                                  |
+| `[aria-expanded="true"]` | attribute selector                              |
+| `hovered & .active`      | AND                                             |
+| `hovered \| focused`     | OR (`,` also means OR)                          |
+| `!disabled`              | NOT                                             |
+| `hovered ^ focused`      | XOR — exactly one (keep chains ≤ 4 operands)    |
 
 Precedence `!` > `^` > `|` > `&`; use parentheses to override.
 
@@ -148,9 +148,10 @@ Rules:
 
 1. **`''` comes first.** The bare default is the lowest-priority state; placing it later would override everything above it.
 2. **Every state map needs `''` or `_`** — except when extending (`tasty(Parent, …)`), where omitting `''` merges into the parent's states and including `''` replaces them wholesale.
-3. **`_` is standalone-only** and always first (with `''` right after it, if present). `_` is a never-negated fallback floor for cases where a higher-priority branch may be *unknown* (`@supports`, container queries). If a map contains only `_` and `''`, drop the `''`.
+3. **`_` is standalone-only** and always first (with `''` right after it, if present). `_` is a never-negated fallback floor for cases where a higher-priority branch may be _unknown_ (`@supports`, container queries). If a map contains only `_` and `''`, drop the `''`.
 4. **No nested maps:** ❌ `{ hovered: { pressed: 'x' } }` → ✅ `{ 'hovered & pressed': 'x' }`
 5. **State keys never sit at the top level** of a styles object — `:hover`, `.active`, `[open]` belong inside a property value.
+6. **Prefer automatic native states:** use `disabled` and `checked` in Tasty component styles instead of `[disabled]` and `[checked]`. The concise states track the corresponding native prop or attribute automatically.
 
 ```jsx
 color: { '': '#text', hovered: '#accent', disabled: '#text.40' }
@@ -158,16 +159,16 @@ color: { '': '#text', hovered: '#accent', disabled: '#text.40' }
 
 Advanced states:
 
-| Prefix | Use | Example |
-|--------|-----|---------|
-| `@media(…)` | media query; dimensions `w` `h`; types `@media:print` `:screen` `:all` `:speech` | `@media(w < 768px)`, `@media(600px <= w < 1200px)` |
-| `@(…)` | container query; dimensions `w` `h` `is` `bs` | `@(layout, w >= 600px)`, `@($variant=primary)` |
-| `@supports(…)` | feature query; `$` first argument tests a selector | `@supports(display: grid)`, `@supports($, :has(*))` |
-| `@root(…)` | condition on `:root` | `@root(schema=dark)` |
-| `@parent(…)` | condition on an ancestor; `, >` for the direct parent | `@parent(hovered, >)` |
-| `@own(…)` | a sub-element's own state — **only inside sub-element styles** | `@own(:hover)` |
-| `@starting` | `@starting-style` entry animation | `@starting` |
-| `@name` | project state alias | `@mobile` |
+| Prefix         | Use                                                                              | Example                                             |
+| -------------- | -------------------------------------------------------------------------------- | --------------------------------------------------- |
+| `@media(…)`    | media query; dimensions `w` `h`; types `@media:print` `:screen` `:all` `:speech` | `@media(w < 768px)`, `@media(600px <= w < 1200px)`  |
+| `@(…)`         | container query; dimensions `w` `h` `is` `bs`                                    | `@(layout, w >= 600px)`, `@($variant=primary)`      |
+| `@supports(…)` | feature query; `$` first argument tests a selector                               | `@supports(display: grid)`, `@supports($, :has(*))` |
+| `@root(…)`     | condition on `:root`                                                             | `@root(schema=dark)`                                |
+| `@parent(…)`   | condition on an ancestor; `, >` for the direct parent                            | `@parent(hovered, >)`                               |
+| `@own(…)`      | a sub-element's own state — **only inside sub-element styles**                   | `@own(:hover)`                                      |
+| `@starting`    | `@starting-style` entry animation                                                | `@starting`                                         |
+| `@name`        | project state alias                                                              | `@mobile`                                           |
 
 - At root level write the selector directly: ❌ `'@own(:hover)'` → ✅ `':hover'`.
 - `@name` aliases must exist in `states` in the config or be declared locally as an `'@name': '<state expression>'` key; alias keys start with `@` and their value must be a valid state expression.
@@ -187,21 +188,21 @@ styles: { Title: { preset: 'h3' }, Icon: { $: '>@:last-child', color: '#accent'
 
 ## 6. Special top-level keys
 
-| Key | Shape |
-|-----|-------|
-| `@keyframes` | `{ name: { '0%': styles, … } }` |
-| `@property` | `{ '$name': { syntax, inherits, initialValue } }` |
-| `@font-face` | `{ 'Family Name': descriptors \| descriptors[] }` |
-| `@counter-style` | `{ name: descriptors }` |
-| `@function` | `{ '$$name': { args, returns?, result, '$local'? } }` |
-| `recipe` | a **string** of configured recipe names: `'card elevated'`, `'reset input / autofill'`, `'none / disabled'` |
+| Key              | Shape                                                                                                       |
+| ---------------- | ----------------------------------------------------------------------------------------------------------- |
+| `@keyframes`     | `{ name: { '0%': styles, … } }`                                                                             |
+| `@property`      | `{ '$name': { syntax, inherits, initialValue } }`                                                           |
+| `@font-face`     | `{ 'Family Name': descriptors \| descriptors[] }`                                                           |
+| `@counter-style` | `{ name: descriptors }`                                                                                     |
+| `@function`      | `{ '$$name': { args, returns?, result, '$local'? } }`                                                       |
+| `recipe`         | a **string** of configured recipe names: `'card elevated'`, `'reset input / autofill'`, `'none / disabled'` |
 
 At-rule keys match the real CSS at-rule names, so they are kebab-case, not camelCase. Inside `@function`, the callable is `$$name` but its parameters and local variables are `$name`:
 
 ```jsx
 styles: {
   '@function': { $$negative: { args: ['$value'], result: '(-1 * $value)' } },
-  marginTop: '$$negative(2x)',
+  margin: '$$negative(2x) top',
 }
 ```