@vibes.diy/prompts 14.3.207 → 14.3.209

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -2,7 +2,7 @@ This look is a room full of cushions. `@vibes.diy/ui` ships every surface, contr
2
2
 
3
3
  ## Composition
4
4
 
5
- One view does one job. Let everything on screen serve it; a second job gets its own view, tab or sheet. Content lives on cushions: a group of related things sits in a `Card`, a list is one `RowCard` per item, a headline number is a `Stat`, an empty list is an `Empty`, and the closing ask on a page is a `CTA`. Those are the only raised surfaces; if something needs to float, it is a `Card`.
5
+ One view does one job. Let everything on screen serve it; a second job gets its own view, tab or sheet. Content lives on cushions: a group of related things sits in a `Card`, a list is one `RowCard` per item, a headline number is a `Stat`, an empty list is an `Empty`, and the closing ask on a page is a `CTA`. Those are the only raised surfaces; whatever needs to float is a `Card`.
6
6
 
7
7
  Every view has exactly one lead: the single element wearing `tone="purple"`, usually the primary `Button`. Most tone-taking components default to the lead — `Button`, `Badge`, `Dot`, `IconTile`, `Avatar`, `Progress`, `CTA`, `NavLink`, `ToggleGroup`, chart series — so set `tone` explicitly on everything but the one lead. An `Empty` may carry its own `purple` `IconTile`: it shows only when the view holds nothing else. A second button takes `variant="quiet"` or a meaning tone (`down` for delete). Three components default to an untaught tone and always get one: `Tabs` and `Segmented` take `tone="info"`, `Highlight` takes `tone="orange"`. `Confirm` defaults to the decorative fill, so a destructive ask passes `tone="down"`.
8
8
 
@@ -10,7 +10,7 @@ Open a view with a `Heading level={1}`, then the job; each section gets a `Headi
10
10
 
11
11
  ## Layout
12
12
 
13
- Placement is a layout primitive. `Stack` stacks children vertically with an even `gap`; `Row` lays them side by side with `gap`, `align`, `justify` and `wrap`, and a `Spacer` inside a `Row` pushes what follows to the far end. `Grid` places cards in two, three or four columns, or main plus side with `cols="sidebar"`, and stacks them on a phone by itself. An app with several sections wears a `Shell` with a `Sidebar` of `NavLink`s beside the main column, and a `BottomNav` on a phone. When a primitive cannot express the placement, a plain wrapping `div` carries the spacing.
13
+ Placement is a layout primitive. `Stack` stacks children vertically with an even `gap`; `Row` lays them side by side with `gap`, `align`, `justify` and `wrap`, and a `Spacer` inside a `Row` pushes what follows to the far end. `Grid` places cards in two, three or four columns, or main plus side with `cols="sidebar"`, and stacks them on a phone. An app with several sections wears a `Shell` with a `Sidebar` of `NavLink`s beside the main column, and a `BottomNav` on a phone. When a primitive cannot express the placement, a plain wrapping `div` carries the spacing.
14
14
 
15
15
  The gap scale runs from `1` to `6`: `gap={3}` between the parts of a card, `gap={5}` or `gap={6}` between sections. Give the page air; cushions never touch.
16
16
 
@@ -150,7 +150,7 @@ What the lines above leave out:
150
150
  - Let exactly one element per view wear `tone="purple"`, and give every other `Button` `variant="quiet"` or a tone that states its meaning.
151
151
  - Set `tone` explicitly on every `Badge`, `Dot`, `IconTile`, `Avatar`, `Progress`, `Tabs`, `Segmented`, `Highlight` and chart series, and pass `tone="down"` to a `Confirm` that deletes.
152
152
  - Wrap every form control in a `Field` and pass its `id` and `describedBy` through the render function.
153
- - Show a `Skeleton` while data loads, an `Empty` for an empty list and an `ErrorNote` when a request fails.
153
+ - Show a `Skeleton` while `callAI`, `fetch` or `ready` is pending, an `Empty` for an empty list and an `ErrorNote` when a request fails.
154
154
  - Ask before an irreversible action with `Confirm` around its button; acknowledge a finished one with `toast`.
155
155
  - Render a person with `<ViewerTag userHandle={...} />` and pick one with `<HandleInput />`.
156
156