Skip to content
Docs
Changelog

Web screens follow ui-sdk's own skill

The ui-sdk agent skill is linked from the installed package, adapted to the shadcn wrappers once, and every web screen workflow routes through it.

Markdown

  • ui-sdk's skill is part of the repository. .agents/skills/ui-sdk and .claude/skills/ui-sdk link to the skill inside the installed @ui-sdk/core, so Claude Code, Codex and Cursor load it at the version packages/ui pins. scripts/web-ui-sdk.test.mjs checks the links and the version, and refuses a @ui-sdk/* import or dependency in apps/web. (72d42208)
  • One adaptation, linked from everywhere. Design patterns says how the skill applies here: shadcn wrappers instead of @ui-sdk/*, a component the skill's table names and packages/ui lacks wrapped there first, our tokens instead of web.css, wiring and agent tests, and which rules win. AGENTS.md, ui-catalog, domain-feature and the review checklist point to it. (d3b156c6, db2c02d2)
  • An agent test for the settings screen. settings.agent.test.tsx drives the screen through ui-sdk's createAgent, re-exported for tests as @template-cloudflare/ui/lib/agent: it finds Name and Save changes by their labels, renames the user and saves. It found the avatar and the tabs without a name; both are now named through i18n (ae8b4b03). The web test setup turns on ui-sdk's strict mode. Nothing new ships to the browser. (46da6551)
  • ui-sdk is no longer called an experiment in the wrappers, the lab page, Libraries and the docs home. (8776901a)

PR #204

Edit on GitHubDocumentation is in English.
Cookie settings
We use essential cookies to make our app work. With your consent, we also use optional cookies to improve your experience.

Read our Cookie Policy and Privacy Policy.