Cult UI 深读：有手感、有个性的组件Cult UI 深讀：有手感、有個性的元件Cult UI deep dive: tactile components with personalityCult UI徹底解説：触感と個性のある部品Cult UI 심층 분석: 촉감과 개성이 있는 컴포넌트Cult UI mendalam: komponen taktil berperibadiCult UI chuyên sâu: component có cảm giác và cá tínhCult UI en profondeur : des composants tactiles avec du caractèreCult UI a fondo: componentes táctiles con personalidadCult UI im Detail: taktile Komponenten mit Charakter

我想把一个 Cult UI 组件（<组件名>）加入这个基于 shadcn 的项目，作为我们唯一的标志性交互。
1. 读组件源码（我会粘贴或给你文件）。总结它的属性、依赖（如 motion），以及所有写死的颜色、圆角、阴影和弹簧数值。
2. 把它放进组件目录，和其他组件放在一起；确保仓库里只有一份。
3. 用我们的 token（<token 文件>）替换写死的样式，用 motion.ts 里的预设替换它的弹簧参数（没有的话就新建 snappy/soft 两个预设）。
4. 补上演示缺少的无障碍：真正的 <button> 或正确角色、可见焦点、键盘支持、aria-expanded/aria-controls；如果内容变化而焦点不动，加实时区域。
5. 用 useReducedMotion 加减少动态效果的降级。
6. 只在 hover 时出现的内容，要提供点击或常显的替代方式。
输出：先给总结，再给 diff，最后列出仍与我们设计系统不一致的地方。提醒我检查仓库许可证。

我想把一个 Cult UI 组件（<组件名>）加入这个基于 shadcn 的项目，作为我们唯一的标志性交互。
1. 读组件源码（我会粘贴或给你文件）。总结它的属性、依赖（如 motion），以及所有写死的颜色、圆角、阴影和弹簧数值。
2. 把它放进组件目录，和其他组件放在一起；确保仓库里只有一份。
3. 用我们的 token（<token 文件>）替换写死的样式，用 motion.ts 里的预设替换它的弹簧参数（没有的话就新建 snappy/soft 两个预设）。
4. 补上演示缺少的无障碍：真正的 <button> 或正确角色、可见焦点、键盘支持、aria-expanded/aria-controls；如果内容变化而焦点不动，加实时区域。
5. 用 useReducedMotion 加减少动态效果的降级。
6. 只在 hover 时出现的内容，要提供点击或常显的替代方式。
输出：先给总结，再给 diff，最后列出仍与我们设计系统不一致的地方。提醒我检查仓库许可证。

I want to add one Cult UI component (<component name>) to this shadcn-based project as our single signature interaction.
1. Read the component's source (I will paste it or give you the file). Summarise its props, its dependencies (e.g. motion) and every hard-coded colour, radius, shadow and spring value.
2. Place it in the kit folder next to the other components; make sure there is only one copy in the repo.
3. Replace hard-coded styling with our tokens (<tokens file>) and replace its spring values with our presets in motion.ts (create snappy/soft presets if none exist).
4. Add accessibility the demo lacks: real <button> or correct role, visible focus, keyboard support, aria-expanded/aria-controls, and a live region if content changes without focus moving.
5. Add a reduced-motion fallback with useReducedMotion.
6. Give a tap/always-visible alternative for anything that only appears on hover.
Output: the summary, then the diff, then a list of anything that still differs from our design system. Remind me to check the repository licence.

I want to add one Cult UI component (<component name>) to this shadcn-based project as our single signature interaction.
1. Read the component's source (I will paste it or give you the file). Summarise its props, its dependencies (e.g. motion) and every hard-coded colour, radius, shadow and spring value.
2. Place it in the kit folder next to the other components; make sure there is only one copy in the repo.
3. Replace hard-coded styling with our tokens (<tokens file>) and replace its spring values with our presets in motion.ts (create snappy/soft presets if none exist).
4. Add accessibility the demo lacks: real <button> or correct role, visible focus, keyboard support, aria-expanded/aria-controls, and a live region if content changes without focus moving.
5. Add a reduced-motion fallback with useReducedMotion.
6. Give a tap/always-visible alternative for anything that only appears on hover.
Output: the summary, then the diff, then a list of anything that still differs from our design system. Remind me to check the repository licence.

I want to add one Cult UI component (<component name>) to this shadcn-based project as our single signature interaction.
1. Read the component's source (I will paste it or give you the file). Summarise its props, its dependencies (e.g. motion) and every hard-coded colour, radius, shadow and spring value.
2. Place it in the kit folder next to the other components; make sure there is only one copy in the repo.
3. Replace hard-coded styling with our tokens (<tokens file>) and replace its spring values with our presets in motion.ts (create snappy/soft presets if none exist).
4. Add accessibility the demo lacks: real <button> or correct role, visible focus, keyboard support, aria-expanded/aria-controls, and a live region if content changes without focus moving.
5. Add a reduced-motion fallback with useReducedMotion.
6. Give a tap/always-visible alternative for anything that only appears on hover.
Output: the summary, then the diff, then a list of anything that still differs from our design system. Remind me to check the repository licence.

