Skip to content

Tags

Tags

v3.20.5

Toggle v3.20.5's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release v3.20.5 (#28)

Version pins 3.20.4 -> 3.20.5 across the site, library headers, MCP
render and skill (digests rebuilt). CHANGELOG and README cover the
Streaming status alignment (#23), hover/press states (#24), Image,
Field value, data-db-dismiss and Navbar phone menu (#25), and the
hosted MCP gaps (#26).

Co-authored-by: Claude <noreply@anthropic.com>

v3.20.4

Toggle v3.20.4's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Release v3.20.4 (#22)

Version pins 3.20.3 -> 3.20.4 across the site, library headers, MCP
render and skill (digests rebuilt). CHANGELOG and README cover the
combo-audit PRs (#8-#18), the design-eval render fixes (#21), weblook
SSRF hardening (#7) and daub-ui skill v2 (#20).

Co-authored-by: Claude <noreply@anthropic.com>

v3.20.3

Toggle v3.20.3's commit message
Consistent renderer coercions, #s= share links, preview state, first-…

…party MCP assets (v3.20.3)

Problem: the three renderers (playground, daub-render.js, MCP) coerced
malformed props differently, so one spec rendered three ways; string
options, object-map columns, 0 cells, flat Sidebar items and footer ids
misrendered. Share links carried the spec in ?s=, which reaches the
server and hits URL limits. The playground preview lost checkbox/radio/
select/slider state because renderers set DOM properties that HTML
serialization drops. MCP HTML pinned daub-ui@3.20.2 on jsDelivr, a
version never published to npm (404). lucide@latest (1.x) dropped brand
icons. The blocking fallback could never succeed.

Solution: one written coercion contract implemented in all three
renderers; footer ids filtered to real elements; scalar table props
treated as empty; DropdownMenu trigger rule; notices carry data-spec-id.
Share links move to #s= with legacy ?s= and hashchange support under the
same shared-code gating. State props also write their attributes. MCP
HTML loads daub.css/daub.js/daub-render.js from daub.dev with ?v=.
lucide pinned to 0.576.0 with SRI everywhere. Blocking fallback parses
SSE. Codegen prompts forbid redeclaring container/preview; planner
shared state is validated.

Checks: CANON probe 0 failures on all three renderers; 1,728-case prop
fuzz 0 new failures; 386-spec corpus vs 511a5fd with every diff
attributed; state probe catches 13 old bugs, 0 now; security ex1/bypass/
inert/ex2 via ?s= and #s=: 0 leaks; 192/192 unit, 35/35 MCP, component
audit 84/84; live e2e on wrangler with real OpenRouter calls.

Co-Authored-By: Claude <noreply@anthropic.com>

v3.20.2

Toggle v3.20.2's commit message
Keep sidebar layouts side by side; gap 0 means 0 in every renderer

Problem: on daub.dev a generated analytics dashboard rendered its sidebar
above the content instead of beside it. Horizontal Stacks default to
flex-wrap: wrap, so a sidebar + wide-content row wrapped whenever the
content's natural width exceeded the space left. Separately,
daub-render.js and the MCP renderer drew Stack gap: 0 as the 8px default,
while the playground and the documented token scale mean 0px.

Solution: when a horizontal Stack holds a Sidebar, the sidebar gets
flex: 0 0 auto and each other child flex: 1 1 480px with min-width 0.
Desktop previews keep the content beside the sidebar; phones, where 480px
does not fit, still stack. Wrap stays on, so nothing else changes. Same
code in all three renderers, plus the gap fix in the two library copies.

Checks: sidebar dashboard in the playground preview at 956px is side by
side (260 + 664), at 375px stacked; 386-spec regression corpus vs the
deployed b9c51df differs only in sidebar flex styles (playground 25
specs) and gap-0 spacing (library copies), with 0 errors or notices;
192/192 unit tests; syntax checks pass.

Co-Authored-By: Claude <noreply@anthropic.com>

v3.19.11

Toggle v3.19.11's commit message
chore: release v3.19.11.

v3.19.10

Toggle v3.19.10's commit message
chore: release v3.19.10.

v3.19.9

Toggle v3.19.9's commit message
chore: release v3.19.9.

v3.19.8

Toggle v3.19.8's commit message
chore: release v3.19.8.

v3.19.5

Toggle v3.19.5's commit message
fix: improve AI spec generation quality — 7 prompt and validation fix…

…es (v3.19.5)

- Strengthen Text tag/content prop guidance to prevent swapping
- Clarify Card footer (array of IDs) vs media (URL string) distinction
- Add inline-data-only warnings to Sidebar sections and CommandPalette groups
- Add "no Icon component type" guideline rule
- Add Badge "success" variant to prompt
- Add Card prop validation warnings for footer:true and media:[array]
- Remove stale Icon/Link types from Cloudflare MCP
- Sync all fixes to both local and Cloudflare MCP

v3.19.4

Toggle v3.19.4's commit message
feat: industry-aware design intelligence for AI spec generation (v3.1…

…9.4)

Add 20 industry categories (SaaS, fintech, healthcare, e-commerce, etc.)
with theme mapping, anti-pattern rules, and layout guidance. Expand theme
heuristics from 6 to 14 mappings. Add UX validation warnings (BottomNav
>5 items, multiple primary buttons, missing labels, empty components).
Add mobile design rules parity and page formulas. 36 new tests.