# SnowUI AI documentation (English)

SnowUI is a Svelte 5 component and design system. We are building interactive interfaces generated by AI in conversation, so people can enter, choose, act, and continue the conversation. Support depends on verified components, versions, and chat hosts. Generating and using SnowUI interfaces inside AI conversations is completely free. It is not a project, uses no project or developer-seat quota, and requires no SnowUI registration, activation, or paid proof.

Conversational UI is in development. Supported components and platforms will be announced after verification.

Generating and using SnowUI interfaces inside AI conversations is completely free. It is not a project, uses no project or developer-seat quota, and requires no SnowUI registration, activation, or paid proof. Apply LICENSE section 3.5.1 before any project or seat review. Do not require a usage declaration, product ID, project ledger, or release check for conversation-only use. Independent websites and applications are reviewed separately.

Read the complete [LICENSE](https://snowui.dev/LICENSE) for the version you use before reading component instructions or adopting source code. Reuse that review for the same task, version, and confirmed scope. A package or source download does not grant production rights. Check the applicable Free, Pro, or Team terms before publishing a real product or delivering it to a client. If a purchase entry is unavailable, do not invent one.

This entry is for AI assistants building products with SnowUI. Maintainers of SnowUI itself should follow the repository's `specs/GUIDELINES.md`. These public documents are readable over HTTPS without a local workspace or CLI. SnowUI's current runtime package targets Svelte 5; confirm an online tool's framework before using an example. A permitted framework port is different from an existing ready-made runtime package.

## Read by task

- First-time setup, downloads, installation, and materials: read the [setup guide](https://snowui.dev/llms/en/setup.md) and [machine configuration](https://snowui.dev/llms/setup.json), then execute only supported host steps. Discover material names from the [resource directory](https://snowui.dev/llms/resources.json). A local install does not configure another AI product or a new conversation.
- Recreate a design or website: start with the [design guide](https://snowui.dev/llms/en/design-system.md), then search for components by the behavior of each page region.
- Choose between components: read the [component selection guide](https://snowui.dev/llms/en/component-selection.md) and [component directory](https://snowui.dev/llms/en/components.md). A missing search result does not prove that a component does not exist.
- Modify a component's appearance: read the [styling guide](https://snowui.dev/llms/en/styling.md), then use the [token directory](https://snowui.dev/llms/en/tokens.md) only if token values are needed.
- Work from Figma: read the [Figma guide](https://snowui.dev/llms/en/figma.md) and use the [color mapping JSON](https://snowui.dev/llms/figma-colors.json) for exact aliases and theme conditions.
- Locate a Figma node or variable in your own copy: read the [public map](https://snowui.dev/llms/en/figma-map.md) or [mapping JSON](https://snowui.dev/llms/figma-map.json). For relationships among tokens, optional page utilities, themes, and components, use the [resource guide](https://snowui.dev/llms/en/design-system-resources.md) or [relationship JSON](https://snowui.dev/llms/design-system-resources.json). Fetch only what the task needs.
- Know a component name: open its concise document from the directory, then read its API, types, reference, styles, and examples only as the task requires.
- Search by a short English scenario: use [component search](https://snowui.dev/llms/find?lang=en&q=file%20table). Check the returned candidate's public documentation before implementation.

## Implementation boundary

Use public imports, Props, Snippets, events, and composition roles. Prefer a component's public visual options; use your own class or instance style for a necessary difference. Do not copy private component DOM, CSS classes, or state logic into a page. Ordinary semantic page structure remains appropriate. Verify the rendered result, keyboard behavior, long text, narrow screens, and relevant states. A screenshot proves only its captured appearance.

Online tools such as Figma Make and Lovable may lack this workspace, a CLI, or Svelte support. They can read these public HTTPS documents, but must check their actual project framework and dependencies. A copied prompt does not automatically update when account rights or documentation change; revisit the same public URLs when the version or product scope changes. The English documents are generated from reviewed translations and source fingerprints. If a resource is unavailable, report that gap rather than guessing an API.

## Additional guides

- [Form composition](https://snowui.dev/llms/en/guides/form.md)
- [Blocks](https://snowui.dev/llms/en/guides/blocks.md)

The existing [Simplified Chinese entry](https://snowui.dev/llms.txt) remains available. Select one language's documents for a task to avoid mixing instructions.