uiarc.dev valid

Arc

Arc is a React component and block library designed for AI-assisted frontend development. It provides copy-paste components, complete interface blocks, machine-readable registry metadata, AI skills, and MCP compatibility. Components and blocks share design tokens, CSS modules, and Motion. Free items install with the shadcn CLI from a public registry; Pro items are licensed and install from the token-gated @uiarc-pro registry.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T14:04:27.014Z. Cached copy · Source on uiarc.dev

# Arc

> Arc is a React component and block library designed for AI-assisted frontend development. It provides copy-paste components, complete interface blocks, machine-readable registry metadata, AI skills, and MCP compatibility. Components and blocks share design tokens, CSS modules, and Motion. Free items install with the shadcn CLI from a public registry; Pro items are licensed and install from the token-gated @uiarc-pro registry.

Arc has 186 components and 111 blocks. 119 components and 22 blocks are free and open source (MIT); 67 components and 89 blocks are Arc Pro. Arc Pro costs $149 per year or $249 once for lifetime access, and a team plan covers up to 10 people for $799 once or $449 per year. Plans: https://uiarc.dev/pricing. Component links point to per-component markdown with when to use it, when not to, usage, props, keyboard, accessibility, motion, responsive, and performance notes. Block links point to per-block markdown with variants, props, sample data, and install notes.

## Install

Arc items are shadcn-compatible registry items. Each one pulls in the motion presets (`arc-motion-tokens`) and any Arc components it builds on. The design tokens (`arc-foundation`, `foundation.css`) install once per app, and no item reinstalls them.

```bash
npx shadcn@latest add https://uiarc.dev/r/arc-foundation.json
npx shadcn@latest add https://uiarc.dev/r/button.json
```

Or register the namespace once in `components.json` and install by name:

```json
{ "registries": { "@uiarc": "https://uiarc.dev/r/{name}.json" } }
```

```bash
npx shadcn@latest add @uiarc/button @uiarc/dialog
```

Import the tokens once in the root layout: `import "@/components/arc/foundation.css";`. Files install into an `arc/` folder under the `components` alias from `components.json` (for example `components/arc/button/button.tsx`, or `src/components/arc/…` in a `src/` project or a monorepo package) and import each other with relative paths, so no `tsconfig.json` change is needed. Import them from there: `import { Button } from "@/components/arc/button/button";`. Components use CSS modules and CSS variables, not Tailwind classes. Dark mode: `data-theme="dark"` on `<html>`. Accent: `data-accent` = neutral, violet, blue, green, amber, orange, coral, or rose.

### Pro items

Pro components, blocks, and templates install from the token-gated `@uiarc-pro` registry. A Pro member creates a token (`arc_pro_…`) at https://uiarc.dev/account#pro-access, sets `ARC_PRO_TOKEN` in the environment or `.env.local` (never committed), and adds the registry to `components.json`:

```json
{ "registries": { "@uiarc": "https://uiarc.dev/r/{name}.json", "@uiarc-pro": { "url": "https://uiarc.dev/r/pro/{name}.json", "headers": { "Authorization": "Bearer ${ARC_PRO_TOKEN}" } } } }
```

```bash
npx shadcn@latest add @uiarc-pro/dock
```

The MCP server unlocks Pro for a Pro account that signed in through the MCP client (OAuth), or with the same token as `Authorization: Bearer …`: `get_component` the
…

Related sites

Explore similar publishers →

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

Machine-readable: GET /v1/resolve?q=uiarc.dev · GET /v1/domain/uiarc.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 uiarc.dev:
1. POST https://agentwebmap.com/v1/sites/uiarc.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://uiarc.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/uiarc.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/uiarc.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.