{"$schema":"https://ui.shadcn.com/schema/registry-item.json","name":"arc-skill","type":"registry:file","title":"Arc agent skill","description":"An Agent Skill that teaches Claude Code and other agents how to choose, install, and compose Arc components, with rule files for design, components, motion, accessibility, composition, and responsive layout.","categories":["ai"],"files":[{"path":"skills/arc/SKILL.md","type":"registry:file","target":"~/.claude/skills/arc/SKILL.md","content":"---\nname: arc\ndescription: Builds and reviews React interfaces with the Arc UI library (uiarc.dev) so they match Arc's design bar, choosing the right Arc component or block, installing it with the shadcn CLI, and applying Arc's rules for tokens, type, copy, layout, motion, accessibility, and responsive behavior. Use when the user mentions Arc or uiarc, when the project contains components/arc/foundation.css (or the older registry/foundation.css) or imports from @/components/arc (or the older @/registry/components and @/registry/blocks), or when asked to build or polish UI such as a settings page, pricing section, dashboard, landing page, sign-in, form, table, chart, dialog, or command palette.\n---\n\n# Arc\n\nArc is a React component and block library (CSS modules, semantic CSS variables, Motion). Free items install with the shadcn CLI; Pro items are licensed. The quality bar is a calm, neutral interface where type, spacing, and one considered interaction carry the character.\n\n## Workflow\n\nCopy this checklist and tick it off:\n\n```\nArc task:\n- [ ] 1. Find: pick an existing Arc block or component for each region (components.md)\n- [ ] 2. Install: one shadcn command for every id, foundation.css imported once\n- [ ] 3. Wire: documented props only, real data, callbacks return promises\n- [ ] 4. Compose: page container, spacing rhythm, states (composition.md)\n- [ ] 5. Style and copy: tokens, sentence case, no eyebrows (design.md, copy.md)\n- [ ] 6. Review: run checklist.md, fix, run it again until every line passes\n```\n\n**Find.** With the Arc MCP server (`https://uiarc.dev/api/mcp`): `search_components` with the user's intent, then `get_component` on the top two or three and compare `whenToUse` and `whenNotToUse`. The first connection opens a browser sign-in to an Arc account (free is enough); if a tool call fails with an auth error, ask the user to reconnect the server rather than guessing. Results mark Pro items `pro, unlocked` when the signed-in account has Pro; otherwise pass `tier: \"free\"`. Without MCP: read `https://uiarc.dev/llms.txt`, then `https://uiarc.dev/components/<id>/markdown`. Never rebuild an Arc item from scratch, and never reconstruct or imitate Pro source.\n\n**Install.**\n\n```bash\nnpx shadcn@latest add @uiarc/button @uiarc/input @uiarc/switch\n```\n\nThis needs `{ \"registries\": { \"@uiarc\": \"https://uiarc.dev/r/{name}.json\" } }` in `components.json`; without it use full URLs (`https://uiarc.dev/r/button.json`). Once per project: `import \"@/components/arc/foundation.css\";` in the root layout (Arc installs into an `arc/` folder under the `components` alias from `components.json`, for example `src/components/arc/`, and its files import each other with relative paths, so no `tsconfig.json` change is needed), and load Geist and Inter as `--font-geist` and `--font-inter`. Pro members install `@uiarc-pro/<id>` with a Pro token (`https://uiarc.dev/docs/ai#pro-access`).\n\n**Wire.** Copy the import line from the item's usage example (a few use a default export, such as `segmented-control`). Selection components take `value` and `onValueChange`; pickers and editors (`date-picker`, `calendar`, `time-picker`) take `value` and `onChange`. When a callback is typed `void | Promise<…>`, return the promise: the item shows its own pending, success, and error states.\n\n## Core principles\n\n1. **Use Arc before writing UI.** Compose components; do not restyle their internals.\n2. **One purpose per surface.** One `h1`, one primary action, one memorable detail. Remove ornamental copy and decoration.\n3. **Neutral surfaces, meaningful color.** Semantic tokens only. The accent marks active, selected, and emphasized data. Status colors mean status.\n4. **Hierarchy from size, spacing, and contrast.** Regular 400 and medium 500 weights only.\n5. **Motion explains a change.** Shared tokens, transform and opacity, one continuous movement, reduced motion respected.\n6. **Every state designed.** Empty, loading, success, error, disabled, long content, 390px, dark mode.\n\n## Never do\n\n- Eyebrow labels, overlines, or kicker text above headings. All caps or `text-transform: uppercase`.\n- Em dashes in copy. Use a period, comma, colon, or parentheses.\n- Hand-made focus rings, outlines, or halos, or any ring on pointer focus. Keyboard focus already gets Arc's subtle `:focus-visible` ring from `foundation.css`; tune it with `--focus-outline` tokens.\n- Raw hex, Tailwind color classes, or arbitrary font sizes on Arc surfaces.\n- Decorative gradients, glows, or colored shadows inside components. Icons inside rounded tiles.\n- Nested cards, double page gutters, or a second page container inside a block.\n- A toast as the only confirmation of a foreground action.\n- Browser-only values (`window`, `Date.now()`, `Math.random()`, `localStorage`) in the first render.\n\n## Quick decisions\n\n| The user wants | Use | Not |\n| --- | --- | --- |\n| 2 to 5 views of the same data | `segmented-control` | `tabs` (tabs swap whole panels) |\n| Peer panels of one object | `tabs` | Separate routes for each panel |\n| On or off that applies now | `switch` | `checkbox` (checkbox is for forms that submit) |\n| One of a few visible options | `radio-group`, or `radio-cards` with descriptions | `select` for fewer than 5 options |\n| Long option list | `select`, `combobox` to search | `radio-group` |\n| A decision that must interrupt | `dialog` | `drawer` |\n| A long form or record detail beside the page | `drawer` | `dialog` |\n| A task on phones | `bottom-sheet` | `dialog` for mobile-first tasks |\n| Destructive action | `confirm-morph`, `hold-to-confirm` for irreversible | A modal for every delete |\n| Records to compare | `sortable-data-table` | Hand-built tables |\n| KPI row | `metric-card` | Hand-built cards |\n| Result of a save | The button or row confirms in place | `toast` (background work only) |\n\nThe full catalog by job, with free and Pro ids, is in components.md.\n\n## Reference files\n\nRead only the file the task needs. Each is one level from here.\n\n| File | Read it when |\n| --- | --- |\n| [components.md](components.md) | Choosing an item: every live id by job, overlays, inputs, data, marketing blocks |\n| [composition.md](composition.md) | Laying out a page: containers, dashboards, marketing sections, states, React correctness |\n| [design.md](design.md) | Tokens for color, type, surfaces, radii, spacing, icons, metallic and brand treatments |\n| [copy.md](copy.md) | Writing any visible text: headings, buttons, errors, empty states, claims |\n| [motion.md](motion.md) | Adding or reviewing animation |\n| [accessibility.md](accessibility.md) | Semantics, keyboard, names, announcements |\n| [responsive.md](responsive.md) | Widths, touch targets, overflow, tables on phones |\n| [checklist.md](checklist.md) | Before you finish. Always |\n| [example-settings.md](example-settings.md) | Worked example: account settings page |\n| [example-pricing.md](example-pricing.md) | Worked example: pricing section with plans, comparison, and FAQ |\n| [example-dashboard.md](example-dashboard.md) | Worked example: analytics overview with KPIs, chart, and table |\n| [INSTRUCTIONS.md](INSTRUCTIONS.md) | Short always-on rules for AGENTS.md, CLAUDE.md, or Cursor rules |\n\nOver MCP, `get_skill` returns any of these by file name without `.md` (`get_skill { \"id\": \"checklist\" }`). Raw copies: `https://uiarc.dev/r/skills/arc/<file>`.\n\n## Before you finish\n\nRun [checklist.md](checklist.md) against your diff. Fix every failing line, then run it again. Then run the project's type check and lint.\n"},{"path":"skills/arc/INSTRUCTIONS.md","type":"registry:file","target":"~/.claude/skills/arc/INSTRUCTIONS.md","content":"# Arc rules for coding agents\n\nKeep this file where your agent reads project rules: paste it into `AGENTS.md` or `CLAUDE.md`, or save it as `.cursor/rules/arc.mdc` with this header:\n\n```\n---\ndescription: Arc UI rules for React components, pages, and CSS modules\nglobs: [\"**/*.tsx\", \"**/*.module.css\"]\nalwaysApply: false\n---\n```\n\nThe full skill (component choice, layout, motion, examples, review checklist) is at `https://uiarc.dev/r/skills/arc/SKILL.md`, installable with `npx shadcn@latest add https://uiarc.dev/r/arc-skill.json`.\n\n## Always\n\n1. Use an existing Arc component or block before writing UI. Search with the Arc MCP server (`https://uiarc.dev/api/mcp`, tools `search_components` and `get_component`; the first connection opens a browser sign-in) or `https://uiarc.dev/llms.txt`, and read `https://uiarc.dev/components/<id>/markdown` before using an item. Follow its \"When not to use\".\n2. Use only documented props. Compose and wrap Arc components; never fork or restyle their internals, and never reconstruct Pro source.\n3. One page container per app. Blocks fill their column with no second gutter or max width.\n4. One `h1`, one primary button per surface (`button` defaults to `variant=\"primary\"`, so set `secondary` or `ghost` on the rest), one memorable detail per view.\n5. Semantic tokens only: `--background`, `--surface`, `--surface-muted`, `--foreground`, `--text-secondary`, `--text-muted`, `--border`, `--accent`, `--success`, `--warning`, `--danger`, `--radius-*`, `--text-*`, `--space-*`.\n6. The accent marks active, selected, progress, and emphasized data. Status colors only for real status, with a label. Third-party logos in their real colors.\n7. Type: Geist for headings 30px and up, Inter for the rest, weights 400 and 500 only, sizes from the scale, `tabular-nums` for changing numbers.\n8. Nested corners are concentric: inner radius = outer radius - padding.\n9. Motion from `@/components/arc/lib/motion-tokens`: `spring.smooth` (no overshoot) for panels and anything that reports state, `spring.snappy` for presses, `spring.morph` for shared highlights. Animate transform and opacity, one continuous movement, and a reduced motion branch for every animation.\n10. First render is server-safe (no `window`, `localStorage`, `Date.now()`, or `Math.random()` output), and animated elements keep stable keys.\n11. Every data region has loading (`skeleton`), empty (`empty-state`), error (inline `alert`), and in-place success states.\n12. Check 390, 768, 1024, and 1440px: no sideways scroll, wide tables scroll inside their card, touch targets at least 44px.\n\n## Never\n\n- Eyebrow labels or overlines above headings; all caps or uppercase transforms.\n- Em dashes in copy. Use a period, comma, colon, or parentheses.\n- Hand-made focus rings, outlines, or halos, or any ring on pointer focus. Keyboard focus already gets Arc's subtle `:focus-visible` ring from `foundation.css`.\n- Raw hex, Tailwind color classes, weights above 500, or arbitrary font sizes.\n- Decorative gradients, glows, or colored shadows in components; icons in rounded tiles; nested decorative cards.\n- A toast as the only confirmation of a foreground action.\n- Motion that loops without meaning or replays on every scroll.\n"},{"path":"skills/arc/accessibility.md","type":"registry:file","target":"~/.claude/skills/arc/accessibility.md","content":"# Arc accessibility\n\nArc components ship with their semantics and keyboard behavior. Keep them intact when you compose.\n\n## Focus: none for the pointer, a subtle ring for the keyboard\n\nArc draws no focus ring on pointer focus (a mouse click or tap). Keyboard focus (`:focus-visible`) gets one subtle ring from `foundation.css`: a 2px softened accent outline with a 2px offset, the same on every component. Text fields show focus with their border and caret instead, and menu items and listbox options with their highlight fill.\n\nDo not write your own outlines, ring `box-shadow`s, or halos. Tune the shared ring with tokens, on `:root` or on one element:\n\n```css\n/* Correct: adjust the shared keyboard ring */\n.tab { --focus-outline-offset: -2px; }          /* inside a container that clips */\n:root { --focus-outline: var(--accent); }       /* a stronger ring for the whole app */\n\n/* Correct: highlighted items in composite widgets look like the hovered one */\n.item:hover, .item[data-highlighted] { background: var(--surface-muted); }\n\n/* Incorrect: a hand-made ring, or one that also shows on mouse clicks */\n.item:focus { outline: 2px solid var(--accent); }\n.item:focus-visible { box-shadow: 0 0 0 3px var(--accent); }\n```\n\nRadix-based Arc menus, selects, and lists already set `data-highlighted` on the active item. Keep focus order logical so people can follow it.\n\n## Semantics\n\n- Buttons do things, links go places. Never `onClick` on a `div` or `span`.\n- Every field has a visible label (Arc's `label` prop). Use `aria-label` only where the context makes the label visually obvious (a search field in a toolbar).\n- Icon-only controls have a specific name: \"Delete invoice\", not \"Delete\".\n- A `switch` in a settings row with its own title and description points at them: `aria-labelledby` on the title id, `aria-describedby` on the description id (see example-settings.md). Use the `label` prop only when the switch stands alone.\n- One `h1` per page, headings in order, landmarks (`header`, `nav`, `main`, `footer`) around page regions. A `section` with a heading gets `aria-labelledby`.\n- Lists are lists; tables of data are tables (`sortable-data-table` already is).\n- Decorative icons and images: `aria-hidden=\"true\"` or `alt=\"\"`. Meaningful images: alt text that says what matters.\n\n## Keyboard\n\n- Everything clickable is reachable with Tab and works with Enter or Space.\n- Composite widgets (tabs, radio group, segmented control, menus, listboxes) have one Tab stop and arrow keys inside.\n- Dialogs, drawers, sheets, and popovers move focus in, keep it there, close on Escape, and return focus to the trigger. Arc's overlays do this; do not rebuild them.\n- Gestures (swipe, drag, long press, hold) always have a button or menu path.\n- Keyboard shortcuts do not steal keys from text fields.\n\n## Feedback and announcements\n\n- Errors are tied to their field (Arc's `error` prop, or `aria-describedby`) and say how to fix the problem.\n- Status that changes without user focus (saving, syncing, streaming) is announced with `role=\"status\"` or `aria-live=\"polite\"`. Blocking errors use `role=\"alert\"`.\n- Never encode state with color alone: pair color with a label, icon, or text.\n- Loading regions set `aria-busy=\"true\"` and keep focus where it was.\n\n## Contrast\n\n- Text 4.5:1 (3:1 at 24px and up, or 18.5px medium). Icons and control borders 3:1. Check both themes, including `--text-muted` on `--surface-muted` and disabled text.\n- Metallic or tinted surfaces: check the ink color against the lightest and darkest stop of the gradient.\n\n## Check\n\nTab through the whole screen without a mouse: you can always tell where you are from the fills, every overlay opens and closes by keyboard, and focus returns. Then turn on reduced motion and a screen reader rotor (headings, landmarks, form controls) and confirm the structure reads correctly.\n"},{"path":"skills/arc/checklist.md","type":"registry:file","target":"~/.claude/skills/arc/checklist.md","content":"# Arc review checklist\n\nRun this before you finish any Arc task. Copy it into your response, check each line against the code you wrote, and fix every failure. Then run it again. Stop only when every line passes or you have told the user why one cannot.\n\n## 1. Automated sweeps\n\nRun these over the files you changed (adjust the paths). Each hit is a fix unless it is inside a string the user supplied.\n\n```bash\ngrep -rn \"$(printf '\\342\\200\\224')\" app components   # em dashes in copy\ngrep -rniE \"uppercase|eyebrow|overline|kicker\" app components\ngrep -rnE \"outline:|:focus-visible|(^|[^a-z])ring-[0-9]\" app components\ngrep -rnE --include=\"*.css\" \"#[0-9a-fA-F]{3,8}\\b|rgb\\(|hsl\\(\" app components   # raw colors\ngrep -rnE \"font-weight: *(600|700|800|bold)\" app components\ngrep -rnE --include=\"*.css\" \"linear-gradient|radial-gradient\" app components     # allowed only for a marketing backdrop or metallic mark\ngrep -rn --include=\"*.css\" \"100vw\" app components\n```\n\nThen run the project's type check and lint.\n\n## 2. Review\n\n```\nArc review:\nType and copy\n- [ ] Sentence case everywhere; no all caps, no uppercase transforms\n- [ ] No eyebrow or overline text above any heading\n- [ ] No em dashes; headings have no trailing period\n- [ ] Only weights 400 and 500; sizes from --text-* tokens\n- [ ] Buttons are verb plus object (a bare verb only where the object is named right beside it); errors say how to fix; claims are true\n- [ ] Changing or aligned numbers use tabular-nums\n\nColor and surfaces\n- [ ] Only semantic tokens; no raw hex, ramp values, or Tailwind colors\n- [ ] Accent only on active, selected, progress, or the emphasized data\n- [ ] Status colors only for real status, always with a label\n- [ ] No decorative gradients, glows, or colored shadows in components\n- [ ] Third-party logos in their real brand colors\n- [ ] Shadows only on floating layers; cards rest on a 1px border\n- [ ] No icons in rounded tiles; no nested decorative cards\n\nLayout\n- [ ] One page container; blocks fill their column with no double gutter\n- [ ] Heading, cards, and table share the same left edge\n- [ ] Sibling cards align (same top and height) with a real gap or shared dividers\n- [ ] Nested radii are concentric (inner = outer - padding)\n- [ ] Spacing on the 4px grid: 16px inside a group, 24px between regions, 32 to 48px between sections of a long form; page padding 24 to 32px; marketing sections 64 to 120px\n- [ ] Wide tables scroll inside their card\n\nComponents\n- [ ] Every region uses an existing Arc item where one fits (components.md)\n- [ ] The choice matches \"when to use\" (tabs vs segmented control, dialog vs drawer vs sheet, switch vs checkbox)\n- [ ] Only documented props; no restyled internals\n- [ ] One primary button per surface (a `button` without `variant` renders primary)\n- [ ] No Pro source reconstructed\n\nStates\n- [ ] Loading (skeleton in final layout), empty (one next step), error (inline, with retry), success (in place), disabled (explained)\n- [ ] Long names and values wrap or truncate with the full value reachable\n\nMotion\n- [ ] Tokens from components/arc/lib/motion-tokens; no hand-tuned durations without reason\n- [ ] Only transform and opacity animate (size only on a spring when it is the information)\n- [ ] State indicators land without overshoot; bounce only for playful moments\n- [ ] One continuous movement per interaction; exits faster than entrances\n- [ ] A reduced motion branch for every animation\n\nReact correctness\n- [ ] First render is server-safe: no window, localStorage, Date.now, Math.random, or locale-dependent output\n- [ ] Animated elements keep stable keys and are not remounted on state change\n- [ ] Changing values reserve their width; nothing jumps\n\nAccessibility\n- [ ] No focus rings on pointer focus and no hand-made rings; keyboard focus shows Arc's shared `:focus-visible` ring (tune with `--focus-outline` tokens)\n- [ ] Real buttons, links, labels, headings in order, landmarks\n- [ ] Icon-only controls have specific names\n- [ ] Overlays trap and return focus and close on Escape\n- [ ] State never shown by color alone; async status announced\n\nResponsive\n- [ ] Checked at 390, 768, 1024, 1440 (if you cannot render, read the CSS for fixed widths, missing min-width: 0, and unwrapped rows); no sideways page scroll\n- [ ] Touch targets at least 44px; hover content reachable by tap or focus\n- [ ] Both themes and two accents (neutral and one hue) read correctly\n```\n\n## 3. Report\n\nTell the user what you built, which Arc items you used, what is simulated or still needs real data, and any checklist line you could not satisfy and why.\n"},{"path":"skills/arc/components.md","type":"registry:file","target":"~/.claude/skills/arc/components.md","content":"# Choosing Arc components and blocks\n\nPick the item whose job matches, not the one that looks closest. Ids below are the install names (`npx shadcn@latest add @uiarc/<id>`). Items marked Pro need Arc Pro (a Pro account signed in to the MCP server, or a Pro token); offer the free pick otherwise. Only ids listed here or returned by `search_components` exist; do not guess others.\n\n## Contents\n- How to decide\n- Actions and menus\n- Inputs and forms\n- Overlays and disclosure\n- Feedback and status\n- Data display and charts\n- Text and motion\n- App blocks\n- Marketing blocks\n- Wiring rules\n\n## How to decide\n\n1. Name the job in one line (\"pick one of three plans\", \"confirm deleting a project\").\n2. Find candidates in the tables below or with `search_components`.\n3. Read each candidate's markdown (`https://uiarc.dev/components/<id>/markdown` or `get_component`). \"When not to use\" names the better alternative; follow it.\n4. Prefer a block for a whole region, a component for a single control. Replace block sample data; do not keep placeholder names or numbers.\n5. Use the same item for the same job everywhere in the app: one confirmation pattern, one menu, one table.\n\n## Actions and menus\n\n| Job | Pick | Instead of |\n| --- | --- | --- |\n| The main action on a surface | `button` (its default `variant` is `\"primary\"`), once per surface | Several primary buttons |\n| Other actions | `button` with `variant=\"secondary\"` or `\"ghost\"` set explicitly | A bare `<Button>`, which renders primary |\n| Dense toolbar action | `action-button` | Full buttons in a toolbar |\n| Main action plus alternatives | `split-button` | A row of equal buttons |\n| Navigate somewhere | A link (`<a>` or your router's `Link`), or a block action with `href` (`hero-section`, `cta-section`) | `button` with a router push |\n| A list of actions on a trigger | `dropdown-menu` | Custom popovers |\n| Actions on a right-click or long press | `context-menu` | Hidden gestures without a menu |\n| Copy a value | `copy-button` | A button plus a toast |\n| Label that changes with state | `button` (new children crossfade in place); `text-morph` outside a button | Swapping two buttons |\n| Global search and commands | `command-palette` | A search field in every page |\n| Account, theme, sign out | `user-menu` | A custom avatar menu |\n| Hierarchy and paging | `breadcrumb`, `pagination` | |\n| Light and dark switch | `theme-switch` | |\n\n## Inputs and forms\n\n| Job | Pick | Instead of |\n| --- | --- | --- |\n| Text | `input`, `textarea`; `mention-input` for @people and #channels | Unlabeled fields |\n| Search inside a page | `search-field`; `expanding-search` in a tight header | |\n| Password | `password-field`, plus `password-strength` on sign up | |\n| Numbers, phone | `number-field`, `phone-input` | Plain `input type=\"number\"` |\n| One of 2 to 5 visible options in a form | `radio-group` | `select` |\n| Options with a price, meta, or longer description | `radio-cards` | Clickable cards you build |\n| One of many options | `select`; `combobox` to type and filter | `radio-group` |\n| Several values | `multi-select`, `tag-input`, `chip-group` for filter facets | Checkbox lists in a popover |\n| On or off that applies immediately | `switch` | `checkbox` |\n| Agree, include, or a checklist inside a submitted form | `checkbox` | `switch` |\n| View mode of the same content (2 to 5) | `segmented-control` | `tabs` |\n| Range or level | `slider` | Two number fields |\n| Date, date range, time | `date-picker`, `date-range-picker`, `time-picker` | `calendar` (inline grid only) |\n| Color | `color-picker` | |\n| Files | `file-dropzone` (target), `file-upload` (full flow with progress) | |\n| Verification code | `otp-input` | Six inputs you wire yourself |\n| Rich text | `rich-text-editor` | A textarea with markdown hints |\n| Signature | `signature-pad` | A canvas you wire yourself |\n| Keyboard shortcut | `shortcut-recorder` | A text field for key names |\n| Rename in place | `inline-edit` | A dialog for one field |\n| A flow in steps | `stepper` with your fields; Pro: `multi-step-form` | |\n| Billing period | `billing-toggle` (with `BillingPrice`) | A segmented control plus hand-rolled prices |\n\n## Overlays and disclosure\n\n| Job | Pick | Instead of |\n| --- | --- | --- |\n| A decision that must interrupt, or a short form | `dialog` | `drawer` |\n| A long form, filters, or record detail beside the page | `drawer` | `dialog` |\n| Mobile-first secondary task with snap heights | `bottom-sheet` | `dialog` on phones |\n| Small anchored controls without dimming the page | `popover` | `dialog` |\n| One-line hint for an unfamiliar control | `tooltip` | Essential information (tooltips hide it) |\n| Preview of a person or link | `hover-card` (also opens on focus) | |\n| Peer panels of one object (Overview, Activity, Settings) | `tabs` | `segmented-control` |\n| Stacked sections read in order, FAQ | `accordion` | `tabs` |\n| A card that needs more room on request | `expandable-card` | Navigating away |\n| Two panes that trade space | `resizable-panels` | |\n| Long content in a fixed box | `scroll-area` | `overflow: auto` with default bars |\n\n## Feedback and status\n\n| Job | Pick | Instead of |\n| --- | --- | --- |\n| Confirm a foreground action | In place: `button` `loading`, then its label | `toast` |\n| Destructive action | `confirm-morph`; `hold-to-confirm` when an accidental tap must be nearly impossible; `dialog` when the consequence needs explaining | A modal for every delete |\n| Result of background work | `toast`, `toast-stack` for several | Inline banners that shift layout |\n| A message that stays until resolved | `alert` with `tone` | `toast` |\n| Status label | `badge` with `tone` | Colored text alone |\n| Known progress | `progress`, `stepper` for steps | A spinner |\n| Loading | `skeleton` in the final layout | A page spinner |\n| Nothing to show yet | `empty-state` with one action | \"No data\" |\n| Quota or allowance | `usage-meter` | A bare progress bar |\n| Site-wide notice | `announcement-bar` | A banner you build |\n| People | `avatar`, `avatar-group` | Initials you draw |\n\n## Data display and charts\n\n| Job | Pick | Instead of |\n| --- | --- | --- |\n| Headline number (KPI) | `metric-card` (label, number, context line, change chip) | Hand-built KPI cards |\n| Number that changes | `animated-counter` | Text that jumps |\n| Records to sort and compare | `sortable-data-table`; Pro: `data-grid` for spreadsheet editing | Div grids |\n| Filters above a collection | `filter-toolbar` | Loose selects |\n| Trend over time | `line-chart`; `sparkline` beside a value | |\n| Compare one measure across categories or days | `bar-chart` | A line chart for categories |\n| Share of a whole (up to about 5 parts) | `donut-chart`; `waffle-chart` for percentages; `treemap` for a hierarchy | A pie with many slices |\n| Dense time series to zoom into | `brush-chart` | A line chart with hundreds of ticks |\n| Before and after across items | `slope-chart` | Two bar charts |\n| Distributions by group | `ridgeline` | |\n| Layered totals over time | `streamgraph` | |\n| Value against a range | `gauge` | |\n| A year of daily activity | `activity-heatmap` | |\n| Events, newest first | `timeline` | |\n| Nested structure | `tree-view` | |\n| Code or JSON | `code-block`, `json-viewer` | `<pre>` |\n| Comments and chat | `comment-thread`, `chat-thread` | |\n| Feature comparison across plans or products | `comparison-table` (block) | A hand-built table |\n| A row of slides | `carousel` | |\n| Before and after images | `image-compare` | |\n| Row actions on touch | `swipe-actions` (always with a menu path) | Swipe only |\n\nPro charts: `funnel-chart`, `radar-chart`, `sunburst`, `sankey-flow`, `race-bar-chart`, `realtime-stream`, `activity-rings`.\n\n## Text and motion\n\nUse one text effect per page, where it explains something.\n\n| Job | Pick |\n| --- | --- |\n| A title entering as it scrolls into view (once) | `in-view-title` |\n| A short reveal on load | `text-reveal` |\n| A label that changes to its next state | `text-morph` |\n| Ongoing work (\"Generating\") | `text-shimmer` |\n| Numbers or short text spinning to a new value | `slot-text` |\n\n## App blocks\n\nFree: `command-palette`, `notification-center`, `file-upload`, `otp-input`, `page-header`, `empty-states` (no results, offline, missing page), `sign-in` (email code card), `login-centered` (passkey card), `signup-form`.\n\nPro, by job:\n\n| Job | Pro blocks |\n| --- | --- |\n| App shell | `sidebar-rail`, `workspace-sidebar`, `inbox-sidebar`, `docs-sidebar` |\n| Sign in, full screen | `login-split`, `login-immersive` |\n| Settings and account | `settings-page`, `security-settings`, `roles-permissions`, `api-keys`, `webhooks`, `integrations` |\n| Billing | `billing-overview`, `usage-billing`, `usage-forecast`, `invoice-studio`, `cancel-flow`, `checkout-summary` |\n| Team | `team-members`, `invite-people`, `team-directory` |\n| Analytics | `metrics-dashboard`, `metric-explorer`, `revenue-explorer`, `cohort-retention`, `mrr-waterfall`, `journey-flow`, `kpi-drilldown` |\n| Boards | `project-board` |\n| Setup flows | `multi-step-form`, `release-readiness` |\n| AI | `ai-chat`, `ai-composer`, `agent-run` |\n| Support and inbox | `support-widget`, `support-conversation`, `inbox-triage` |\n| Commerce | `product-listing`, `product-detail`, `cart-drawer` |\n| Scheduling and media | `week-calendar`, `availability-picker`, `media-player` |\n\n## Marketing blocks\n\nFree: `site-header`, `hero-section`, `logo-marquee`, `stats-band`, `plan-comparison`, `comparison-table`, `faq-section`, `cta-section`, `newsletter-signup`, `contact-section`, `blog-grid`, `changelog-feed`, `site-footer`.\n\nPro: `hero-signup`, `feature-bento`, `scroll-story`, `spotlight-grid`, `testimonial-stage`, `team-showcase`, `pricing-calculator`, `usage-pricing`.\n\nNotes:\n- `plan-comparison` is a finished two-plan demo with its own billing switch and sample data. For your own plans, compose `billing-toggle`, your plan cards (or `radio-cards`), and `comparison-table` (see example-pricing.md).\n- Blocks with props (`hero-section`, `cta-section`, `faq-section`, `stats-band`, `comparison-table`, `site-header`) take your content directly. Blocks without props (`page-header`, `plan-comparison`) are starting points: edit their data in the installed file.\n\n## Wiring rules\n\n- Copy the import from the usage example: `import { Button } from \"@/components/arc/button/button\";`, `import SegmentedControl from \"@/components/arc/segmented-control/segmented-control\";`, blocks from `@/components/arc/blocks/<id>/<id>`.\n- Use only documented props. Where an item accepts `className` or native props (check its props table), use them for layout (margin, grid placement), never to restyle internals.\n- Pick controlled (`value` plus a change handler) or uncontrolled (`defaultValue`), not both.\n- Async callbacks (`onConfirm`, `onSubmit`, `onSave`) return the promise; reject to show the item's error state. Do not add a second spinner.\n- Wrap an Arc component to add behavior; do not fork its source.\n"},{"path":"skills/arc/composition.md","type":"registry:file","target":"~/.claude/skills/arc/composition.md","content":"# Composing pages with Arc\n\nArc components own their internals; your CSS module owns the layout.\n\n## Contents\n- Plan the page\n- One page container\n- Product pages and dashboards\n- Marketing pages\n- States\n- React correctness\n- Page recipes\n\n## Plan the page\n\nWrite three lines before you choose anything:\n\n```\nJob: what the person comes here to do (\"change their plan and see what it costs\")\nPrimary action: exactly one (\"Upgrade to Team\")\nRegions: each region and the Arc item it uses (components.md)\n```\n\nHierarchy: one `h1`; section headings describe content; the primary action is the only primary `button` on screen (`button` defaults to primary, so set `variant` on every other one); secondary actions go in `split-button` or `dropdown-menu`.\n\n## One page container\n\nAn app has one page container that sets the max width and the gutters, usually in the app layout. Everything inside fills its column. Blocks and cards never add their own page gutter. A page may narrow its reading column with `max-width` alone (settings and forms at 640 to 720px), never with extra padding.\n\n```css\n/* Correct: one container, children fill it */\n.page {\n  width: 100%;\n  max-width: 1200px;\n  margin-inline: auto;\n  padding: 32px clamp(16px, 4vw, 32px);\n  display: grid;\n  gap: 24px;\n}\n.page > * { min-width: 0; }\n```\n\n```tsx\n// Incorrect: a second container inside the page doubles the gutter\n<main className={styles.page}>\n  <section style={{ maxWidth: 960, margin: \"0 auto\", padding: \"0 24px\" }}>...</section>\n</main>\n```\n\nChecks:\n- The left edge of the heading, the first card, and the table line up.\n- An embedded block fills its column edge to edge; if the block ships with outer padding for its demo, remove it rather than stacking it on yours.\n- Grid and flex children get `min-width: 0` so long content cannot push the page sideways.\n\n## Product pages and dashboards\n\n- Page padding 24 to 32px (16px on phones). 16px between related cards and fields, 24px between regions, 32 to 48px between the sections of a long settings or form page.\n- Content widths: forms and settings read best at 640 to 720px; dashboards and tables use the full container.\n- A KPI row is a grid of `metric-card`s with equal heights: `grid-template-columns: repeat(auto-fit, minmax(200px, 1fr))`.\n- Sibling cards share edges: same top and height, outer edges flush with the column. See design.md.\n- Wide tables scroll inside their card, never the page:\n\n```css\n.tableCard { border: 1px solid var(--border); border-radius: var(--radius-surface); overflow: hidden; }\n.tableScroll { overflow-x: auto; overscroll-behavior-x: contain; }\n```\n\n- Settings: a list of rows (label and description on the left, control on the right) inside one bordered group per section, with `--border-subtle` dividers. Do not wrap each row in its own card.\n\n```tsx\n// Correct: one group, divided rows\n<section aria-labelledby=\"notifications\">\n  <h2 id=\"notifications\">Notifications</h2>\n  <div className={styles.group}>\n    <div className={styles.row}><span id=\"updates\">Product updates</span><Switch aria-labelledby=\"updates\" /></div>\n    <div className={styles.row}><span id=\"summary\">Weekly summary</span><Switch aria-labelledby=\"summary\" /></div>\n  </div>\n</section>\n\n// Incorrect: a card per row, an eyebrow, and a second heading level for nothing\n<p className=\"eyebrow\">PREFERENCES</p>\n<Card title=\"Product updates\"><Switch /></Card>\n<Card title=\"Weekly summary\"><Switch /></Card>\n```\n\n## Marketing pages\n\n- Sections breathe: 64 to 120px vertical padding (64px on phones), same container and gutters as the rest of the page.\n- One idea per section. Do not repeat the same card grid or split layout in consecutive sections.\n- Default order: `site-header`, `hero-section`, proof (`logo-marquee` with real brand colors, `stats-band` with true numbers), features, pricing (see example-pricing.md), `faq-section`, `cta-section`, `site-footer`.\n- Headings are Geist at `--text-3xl` to `--text-5xl`, weight 400 or 500, with no eyebrow above them.\n- The brand gradient (`--arc-gradient-soft`) may sit behind one section as a subtle backdrop. Nothing else is gradient.\n- One entrance animation per page at most (`in-view-title` on the hero or first heading). No slide-up on every section.\n\n## States\n\nDesign every data region for all of them before you finish:\n\n| State | Treatment |\n| --- | --- |\n| Loading | `skeleton` in the final layout, same dimensions, `aria-busy` on the region |\n| Empty | `empty-state` with why it is empty and one next step |\n| Error | Inline `alert` next to the cause, with a retry |\n| Success | Confirm in place: the button label, the row, the value |\n| Disabled | Explain why nearby, or hide the control. A save button disabled until something changes needs no explanation |\n| Long content | Wrap or truncate with the full value reachable |\n\n## React correctness\n\n- **Server-safe first render.** The first render must match on server and client. Read `window`, `matchMedia`, `localStorage`, `Date.now()`, `Math.random()`, and the user's locale or time zone in an effect or with `useSyncExternalStore` and a server snapshot. Format dates with an explicit locale and `timeZone`.\n\n```tsx\n// Incorrect: differs between server and client\nconst [theme] = useState(localStorage.getItem(\"theme\") ?? \"light\");\n\n// Correct: the server snapshot (\"light\") is also the first client render, then it syncs\nconst subscribe = (onChange: () => void) => {\n  window.addEventListener(\"storage\", onChange);\n  return () => window.removeEventListener(\"storage\", onChange);\n};\nconst theme = useSyncExternalStore(subscribe, () => localStorage.getItem(\"theme\") ?? \"light\", () => \"light\");\n```\n\n- **Do not remount animated elements.** Keep `key` stable on anything that animates, never define a component inside another component's render, and never swap the element type of an animated node on state change. A remount restarts the animation and loses focus.\n- **Stable dimensions.** Reserve space for values that change (tabular numerals, fixed min widths) so neighbours do not jump.\n- Add `\"use client\"` only to files that use state, effects, or event handlers; keep the page shell a server component when the framework supports it.\n\n## Page recipes\n\nFree items unless marked Pro. Full worked code: example-settings.md, example-pricing.md, example-dashboard.md.\n\n| Page | Build it from |\n| --- | --- |\n| Sign in and sign up | `sign-in` or `login-centered`, then `signup-form`, `otp-input`. Pro: `login-split`, `login-immersive` |\n| Dashboard | `h1` and `segmented-control` for range, `metric-card` row, `line-chart` or `bar-chart`, `sortable-data-table`. Pro: `metrics-dashboard`, `metric-explorer` |\n| Settings | Sections of `input`, `select`, `switch` rows, a save `button`, `confirm-morph` for deleting. Pro: `settings-page`, `security-settings` |\n| Record list | `filter-toolbar` or `search-field`, `sortable-data-table`, `pagination`, `empty-state`. Pro: `data-grid` |\n| Pricing | `billing-toggle` and `BillingPrice`, plan cards or `radio-cards`, `comparison-table`, `faq-section`. Pro: `pricing-calculator`, `usage-pricing` |\n| Landing page | `site-header`, `hero-section`, `logo-marquee`, `stats-band`, `comparison-table`, `faq-section`, `cta-section`, `site-footer`. Pro: `feature-bento`, `scroll-story` |\n| App shell | `command-palette`, `user-menu`, `notification-center`. Pro: `sidebar-rail`, `workspace-sidebar` |\n| Not found, offline, no results | `empty-states` block, or `empty-state` inside a region |\n"},{"path":"skills/arc/copy.md","type":"registry:file","target":"~/.claude/skills/arc/copy.md","content":"# Arc copy\n\nArc copy is short, specific, and honest.\n\n## Rules\n\n1. **Sentence case everywhere**: headings, buttons, tabs, menu items, table headers, badges. Capitalize only the first word and proper nouns. Never all caps, never `text-transform: uppercase`.\n2. **No eyebrow labels.** No small text above a heading (\"FEATURES\", \"Pricing\", \"Why teams switch\"). If the context matters, put it in the heading or the description below it. A badge beside a heading that carries information (\"Recommended\" on a plan name, \"Beta\" on a feature) is not an eyebrow; a kicker line above the heading is.\n3. **No em dashes** (the long dash, U+2014). Use a period, comma, colon, or parentheses. For ranges write \"9 to 17\" or \"Mon to Fri\".\n4. **No period at the end of a heading**, and no ornamental punctuation (trailing dots, slashes, arrows as decoration).\n5. **Buttons are verbs with an object**: \"Save changes\", \"Invite member\", \"Delete project\", \"Start free trial\". Not \"Submit\", \"OK\", \"Click here\", or \"Learn more\" alone. A bare verb is fine only when the object is named right beside it, such as \"Delete\" in a confirmation that asks \"Delete Harbour?\".\n6. **One subtitle at most**, and only when it adds information the heading cannot. Drop it when the content explains itself.\n7. **Honest claims.** No invented numbers, testimonials, customer logos, or awards. Sample data is realistic and clearly sample. A simulated payment, deploy, or email says so.\n8. **Consistent terms.** One word per concept across the product (\"workspace\" everywhere, not workspace, team, and org).\n\n## Examples\n\n| Incorrect | Correct |\n| --- | --- |\n| `<p class=\"eyebrow\">PRICING</p><h2>Simple, Transparent Pricing.</h2>` | `<h2>Pricing that grows with your team</h2>` |\n| Two clauses joined by an em dash (\"Fast builds, em dash, every time\") | \"Builds finish in under a minute.\" |\n| Button: \"Submit\" | Button: \"Save changes\" |\n| \"Oops! Something went wrong!!\" | \"We could not save your changes. Check your connection and try again.\" |\n| \"No data\" | \"No invoices yet. Your first invoice appears after the trial ends.\" |\n| \"Trusted by 10,000+ teams\" (unverified) | Remove it, or state what is true: \"Used by the Arc team every day\" |\n| Tab: \"ACTIVITY LOG\" | Tab: \"Activity\" |\n\n## Patterns\n\n- **Errors** say what happened and how to fix it, next to the field: \"Enter an email like name@company.com\".\n- **Empty states** say why it is empty and offer one next step: title \"No projects yet\", description \"Projects you create or join appear here.\", action \"Create project\".\n- **Destructive confirmations** name the object and the consequence: \"Delete Harbour? Its 12 files are removed for everyone.\"\n- **Success** is a state change in place (\"Saved\", a check, the new value), not a paragraph.\n- **Numbers** use real formatting: \"$1,240\", \"12.5%\", \"3 of 5 seats\". Use tabular numerals where they change.\n- **Dates** are human and unambiguous: \"Sep 24\", \"Tomorrow at 9:00\", \"2 hours ago\".\n\n## Check\n\nSearch your diff for the em dash (`grep -rn \"$(printf '\\342\\200\\224')\" .`), `uppercase`, `letter-spacing` on small labels, headings ending in `.`, and any text node above a heading that is smaller than the heading. Each hit is a fix.\n"},{"path":"skills/arc/design.md","type":"registry:file","target":"~/.claude/skills/arc/design.md","content":"# Arc design\n\nThe visual rules for anything built with or next to Arc components. Every token below is defined in `components/arc/foundation.css`.\n\n## Contents\n- Color\n- Brand, metallic, and logo treatments\n- Type\n- Surfaces, borders, and shadows\n- Radii (concentric corners)\n- Spacing and sizing\n- Icons\n- Themes and accents\n\n## Color\n\nComponents and pages use semantic roles only. Never the `--neutral-*` ramp, raw hex, or Tailwind color classes.\n\n| Role | Tokens |\n| --- | --- |\n| Page and surfaces | `--background`, `--surface`, `--surface-raised`, `--surface-muted` |\n| Text | `--foreground`, `--text-secondary`, `--text-muted` |\n| Lines | `--border` (default), `--border-subtle` (inside a surface), `--border-strong` (inputs, emphasis) |\n| Accent | `--accent`, `--accent-strong`, `--accent-subtle`, `--accent-foreground` |\n| Status | `--success`, `--warning`, `--danger` (and `--accent` for info) |\n| Selection controls | `--control-on`, `--control-glyph`, `--control-track`, `--control-thumb`, `--control-thumb-on` |\n| Chart series | `--series-1` to `--series-4` |\n\n**Accent with intent.** Most of the screen stays neutral. Spend `--accent` on: the active nav item, a selected row or option, the one data series that matters, progress, and a few interaction details (a link, a count that just changed). Tint with `--accent-subtle` behind accent text or icons. Do not color headings, card backgrounds, or every icon with it.\n\n**Status means status.** `--success`, `--warning`, and `--danger` appear only when something succeeded, needs attention, or failed. `badge` `tone=\"info\"` uses the accent and may mark emphasis (\"Recommended\", \"New\"); the other tones are for status only. Put most of the color on the icon with a faint tint behind it, and always pair it with a short label. Never use green for \"nice\" or red for \"important\".\n\n**Selection controls** that you build yourself use the `--control-*` tokens, not `--accent` with `--accent-foreground`. They are tuned per accent so a thumb always reads against its track.\n\n## Brand, metallic, and logo treatments\n\n- **Third-party logos use their real brand colors** (the multicolor Google G, Slack, Stripe purple). A grey logo row looks like placeholder content. Brand marks are sample content, never implied endorsements.\n- **The Arc brand gradient** (`--arc-gradient`, `--arc-gradient-soft`) is only a subtle backdrop behind a marketing section. Never inside a component, on a button, on text in product UI, or on a card surface.\n- **Metallic surfaces** are an allowed premium treatment for one element per view: a Pro plan card, an avatar fallback, a premium badge. Brushed silver in light, graphite in dark, near-zero chroma, a hairline edge, text contrast checked in both themes. Define the values locally and redefine them for dark mode:\n\n```css\n.premium {\n  --metal-plate: linear-gradient(112deg, oklch(93.4% .003 260), oklch(98.6% .002 260) 24%, oklch(91.2% .004 260) 50%, oklch(96.8% .003 260) 74%, oklch(92.6% .004 260));\n  --metal-edge: inset 0 0 0 1px oklch(0% 0 0 / .075), inset 0 1px 0 oklch(100% 0 0 / .95);\n  --metal-ink: oklch(26% .012 260);\n  background: var(--metal-plate);\n  box-shadow: var(--metal-edge);\n  color: var(--metal-ink);\n}\n:root[data-theme=\"dark\"] .premium {\n  --metal-plate: linear-gradient(112deg, oklch(24.5% .004 260), oklch(30.5% .005 260) 24%, oklch(22.5% .004 260) 50%, oklch(28.5% .005 260) 74%, oklch(24% .004 260));\n  --metal-edge: inset 0 0 0 1px oklch(100% 0 0 / .09), inset 0 1px 0 oklch(100% 0 0 / .06);\n  --metal-ink: oklch(95.5% .004 260);\n}\n```\n\n## Type\n\n| Face | Token | Use | Settings |\n| --- | --- | --- | --- |\n| Geist | `--font-display` | Headings 28px and up | 400 or 500, `letter-spacing: var(--tracking-display)` (-0.03em), `line-height: var(--leading-display)` (1.1) |\n| Inter | `--font-body` | Body, labels, controls, small headings | 400 or 500, `letter-spacing: var(--tracking-body)` (-0.01em), `line-height: var(--leading-body)` (1.4) |\n\n- Sizes come from the scale only: `--text-xs` 12, `--text-sm` 13, `--text-base` 15, `--text-lg` 17, `--text-xl` 20, `--text-2xl` 22, `--text-3xl` 28, `--text-4xl` 34, `--text-5xl` 40. Typed text uses `--text-field` (14px, 16px on phones).\n- Weights are 400 and 500. Never 600 or bold. Hierarchy comes from size, color (`--foreground` over `--text-secondary`), and spacing.\n- Keep Geist out of controls and small labels; keep Inter out of hero headlines.\n- Numbers that change or align in columns use `font-variant-numeric: tabular-nums`.\n- No `text-transform: uppercase`, no wide letter-spacing on small labels, no eyebrow line above a heading. See copy.md.\n\n## Surfaces, borders, and shadows\n\n- Group with proximity first, a one pixel `--border` second, a card only for a real boundary.\n- Shadows only on layers that float: menus, popovers, dialogs, sheets (`--shadow-floating`). Cards rest on a border with no shadow. `--shadow-resting` and `--shadow-raised` exist for the rare lifted element; never stack them.\n- No nested rounded cards, decorative pills, glows, or scattered symbols.\n- Sibling cards share edges: cards in a row have the same top, the same height (`align-items: stretch`), and their outer edges sit flush with the content column. Either separate them with a real gap (16 to 24px) or join them into one bordered group with hairline dividers. Never a 1 to 4px gap where two borders nearly touch.\n\n## Radii (concentric corners)\n\n`--radius-control` 14px (inputs, buttons), `--radius-panel` 20px (menus, nested panels), `--radius-surface` 24px (cards, large surfaces), `--radius-pill` (tags, status marks).\n\nA nested corner is the outer radius minus the padding between them, so the curves stay parallel:\n\n```css\n/* Correct: inner = outer - padding */\n.card  { border-radius: var(--radius-surface); padding: 8px; }\n.inner { border-radius: calc(var(--radius-surface) - 8px); } /* 16px */\n\n.panel { border-radius: var(--radius-surface); padding: 16px; }\n.panel > .media { border-radius: calc(var(--radius-surface) - 16px); } /* 8px */\n```\n\n```css\n/* Incorrect: the same radius inside and out makes a thick, uneven corner */\n.card  { border-radius: 24px; padding: 16px; }\n.inner { border-radius: 24px; }\n```\n\nClamp the result at a small positive value (`max(6px, calc(...))`) when padding is large.\n\n## Spacing and sizing\n\n- A 4px grid: 4, 8, 12, 16, 24, 32, then 48, 64, 96, 120 for sections. Tokens are `--space-N` = N × 4px for N = 1 to 6, 8, 10, 12, 16, 20, 24 (no `--space-7`, `--space-9`, and so on).\n- Controls: `--control-height-sm` 36px, `--control-height-md` 44px (default for anything tapped on phones), `--control-height-lg` 50px.\n- Rhythm by context (details in composition.md): product pages use 16px inside groups, 24px between regions, 32 to 48px between long-form sections, and 24 to 32px page padding; marketing sections use 64 to 120px vertical padding.\n- Internal control spacing stays fixed as the viewport grows; only outer gutters grow.\n\n## Icons\n\n- `lucide-react` at 16, 20, or 24px with `strokeWidth={1.75}`. Decorative icons get `aria-hidden=\"true\"`.\n- A plain icon beside its label. No icon inside a rounded tile or circle unless the shape is the control itself or carries a status.\n- Use a text label when it is clearer than an icon, especially for destructive or unfamiliar actions.\n\n## Themes and accents\n\n- Dark mode is `data-theme=\"dark\"` on `<html>`; the accent is `data-accent` (`neutral`, `violet`, `blue`, `green`, `amber`, `orange`, `coral`, `rose`). Every token already has a dark value, so tokens alone make a screen work in both themes.\n- Check both themes and at least two accents (neutral and one saturated hue). A screen that only works in neutral is using the accent wrong.\n"},{"path":"skills/arc/example-dashboard.md","type":"registry:file","target":"~/.claude/skills/arc/example-dashboard.md","content":"# Example: analytics overview\n\nRequest: \"An overview page for our signups: a few KPIs, a chart for the selected range, and the top sources.\"\n\n## Plan\n\n```\nJob: see how signups are trending and where they come from\nPrimary action: Export (one primary button)\nRegions: header (h1, range, export), KPI row (metric-card x4), trend (line-chart), sources (sortable-data-table)\nStates: loading (skeleton per region), empty (empty-state), error (alert with retry)\n```\n\nChoices: `segmented-control` for the range because it changes the view of the same data (not `tabs`, which swap panels); `metric-card` for the KPIs; the table scrolls inside its card on phones. Pro alternative for the whole page: `metrics-dashboard`.\n\n```bash\nnpx shadcn@latest add @uiarc/button @uiarc/segmented-control @uiarc/metric-card @uiarc/line-chart @uiarc/sortable-data-table @uiarc/skeleton @uiarc/empty-state @uiarc/alert\n```\n\n## overview.tsx\n\n```tsx\n\"use client\";\n\nimport { Download } from \"lucide-react\";\nimport { Alert } from \"@/components/arc/alert/alert\";\nimport { Button } from \"@/components/arc/button/button\";\nimport { EmptyState } from \"@/components/arc/empty-state/empty-state\";\nimport { LineChart, type LineChartDatum } from \"@/components/arc/line-chart/line-chart\";\nimport { MetricCard } from \"@/components/arc/metric-card/metric-card\";\nimport SegmentedControl from \"@/components/arc/segmented-control/segmented-control\";\nimport { Skeleton } from \"@/components/arc/skeleton/skeleton\";\nimport { SortableDataTable } from \"@/components/arc/sortable-data-table/sortable-data-table\";\nimport styles from \"./overview.module.css\";\n\ntype Kpi = { label: string; value: number; suffix?: string; change: string }; // change carries its sign: \"+12%\"\ntype Source = { id: string; source: string; signups: number; conversion: string };\ntype Data = { kpis: Kpi[]; trend: LineChartDatum[]; sources: Source[] };\ntype Props = {\n  range: string;\n  onRangeChange: (range: string) => void;\n  state: { status: \"loading\" } | { status: \"error\"; retry: () => void } | { status: \"ready\"; data: Data };\n  onExport: () => void;\n};\n\nconst ranges = [{ value: \"7d\", label: \"7 days\" }, { value: \"30d\", label: \"30 days\" }, { value: \"90d\", label: \"90 days\" }];\n\nexport function Overview({ range, onRangeChange, state, onExport }: Props) {\n  return (\n    <main className={styles.page}>\n      <header className={styles.header}>\n        <h1 className={styles.title}>Signups</h1>\n        <div className={styles.tools}>\n          <SegmentedControl label=\"Range\" options={ranges} value={range} onValueChange={onRangeChange} />\n          <Button onClick={onExport}><Download size={16} strokeWidth={1.75} aria-hidden=\"true\" />Export</Button>\n        </div>\n      </header>\n\n      {state.status === \"error\" && (\n        <Alert tone=\"danger\" title=\"Signups could not load\">\n          <Button variant=\"secondary\" size=\"sm\" onClick={state.retry}>Try again</Button>\n        </Alert>\n      )}\n\n      <section className={styles.kpis} aria-label=\"Key numbers\" aria-busy={state.status === \"loading\"}>\n        {state.status === \"ready\"\n          ? state.data.kpis.map(kpi => <MetricCard key={kpi.label} label={kpi.label} value={kpi.value} suffix={kpi.suffix} change={kpi.change} context=\"vs previous period\" />)\n          : [0, 1, 2, 3].map(i => <Skeleton key={i} lines={2} className={styles.kpiSkeleton} />)}\n      </section>\n\n      <section className={styles.card} aria-label=\"Signups over time\">\n        {state.status === \"ready\"\n          ? <LineChart label=\"Signups\" data={state.data.trend} series={[{ key: \"signups\", label: \"Signups\" }]} height={280} />\n          : <Skeleton lines={6} />}\n      </section>\n\n      <section className={styles.card} aria-label=\"Top sources\">\n        {state.status !== \"ready\" ? <Skeleton lines={5} /> : state.data.sources.length === 0\n          ? <EmptyState title=\"No sources yet\" description=\"Sources appear after your first tracked signup.\" />\n          : <div className={styles.tableScroll}>\n              <SortableDataTable rows={state.data.sources} rowKey=\"id\" caption=\"Top sources\"\n                columns={[\n                  { key: \"source\", label: \"Source\" },\n                  { key: \"signups\", label: \"Signups\", numeric: true, sortable: true },\n                  { key: \"conversion\", label: \"Conversion\", numeric: true },\n                ]}\n                defaultSort={{ key: \"signups\", direction: \"desc\" }} />\n            </div>}\n      </section>\n    </main>\n  );\n}\n```\n\n## overview.module.css\n\n```css\n.page { width: 100%; max-width: 1200px; margin-inline: auto; padding: 32px clamp(16px, 4vw, 32px); display: grid; gap: 24px; }\n.page > * { min-width: 0; }\n.header { display: flex; flex-wrap: wrap; align-items: center; justify-content: space-between; gap: 16px; }\n.title { margin: 0; font-family: var(--font-display); font-size: var(--text-3xl); font-weight: 500; letter-spacing: var(--tracking-display); line-height: var(--leading-display); color: var(--foreground); }\n.tools { display: flex; flex-wrap: wrap; align-items: center; gap: 12px; }\n.kpis { display: grid; grid-template-columns: repeat(auto-fit, minmax(200px, 1fr)); gap: 16px; align-items: stretch; }\n.kpiSkeleton { min-height: 112px; }\n.card { border: 1px solid var(--border); border-radius: var(--radius-surface); background: var(--surface); padding: 24px; overflow: hidden; }\n.tableScroll { overflow-x: auto; overscroll-behavior-x: contain; margin: -24px; padding: 8px; }\n```\n\n## Why it passes the checklist\n\n- One container; header, KPI row, chart, and table share the same left edge; gaps 24px between regions and 16px between cards.\n- `segmented-control` for a view of the same data, one primary button (Export uses the default variant; Try again is `secondary`), the export icon is plain and `aria-hidden`.\n- Every region has loading, error, and empty states in its final layout; `aria-busy` while loading.\n- The table scrolls inside its card; values are right-aligned numeric columns with tabular numerals from the component.\n- Data arrives as props, so the first render is the same on server and client.\n"},{"path":"skills/arc/example-pricing.md","type":"registry:file","target":"~/.claude/skills/arc/example-pricing.md","content":"# Example: pricing section\n\nRequest: \"Add a pricing section with three plans, monthly and yearly billing, a feature comparison, and an FAQ.\"\n\n## Plan\n\n```\nJob: pick a plan and understand what the price includes\nPrimary action: one per plan card; the recommended plan's button is the only primary\nRegions: heading, billing-toggle, three plan cards with BillingPrice, comparison-table, faq-section\nStates: prices roll when billing changes (BillingPrice), the table can hide identical rows and stacks on phones\n```\n\nChoices: `billing-toggle` rather than `segmented-control` (it carries the savings badge and pairs with `BillingPrice`); `comparison-table` with your plans as columns rather than `plan-comparison` (a fixed two-plan demo); `faq-section` with props.\n\n```bash\nnpx shadcn@latest add @uiarc/billing-toggle @uiarc/button @uiarc/badge @uiarc/comparison-table @uiarc/faq-section\n```\n\n## pricing.tsx\n\n```tsx\n\"use client\";\n\nimport { useId, useState } from \"react\";\nimport { Check } from \"lucide-react\";\nimport { Badge } from \"@/components/arc/badge/badge\";\nimport { BillingPrice, BillingToggle } from \"@/components/arc/billing-toggle/billing-toggle\";\nimport { Button } from \"@/components/arc/button/button\";\nimport { ComparisonTable, type ComparisonSection } from \"@/components/arc/blocks/comparison-table/comparison-table\";\nimport { FaqSection } from \"@/components/arc/blocks/faq-section/faq-section\";\nimport styles from \"./pricing.module.css\";\n\nconst plans = [\n  { id: \"starter\", name: \"Starter\", monthly: 0, yearly: 0, blurb: \"For one person trying things out.\", cta: \"Start free\", points: [\"3 projects\", \"Community support\"] },\n  { id: \"team\", name: \"Team\", monthly: 24, yearly: 19, blurb: \"For small teams shipping together.\", cta: \"Start 14-day trial\", points: [\"Unlimited projects\", \"Shared workspaces\", \"Email support\"], recommended: true },\n  { id: \"business\", name: \"Business\", monthly: 49, yearly: 39, blurb: \"For companies with review and security needs.\", cta: \"Talk to sales\", points: [\"Everything in Team\", \"SSO and audit log\", \"Priority support\"] },\n];\n\nconst sections: ComparisonSection[] = [\n  { id: \"core\", title: \"Core\", rows: [\n    { id: \"projects\", feature: \"Projects\", values: { starter: \"3\", team: \"Unlimited\", business: \"Unlimited\" } },\n    { id: \"history\", feature: \"Version history\", values: { starter: \"7 days\", team: \"90 days\", business: \"Unlimited\" } },\n  ] },\n  { id: \"security\", title: \"Security\", rows: [\n    { id: \"sso\", feature: \"Single sign-on\", values: { starter: false, team: false, business: true } },\n    { id: \"audit\", feature: \"Audit log\", values: { starter: false, team: false, business: true } },\n  ] },\n];\n\nconst faq = [\n  { question: \"Can I switch plans later?\", answer: \"Yes. Upgrades apply right away and downgrades at the end of the billing period.\" },\n  { question: \"What happens after the trial?\", answer: \"You choose a plan or stay on Starter. Nothing is charged without your confirmation.\" },\n];\n\nexport function Pricing({ onChoose }: { onChoose: (planId: string, period: string) => void }) {\n  const id = useId();\n  const [period, setPeriod] = useState(\"yearly\");\n  const yearly = period === \"yearly\";\n\n  return (\n    <section className={styles.section} aria-labelledby={`${id}-title`}>\n      <header className={styles.header}>\n        <h2 id={`${id}-title`} className={styles.title}>Pricing that grows with your team</h2>\n        <p className={styles.lede}>Start free. Upgrade when you invite your first teammate.</p>\n        <BillingToggle value={period} onValueChange={setPeriod} />\n      </header>\n\n      <ul className={styles.plans}>\n        {plans.map(plan => (\n          <li key={plan.id} className={styles.plan} data-recommended={plan.recommended || undefined}>\n            <div className={styles.planHead}>\n              <h3 className={styles.planName}>{plan.name}</h3>\n              {plan.recommended && <Badge tone=\"info\" size=\"sm\">Recommended</Badge>}\n            </div>\n            <BillingPrice amount={yearly ? plan.yearly : plan.monthly} was={yearly && plan.monthly > plan.yearly ? plan.monthly : undefined}\n              period={plan.monthly === 0 ? \"forever\" : yearly ? \"per seat per month, billed yearly\" : \"per seat per month\"} />\n            <p className={styles.blurb}>{plan.blurb}</p>\n            <ul className={styles.points}>\n              {plan.points.map(point => <li key={point}><Check size={16} strokeWidth={1.75} aria-hidden=\"true\" />{point}</li>)}\n            </ul>\n            <Button variant={plan.recommended ? \"primary\" : \"secondary\"} className={styles.cta} onClick={() => onChoose(plan.id, period)}>{plan.cta}</Button>\n          </li>\n        ))}\n      </ul>\n\n      <ComparisonTable title=\"Compare plans\" description=\"What each plan includes.\"\n        columns={plans.map(({ id, name, recommended }) => ({ id, name, highlight: recommended }))} sections={sections} stickyTop={64} />\n      <FaqSection title=\"Questions about billing\" items={faq} contact={{ label: \"Talk to billing\", href: \"mailto:billing@example.com\" }} />\n    </section>\n  );\n}\n```\n\n## pricing.module.css\n\n```css\n.section { display: grid; gap: 64px; padding-block: clamp(64px, 10vw, 120px); }\n.header { display: grid; justify-items: center; gap: 16px; text-align: center; }\n.title { margin: 0; font-family: var(--font-display); font-size: clamp(var(--text-3xl), 5vw, var(--text-4xl)); font-weight: 500; letter-spacing: var(--tracking-display); line-height: var(--leading-display); color: var(--foreground); text-wrap: balance; }\n.lede { margin: 0; max-width: 48ch; font-size: var(--text-lg); color: var(--text-secondary); }\n.plans { display: grid; grid-template-columns: repeat(auto-fit, minmax(260px, 1fr)); gap: 16px; margin: 0; padding: 0; list-style: none; align-items: stretch; }\n.plan { display: flex; flex-direction: column; gap: 16px; padding: 24px; border: 1px solid var(--border); border-radius: var(--radius-surface); background: var(--surface); min-width: 0; }\n.plan[data-recommended] { border-color: var(--border-strong); }\n.planHead { display: flex; align-items: center; justify-content: space-between; gap: 8px; }\n.planName { margin: 0; font-size: var(--text-lg); font-weight: 500; color: var(--foreground); }\n.blurb { margin: 0; font-size: var(--text-sm); color: var(--text-secondary); }\n.points { display: grid; gap: 8px; margin: 0; padding: 0; list-style: none; font-size: var(--text-sm); color: var(--foreground); }\n.points li { display: flex; align-items: center; gap: 8px; }\n.points svg { color: var(--text-secondary); flex: none; }\n.cta { margin-top: auto; width: 100%; }\n```\n\n`onChoose` starts checkout or opens sign up; the buttons act, so they are buttons. A CTA that only navigates is a link (`<a>` styled in your module, or a block action with `href`).\n\nPlace `<Pricing onChoose={...} />` inside the page's one container; the section adds vertical rhythm only, no gutters or max width of its own.\n\n## Why it passes the checklist\n\n- No eyebrow above the heading, sentence case, no em dashes, prices roll with tabular numerals (`BillingPrice`).\n- Cards are siblings with equal height and a 16px gap; the buttons align at the bottom (`margin-top: auto`).\n- Accent appears only on the recommended badge, the selected billing option, and the recommended plan's column in the table. No gradient on the cards.\n- One primary button (the recommended plan). Claims are about the product, not invented social proof.\n- Optional premium touch: the recommended card may use the metallic treatment from design.md instead of `--border-strong`, but only one card.\n"},{"path":"skills/arc/example-settings.md","type":"registry:file","target":"~/.claude/skills/arc/example-settings.md","content":"# Example: account settings page\n\nRequest: \"Add a settings page where people edit their profile, choose notifications, and can delete their account.\"\n\n## Plan\n\n```\nJob: update profile and notification preferences, or delete the account\nPrimary action: Save changes\nRegions: profile fields (input, select), notifications (switch rows), danger zone (confirm-morph)\nStates: saving (button loading), saved (button label), save error (inline alert), delete pending and done (confirm-morph)\n```\n\nChoices: `switch` because each preference applies on its own and reads as on or off; `select` for time zone (long list); `confirm-morph` instead of a dialog because the consequence fits in one line.\n\n```bash\nnpx shadcn@latest add @uiarc/input @uiarc/select @uiarc/switch @uiarc/button @uiarc/alert @uiarc/confirm-morph\n```\n\n## settings-form.tsx\n\n```tsx\n\"use client\";\n\nimport { useId, useState, type FormEvent } from \"react\";\nimport { Trash2 } from \"lucide-react\";\nimport { Alert } from \"@/components/arc/alert/alert\";\nimport { Button } from \"@/components/arc/button/button\";\nimport { ConfirmMorph } from \"@/components/arc/confirm-morph/confirm-morph\";\nimport { Input } from \"@/components/arc/input/input\";\nimport { Select } from \"@/components/arc/select/select\";\nimport { Switch } from \"@/components/arc/switch/switch\";\nimport styles from \"./settings.module.css\";\n\ntype Profile = { name: string; email: string; timeZone: string };\ntype Props = {\n  initial: Profile;\n  saveProfile: (profile: Profile) => Promise<void>;\n  deleteAccount: () => Promise<void>;\n};\n\nconst zones = [\n  { value: \"Europe/Zurich\", label: \"Zurich (UTC+1)\" },\n  { value: \"America/New_York\", label: \"New York (UTC-5)\" },\n  { value: \"Asia/Tokyo\", label: \"Tokyo (UTC+9)\" },\n];\n\nconst preferences = [\n  { id: \"mentions\", title: \"Mentions\", description: \"When someone mentions you in a comment.\" },\n  { id: \"digest\", title: \"Weekly summary\", description: \"A Monday email with last week's activity.\" },\n];\n\nexport function SettingsForm({ initial, saveProfile, deleteAccount }: Props) {\n  const id = useId();\n  const [profile, setProfile] = useState(initial);\n  const [notify, setNotify] = useState<Record<string, boolean>>({ mentions: true, digest: false });\n  const [status, setStatus] = useState<\"idle\" | \"saving\" | \"saved\" | \"error\">(\"idle\");\n  const dirty = status !== \"saving\" && JSON.stringify(profile) !== JSON.stringify(initial);\n\n  async function save(event: FormEvent) {\n    event.preventDefault();\n    setStatus(\"saving\");\n    try { await saveProfile(profile); setStatus(\"saved\"); } catch { setStatus(\"error\"); }\n  }\n\n  return (\n    <div className={styles.stack}>\n      <form className={styles.section} onSubmit={save} aria-labelledby={`${id}-profile`}>\n        <h2 id={`${id}-profile`} className={styles.heading}>Profile</h2>\n        <div className={styles.fields}>\n          <Input label=\"Name\" autoComplete=\"name\" value={profile.name}\n            onChange={e => { setProfile({ ...profile, name: e.target.value }); setStatus(\"idle\"); }} />\n          <Input label=\"Email\" type=\"email\" autoComplete=\"email\" value={profile.email}\n            description=\"We send receipts and sign-in codes here.\"\n            onChange={e => { setProfile({ ...profile, email: e.target.value }); setStatus(\"idle\"); }} />\n          <Select label=\"Time zone\" options={zones} value={profile.timeZone}\n            onValueChange={timeZone => { setProfile({ ...profile, timeZone }); setStatus(\"idle\"); }} />\n        </div>\n        {status === \"error\" && <Alert tone=\"danger\" title=\"Your changes were not saved\">Check your connection and try again.</Alert>}\n        <div className={styles.actions}>\n          <Button type=\"submit\" loading={status === \"saving\"} disabled={!dirty && status !== \"error\"}>\n            {status === \"saved\" ? \"Saved\" : \"Save changes\"}\n          </Button>\n        </div>\n      </form>\n\n      <section className={styles.section} aria-labelledby={`${id}-notify`}>\n        <h2 id={`${id}-notify`} className={styles.heading}>Notifications</h2>\n        <div className={styles.group}>\n          {preferences.map(pref => (\n            <div key={pref.id} className={styles.row}>\n              <div className={styles.rowText}>\n                <span id={`${id}-${pref.id}`} className={styles.rowTitle}>{pref.title}</span>\n                <span id={`${id}-${pref.id}-hint`} className={styles.rowHint}>{pref.description}</span>\n              </div>\n              <Switch aria-labelledby={`${id}-${pref.id}`} aria-describedby={`${id}-${pref.id}-hint`}\n                checked={notify[pref.id]} onCheckedChange={on => setNotify({ ...notify, [pref.id]: on })} />\n            </div>\n          ))}\n        </div>\n      </section>\n\n      <section className={styles.section} aria-labelledby={`${id}-delete`}>\n        <h2 id={`${id}-delete`} className={styles.heading}>Delete account</h2>\n        <div className={styles.group}>\n          <div className={styles.row}>\n            <p className={styles.rowHint}>Removes your profile and projects for everyone. This cannot be undone.</p>\n            <ConfirmMorph label=\"Delete account\" icon={<Trash2 size={16} strokeWidth={1.75} aria-hidden=\"true\" />}\n              prompt=\"Delete your account?\" confirmLabel=\"Delete\" onConfirm={deleteAccount} />\n          </div>\n        </div>\n      </section>\n    </div>\n  );\n}\n```\n\nThe page (`page.tsx`) is a server component: `<main className={styles.page}><h1 className={styles.title}>Settings</h1><SettingsForm ... /></main>`. This example owns the page container. If your app layout already renders one, keep only `max-width: 720px` on `.page` and drop its padding and `margin-inline`.\n\n## settings.module.css\n\n```css\n.page { width: 100%; max-width: 720px; margin-inline: auto; padding: 32px clamp(16px, 4vw, 32px); display: grid; gap: 32px; }\n.title { margin: 0; font-family: var(--font-display); font-size: var(--text-3xl); font-weight: 500; letter-spacing: var(--tracking-display); line-height: var(--leading-display); color: var(--foreground); }\n.stack { display: grid; gap: 40px; }\n.section { display: grid; gap: 16px; min-width: 0; }\n.heading { margin: 0; font-size: var(--text-lg); font-weight: 500; color: var(--foreground); }\n.fields { display: grid; gap: 16px; }\n.actions { display: flex; justify-content: flex-end; }\n.group { border: 1px solid var(--border); border-radius: var(--radius-surface); background: var(--surface); }\n.row { display: flex; align-items: center; justify-content: space-between; gap: 16px; min-height: 64px; padding: 16px 24px; }\n.row + .row { border-top: 1px solid var(--border-subtle); }\n.rowText { display: grid; gap: 2px; min-width: 0; }\n.rowTitle { font-size: var(--text-sm); font-weight: 500; color: var(--foreground); }\n.rowHint { margin: 0; font-size: var(--text-sm); color: var(--text-secondary); }\n@media (max-width: 560px) { .row { flex-direction: column; align-items: flex-start; } }\n```\n\n## Why it passes the checklist\n\n- One container (720px, fluid gutters), one `h1`, one primary button; sections are plain headings with no eyebrow.\n- Notification rows are one bordered group with hairline dividers, not a card per row.\n- Save confirms in place (\"Saved\"), errors appear inline next to the action, delete confirms inline with its own pending and done states.\n- Only semantic tokens; weights 400 and 500; no focus styles added.\n"},{"path":"skills/arc/motion.md","type":"registry:file","target":"~/.claude/skills/arc/motion.md","content":"# Arc motion\n\nMotion shows cause and effect: what opened, what changed, where it came from, what is ready next. If an animation explains nothing, remove it.\n\n## Contents\n- Tokens\n- Choosing a spring\n- Rules\n- Patterns with code\n- Reduced motion\n\n## Tokens\n\nImport from `@/components/arc/lib/motion-tokens` (installed with the first Arc item).\n\n| Token | Value | Use for |\n| --- | --- | --- |\n| `spring.smooth` | 0.4s, bounce 0 | Panels, height, drawers, progress, layout shifts. Never overshoots |\n| `spring.snappy` | 0.26s, bounce 0.12 | Press feedback, small indicators, icon swaps |\n| `spring.morph` | 0.42s, bounce 0.16 | Shared highlights (`layoutId`), width that follows new content, shape morphs |\n| `duration.instant` / `fast` / `exit` / `standard` / `considered` | 0.12 / 0.16 / 0.18 / 0.24 / 0.48s | Tweens for color, opacity, and small fades |\n| `ease.enter`, `ease.exit`, `ease.standard`, `ease.inOut` | cubic-bezier arrays | Entrances, exits, color changes, on-screen moves |\n| `stagger.item` / `line` / `word` / `char` | 0.035 / 0.08 / 0.04 / 0.016s | Lists and text, total under about 0.4s |\n| `blur.subtle` / `soft` / `text` | 2 / 4 / 8px | Brief crossfades only |\n\nCSS transitions use the matching variables: `var(--duration-fast)` with `var(--ease-standard)` for color and opacity, `var(--duration-spring)` (580ms) with `var(--ease-spring)` for transforms. CSS has `--duration-instant`, `-fast`, `-standard`, `-considered`, and `-spring`; there is no `--duration-exit`.\n\n## Choosing a spring\n\n- **Anything that reports state lands without overshoot**: a switch thumb, a drawer edge, a panel height, a progress fill, a value. Use `spring.smooth` (or another `bounce: 0` spring). An overshoot there briefly shows a state that is not true.\n- **Small life is for feedback**: `spring.snappy` on a press, `spring.morph` for a selection highlight gliding between options.\n- **Visible bounce is for playful moments only**: a reaction, a celebration, a physics toy. Never on routine product UI.\n\n## Rules\n\n1. Animate `transform` and `opacity` (and brief `filter: blur`). Animate `width` or `height` only when the size change is the information, and then on a spring.\n2. **One continuous gesture per interaction.** A state change is one spatial movement, not a fade, then a slide, then a scale on separate timings.\n3. Everything is interruptible: use springs for anything the user can reverse, so reversing mid-way never jumps.\n4. Nothing resizes in one frame. Animate the size or reserve the space.\n5. Numbers count to their new value with `font-variant-numeric: tabular-nums` and a stable width (`animated-counter`, `BillingPrice`).\n6. Presses scale to about 0.97, except an element that anchors a popover or menu: answer that press with color, because the popup positions against the pressed size.\n7. Exits are faster than entrances (`duration.exit`, `ease.exit`).\n8. One orchestrated entrance per page at most. No scroll reveal on every section, no loops unless they show live status.\n9. Keep the animated element mounted. Changing its `key` or conditionally swapping its component restarts the animation (see composition.md).\n\n## Patterns with code\n\nSelected highlight that glides between options (what `segmented-control` and `tabs` do):\n\n```tsx\nimport { motion, useReducedMotion } from \"motion/react\";\nimport { motionTokens } from \"@/components/arc/lib/motion-tokens\";\n\nconst reduce = useReducedMotion();\n{options.map(option => (\n  <button key={option.value} onClick={() => setValue(option.value)} aria-pressed={value === option.value}>\n    {value === option.value && (\n      <motion.span layoutId=\"view-highlight\" className={styles.highlight}\n        transition={reduce ? { duration: 0 } : motionTokens.spring.morph} aria-hidden=\"true\" />\n    )}\n    <span className={styles.label}>{option.label}</span>\n  </button>\n))}\n```\n\nPanel that opens with height and opacity together, no overshoot:\n\n```tsx\n<AnimatePresence initial={false}>\n  {open && (\n    <motion.div key=\"details\"\n      initial={{ height: 0, opacity: 0 }}\n      animate={{ height: \"auto\", opacity: 1 }}\n      exit={{ height: 0, opacity: 0, transition: { duration: motionTokens.duration.exit, ease: [...motionTokens.ease.exit] } }}\n      transition={reduce ? { duration: 0 } : motionTokens.spring.smooth}\n      style={{ overflow: \"hidden\" }}>\n      {children}\n    </motion.div>\n  )}\n</AnimatePresence>\n```\n\nHover and press in CSS:\n\n```css\n.row { transition: background-color var(--duration-fast) var(--ease-standard); }\n.row:hover, .row[data-selected] { background: var(--surface-muted); }\n.press { transition: transform var(--duration-spring) var(--ease-spring); }\n.press:active { transform: scale(.97); }\n@media (prefers-reduced-motion: reduce) { .press, .row { transition: none; } }\n```\n\nSave confirmation in place: pass the promise to the Arc item (`onConfirm`, `onSave`) or set `loading` on `button`, then change its label to \"Saved\". Do not add a toast for a foreground action.\n\n## Reduced motion\n\nEvery animation has a branch:\n\n```tsx\nconst reduce = useReducedMotion();\n<motion.div transition={reduce ? { duration: 0 } : motionTokens.spring.smooth} />\n```\n\nKeep the final state, focus, and feedback. Remove travel, loops, parallax, and autoplay. A counter jumps straight to its value; a panel appears at full height.\n"},{"path":"skills/arc/responsive.md","type":"registry:file","target":"~/.claude/skills/arc/responsive.md","content":"# Responsive Arc\n\nArc components fit their container. Your page layout decides the widths.\n\n## Widths to check\n\nRender at **390, 768, 1024, and 1440px** (and 320px for anything with long labels or tables). At every width:\n\n- No sideways page scroll. The only horizontal scrollers are code blocks, wide tables, and segmented rows, each inside its own container.\n- Nothing is clipped, overlapped, or cut mid-word.\n- The primary action is visible without hunting.\n\n## Layout\n\n- Gutters are 16px on phones and grow with width (`padding-inline: clamp(16px, 4vw, 32px)`). Internal control spacing stays fixed.\n- Collapse multi-column layouts to one column below about 800px. Settings rows stack label above control below about 560px.\n- Grid and flex children get `min-width: 0`; user content gets `overflow-wrap: anywhere`.\n- Never `width: 100vw` inside the page (it includes the scrollbar). Use `width: 100%`.\n- Reading measure stays near 65 characters (`max-width: 65ch` on long text).\n- Prefer container queries for component-level changes and media queries for page layout.\n\n## Tables and charts\n\n- Wide tables scroll inside their card (`overflow-x: auto` on a wrapper inside the bordered card), or switch to a stacked list on phones. The page itself never scrolls sideways.\n- `comparison-table` stacks into two columns below `stackBelow` (640px by default) and keeps a sticky header offset by `stickyTop`.\n- Charts (`line-chart`, `bar-chart`, `sparkline`, `activity-heatmap`) follow their container width. Set height with the `height` prop when there is one.\n\n## Touch\n\n- Controls use `--control-height-md` (40px), with small icon buttons keeping a 40px touch area. Keep at least 8px between adjacent targets.\n- Hover is an enhancement. Anything shown on hover (`hover-card`, `tooltip`, row actions) is also reachable by tap or focus.\n- Gestures (`swipe-actions`, `bottom-sheet`) always have a button path.\n- On phones, prefer `bottom-sheet` for tasks and long menus; keep `popover` for small choices. `user-menu` already opens as a sheet on phones.\n\n## Type\n\n- Hero and section headings scale with `clamp()` between two steps of the scale, for example `font-size: clamp(var(--text-3xl), 5vw, var(--text-5xl))`.\n- Body text stays at `--text-base` or `--text-sm`. Nothing below `--text-xs`.\n- The type scale is compact at every width (body 15, secondary 13, caption 12, headings 20 to 40). Use tokens for every font size, and `--text-field` for text people type (16px on phones, so iOS never zooms on focus).\n\n## Before placing a component\n\nEach item's markdown has a \"Responsive behavior\" section (`https://uiarc.dev/components/<id>/markdown`). Read it before putting the item in a narrow column, and pass its props (such as `stackBelow` or `stickyTop`) instead of wrapping it in your own media queries.\n"}],"docs":"Installed to .claude/skills/arc/. SKILL.md is the entry point; INSTRUCTIONS.md holds the rules to keep in AGENTS.md or CLAUDE.md. Raw copies live at /r/skills/arc/<file>.","meta":{"tier":"free","kind":"skill","docs":"https://uiarc.dev/docs/ai"}}