组件组合：为什么"无样式 + 复制粘贴"赢了元件組合：為什麼「無樣式 + 複製貼上」贏了Component composition: why headless + copy-paste wonコンポーネント合成：ヘッドレス＋コピペが勝った理由컴포넌트 합성: 헤드리스 + 복붙이 이긴 이유Komposisi komponen: mengapa headless + salin-tampal menangKết hợp component: vì sao headless + copy-paste thắngComposition de composants : pourquoi headless + copier-coller a gagnéComposición de componentes: por qué headless + copiar y pegar ganóKomponenten-Komposition: warum Headless + Copy-Paste gewonnen hat

你在一个 React 代码库里工作，结构是：无头原语（Radix / React Aria / Ark）+ 带样式的组件层（shadcn 式，源码在本仓库）+ 页面区块。
任务：新建一个区块：<描述这个区块>。
规则：
1. 先列出要用的组件，以及缺少的组件。新建组件之前先停下来问我。
2. 只用组件和布局工具类拼装。不要 <div onClick>，不要嵌套可交互元素；原语部件包裹组件时使用 asChild。
3. 不要修改原语层的文件。任何地方都不要再建第二个 Button/Input/Card。
4. 新的样式选项加到组件的变体表（cva）里，使用现有 token 类名。
5. 每个弹层/对话框/菜单都要实现键盘操作和焦点回归。
输出：组件清单 → 代码 → 指出哪些组合已在 3 个以上区块出现、应该提升为组件。

你在一个 React 代码库里工作，结构是：无头原语（Radix / React Aria / Ark）+ 带样式的组件层（shadcn 式，源码在本仓库）+ 页面区块。
任务：新建一个区块：<描述这个区块>。
规则：
1. 先列出要用的组件，以及缺少的组件。新建组件之前先停下来问我。
2. 只用组件和布局工具类拼装。不要 <div onClick>，不要嵌套可交互元素；原语部件包裹组件时使用 asChild。
3. 不要修改原语层的文件。任何地方都不要再建第二个 Button/Input/Card。
4. 新的样式选项加到组件的变体表（cva）里，使用现有 token 类名。
5. 每个弹层/对话框/菜单都要实现键盘操作和焦点回归。
输出：组件清单 → 代码 → 指出哪些组合已在 3 个以上区块出现、应该提升为组件。

You are working in a React codebase that uses headless primitives (Radix / React Aria / Ark) + a styled kit (shadcn-style, source in this repo) + page blocks.
Task: build <describe the block> as a new block.
Rules:
1. First list the kit components you will use and any that are missing. Stop and ask before creating a new kit component.
2. Compose only from kit components and layout utilities. No <div onClick>, no nested interactive elements; use asChild when a primitive part wraps a kit component.
3. Do not edit files in the primitives layer. Do not create a second Button/Input/Card anywhere.
4. New styling options go into the component's variants table (cva), using existing token classes.
5. Implement keyboard behaviour and focus return for every popover/dialog/menu.
Output: component list → code → a note on anything that appears in 3+ blocks and should be promoted to the kit.

You are working in a React codebase that uses headless primitives (Radix / React Aria / Ark) + a styled kit (shadcn-style, source in this repo) + page blocks.
Task: build <describe the block> as a new block.
Rules:
1. First list the kit components you will use and any that are missing. Stop and ask before creating a new kit component.
2. Compose only from kit components and layout utilities. No <div onClick>, no nested interactive elements; use asChild when a primitive part wraps a kit component.
3. Do not edit files in the primitives layer. Do not create a second Button/Input/Card anywhere.
4. New styling options go into the component's variants table (cva), using existing token classes.
5. Implement keyboard behaviour and focus return for every popover/dialog/menu.
Output: component list → code → a note on anything that appears in 3+ blocks and should be promoted to the kit.

