control-ui.dev valid

Control UI

100+ open-source React components for Tailwind and shadcn/ui: pickers, trees, editors, app blocks, and AI chat, with swappable skins. Source you own.

For agents: Control UI: 100+ open-source React components for Tailwind and shadcn/ui, with swappable skins and theming docs; installs as source you own.

react componentstailwind cssshadcn uiopen source ui kittheming

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T04:54:05.622Z. Cached copy · Source on control-ui.dev

# Control UI

> 100+ open-source React components for Tailwind and shadcn/ui: pickers, trees, editors, app blocks, and AI chat, with swappable skins. Source you own.

Control UI installs editable React source through the shadcn CLI. The catalog below is generated from the same page manifest used by the website, sitemap, search, and registry API.

## Documentation

- [Create app](https://control-ui.dev/create): Scaffold a Next.js app with every Control UI component installed as source you own, or hand the whole install to the coding agent already open in your project.
- [Install](https://control-ui.dev/get-started): One command installs every component, kit, and template as source you own, with neutral light and dark defaults. The CSS entry is the only wiring you write.
- [Theme it](https://control-ui.dev/theming): Pick the pack, re-value the token contract in one artifact, and check the contrast the components actually paint.
- [Build a screen](https://control-ui.dev/build-a-screen): Render provider-owned messages with plain props and children. No intermediary message schema, no runtime coupling.
- [Create a skin](https://control-ui.dev/create-a-skin): Re-value the token contract over an installed pack, or own a full pack of three files, then reach the component knobs beneath.
- [Foundations](https://control-ui.dev/foundations): Every foundation of the design system, rendered live in the active skin: color, type, surfaces, elevation, radius, sizing, motion, and focus.
- [Theme editor](https://control-ui.dev/theme-editor): Edit theme tokens category by category and watch real components repaint as you go.
- [Theme accessibility](https://control-ui.dev/theme-accessibility): Audit canonical theme colors plus rendered popup, badge, and active-tab states, then run the same checks from the CLI.
- [Update & diff](https://control-ui.dev/update): Updating is a reinstall: the update manifest refreshes every installed source and never touches the three skin-owned files.
- [Setup prompt](https://control-ui.dev/setup-prompt): One prompt that makes the agent already open in your project read the repository, install from the registry, wire the CSS, run the doctor, and design the theme with you.
- [Agent skill](https://control-ui.dev/agent-skill): The skill installed with every pack: the token contract and the working rules, refreshed by every update, so later sessions build without the prompt.
- [Machine docs](https://control-ui.dev/agent-surface): Inspect and install registry items through HTTP, MCP, shadcn manifests, markdown negotiation, and machine-readable docs.
- [Why Control UI](https://control-ui.dev/overview): An owned-source registry of components, kits, complete templates, and swappable skins.
- [Architecture](https://control-ui.dev/architecture): Runtime ownership, skin layering, customization paths, and registry derivation.
- [Lock-in](https://control-ui.dev/lock-in): What you own at each layer, what stays proprietary, and what leaving costs — meas
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=control-ui.dev · GET /v1/domain/control-ui.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for control-ui.dev:
1. POST https://agentwebmap.com/v1/sites/control-ui.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://control-ui.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/control-ui.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/control-ui.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.