brand-ui — AbstractionControls

import { AbstractionControls } from "@elabs-ai/components-process";

Install

npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-process

Skipping the @source line is the most common first failure: Tailwind does not scan node_modules, so every component renders unstyled. The one-time wiring

Prompt for your coding agent

Paste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.

Add the brand-ui AbstractionControls component (from @elabs-ai/components-process) to this project.

1. Read https://elabs-ai.com/llms.txt first: it maps every package and the rules. If you can use MCP servers, connect https://elabs-ai.com/mcp and use its search, docs and tokens tools. If not, run the same lookups in the terminal: `npx -y @elabs-ai/components-cli search "<what you need>"` and `npx -y @elabs-ai/components-cli docs <Component>`.
2. Look AbstractionControls up before writing code: `npx -y @elabs-ai/components-cli docs AbstractionControls` prints its real props, variants, what it pairs with and what to avoid.
3. If @elabs-ai/components-process is not installed yet: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-process` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-process`). If this is the first brand-ui package in the project, wire it once: import `@elabs-ai/components-tokens/styles.css` plus the `themes/light.css` and `themes/dark.css` stylesheets in the CSS entry, add one Tailwind `@source` line per installed @elabs-ai package (Tailwind does not scan node_modules, so without it everything renders unstyled), and wrap the app root in `ThemeProvider` from `@elabs-ai/components-tokens`.
4. Use it here: [the screen or file, and what it should show]
5. Rules: use only @elabs-ai/components-* components and the semantic tokens — no raw colours, no raw font sizes, no arbitrary Tailwind values. Look up each component's real props with the docs tool before you use it; never guess a prop.
6. Done means: the typecheck passes, `npx -y @elabs-ai/components-cli audit src --strict` reports nothing, and you have opened the app and looked at every screen you touched in the light and the dark theme.

Examples

5 live examples

Partially Abstracted

Half the activities kept — the hidden-count status line reflects the real hidden count.

Inverted

The "what is rare here" reading — `invert` hides the MOST frequent instead of the least.

Interaction

Dragging a percentage tick sets the corresponding slider directly, and clicking "Auto" runs the bounded heuristic and narrows `busyGraph` (its backbone-plus-detours topology, see {@link backboneGraph}) down to fit its default 25-activity budget — the RM-052 acceptance criterion for the control, exercised against a real, oversized graph rather than a stub. This holds for THIS fixture's topology; it is not a general guarantee of "Auto" — on a strict activity chain the same heuristic's prediction and the abstracted result can diverge (`keepConnected`'s reachability repair re-adds the whole chain; see #343, which owns that runtime behaviour and is out of scope here).

Per Object Type

Object-centric (RM-066): one collapsible slider pair per object type under the global pair. Linked types follow the global sliders proportionally; `item` is unlinked here, so moving the global activities slider to 50% halves `order` and `package` only.

API

`AbstractionControls`

Prop	Type	Description
`abstraction`required	`AbstractionOptions`	The current abstraction — both fractions, `invert`, and (read-only here) `keepConnected`.
`graph`required	`Pick<ProcessGraph, "activities">`	The CURRENT (already-abstracted) graph — only `activities.length` is read.
`hiddenCounts`required	`{ activities: number; paths: number }`	What the current abstraction hides, straight from `AbstractedGraph.hidden`.
`autoMaxActivities`	`number`	Node budget the "Auto" button searches for. Default `25`.
`label`	`string`	Accessible name for the control group. Default from locale.
`perType`	`Readonly<Record<string, ObjectTypeAbstraction>>`	Object-centric — RM-066. One slider pair per object type, keyed by type, rendered as collapsible rows under the global pair. A `linked` type (the default) follows the global sliders proportionally; toggle its link to abstract it on its own. Feed the result to `abstractObjectCentricGraph`.
`perTypeLabels`	`ObjectTypeAbstractionLabels`	Object-centric — RM-066. Strings for the per-type rows.

Also accepts: Omit<HTMLAttributes<HTMLDivElement>, "onChange">