Opt ui install
Agent skills for the reopt ecosystem — CLI workflows, Brandapp SDK install/review, and @reopt-ai/opt-* component package setup. Installs into Claude Code, Cursor, Codex, Cline, Gemini CLI, and more via skills.sh.
npx -y skills add reopt-ai/reopt-skills --skill opt-ui-installAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 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 or upgrade @reopt-ai/opt-ui in a consumer project, or add a Surface page template. Auto-branches by current install state. Triggers on "opt-ui install", "opt-ui init", "opt-ui setup", "opt-ui upgrade", "opt-ui update", "opt-ui surface", "opt-cli surface add", "add Surface".
SKILL.md
4.9 KB, as published. Nobody here has run it
opt-ui Install
This is NOT the opt-ui you know. Read
node_modules/@reopt-ai/opt-ui/dist/docs/before writing code.
When to apply
Consumer project depends on @reopt-ai/opt-ui. Triggers: "install", "init", "setup", "upgrade", "update", "surface", "add Surface". Never use packages/opt-ui/src/... paths in consumer code — monorepo-internal.
Invocation
/opt-ui-install # Auto-branch (missing → init, installed → upgrade)
/opt-ui-install surface <name> # Add a Surface page template
/opt-ui-install --upgrade # Explicit upgrade
/opt-ui-install --check # Analyze only (no edits)
/opt-ui-install --target=1.2.0 # Pin a specific version
/opt-ui-install --dry-run # Analyze only
Step 1 — Pin agent rules into AGENTS.md / CLAUDE.md
Source: the module's own agent-rules file once it ships one (@reopt-ai/opt-ui does not, as of 1.5.0). Fallback: agent-rules.md bundled with this skill. Wrap content between:
<!-- BEGIN:reopt/opt-ui-agent-rules -->
…content from source…
<!-- END:reopt/opt-ui-agent-rules -->
Idempotent: replace only between markers. Never touch outside.
Step 2 — Consumer-side setup (this skill owns; docs cannot)
-
Public npm registry — no token or scoped
.npmrcentry is required. Inspect the project.npmrcandnpm config get @reopt-ai:registry; if the scope still resolves to GitHub Packages, remove only the legacy project entry@reopt-ai:registry=https://npm.pkg.github.com. Preserve unrelated registry/auth settings, and ask before changing user/global npm config. -
Prereqs — Node 18+, React 19+, Tailwind CSS v4. bun or npm.
-
App-shell wiring — properties of the consumer app:
- Tailwind CSS v4:
@import "tailwindcss";then@import "@reopt-ai/opt-ui/tailwind.css";in the root stylesheet (plus the@sourcedirective — see getting-started). <OptThemeProvider>at the app root (Next.js:app/layout.tsxoutermost).- Surface CLI:
npx @reopt-ai/opt-cli surface add <slug>for page templates (Surfaces live in the internalopt-ui-surfacepackage — not installed directly).opt surface diff(opt-cli 1.2+) bulk-checks every installed Surface against the bundled registry (--json/--exit-codefor CI). - Component lookup:
npx @reopt-ai/opt-cli component [name](opt-cli 1.2+) prints bundled opt-ui / opt-charts metadata, props, and example code.
- Tailwind CSS v4:
-
Doctor —
npx @reopt-ai/opt-cli doctorruns the environment audit (unified design CLI; there is noopt-ui-cli). opt-cli 1.2+ lists@reopt-ai/opt-shell@^1.0.0as a peer — install it ifoptwarns about a missing peer.
Step 3 — Route to module docs
Real layout is a numeric-prefixed tree under dist/docs/; start at index.md.
| Task signal | Read |
|---|---|
| Start here — doc index | dist/docs/index.md |
| Getting started / install / upgrade | dist/docs/01-getting-started.md |
| Component API & props (core / visuals / shells / surfaces) | dist/docs/02-components/ |
| Surface components | dist/docs/02-components/04-surfaces.md |
| Recipes (forms, dashboards, layouts) | dist/docs/03-recipes/ |
| Theme, styling, design tokens | dist/docs/04-theming.md |
| Breaking changes by version | dist/docs/05-migration/01-breaking-changes.md |
| FormStore migration | dist/docs/05-migration/02-formstore.md |
| Troubleshooting | dist/docs/06-troubleshooting.md |
Pipeline (auto-branch)
| # | Step | Init | Upgrade | Surface |
|---|---|---|---|---|
| 1 | Detect current state | ✓ | ✓ | ✓ |
| 2 | Public-registry preflight + legacy override cleanup | ✓ | ✓ | ✓ |
| 3 | Install / update package | ✓ | ✓ | – |
| 4 | CSS import check | ✓ | ✓ | – |
| 5 | OptThemeProvider setup | ✓ | – | – |
| 6 | Breaking-change edits | – | ✓ | – |
| 7 | Deprecated fixes (opt-in) | – | ✓ | – |
| 8 | Surface CLI workflow | opt | opt | ✓ |
| 9 | Doctor (environment audit) | ✓ | ✓ | ✓ |
| 10 | Summary + rollback path | ✓ | ✓ | ✓ |
Detailed step procedures live in module docs — start at dist/docs/index.md, then dist/docs/01-getting-started.md. Read before acting.
Safety
- Never upgrade without an impact scan (run
--checkfirst). - Confirm before overwriting existing files.
- Apply breaking-change edits in logical groups — never bulk-apply across categories.
- Do not finish until
tsc --noEmitpasses. - Always provide a rollback path (previous version pin + git revert range).
Verify
npx @reopt-ai/opt-cli doctorpasses (or explained skips).npx tsc --noEmitpasses.- App renders without OptThemeProvider warnings.