You are working in a React codebase that uses headless primitives (Radix / React Aria / Ark) + a styled kit (shadcn-style, source in this repo) + page blocks.
Task: build <describe the block> as a new block.
Rules:
1. First list the kit components you will use and any that are missing. Stop and ask before creating a new kit component.
2. Compose only from kit components and layout utilities. No <div onClick>, no nested interactive elements; use asChild when a primitive part wraps a kit component.
3. Do not edit files in the primitives layer. Do not create a second Button/Input/Card anywhere.
4. New styling options go into the component's variants table (cva), using existing token classes.
5. Implement keyboard behaviour and focus return for every popover/dialog/menu.
Output: component list → code → a note on anything that appears in 3+ blocks and should be promoted to the kit.

You are working in a React codebase that uses headless primitives (Radix / React Aria / Ark) + a styled kit (shadcn-style, source in this repo) + page blocks.
Task: build <describe the block> as a new block.
Rules:
1. First list the kit components you will use and any that are missing. Stop and ask before creating a new kit component.
2. Compose only from kit components and layout utilities. No <div onClick>, no nested interactive elements; use asChild when a primitive part wraps a kit component.
3. Do not edit files in the primitives layer. Do not create a second Button/Input/Card anywhere.
4. New styling options go into the component's variants table (cva), using existing token classes.
5. Implement keyboard behaviour and focus return for every popover/dialog/menu.
Output: component list → code → a note on anything that appears in 3+ blocks and should be promoted to the kit.

You are working in a React codebase that uses headless primitives (Radix / React Aria / Ark) + a styled kit (shadcn-style, source in this repo) + page blocks.
Task: build <describe the block> as a new block.
Rules:
1. First list the kit components you will use and any that are missing. Stop and ask before creating a new kit component.
2. Compose only from kit components and layout utilities. No <div onClick>, no nested interactive elements; use asChild when a primitive part wraps a kit component.
3. Do not edit files in the primitives layer. Do not create a second Button/Input/Card anywhere.
4. New styling options go into the component's variants table (cva), using existing token classes.
5. Implement keyboard behaviour and focus return for every popover/dialog/menu.
Output: component list → code → a note on anything that appears in 3+ blocks and should be promoted to the kit.

You are working in a React codebase that uses headless primitives (Radix / React Aria / Ark) + a styled kit (shadcn-style, source in this repo) + page blocks.
Task: build <describe the block> as a new block.
Rules:
1. First list the kit components you will use and any that are missing. Stop and ask before creating a new kit component.
2. Compose only from kit components and layout utilities. No <div onClick>, no nested interactive elements; use asChild when a primitive part wraps a kit component.
3. Do not edit files in the primitives layer. Do not create a second Button/Input/Card anywhere.
4. New styling options go into the component's variants table (cva), using existing token classes.
5. Implement keyboard behaviour and focus return for every popover/dialog/menu.
Output: component list → code → a note on anything that appears in 3+ blocks and should be promoted to the kit.

You are working in a React codebase that uses headless primitives (Radix / React Aria / Ark) + a styled kit (shadcn-style, source in this repo) + page blocks.
Task: build <describe the block> as a new block.
Rules:
1. First list the kit components you will use and any that are missing. Stop and ask before creating a new kit component.
2. Compose only from kit components and layout utilities. No <div onClick>, no nested interactive elements; use asChild when a primitive part wraps a kit component.
3. Do not edit files in the primitives layer. Do not create a second Button/Input/Card anywhere.
4. New styling options go into the component's variants table (cva), using existing token classes.
5. Implement keyboard behaviour and focus return for every popover/dialog/menu.
Output: component list → code → a note on anything that appears in 3+ blocks and should be promoted to the kit.

You are working in a React codebase that uses headless primitives (Radix / React Aria / Ark) + a styled kit (shadcn-style, source in this repo) + page blocks.
Task: build <describe the block> as a new block.
Rules:
1. First list the kit components you will use and any that are missing. Stop and ask before creating a new kit component.
2. Compose only from kit components and layout utilities. No <div onClick>, no nested interactive elements; use asChild when a primitive part wraps a kit component.
3. Do not edit files in the primitives layer. Do not create a second Button/Input/Card anywhere.
4. New styling options go into the component's variants table (cva), using existing token classes.
5. Implement keyboard behaviour and focus return for every popover/dialog/menu.
Output: component list → code → a note on anything that appears in 3+ blocks and should be promoted to the kit.