Recipes
Compositions, not registry items
Recipes show how the registry components fit together. They are documentation only: loseta add never installs a recipe, and the markup uses the same public classes and state contract as the component pages.
FormField layout, native validation, choices and actions.Data tableA table with selection, status badges and row actions.Date pickerA calendar composed with a popover and a trigger.TypographyThe type scale, prose defaults and the reading rules.
Why recipes are not items
A registry item has a stable root selector, a documented anatomy and one style file per declared style. A recipe has consumer data, column definitions or a date library; shipping it as CSS would either hard-code a data model or ship behavior. Recipes stay in the docs so the registry can remain CSS-only.
Remaining shadcn names
Two shadcn names are not visual components and do not become registry items:
- Direction is the native
dirattribute and logical properties. See Direction in Theming. - Sonner is a toast library. The Toastcomponent documents it as a compatibility note; add the library in consumer code.
Typography is a guidelines page because the registry already styles prose through the base layer. There is no separate typography class to install.