
Build React apps with Salesforce Lightning's look on shadcn/ui: find the right component, read its docs and examples, and get the command t…
Listed on
First seen 5 Nov 2026. One server, whatever directories list it: each directory listing keeps its own page and history.
2
Directories
Collected by InvokeRank
5
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data
Tools
| Tool | Description | Behaviour |
|---|---|---|
| get_component | Read one Wisty UI item to choose and compose it: its install command, examples by name, When to use, When not to use, Usage, Rules, API reference. | Read-only |
| get_example | Get one example's code for a Wisty UI item, for the project's base: a complete, working use to adapt. | Read-only |
| get_install_command | Get the steps to install one Wisty UI item: the shadcn command, and the theme and icon steps it needs. First read style and tailwind.css from the project's components.json, and whether it has a src/ folder; a project without components.json runs npx shadcn@latest init first. | Read-only |
| list_components | List every Wisty UI item by kind, with its first sentence. Primitives are shadcn's own components with the Salesforce look; components are what shadcn lacks, like lookup; blocks are finished Salesforce sections over sample data; helpers turn records into a block's props. Prefer search_components when you know the job. | Read-only |
| search_components | Find Wisty UI items by the job they do, best first. Each match gives its name, kind (primitive, component, block, helper) and description. A block is a finished section built from components and primitives over sample data, to install and edit: when the job is a whole section, start from its block, not its parts. Read a match with get_component. | Read-only |