Wensity

Find Wensity components, UI primitives, and blocks by need, name, slug, category, tag, tier, dependency, or similarity. Call first for any find/which/show-me request. Show each result's accessLabel (Free, Pro, Needs Pro) next to its name; if the user picks a Needs Pro item, say so and offer the closest Free result. Never recreate a Needs Pro item.

Public metadata for one Wensity component or block: description, usage snippet, props, npm dependencies, install command, detail and live-preview links, and whether this machine can install it. Never returns source. Use usage verbatim and props to explain configuration; link detailUrl for examples.

Whether this machine has a Wensity API token, its plan, and whether Pro items can be installed. When not connected, relay howToConnect.steps so the user signs in from their own terminal. Never ask for or accept a token in the conversation.

Describe the local project so you know whether and how Wensity can install into it: root, framework, language, package manager, aliases, Tailwind CSS file, cn helper, and Wensity files already installed. Local only: no network, never returns file contents. Call once at the start of an install conversation, and again afterwards to confirm state.

Plan installing a Wensity component or block, writing nothing: every file, dependency, and conflict. Call before wensity_install and show the user files, dependencies (toInstall, command, caveat), and conflicts. For a Needs Pro item, say so first and offer a Free one; never recreate it. Never returns source. The planToken binds one install to this plan; it is not proof of approval.

Install exactly one plan from wensity_plan_install, by its planToken alone. Only call after showing the user that plan. Re-checks preconditions and access, writes files with rollback on failure, then runs the planned package-manager command. Reports file and dependency outcomes separately. A repeated call changes nothing and returns the recorded result with replayed: true. Never returns source.