# Smoothie Framework docs > Product documentation for Smoothie Framework: install the CLI, create an > application from a Starter, build Agents, Models, Tools and Services, and > look up Recipes, whisk/ui and reference material. Each page is served as static HTML containing the full page text, so it can be read without JavaScript or a customer account. ## Agent setup after purchase 1. [Start with the setup prompt](https://smoothie.dev/docs/framework/coding-agents#after-purchase): Inspect the workspace, clarify the product and destination, and preserve existing files. 2. [Install the CLI](https://smoothie.dev/docs/framework/install): Use the official installer for the current platform and check command help. 3. [Verify GitHub access and acquire a release](https://smoothie.dev/docs/framework/get-framework): Use the invited personal account through gh. Interactive sign-in and invitation acceptance belong to the user; never paste credentials into a prompt. 4. [Choose a Starter](https://smoothie.dev/docs/framework/choose-starter) and [create an application](https://smoothie.dev/docs/framework/build), or [adapt an existing project](https://smoothie.dev/docs/framework/existing-project). Review plans before applying changes. 5. [Install release-matched skills](https://smoothie.dev/docs/framework/skills/installation) and [connect MCP](https://smoothie.dev/docs/framework/mcp-cli/mcp-clients). Verify a context search and reference read; do not claim a saved config is a working connection. 6. [Run the project's checks](https://smoothie.dev/docs/framework/applications/testing): Report actual results, skipped checks and platform limitations. Deployment and model spending require separate authority. Use this index for navigation; read only the guides relevant to the task. For a complete public documentation snapshot, download [llms-full.txt](https://smoothie.dev/docs/llms-full.txt). After acquisition, use the installed release's retained references for its APIs; report differences from current online docs rather than guessing. These public files contain no private Framework release or account data. ## Start here - [Smoothie Framework](https://smoothie.dev/docs/framework/overview): Smoothie Framework is a pre-release set of TypeScript packages and editable Starters, installed and managed with the public Smoothie CLI. - [Install the CLI](https://smoothie.dev/docs/framework/install): Install the public executable, separately from the access-controlled Framework, and check its version. - [Obtain a Framework release](https://smoothie.dev/docs/framework/get-framework): Download a matching source and package release with your Framework access, or verify artifacts you already have. - [Choose a Starter](https://smoothie.dev/docs/framework/choose-starter): Compare the web, interactive Agent, and durable Worker Starters before creating a new application from one. - [Create your first application](https://smoothie.dev/docs/framework/build): Create Smoothie Starter from a verified release, run selected checks, and open a working web application. - [Add Smoothie to an existing project](https://smoothie.dev/docs/framework/existing-project): Add prepared Framework packages to a single Bun project without replacing product source or native tooling. - [Develop with a coding agent](https://smoothie.dev/docs/framework/coding-agents): Install release-matched skills, give a coding agent scoped project context, and keep task execution explicit. - [Capabilities and contracts](https://smoothie.dev/docs/framework/capability-layer): Understand capabilities, contracts, adapters, and native ownership without a universal Application facade. - [Compatibility and release scope](https://smoothie.dev/docs/framework/sdk-profiles): Check the TypeScript toolchain, tested hosts, rendering limits, and what verification results prove. ## Guides - [Application guides](https://smoothie.dev/docs/framework/applications): Develop, verify, update, and deploy a TypeScript application with native tooling and explicit CLI operations. - [Application structure](https://smoothie.dev/docs/framework/applications/structure): Organize browser/server targets, shared contracts, native configuration, and retained Framework artifacts. - [Configuration and environment](https://smoothie.dev/docs/framework/applications/configuration): Keep project metadata, native configuration, capability bindings, and server-only secrets with their owners. - [Local development](https://smoothie.dev/docs/framework/applications/local-development): Install retained packages and run native development without a second application runtime. - [Testing and verification](https://smoothie.dev/docs/framework/applications/testing): Distinguish artifact integrity, project metadata, selected native tasks, and actual browser or deployment behavior. - [Build and deployment](https://smoothie.dev/docs/framework/applications/deployment): Prepare and review a native application payload, deploy exact bytes, and verify the selected target deliberately. - [Updates and rollback](https://smoothie.dev/docs/framework/applications/updates): Switch retained Framework package selections without overwriting product source, and recover controlled writes safely. - [Customize Framework source](https://smoothie.dev/docs/framework/applications/customize-framework): Keep SDK changes in a private source checkout and verify explicitly identified custom package archives before installation. - [CI and troubleshooting](https://smoothie.dev/docs/framework/applications/ci-troubleshooting): Automate explicit native checks, interpret structured outcomes, and diagnose failures at the boundary that owns them. ## TypeScript SDK - [TypeScript SDK](https://smoothie.dev/docs/framework/typescript): Choose the capabilities your application needs and compose them with native hosts, tools and UI. - [Services and typed clients](https://smoothie.dev/docs/framework/services): Define an operation once, implement it on the server, and call it through a validated typed client. - [Define contracts and handlers](https://smoothie.dev/docs/framework/services/contracts): Describe public DTOs independently, then bind handlers and request state on the server. - [Run an HTTP service](https://smoothie.dev/docs/framework/services/http): Mount a checked Service on Elysia and make server startup and resource ownership explicit. - [Call services from your application](https://smoothie.dev/docs/framework/services/client): Use contract-derived DTO types while keeping credentials and implementation code server-only. - [Query caching with TanStack Query](https://smoothie.dev/docs/framework/services/query-caching): Derive native query and mutation options from Service contracts without adding a wrapper hook layer. - [Streaming, errors and cancellation](https://smoothie.dev/docs/framework/services/streaming): Distinguish HTTP results from long-lived streams and keep cancellation separate from rollback. - [Browser-safe contracts and OpenAPI](https://smoothie.dev/docs/framework/services/browser-contracts): Optionally project trusted contract modules for browsers and export the bounded JSON OpenAPI profile. - [Database](https://smoothie.dev/docs/framework/database): Use Bun SQLite directly or add Drizzle while retaining native query and transaction APIs. - [Bun SQLite and optional Drizzle](https://smoothie.dev/docs/framework/database/bun-sqlite): Open a native SQLite connection without hiding SQL or replacing Drizzle's type system. - [Connection ownership and migrations](https://smoothie.dev/docs/framework/database/lifecycle): Make the native target responsible for its connection, schema readiness and recovery. - [Authentication](https://smoothie.dev/docs/framework/authentication): Verify identity at request boundaries and keep provider sessions separate from application permissions. - [Verify requests and sessions](https://smoothie.dev/docs/framework/authentication/requests): Admit protected requests using a fresh verified session and exact trusted origins. - [Connect Better Auth](https://smoothie.dev/docs/framework/authentication/better-auth): Reuse native Better Auth session handling while exposing only verified identity to Smoothie. - [Authentication forms](https://smoothie.dev/docs/framework/authentication/forms): Use accessible Octane forms while retaining control of transport, sessions and navigation. - [Storage](https://smoothie.dev/docs/framework/storage): Store bounded immutable blobs with shared integrity checks and explicit application ownership. - [Store and retrieve files](https://smoothie.dev/docs/framework/storage/files): Persist an immutable blob and validate its bytes against a retained descriptor. - [Filesystem, S3 and R2](https://smoothie.dev/docs/framework/storage/adapters): Select an optional storage implementation without widening the common blob contract. - [Email](https://smoothie.dev/docs/framework/email): Send bounded transactional messages through an explicit delivery adapter. - [Send transactional email](https://smoothie.dev/docs/framework/email/send): Validate the message before delivery and interpret the provider's result conservatively. - [Configure SMTP](https://smoothie.dev/docs/framework/email/smtp): Connect a verified TLS relay or explicitly local development capture without exposing credentials. - [Models](https://smoothie.dev/docs/framework/models): Call models through explicit provider bindings, validated outputs and bounded execution policies. - [Providers and credentials](https://smoothie.dev/docs/framework/models/providers-adapters): Choose a provider integration and resolve credentials at the server execution boundary. - [Generate text and structured output](https://smoothie.dev/docs/framework/models/structured-output): Request ordinary text or a schema-validated terminal object without trusting unparsed model output. - [Streaming and cancellation](https://smoothie.dev/docs/framework/models/streaming-cancellation): Consume incremental model events while preserving terminal validation and cancellation ownership. - [Routing, retries and fallbacks](https://smoothie.dev/docs/framework/models/routing): Declare candidate models and bound physical attempts without hiding route changes. - [Usage and inference budgets](https://smoothie.dev/docs/framework/models/usage-cost): Separate recorded usage from atomic admission of each physical model attempt. - [Tools](https://smoothie.dev/docs/framework/tools): Expose application operations through validated contracts, explicit bindings and execution controls. - [Define, bind and execute tools](https://smoothie.dev/docs/framework/tools/define): Give an operation typed JSON contracts and a stable implementation identity before exposing it to a model. - [Connect MCP tools](https://smoothie.dev/docs/framework/tools/mcp): Adapt an application-owned MCP client into Smoothie Tool definitions without adding a transport to Core. - [Failures and effect recovery](https://smoothie.dev/docs/framework/tools/recovery): Distinguish safe input repair from uncertain execution so retries cannot silently duplicate effects. - [Agents](https://smoothie.dev/docs/framework/agents): Compose model and Tool execution with explicit run state, context and application ownership. - [Define and run an agent](https://smoothie.dev/docs/framework/agents/define): Create a typed definition, choose an execution runtime, and own the resulting Agent lifetime. - [Instructions and model context](https://smoothie.dev/docs/framework/agents/instructions-context): Separate trusted instructions from user data and select bounded completed history explicitly. - [Sessions and conversation threads](https://smoothie.dev/docs/framework/agents/sessions-state): Keep Core run coordination distinct from application-owned durable conversation history. - [Application execution ownership](https://smoothie.dev/docs/framework/agents/execution): Coordinate admission, dispatch, publication and cleanup without introducing another Agent loop. - [Streaming, cancellation and recovery](https://smoothie.dev/docs/framework/agents/streaming): Observe run state and distinguish stopping observation from cancelling durable work. - [Workers and background execution](https://smoothie.dev/docs/framework/workers): Dispatch typed background work and observe its lifecycle independently of a request or UI. - [Define and run a worker](https://smoothie.dev/docs/framework/workers/define): Declare typed input and output, bind a handler, and dispatch a local run. - [Redis queues](https://smoothie.dev/docs/framework/workers/redis): Use explicit scoped Redis transport while retaining run persistence and host ownership. - [Persistence, controls and recovery](https://smoothie.dev/docs/framework/workers/recovery): Persist accepted work, project lifecycle records atomically and reconcile before admitting new requests. - [Policies, approvals and audit](https://smoothie.dev/docs/framework/governance): Control Tool execution and retain evidence without confusing permissions, usage and external effects. - [Tool policies](https://smoothie.dev/docs/framework/governance/policies): Select explicit decisions by Tool or capability and apply them in trusted runtime composition. - [Approval requests and decisions](https://smoothie.dev/docs/framework/governance/approvals): Record an explicit human decision and resume only the intended pending operation. - [Timeline and usage records](https://smoothie.dev/docs/framework/governance/timeline): Retain bounded execution history and usage while preserving the distinction between observation and enforcement. - [API and adapter index](https://smoothie.dev/docs/framework/typescript/reference): Find exact public imports, shared contract rules and capability-owned adapter documentation. - [Public entrypoints](https://smoothie.dev/docs/framework/reference/framework-api): Look up the package exports in the current TypeScript commercial selection. - [Contracts and JSON validation](https://smoothie.dev/docs/framework/reference/contracts): Understand what TypeScript inference proves, what runtime validation checks and which values are portable. - [Adapter reference](https://smoothie.dev/docs/framework/reference/adapters): Find the native integration for each capability without introducing a universal adapter layer. ## CLI - [Smoothie CLI](https://smoothie.dev/docs/framework/mcp-cli): Create an app, manage Framework releases, check your project, or connect a coding agent. - [Framework releases](https://smoothie.dev/docs/framework/mcp-cli/framework-releases): Download a release, verify its files, and choose the packages your app needs. - [Recipe commands](https://smoothie.dev/docs/framework/mcp-cli/recipes): Find a Recipe in your release and turn it into an editable application. - [Project operations](https://smoothie.dev/docs/framework/mcp-cli/project-operations): Inspect project settings, find available checks, and follow the supported deployment flow. - [Context and search](https://smoothie.dev/docs/framework/mcp-cli/context): Search your app's retained references or your own Markdown, then read a matching page. - [MCP and coding agents](https://smoothie.dev/docs/framework/mcp-cli/mcp): Give your coding agent access to selected docs, project checks, and approved tools. - [Connect a coding agent](https://smoothie.dev/docs/framework/mcp-cli/mcp-clients): Add Smoothie to Codex or Claude Code and check that the connection works. - [Context and tool discovery](https://smoothie.dev/docs/framework/mcp-cli/local-embeddings): Help your agent find relevant context while you control tool access. Add local embeddings for optional semantic search. - [Tools and permissions](https://smoothie.dev/docs/framework/mcp-cli/tools-permissions): Choose which tools your agent can call, pin the revisions you reviewed, and limit attempts per session. - [Connect external tools](https://smoothie.dev/docs/framework/mcp-cli/upstreams): Let your agent use existing MCP tools through Smoothie, with a reviewed selection and per-session call limits. - [Commands and structured output](https://smoothie.dev/docs/framework/mcp-cli/cli-reference): Look up commands, execution flags, JSON results, MCP formats, and exit codes. ## Skills - [Framework skills](https://smoothie.dev/docs/framework/skills): Use release-matched instructions for coding agents to set up, develop, update, and deploy Framework applications. - [Installation and agent-host setup](https://smoothie.dev/docs/framework/skills/installation): Plan and install retained Framework skills for Codex or Claude Code, then confirm discovery in the chosen host. - [Skills list](https://smoothie.dev/docs/framework/skills/list): Find the currently distributed Framework skills by concern; the planned 0.1.0 skill inventory is not final. - [Framework usage](https://smoothie.dev/docs/framework/skills/framework-usage): Guide an agent through release selection, Starter adoption, package updates, and customer source customization. - [Design](https://smoothie.dev/docs/framework/skills/design): Define UI intent, design-system constraints, and interaction evidence for agent-assisted Whisk authoring. - [Development](https://smoothie.dev/docs/framework/skills/development): Scope feature work, debugging, and verification for coding agents while preserving application ownership and native tools. - [Delivery](https://smoothie.dev/docs/framework/skills/deployment): Set the authority, artifact, and evidence boundaries for agent-assisted deployment and operational checks. - [Skill versions, updates, and conflicts](https://smoothie.dev/docs/framework/skills/versions): Keep installed instructions matched to retained packages without overwriting customer edits or confusing receipts with execution permission. - [Troubleshoot Framework skills](https://smoothie.dev/docs/framework/skills/troubleshooting): Distinguish CLI installation, retained skill inputs, host discovery, and agent execution failures. ## Recipes - [Recipes](https://smoothie.dev/docs/framework/recipes): Explore three editable Starters and understand what you take ownership of after adoption. - [Smoothie Starter](https://smoothie.dev/docs/framework/recipes/smoothie-starter): Build on a client-rendered Octane/Whisk interface, native routing and a typed HTTP service. - [Interactive Agent](https://smoothie.dev/docs/framework/recipes/interactive-agent): Adapt a local scratchpad assistant with streaming, approval-gated note writes and SQLite conversation history. - [Durable Worker](https://smoothie.dev/docs/framework/recipes/durable-worker): Adapt Redis-backed background work with Postgres Run records, restart recovery and explicit effect idempotency. - [Adoption and customization](https://smoothie.dev/docs/framework/recipes/adapt): Own the copied application source, preserve its adoption baseline and keep Framework updates separate. ## whisk/ui - [whisk/ui overview](https://smoothie.dev/docs/framework/whisk-ui): Build accessible, themed Framework interfaces with shared foundations, styling props, and composable components. - [Get started with whisk/ui](https://smoothie.dev/docs/framework/whisk-ui/get-started): Install whisk/ui, choose a runtime adapter, provide a theme, and render your first component. - [Get started with whisk/ui and Octane](https://smoothie.dev/docs/framework/whisk-ui/get-started/octane): Install the whisk/ui Octane adapter, load the shared stylesheet, provide a theme, and render a component. - [Get started with whisk/ui and React](https://smoothie.dev/docs/framework/whisk-ui/get-started/react): Install the whisk/ui React adapter, load the shared stylesheet, provide a theme, and render a component. - [whisk/ui foundations](https://smoothie.dev/docs/framework/whisk-ui/foundations): Learn the visual vocabulary shared by whisk/ui components before choosing a component. - [Colors](https://smoothie.dev/docs/framework/whisk-ui/foundations/colors): Explore the list of available default whisk/ui color families. - [Typography](https://smoothie.dev/docs/framework/whisk-ui/foundations/typography): Use the shared type scale, font weights, line heights, tracking, and text styles to create a clear hierarchy. - [Spacing](https://smoothie.dev/docs/framework/whisk-ui/foundations/spacing): Build a consistent layout rhythm with the shared spacing scale. - [Sizes](https://smoothie.dev/docs/framework/whisk-ui/foundations/sizes): Choose predictable dimensions with numeric, named, fractional, and viewport size tokens. - [Borders and radii](https://smoothie.dev/docs/framework/whisk-ui/foundations/surfaces): Use border and radius scales to make surfaces legible without one-off CSS values. - [Shadows](https://smoothie.dev/docs/framework/whisk-ui/foundations/shadows): Use the shared shadow scale to express elevation without copying raw box-shadow values. - [Z-index and layering](https://smoothie.dev/docs/framework/whisk-ui/foundations/z-index): Place menus, overlays, and composed surfaces on predictable layers with named z-index tokens. - [Responsive breakpoints](https://smoothie.dev/docs/framework/whisk-ui/foundations/responsive): Adapt layout and visibility with breakpoint-aware values instead of duplicating component markup. - [Style whisk/ui](https://smoothie.dev/docs/framework/whisk-ui/styling): Apply the foundation tokens through component props, responsive values, interaction states, and recipes. - [Style props](https://smoothie.dev/docs/framework/whisk-ui/styling/style-props): Use component props for layout, color, typography, borders, and visual states. - [Responsive styles](https://smoothie.dev/docs/framework/whisk-ui/styling/responsive): Describe how a component changes at breakpoints with sparse responsive values. - [Interaction and pseudo props](https://smoothie.dev/docs/framework/whisk-ui/styling/interactions): Style hover, focus, active, and disabled states with the same token language as the base component. - [Focus styles](https://smoothie.dev/docs/framework/whisk-ui/styling/focus-styles): Make keyboard focus visible and consistent across custom interactive surfaces. - [Layer styles](https://smoothie.dev/docs/framework/whisk-ui/styling/layer-styles): Reuse a surface treatment made from background, border, radius, shadow, and opacity tokens. - [Component recipes](https://smoothie.dev/docs/framework/whisk-ui/styling/recipes): Create reusable product patterns on top of whisk/ui without losing theme and variant consistency. - [Custom CSS](https://smoothie.dev/docs/framework/whisk-ui/styling/css): Use application CSS only for integration boundaries that Whisk/UI utility props and recipes do not cover. - [Component catalog](https://smoothie.dev/docs/framework/whisk-ui/components): Browse whisk/ui by purpose, then open a component page for examples, props, and accessibility notes. - [Box](https://smoothie.dev/docs/framework/whisk-ui/components/box): Wrap content with semantic HTML and shared utility props. - [Flex](https://smoothie.dev/docs/framework/whisk-ui/components/flex): Arrange content with direct flex layout controls. - [Stack](https://smoothie.dev/docs/framework/whisk-ui/components/stack): Arrange related content with a consistent gap. - [StackRow](https://smoothie.dev/docs/framework/whisk-ui/components/stack-row): Arrange related content horizontally. - [StackCol](https://smoothie.dev/docs/framework/whisk-ui/components/stack-col): Arrange related content vertically. - [Grid](https://smoothie.dev/docs/framework/whisk-ui/components/grid): Create responsive two-dimensional layouts. - [GridItem](https://smoothie.dev/docs/framework/whisk-ui/components/grid-item): Place and span an item inside Grid. - [Spacer](https://smoothie.dev/docs/framework/whisk-ui/components/spacer): Distribute space between flex children. - [Divider](https://smoothie.dev/docs/framework/whisk-ui/components/divider): Separate related content with a theme-aware rule. - [ScrollArea](https://smoothie.dev/docs/framework/whisk-ui/components/scroll-area): Contain overflow while preserving an accessible scroll region. - [Text](https://smoothie.dev/docs/framework/whisk-ui/components/text): Render readable body text with shared typography tokens. - [Heading](https://smoothie.dev/docs/framework/whisk-ui/components/heading): Create a semantic heading with an independent visual style. - [Code](https://smoothie.dev/docs/framework/whisk-ui/components/code): Show a short inline code fragment. - [CodeBlock](https://smoothie.dev/docs/framework/whisk-ui/components/code-block): Show multi-line source, commands, and output in a readable surface. - [Link](https://smoothie.dev/docs/framework/whisk-ui/components/link): Navigate to another resource with accessible link semantics. - [Markdown](https://smoothie.dev/docs/framework/whisk-ui/components/markdown): Render read-only Markdown with Whisk/UI presentation rules. - [Field](https://smoothie.dev/docs/framework/whisk-ui/components/field): Compose a label, control, help text, and validation message. - [Label](https://smoothie.dev/docs/framework/whisk-ui/components/label): Associate visible text with a form control. - [TextInput](https://smoothie.dev/docs/framework/whisk-ui/components/text-input): Collect a single-line value. - [Textarea](https://smoothie.dev/docs/framework/whisk-ui/components/textarea): Collect a longer text value. - [InputGroup](https://smoothie.dev/docs/framework/whisk-ui/components/input-group): Add contextual controls and text around an input. Status: beta. - [Select](https://smoothie.dev/docs/framework/whisk-ui/components/select): Choose one option from a labelled list. - [Combobox](https://smoothie.dev/docs/framework/whisk-ui/components/combobox): Search and choose from a larger option set. - [Checkbox](https://smoothie.dev/docs/framework/whisk-ui/components/checkbox): Turn one independent option on or off. - [Radio](https://smoothie.dev/docs/framework/whisk-ui/components/radio): Choose one option from a related set. - [Switch](https://smoothie.dev/docs/framework/whisk-ui/components/switch): Turn a setting on or off. - [SegmentedControl](https://smoothie.dev/docs/framework/whisk-ui/components/segmented-control): Choose one visible option from a compact set. - [Button](https://smoothie.dev/docs/framework/whisk-ui/components/button): Trigger a clear user action. - [ButtonGroup](https://smoothie.dev/docs/framework/whisk-ui/components/button-group): Lay out related actions as a group. - [Breadcrumb](https://smoothie.dev/docs/framework/whisk-ui/components/breadcrumb): Show the current location in a hierarchy. - [Tabs](https://smoothie.dev/docs/framework/whisk-ui/components/navigation/tabs): Switch between related views in one context. - [Accordion](https://smoothie.dev/docs/framework/whisk-ui/components/accordion): Reveal and hide related sections of content. - [NavTree](https://smoothie.dev/docs/framework/whisk-ui/components/navigation/nav-tree): Navigate a nested hierarchy of pages or resources. - [DropdownMenu](https://smoothie.dev/docs/framework/whisk-ui/components/dropdown-menu): Offer contextual actions from a trigger. - [Flyout](https://smoothie.dev/docs/framework/whisk-ui/components/flyout): Position application-owned contextual content at an anchor. - [Alert](https://smoothie.dev/docs/framework/whisk-ui/components/feedback/alert): Communicate an important status in context. - [Spinner](https://smoothie.dev/docs/framework/whisk-ui/components/spinner): Show that a local operation is in progress. - [Progress](https://smoothie.dev/docs/framework/whisk-ui/components/progress): Show known progress toward completion. - [Toast](https://smoothie.dev/docs/framework/whisk-ui/components/overlay/toast): Provide short-lived feedback after an action. - [Table](https://smoothie.dev/docs/framework/whisk-ui/components/table): Present structured data with semantic table markup. - [DataTable](https://smoothie.dev/docs/framework/whisk-ui/components/data-table): Render application data with the portable data-table contract. - [Chart](https://smoothie.dev/docs/framework/whisk-ui/components/chart): Render supported data visualizations from structured data. - [Modal](https://smoothie.dev/docs/framework/whisk-ui/components/overlay/modal): Focus attention on a task or decision. - [Composer](https://smoothie.dev/docs/framework/whisk-ui/components/composer): Collect a user message and its related actions. - [StreamingText](https://smoothie.dev/docs/framework/whisk-ui/components/streaming-text): Render generated text as it arrives. - [MessagePair](https://smoothie.dev/docs/framework/whisk-ui/components/message-pair): Present a user message and assistant response together. - [ToolCall](https://smoothie.dev/docs/framework/whisk-ui/components/tool-call): Show an application-owned tool invocation and its result. - [Generative UI primitives](https://smoothie.dev/docs/framework/whisk-ui/components/generative-ui-primitives): Compose approved primitives in bounded generated interfaces. - [Theming overview](https://smoothie.dev/docs/framework/whisk-ui/theming): Understand how the default whisk/ui theme, token vocabulary, and application overrides fit together. - [Theme model](https://smoothie.dev/docs/framework/whisk-ui/theming/model): Understand how the default theme, token vocabulary, and application-owned customization fit together. - [Design tokens](https://smoothie.dev/docs/framework/whisk-ui/theming/tokens): Define and use atomic visual decisions such as colors, spacing, fonts, radii, shadows, and breakpoints. - [Semantic tokens](https://smoothie.dev/docs/framework/whisk-ui/theming/semantic-tokens): Use names that describe interface meaning so the same component can adapt across themes and color modes. - [Light and dark modes](https://smoothie.dev/docs/framework/whisk-ui/theming/modes): Keep component code stable while themes provide appropriate values for light and dark color modes. - [Theme provider](https://smoothie.dev/docs/framework/whisk-ui/theming/provider): Provide one theme boundary so components share color mode, tokens, typography, and recipes. - [Custom themes](https://smoothie.dev/docs/framework/whisk-ui/theming/custom-themes): Extend the shared whisk/ui contract with application-owned tokens and component recipes without changing defaults. - [CSS variables and global CSS](https://smoothie.dev/docs/framework/whisk-ui/theming/css): Understand the theme CSS boundary, global rules, and the small set of cases where custom CSS is justified. - [whisk/ui adapters](https://smoothie.dev/docs/framework/whisk-ui/adapters): Choose the renderer adapter that connects whisk/ui semantics to your application runtime. - [whisk/ui adapter model](https://smoothie.dev/docs/framework/whisk-ui/adapters/model): Understand the shared component contract and the runtime boundary each adapter owns. - [whisk/ui with Octane](https://smoothie.dev/docs/framework/whisk-ui/adapters/octane): Use the Octane adapter to render whisk/ui components in an Octane application. - [whisk/ui with React](https://smoothie.dev/docs/framework/whisk-ui/adapters/react): Use the React adapter to render whisk/ui components in a React application. - [Generated UI with whisk/ui](https://smoothie.dev/docs/framework/whisk-ui/generated-ui): Render bounded generated interfaces with the same component, theme, accessibility, and host-ownership rules as hand-authored UI. - [Generated UI overview](https://smoothie.dev/docs/framework/whisk-ui/generated-ui/overview): Render bounded generated interfaces with whisk/ui while the host application owns data, actions, and permissions. - [Generated UI renderer setup](https://smoothie.dev/docs/framework/whisk-ui/generated-ui/renderer): Connect the generated UI renderer to a whisk/ui adapter while keeping application data and actions outside the renderer. - [Generated UI catalog integration](https://smoothie.dev/docs/framework/whisk-ui/generated-ui/catalogs): Connect an approved component catalog to the generated UI renderer and validate every generated structure. - [Generated UI actions and host ownership](https://smoothie.dev/docs/framework/whisk-ui/generated-ui/actions): Keep generated UI declarative while the host application owns side effects, permissions, data, and approvals. - [Generated UI security and validation](https://smoothie.dev/docs/framework/whisk-ui/generated-ui/security): Treat generated content as untrusted input and enforce catalog, data, action, and accessibility validation at the host boundary. - [whisk/ui accessibility foundations](https://smoothie.dev/docs/framework/whisk-ui/foundations/accessibility): Use semantic elements, labels, focus behavior, and readable contrast as part of the component contract. - [Integrate whisk/ui](https://smoothie.dev/docs/framework/whisk-ui/integrate): Install whisk/ui, provide its theme, and connect it to the application host without hiding the runtime boundary. ## Reference - [Whisk/UI API](https://smoothie.dev/docs/framework/whisk-ui/api): Look up public whisk/ui exports, shared props, and composition conventions. - [Configuration reference](https://smoothie.dev/docs/framework/reference/configuration): Look up schema-1 project/workspace fields and the native tools or capability APIs that own other configuration. - [Errors and events](https://smoothie.dev/docs/framework/reference/errors-events): Find capability-owned error and event contracts without confusing SDK results, transport messages and CLI diagnostics. - [Compatibility matrix](https://smoothie.dev/docs/framework/0.1): See the exact language, capability, package, contract, and availability boundary of the first Framework profile. - [Release notes](https://smoothie.dev/docs/framework/reference/release-notes): Read dated CLI and private Framework changes, their separate identities and the applicable update guidance.