Add component
Official IntelliHelper UI agent plugin — Liquid Glass React components via MCP, skills, and slash commands
npx -y skills add IntelliHelper/agent-skills --skill add-componentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Install IntelliHelper UI components into a project correctly: init components.json, resolve dependencies, run CLI add, verify imports, and audit. Use when the user wants to add, install, scaffold, update, or diff IntelliHelper/shadcn-style components, fix missing components.json, or wire the registry. Triggers: "add button", "install dialog", "npx @intellihelper/cli", "init components.json", "update components", "registry add".
SKILL.md
3.9 KB, as published. Nobody here has run it
Add IntelliHelper components
Goal: leave the project with installed, compiling, correctly imported components — not just a pasted snippet.
Decision tree
components.json missing?
YES → init first (non-interactive)
NO → read config (MCP get_project_config)
Know exact component names?
YES → get_component → get_add_command → CLI add
NO → search_components / list_components → then install
1. Project config
MCP: get_project_config
CLI:
npx @intellihelper/cli@latest init -y
Always prefer -y / non-interactive flags in agent shells so prompts do not hang.
Default config highlights:
- Style:
intelli-glass - Registry:
https://ui.intellihelper.in/r - UI alias:
@/components/ui - Utils alias:
@/lib/utils - CSS:
app/globals.css(adjust if project usessrc/app)
Ensure tsconfig path aliases match components.json.
2. Discover names
MCP:
search_components { "query": "dialog" }
list_components { "category": "forms" }
CLI:
npx @intellihelper/cli@latest list
Use registry slugs (button, dialog, glass-bar) — not React display names alone.
3. Read API before coding
MCP:
get_component { "name": "button" }
get_component { "names": ["dialog", "button"] }
get_component_examples { "name": "dialog" }
Extract: exports, variants, sizes, shapes, "use client", npm + registry deps.
4. Install (source of truth)
MCP: get_add_command with { "components": ["button", "dialog"] }
Then run the returned command in the project shell.
CLI direct:
npx @intellihelper/cli@latest add button dialog card -y
Useful flags:
| Flag | Purpose |
|---|---|
-y, --yes | Skip confirmations (agent default) |
-o, --overwrite | Overwrite local files |
--dry-run | Preview only |
The CLI resolves registry dependencies (e.g. utils) and installs npm dependencies.
5. Update / diff
npx @intellihelper/cli@latest update -y
npx @intellihelper/cli@latest update button --skip-modified
npx @intellihelper/cli@latest diff button
npx @intellihelper/cli@latest list --installed
Never blindly overwrite user-customized files without checking diff / modified state.
6. Audit
MCP: get_audit_checklist
Verify at minimum:
-
components.jsonpresent; aliases match tsconfig - Imports use UI alias (
@/components/ui/...) - Named/default imports match exports
- Registry + npm deps installed
- Theme/token CSS loaded
- Chrome vs content variants chosen deliberately
- Client components marked
"use client"when needed - No TS/lint errors
7. Compose
After install, import from local paths:
import { Button } from "@/components/ui/button"
Do not import from @intelli/ui in consumer apps — that is monorepo-internal.
For layout recipes, use skill compose-ui. For glass rules, use skill liquid-glass.
Failure modes & fixes
| Symptom | Fix |
|---|---|
| Interactive CLI hanging | Re-run with -y |
Module not found @/lib/utils | add utils / re-init aliases |
| Wrong import path | Read components.json aliases |
| Missing glass styles | Check global CSS / theme setup in docs |
| Props TypeScript errors | Re-run get_component; stop inventing props |
| MCP tools missing | Plugin trust/MCP enable, or CLI fallback |