[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AR70PYHNQDG2QAZYBGASK1":3,"skill-same:01M7AR70PYHNQDG2QAZYBGASK1":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":50},"01M7AR70PYHNQDG2QAZYBGASK1","brand-ui-migrate",null,"Bring an app that already exists onto brand-ui (@elabs-ai\u002Fcomponents-*). Use when someone wants to migrate, port, adopt or \"move to\" the design system in a codebase they already have (\"migrate this project to brand-ui\", \"we use MUI, can we switch\", \"adopt your design system in our admin app\", \"replace our components with yours\"). Profiles the repo, maps every component it finds to a brand-ui verdict, writes a phased migration plan, and then walks the phases with the user approving each one. Read-only until the plan is approved. For a brand-new app use `brand-ui-new-app`; for using components in an app already on brand-ui use `brand-ui`.","mreimitz\u002Felabs-components","mreimitz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F27810221?v=4","01M7AR5BCPZJ6V2RNWHAZTS47W","Manuel Reimitz","01M7AR5BDN5NMH80W8GCXACXXD",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmreimitz\u002Felabs-components\u002Fblob\u002Fmain\u002Fskills\u002Fbrand-ui-migrate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: brand-ui-migrate\ndescription: Bring an app that already exists onto brand-ui (@elabs-ai\u002Fcomponents-*). Use when someone wants to migrate, port, adopt or \"move to\" the design system in a codebase they already have (\"migrate this project to brand-ui\", \"we use MUI, can we switch\", \"adopt your design system in our admin app\", \"replace our components with yours\"). Profiles the repo, maps every component it finds to a brand-ui verdict, writes a phased migration plan, and then walks the phases with the user approving each one. Read-only until the plan is approved. For a brand-new app use `brand-ui-new-app`; for using components in an app already on brand-ui use `brand-ui`.\nuser-invocable: true\nargument-hint: \"[path to the project, defaults to the current directory]\"\nallowed-tools:\n  - Bash(npx @elabs-ai\u002Fcomponents-cli *)\n  - Bash(pnpm brand-ui *)\n  - Bash(npx brand-ui *)\n  - Bash(pnpm exec brand-ui *)\n---\n\n# brand-ui-migrate (brownfield adoption)\n\nMove an existing UI onto brand-ui **in reviewable steps**, never in one sweep.\nThe CLI does the deterministic analysis; you do the edits; the user approves\nevery phase. The order matters: understand → map → plan → migrate → verify.\n\n## 0 · Preconditions (check, don't assume)\n\nThe analysis commands come from the brand-ui CLI, a **public package** —\n`pnpm add -D @elabs-ai\u002Fcomponents-cli` installs anonymously, nothing to\nconfigure (see `docs\u002FCONSUMING.md` §1 and §7a). If `brand-ui` is not already\nrunnable in the project, say so and point the user at that one install command\nbefore running anything. Do not paper over a missing CLI by guessing at the\ncodebase.\n\nInside the brand-ui repository itself, use `pnpm brand-ui \u003Ccmd>`; in a consuming\nproject, `pnpm exec brand-ui \u003Ccmd>` once the CLI is installed.\n\n## 1 · Understand — change nothing\n\n```bash\nbrand-ui scan . --json > brand-ui-scan.json\nbrand-ui map brand-ui-scan.json --json > brand-ui-map.json\nbrand-ui scan . --out migration\u002F\nbrand-ui map brand-ui-scan.json --out migration\u002F\nbrand-ui audit src\u002F --json\n```\n\n`--out` is the only thing these commands write, and it only creates\n`migration\u002Frepo-profile.md`, `migration\u002Fanalysis.md` and `migration\u002Fplan.md`.\nNo source file is touched at this stage — say that out loud, so the user knows\nit is safe to run.\n\nThen **read the three documents and report back**, in the user's terms:\n\n- what the project is built on (framework, UI library, styling approach);\n- the coverage number — the share of component **usages** a direct match or a\n  prop remap already covers;\n- the verdict split, and specifically what falls into `gap`;\n- the token debt — how many raw colour, spacing and font values need replacing.\n\n## 2 · Read the verdicts honestly\n\n| Verdict     | What you do with it                                                            |\n| ----------- | ------------------------------------------------------------------------------ |\n| **direct**  | Rename plus an import change. The safe bulk of the work.                       |\n| **props**   | Same idea, different API. Apply the prop remap the analysis lists.             |\n| **compose** | No single equivalent — rebuild it from primitives. Show the composition first. |\n| **gap**     | Nothing matched. Search before you conclude — then keep theirs and record why. |\n| **drop**    | Not UI (routing, document head, language constructs). Leave it alone.          |\n\nTwo limits to state plainly rather than discover later:\n\n- the inventory is a **heuristic source scan, not an AST parse** — good enough to\n  rank work by blast radius, not a refactoring index;\n- `gap` means \"the map has no entry\", not \"no equivalent exists\". Run\n  `brand-ui search \u003Cname>` before telling the user something is missing.\n- a verdict is made per (name, **library**) — the `lib` column. A brand-ui\n  export that merely shares the name (`Grid` in charts is gridlines, `List` in\n  editor is a markdown block) is reported as a `gap` with a \"name coincidence\"\n  note, never as a direct match. Do not \"fix\" that by importing the namesake.\n\n## 3 · Plan — the strangler-fig phases\n\n`migration\u002Fplan.md` already lays these out with the actual components per phase.\nWalk them in order and **stop for approval between each**:\n\n1. **Coexistence** — install, wire the tokens stylesheet and one Tailwind\n   `@source` line per installed package, wrap the root in `ThemeProvider`. The\n   app must still build and render before anything else happens. A missing\n   `@source` renders components unstyled — verify each one. **Decide the theme\n   here**: an app that had a brand (the old library's palette, a corporate typeface) gets\n   it back as a brand-ui theme — a family from `themes\u002F\u003Cfamily>\u002F` in the\n   brand-ui repository, or one built with `brand-ui-create-theme` — registered\n   on `ThemeProvider` and added to the `@custom-variant dark (…)` line. The\n   brand never re-enters as per-component colours in a later phase.\n2. **Leaf components** — the `direct` matches, lowest blast radius first.\n3. **Composite surfaces** — the `props` remaps and the `compose` rebuilds.\n4. **App shell** — the frame itself: navigation, header, page scaffold. **Ask\n   which of the library's shells the app moves into** — flagship (recommended)\n   · dashboard · mail · double-sided, the entries under Storybook's\n   _Layout\u002FApp Shell_ — with the question, the story ids to render and the\n   block each maps to in `..\u002Fbrand-ui-new-app\u002Freference\u002Fapp-shells.md`. Show the\n   rendered shells before the person picks, then copy the chosen block in\n   (`npx shadcn add \u003Cregistry>\u002F\u003Cblock>.json` → `src\u002Fcomponents\u002F\u003Cblock>\u002F`) and\n   make the app's screens its `children` (the flagship `WorkspaceShell` takes\n   the nav, the signed-in user and the trail as props; the other three carry\n   their nav in `nav-items.ts` — rewrite it from the app's routes). **Never\n   hand-roll the frame** from `SidebarProvider` + `Sidebar` + `SidebarInset`:\n   that bare composition is the stand-in the archetype stories use, not a\n   finished shell, and it is how a migrated app ends up looking like a plain\n   rail with a one-word header. Charts and KPI tiles move into `ChartFrame` \u002F\n   `MetricCard` in the same pass, not into bare `Card`s. Any custom grid cell\n   holding a table or chart keeps `min-w-0`, or one wide child pushes the page\n   past the viewport. Record the chosen shell in `migration\u002Fplan.md`.\n5. **Theming cutover** — raw values become semantic tokens.\n6. **Remove the old library** — or document what stays and why.\n\nKeep every phase to a diff a person can actually read. Run the project's build\nand tests after each batch, not at the end.\n\n## 4 · Migrate — the rules that do not bend\n\n- **Never guess a prop.** Run `brand-ui docs \u003CName>` and use the real API. If it\n  lists anti-patterns for that component, follow them.\n- **Semantic tokens only** — `bg-background`, `text-foreground`, `border-border`.\n  Never a raw hex.\n- **Prefer composing what exists** over writing a new component.\n- **Do not force a bad fit.** A `gap` stays the user's component until they say\n  otherwise.\n- **Visual decisions run the loop.** Any choice the user can see — which shell,\n  which theme, which layout — goes through propose → preview → pick → refine, on\n  a render rather than on prose. The shell is the first of these and is never\n  skipped (`..\u002Fbrand-ui-new-app\u002Freference\u002Fapp-shells.md`). The loop and its fidelity ladder are in\n  `..\u002Fbrand-ui-new-app\u002Freference\u002Fvisual-loop.md`; there is one copy, and both\n  flows use it.\n\n## 5 · Verify — per screen, per theme\n\n- `brand-ui audit src\u002F` and fix what it reports.\n- Check every migrated screen in **every registered theme** — light, dark and\n  the brand family. A screen that only works in one theme is not migrated.\n- Report honestly: what moved, what was skipped and why, and what the user should\n  look at closely. Lead with what you did **not** verify.\n\n## What this skill does not do\n\nIt does not run an automated codemod. The transform engine is not implemented —\n`brand-ui codemod \u003Cmap.json>` emits a plan and a dry-run contract and edits no\nfiles. The edits are yours to make and the user's to review. Say that up front\nrather than implying a one-command migration.\n","# brand-ui-migrate (brownfield adoption)\n\nMove an existing UI onto brand-ui **in reviewable steps**, never in one sweep.\nThe CLI does the deterministic analysis; you do the edits; the user approves\nevery phase. The order matters: understand → map → plan → migrate → verify.\n\n## 0 · Preconditions (check, don't assume)\n\nThe analysis commands come from the brand-ui CLI, a **public package** —\n`pnpm add -D @elabs-ai\u002Fcomponents-cli` installs anonymously, nothing to\nconfigure (see `docs\u002FCONSUMING.md` §1 and §7a). If `brand-ui` is not already\nrunnable in the project, say so and point the user at that one install command\nbefore running anything. Do not paper over a missing CLI by guessing at the\ncodebase.\n\nInside the brand-ui repository itself, use `pnpm brand-ui \u003Ccmd>`; in a consuming\nproject, `pnpm exec brand-ui \u003Ccmd>` once the CLI is installed.\n\n## 1 · Understand — change nothing\n\n```bash\nbrand-ui scan . --json > brand-ui-scan.json\nbrand-ui map brand-ui-scan.json --json > brand-ui-map.json\nbrand-ui scan . --out migration\u002F\nbrand-ui map brand-ui-scan.json --out migration\u002F\nbrand-ui audit src\u002F --json\n```\n\n`--out` is the only thing these commands write, and it only creates\n`migration\u002Frepo-profile.md`, `migration\u002Fanalysis.md` and `migration\u002Fplan.md`.\nNo source file is touched at this stage — say that out loud, so the user knows\nit is safe to run.\n\nThen **read the three documents and report back**, in the user's terms:\n\n- what the project is built on (framework, UI library, styling approach);\n- the coverage number — the share of component **usages** a direct match or a\n  prop remap already covers;\n- the verdict split, and specifically what falls into `gap`;\n- the token debt — how many raw colour, spacing and font values need replacing.\n\n## 2 · Read the verdicts honestly\n\n| Verdict     | What you do with it                                                            |\n| ----------- | ------------------------------------------------------------------------------ |\n| **direct**  | Rename plus an import change. The safe bulk of the work.                       |\n| **props**   | Same idea, different API. Apply the prop remap the analysis lists.             |\n| **compose** | No single equivalent — rebuild it from primitives. Show the composition first. |\n| **gap**     | Nothing matched. Search before you conclude — then keep theirs and record why. |\n| **drop**    | Not UI (routing, document head, language constructs). Leave it alone.          |\n\nTwo limits to state plainly rather than discover later:\n\n- the inventory is a **heuristic source scan, not an AST parse** — good enough to\n  rank work by blast radius, not a refactoring index;\n- `gap` means \"the map has no entry\", not \"no equivalent exists\". Run\n  `brand-ui search \u003Cname>` before telling the user something is missing.\n- a verdict is made per (name, **library**) — the `lib` column. A brand-ui\n  export that merely shares the name (`Grid` in charts is gridlines, `List` in\n  editor is a markdown block) is reported as a `gap` with a \"name coincidence\"\n  note, never as a direct match. Do not \"fix\" that by importing the namesake.\n\n## 3 · Plan — the strangler-fig phases\n\n`migration\u002Fplan.md` already lays these out with the actual components per phase.\nWalk them in order and **stop for approval between each**:\n\n1. **Coexistence** — install, wire the tokens stylesheet and one Tailwind\n   `@source` line per installed package, wrap the root in `ThemeProvider`. The\n   app must still build and render before anything else happens. A missing\n   `@source` renders components unstyled — verify each one. **Decide the theme\n   here**: an app that had a brand (the old library's palette, a corporate typeface) gets\n   it back as a brand-ui theme — a family from `themes\u002F\u003Cfamily>\u002F` in the\n   brand-ui repository, or one built with `brand-ui-create-theme` — registered\n   on `ThemeProvider` and added to the `@custom-variant dark (…)` line. The\n   brand never re-enters as per-component colours in a later phase.\n2. **Leaf components** — the `direct` matches, lowest blast radius first.\n3. **Composite surfaces** — the `props` remaps and the `compose` rebuilds.\n4. **App shell** — the frame itself: navigation, header, page scaffold. **Ask\n   which of the library's shells the app moves into** — flagship (recommended)\n   · dashboard · mail · double-sided, the entries under Storybook's\n   _Layout\u002FApp Shell_ — with the question, the story ids to render and the\n   block each maps to in `..\u002Fbrand-ui-new-app\u002Freference\u002Fapp-shells.md`. Show the\n   rendered shells before the person picks, then copy the chosen block in\n   (`npx shadcn add \u003Cregistry>\u002F\u003Cblock>.json` → `src\u002Fcomponents\u002F\u003Cblock>\u002F`) and\n   make the app's screens its `children` (the flagship `WorkspaceShell` takes\n   the nav, the signed-in user and the trail as props; the other three carry\n   their nav in `nav-items.ts` — rewrite it from the app's routes). **Never\n   hand-roll the frame** from `SidebarProvider` + `Sidebar` + `SidebarInset`:\n   that bare composition is the stand-in the archetype stories use, not a\n   finished shell, and it is how a migrated app ends up looking like a plain\n   rail with a one-word header. Charts and KPI tiles move into `ChartFrame` \u002F\n   `MetricCard` in the same pass, not into bare `Card`s. Any custom grid cell\n   holding a table or chart keeps `min-w-0`, or one wide child pushes the page\n   past the viewport. Record the chosen shell in `migration\u002Fplan.md`.\n5. **Theming cutover** — raw values become semantic tokens.\n6. **Remove the old library** — or document what stays and why.\n\nKeep every phase to a diff a person can actually read. Run the project's build\nand tests after each batch, not at the end.\n\n## 4 · Migrate — the rules that do not bend\n\n- **Never guess a prop.** Run `brand-ui docs \u003CName>` and use the real API. If it\n  lists anti-patterns for that component, follow them.\n- **Semantic tokens only** — `bg-background`, `text-foreground`, `border-border`.\n  Never a raw hex.\n- **Prefer composing what exists** over writing a new component.\n- **Do not force a bad fit.** A `gap` stays the user's component until they say\n  otherwise.\n- **Visual decisions run the loop.** Any choice the user can see — which shell,\n  which theme, which layout — goes through propose → preview → pick → refine, on\n  a render rather than on prose. The shell is the first of these and is never\n  skipped (`..\u002Fbrand-ui-new-app\u002Freference\u002Fapp-shells.md`). The loop and its fidelity ladder are in\n  `..\u002Fbrand-ui-new-app\u002Freference\u002Fvisual-loop.md`; there is one copy, and both\n  flows use it.\n\n## 5 · Verify — per screen, per theme\n\n- `brand-ui audit src\u002F` and fix what it reports.\n- Check every migrated screen in **every registered theme** — light, dark and\n  the brand family. A screen that only works in one theme is not migrated.\n- Report honestly: what moved, what was skipped and why, and what the user should\n  look at closely. Lead with what you did **not** verify.\n\n## What this skill does not do\n\nIt does not run an automated codemod. The transform engine is not implemented —\n`brand-ui codemod \u003Cmap.json>` emits a plan and a dry-run contract and edits no\nfiles. The edits are yours to make and the user's to review. Say that up front\nrather than implying a one-command migration.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":29,"user-invocable":30},[25,26,27,28],"Bash(npx @elabs-ai\u002Fcomponents-cli *)","Bash(pnpm brand-ui *)","Bash(npx brand-ui *)","Bash(pnpm exec brand-ui *)","[path to the project, defaults to the current directory]",true,"main","f327bf0c3cd1eb26e3d5de071c864afa989b6c72","skills\u002Fbrand-ui-migrate","https:\u002F\u002Fgithub.com\u002Fmreimitz\u002Felabs-components","https:\u002F\u002Felabs-ai.com\u002F","https:\u002F\u002Fgithub.com\u002Fmreimitz","2026-10-07 20:39:57",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":30},[40,43,46],{"tool":41,"command":42},"npx","npx skills add mreimitz\u002Felabs-components --skill brand-ui-migrate",{"tool":44,"command":45},"bunx","bunx skills add mreimitz\u002Felabs-components --skill brand-ui-migrate",{"tool":47,"command":48},"pnpm","pnpm dlx skills add mreimitz\u002Felabs-components --skill brand-ui-migrate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmreimitz\u002Felabs-components\u002Fblob\u002Fmain\u002Fskills\u002Fbrand-ui-migrate\u002FSKILL.md",[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AR8KP3VE2Y0QRA5D1RQNPZ","brand-ui","Build UI with the brand-ui component system (@elabs-ai\u002Fcomponents-* packages — ui, data, ai, flow, maps, charts, marketing, editor, viewer, terminal, tokens, icons). Use when working in a project that depends on @elabs-ai\u002Fcomponents-ui or any @elabs-ai\u002Fcomponents-* package, when adding\u002Fcomposing components, building dashboards, data tables, AI\u002Fchat surfaces, React Flow canvases, MapLibre maps, code editors, file\u002Fdocument viewers, app shells, forms, or marketing sections, when theming with the token system, or when the user mentions brand-ui, @brand, light\u002Fdark themes, or \"our design system\". Provides live project context, the real component API, composition patterns, and the rules that keep components token-driven, accessible, and theme-safe.","https:\u002F\u002Fgithub.com\u002Fmreimitz\u002Felabs-components\u002Fblob\u002Fmain\u002Fskills\u002Fbrand-ui\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7AR8DHBD6W72TY76VJ6Z6FT","brand-ui-update-theme","Use when an existing brand-ui theme family should be improved from new material — updated brand guidelines, a new logo, product screenshots, a live site, feedback like \"the green is off\" or \"match their new design system\" — e.g. \"update the qlik theme with these links\", \"refresh our theme from the new brand book\", \"\u002Fupdate-theme\". For a brand with no theme yet, use brand-ui-create-theme.","https:\u002F\u002Fgithub.com\u002Fmreimitz\u002Felabs-components\u002Fblob\u002Fmain\u002Fskills\u002Fbrand-ui-update-theme\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7AR86YT6GTFP4X1KEQ3TKG2","brand-ui-theme","Create or retune a brand-ui theme (token work). Use when adding a new theme, re-branding the system to a customer's palette, adjusting global radius\u002Fspacing\u002Fsurfaces, or fixing token-level contrast across themes. Use when the user says \"new theme\", \"brand it for \u003Ccustomer>\", \"make corners less rounded\", \"dark theme\", \"adjust the tokens\", or \"our colors\". Every change is a token in a theme stylesheet — never a hardcoded value in a component.","https:\u002F\u002Fgithub.com\u002Fmreimitz\u002Felabs-components\u002Fblob\u002Fmain\u002Fskills\u002Fbrand-ui-theme\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7AR7X95MZNM7YTSD56F38HQ","brand-ui-start","The front door for building UI with brand-ui — a router\u002Fconcierge that asks what you want to do and hands you to the right flow. Use when someone is starting out and unsure where to begin (\"help me with brand-ui\", \"where do I start\", \"I want to build something\", \"what can brand-ui do\", \"get me going\"), or types \u002Fbrand-ui-start. Routes to three flows — build a NEW app (brand-ui-new-app), improve\u002Fmigrate an EXISTING app (brand-ui-migrate), or just help me USE brand-ui in an app that already has it (brand-ui). If the intent is already obvious (the person said \"build me a dashboard\" or \"audit this screen\"), skip the question and go straight to that flow.","https:\u002F\u002Fgithub.com\u002Fmreimitz\u002Felabs-components\u002Fblob\u002Fmain\u002Fskills\u002Fbrand-ui-start\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7AR7MAA8KRQ4HDKPYGXDGG6","brand-ui-registry","Curate the brand-ui shadcn-compatible registry (maintainer workflow). Use when deciding whether something belongs as an imported @elabs-ai\u002Fcomponents-* primitive vs a copy-own registry block\u002Ftemplate, when adding or editing a registry item, or when validating\u002Fbuilding the registry for distribution. Use when the user says \"add a registry item\", \"make this a block\", \"publish to the registry\", or \"package vs registry\". For consuming registry items in an app, use the `brand-ui` skill (npx shadcn add).","https:\u002F\u002Fgithub.com\u002Fmreimitz\u002Felabs-components\u002Fblob\u002Fmain\u002Fskills\u002Fbrand-ui-registry\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7AR79ZG2N23Z7GAXGVAZKA7","brand-ui-new-app","Define-to-build — scaffold a new brand-ui app from a plain-language description (VP-02). Use when the user wants to START an app, page, or demo (\"build me a sales dashboard\", \"I need an admin console for X\", \"new app\", \"scaffold a chat assistant\", \"create a landing page for a pitch\") rather than add to an existing one. Runs a staged interview (quick 3-question mode or full 7-stage spec mode), writes an app-spec.md, then scaffolds from the matching template + playbook with every wiring point annotated and a starter CLAUDE.md so later agent sessions stay on-brand. For adding components to an existing app use `brand-ui`; for authoring library components use `brand-ui-component`.","https:\u002F\u002Fgithub.com\u002Fmreimitz\u002Felabs-components\u002Fblob\u002Fmain\u002Fskills\u002Fbrand-ui-new-app\u002FSKILL.md",[],[]]