Catalog

The Catalog category is the loop a build runs before it writes any code: catalog_search → catalog_install, with catalog_list_installed telling an edit call which version a project already has.

Search before you write a section, form, auth flow, payment flow, or onchain widget. Only write from scratch when nothing in the catalog fits, and say so in your summary.

The three toolsCopy Anchor Link

• catalog_search — matches query against each item's title, description and tags, and ANDs the kind, templateId and tag filters together. Results are the caller's own private items plus every public one, ordered by install count then recency, with a short usage note each. A search that matches nothing returns an empty list rather than an error.
• catalog_install — writes every file the item's manifest declares into the project's sandbox, then records the install against the project, so a later version updates rather than duplicates. It returns the files it wrote and the dependencies the item declares. It does not run your package manager — add any returned dependencies yourself.
• catalog_list_installed — what a project has installed, most recent first, with the version each is pinned to and the params it was installed with. Read it before you edit an installed block by hand.

What an item isCopy Anchor Link

An item's kind is one of template, block, contract, hook, or skill. block is the installable code-snippet kind; template is a whole starter project. The template ids the catalog knows are landing and webapp, declared once in packages/catalog.

OwnershipCopy Anchor Link

A private item belongs to its owner and to nobody else. A search never returns another user's private item, and installing one answers with the same not-found a missing item does. A project that is not the caller's is never reached, with a not-found that does not say which of the two it was.