# Models, libraries, and skills

Choose how Tenor approaches your interface.

Source: https://tenor.design/docs/reference/models-and-libraries

## Use Tenor Auto

Tenor Auto selects a model for the request. Open the model picker to choose an available alternative when you have a specific reason to compare.

The picker reflects the models available to your account. Tenor will let you know when your included usage is running low.

## Choose a foundation

New text-only UI interfaces use a bundled shadcn foundation. Screenshot and Figma work follow the supplied visual reference; edits preserve the existing component’s foundation.

Use Settings → Libraries to manage supported options. Name a library in your request when it is a requirement.

## Guide the design approach

Settings → Skills lets you manage supported design guidance. A skill helps shape the approach; it does not replace explaining the interface’s purpose and constraints.

Keep guidance relevant. If instructions conflict, clarify which direction should govern the next result.

## Compare results

Try the same bounded task with another model when you want to compare approaches. Judge behavior, code, and reference fidelity as well as the first impression.

## Next steps

- [Create from a prompt](https://tenor.design/docs/create/from-a-prompt) — Describe the interface, its content, and what it should do.
- [Troubleshooting and limits](https://tenor.design/docs/reference/limits) — Find the next useful step when something does not work as expected.