I want to add one Cult UI component (<component name>) to this shadcn-based project as our single signature interaction.
1. Read the component's source (I will paste it or give you the file). Summarise its props, its dependencies (e.g. motion) and every hard-coded colour, radius, shadow and spring value.
2. Place it in the kit folder next to the other components; make sure there is only one copy in the repo.
3. Replace hard-coded styling with our tokens (<tokens file>) and replace its spring values with our presets in motion.ts (create snappy/soft presets if none exist).
4. Add accessibility the demo lacks: real <button> or correct role, visible focus, keyboard support, aria-expanded/aria-controls, and a live region if content changes without focus moving.
5. Add a reduced-motion fallback with useReducedMotion.
6. Give a tap/always-visible alternative for anything that only appears on hover.
Output: the summary, then the diff, then a list of anything that still differs from our design system. Remind me to check the repository licence.

I want to add one Cult UI component (<component name>) to this shadcn-based project as our single signature interaction.
1. Read the component's source (I will paste it or give you the file). Summarise its props, its dependencies (e.g. motion) and every hard-coded colour, radius, shadow and spring value.
2. Place it in the kit folder next to the other components; make sure there is only one copy in the repo.
3. Replace hard-coded styling with our tokens (<tokens file>) and replace its spring values with our presets in motion.ts (create snappy/soft presets if none exist).
4. Add accessibility the demo lacks: real <button> or correct role, visible focus, keyboard support, aria-expanded/aria-controls, and a live region if content changes without focus moving.
5. Add a reduced-motion fallback with useReducedMotion.
6. Give a tap/always-visible alternative for anything that only appears on hover.
Output: the summary, then the diff, then a list of anything that still differs from our design system. Remind me to check the repository licence.

I want to add one Cult UI component (<component name>) to this shadcn-based project as our single signature interaction.
1. Read the component's source (I will paste it or give you the file). Summarise its props, its dependencies (e.g. motion) and every hard-coded colour, radius, shadow and spring value.
2. Place it in the kit folder next to the other components; make sure there is only one copy in the repo.
3. Replace hard-coded styling with our tokens (<tokens file>) and replace its spring values with our presets in motion.ts (create snappy/soft presets if none exist).
4. Add accessibility the demo lacks: real <button> or correct role, visible focus, keyboard support, aria-expanded/aria-controls, and a live region if content changes without focus moving.
5. Add a reduced-motion fallback with useReducedMotion.
6. Give a tap/always-visible alternative for anything that only appears on hover.
Output: the summary, then the diff, then a list of anything that still differs from our design system. Remind me to check the repository licence.

I want to add one Cult UI component (<component name>) to this shadcn-based project as our single signature interaction.
1. Read the component's source (I will paste it or give you the file). Summarise its props, its dependencies (e.g. motion) and every hard-coded colour, radius, shadow and spring value.
2. Place it in the kit folder next to the other components; make sure there is only one copy in the repo.
3. Replace hard-coded styling with our tokens (<tokens file>) and replace its spring values with our presets in motion.ts (create snappy/soft presets if none exist).
4. Add accessibility the demo lacks: real <button> or correct role, visible focus, keyboard support, aria-expanded/aria-controls, and a live region if content changes without focus moving.
5. Add a reduced-motion fallback with useReducedMotion.
6. Give a tap/always-visible alternative for anything that only appears on hover.
Output: the summary, then the diff, then a list of anything that still differs from our design system. Remind me to check the repository licence.

I want to add one Cult UI component (<component name>) to this shadcn-based project as our single signature interaction.
1. Read the component's source (I will paste it or give you the file). Summarise its props, its dependencies (e.g. motion) and every hard-coded colour, radius, shadow and spring value.
2. Place it in the kit folder next to the other components; make sure there is only one copy in the repo.
3. Replace hard-coded styling with our tokens (<tokens file>) and replace its spring values with our presets in motion.ts (create snappy/soft presets if none exist).
4. Add accessibility the demo lacks: real <button> or correct role, visible focus, keyboard support, aria-expanded/aria-controls, and a live region if content changes without focus moving.
5. Add a reduced-motion fallback with useReducedMotion.
6. Give a tap/always-visible alternative for anything that only appears on hover.
Output: the summary, then the diff, then a list of anything that still differs from our design system. Remind me to check the repository licence.