Skip to content
Browse documentation
skills

Design

Define UI intent, design-system constraints, and interaction evidence for agent-assisted Whisk authoring.

Give the agent a design boundary

Describe the audience, task, content hierarchy, existing visual system, and desired interaction before asking an agent to change an interface. Name what must remain stable and which browser, accessibility, and responsive checks will demonstrate improvement. Design intent is different from implementing application behavior, although a single task may need both.

Use smoothie-design for product pages and application UI. It follows the selected release's design guide, preserves the existing theme unless you request a custom one, and checks responsive layout and accessibility. Figma alignment is optional. Supply the application, existing renderer, desired interaction, and validation scope. Combine it with development for wider application changes.

Use smoothie-whisk-authoring for specialist style recipes, renderer integration, or an explicitly requested genUI surface. Both skills preserve React or Octane rather than switching renderers to implement a control.

Component APIs, styling, and generated-UI contracts have one documentation home: whisk/ui. Read the installed package references when they differ from current website examples; this workflow does not redefine those APIs.

Specify the UI behavior

text
Use smoothie-design in /absolute/my-product.
Build an accessible task filter using the existing native renderer and Whisk components.
Reuse the app's tokens, theme, and build-time styling pipeline.
Test labels, keyboard focus, empty results, and narrow/wide layouts.
Local type, test, build, and browser checks are authorized.
Do not add genUI, change renderers, or patch dependencies.
Report the component/style changes and the interaction checks performed.

Request genUI separately when a model or transported document needs to describe the surface. Then specify the selected catalog and trusted action handlers, and require validation and client reparsing across transport boundaries. Ordinary handwritten JSX should not be routed through a document merely to use Whisk components.

Review the UI result

Expect native interaction and compiled-style evidence, not just a screenshot or successful document parse. For genUI, require malformed-document, binding, action, and update checks. If SSR is part of the task, require server/client agreement, DOM adoption, early-edit, update, and disposal checks for the selected renderer. A passing bounded fixture is not proof of arbitrary Octane hydration; warnings must not be hidden or dependencies patched.