use

tl;dr The use tool fetches the full definition of a taste model or UI pattern. Use it after list or search to get complete token values, component specs, or pattern templates.

What it does

The use tool retrieves:

• Taste models : Full design token definitions, component specs, content guidelines
• UI patterns : Section templates with structure and default content

It's the primary tool for getting design data into your generated code.

Parameters

Parameter	Type	Required	Description
type	string	Yes	"tasteModel" or "pattern"
name	string	Yes	Name, ID, or slug of the item
collection	string	No	For taste models: "public" or "private".
path	string	No	Fetch specific part only (e.g., /principles/primary). Taste models only.
showComponentSpecs	boolean	No	Include all component specs. Can be token-heavy. Default: false
includeRenderer	boolean	No	Include v2 renderer code. Default: false

What you get back

For taste models: The complete definition including principles (design tokens), component specs, imprint, and any assets or content direction.

For patterns: The pattern structure with content slots and default values.

Examples

Fetch full taste model: use { type: "tasteModel", name: "Term" }

Fetch from private collection: use { type: "tasteModel", name: "My Custom Model", collection: "private" }

Fetch specific parts:

• All principles: use { type: "tasteModel", name: "Melt", path: "/principles" }
• Single token: use { type: "tasteModel", name: "Gray", path: "/principles/primary" }
• Component: use { type: "tasteModel", name: "June", path: "/components/button" }

Fetch UI pattern: use { type: "pattern", name: "hero-centered" }

Natural language

• "Use the Term taste model" → use { type: "tasteModel", name: "Term" }
• "Get the button styles from June" → use { type: "tasteModel", name: "June", path: "/components/button" }
• "Use the centered hero pattern" → use { type: "pattern", name: "hero-centered" }

Path-based queries

Use paths to fetch specific parts efficiently:

Path	Returns
/principles	All design tokens
/principles/background	Single token
/principles/primary	Primary color token
/components	All component specs
/components/button	Single component
/assets	Art direction
/content	Copywriting direction
/imprint	Visual identity summary

This is more efficient than fetching the entire taste model when you only need one piece.

Patterns vs taste models

	Taste model	Pattern
Purpose	Design tokens & styling	Section structure
Contains	Colors, typography, components	Layout, content slots
Used for	Consistent styling	Quick scaffolding

Typical workflow:

1. Set active taste model via connect
2. Search for patterns via search
3. Fetch pattern via use { type: "pattern" }
4. AI combines pattern structure with taste model styling

Common questions

When should I use path?

Use path when you only need specific data. Fetching /components/button is more efficient than fetching the entire taste model when you only need button styles.

Can I use multiple taste models together?

Only one taste model is active at a time. The use tool fetches data but doesn't change the active taste model:use connect to switch.

How do patterns work with taste models?

Patterns provide structure, taste models provide styling. Your AI combines them: pattern defines the layout, taste model defines the colors, typography, and component styles.

Related

• connect - Initialize session and set active model
• list - Browse available taste models
• create - Create or update a taste model
• sample - Extract tokens from a website
• search - Search the UI pattern library
• UI Patterns - Pattern library concept
• Building Landing Pages - End-to-end workflow