orea Animated UI
You are an expert at building beautiful, self-contained animated UI components
in the visual and technical style of the orea component library. Each
component is a single, copy-pasteable file that looks great in a small preview
tile and animates with tasteful, physics-based motion.
When to use this skill
Trigger on requests like:
- "Add an animated component"
- "Make a hover / tilt / magnetic / spotlight / marquee / ticker effect"
- "Build a micro-interaction for <button|card|input|toggle>"
- "Add a new component to the registry / library"
- "Make it feel more alive / animated / premium"
Core principles (non-negotiable)
- Self-contained. One file, one named export,
"use client" at the top.
No required props — the component renders a complete, attractive demo on its
own so it works in a preview tile.
- Framer Motion is the motion engine. Import from
framer-motion. Prefer
useMotionValue + useSpring + useMotionTemplate for pointer/physics work,
and AnimatePresence + layout for enter/exit and layout transitions.
- Dark-first aesthetic. Neutral-900/950 surfaces, subtle
white/10 borders,
generous rounding (rounded-2xl/rounded-3xl), one restrained accent
(blue-500 family). No purple/violet unless asked. See
references/design-tokens.md.
- Fixed, tidy preview dimensions. Demos should size themselves (e.g.
h-44 w-72, or a compact centered element) so they sit nicely in a
h-64 preview area. Never render full-width/full-page layouts.
- Accessible & respectful of motion. Real semantic elements,
aria-*
where needed, keyboard support for interactive controls, and honor
prefers-reduced-motion for non-essential animation.
- Performance. Animate only
transform/opacity/filter where possible.
Clean up timers, animate() controls, and listeners. No layout thrash.
Workflow
Follow these steps in order. Read the referenced files the first time you build
a component in a session.
1. Understand the target style
Read references/design-tokens.md (visual language) and
references/animation-patterns.md (the exact Framer Motion recipes used across
the library). Match them precisely — the components must feel like siblings of
the existing ones.
2. Scaffold the component file
Create components/library/<kebab-name>.tsx using
examples/component-template.tsx as the starting point. Rules:
- First line:
"use client".
- Export a single named function:
export function PascalName() { ... }.
- No required props. If you add props, give every one a default.
- Keep it under ~120 lines. If it needs more, simplify the idea.
- Use Tailwind classes only (v4 — no config file). Follow the token palette.
3. Make the motion excellent
Pick the matching recipe from references/animation-patterns.md:
- Pointer-driven 3D / glare →
useMotionValue + useSpring + useMotionTemplate
- Magnetic / follow-cursor → spring-wrapped
x/y motion values
- Count-up / progress →
animate() + useTransform + useInView
- Enter/exit, stacks, toasts →
AnimatePresence (+ mode="popLayout"/layout)
- Looping (marquee, shimmer, aurora) →
animate prop with repeat: Infinity
Tune springs like the library does: snappy interactions use
{ stiffness: 220–300, damping: 15–20 }; soft settles use lower stiffness.
4. Register it in the orea registry
Add the component to components/library/registry.tsx. This is the step that
makes it show up on the site. Follow references/registry-workflow.md exactly:
- Add the
import { PascalName } from "./kebab-name".
- Append an
Entry object to the registry array with id, title,
description, Component, and a code template string.
- The
code string must be a faithful, standalone copy of the component's
source (this is what users copy). Escape backticks and ${...} as
\`` and ${...}` inside the template literal.
- Set
span: 2 | 3 only for wide demos (chat, command palette, marquee) and
pro: true only if explicitly requested.
5. Verify
- The component compiles and renders centered in the preview tile.
- Toggling the card's code view shows source that matches the file.
- Motion runs at 60fps and settles (no perpetual repaint unless intentional).
- Reduced-motion users get a calm, non-jarring experience.
Quality bar / self-check
Before declaring done, confirm every item:
Reference files
references/design-tokens.md — colors, radii, spacing, typography, preview sizing
references/animation-patterns.md — copy-ready Framer Motion recipes
references/registry-workflow.md — exact steps + code escaping rules
examples/component-template.tsx — starting scaffold
1---2name: orea-animated-ui3description: >-4 Build polished, self-contained animated React UI components in the "orea"5 style — dark theme, Framer Motion physics, copy-pasteable code — and register6 them in the orea component library. Use this skill whenever the user asks to7 create, design, or add an animated component, micro-interaction, hover effect,8 motion demo, or a new entry to the orea registry.9license: MIT10compatible_tools:11 - Claude Code12 - Antigravity13 - Codex14 - OpenCode15 - Cursor16 - Windsurf17 - any AGENTS.md-aware agent18metadata:19 source: https://skillmd.com/skills/oreaui/orea-animated-ui20---2122# orea Animated UI2324You are an expert at building **beautiful, self-contained animated UI components**25in the visual and technical style of the **orea** component library. Each26component is a single, copy-pasteable file that looks great in a small preview27tile and animates with tasteful, physics-based motion.2829## When to use this skill3031Trigger on requests like:3233- "Add an animated <thing> component"34- "Make a hover / tilt / magnetic / spotlight / marquee / ticker effect"35- "Build a micro-interaction for <button|card|input|toggle>"36- "Add a new component to the registry / library"37- "Make it feel more alive / animated / premium"3839## Core principles (non-negotiable)40411. **Self-contained.** One file, one named export, `"use client"` at the top.42 No required props — the component renders a complete, attractive demo on its43 own so it works in a preview tile.442. **Framer Motion is the motion engine.** Import from `framer-motion`. Prefer45 `useMotionValue` + `useSpring` + `useMotionTemplate` for pointer/physics work,46 and `AnimatePresence` + `layout` for enter/exit and layout transitions.473. **Dark-first aesthetic.** Neutral-900/950 surfaces, subtle `white/10` borders,48 generous rounding (`rounded-2xl`/`rounded-3xl`), one restrained accent49 (blue-500 family). No purple/violet unless asked. See50 `references/design-tokens.md`.514. **Fixed, tidy preview dimensions.** Demos should size themselves (e.g.52 `h-44 w-72`, or a compact centered element) so they sit nicely in a53 `h-64` preview area. Never render full-width/full-page layouts.545. **Accessible & respectful of motion.** Real semantic elements, `aria-*`55 where needed, keyboard support for interactive controls, and honor56 `prefers-reduced-motion` for non-essential animation.576. **Performance.** Animate only `transform`/`opacity`/filter where possible.58 Clean up timers, `animate()` controls, and listeners. No layout thrash.5960## Workflow6162Follow these steps in order. Read the referenced files the first time you build63a component in a session.6465### 1. Understand the target style6667Read `references/design-tokens.md` (visual language) and68`references/animation-patterns.md` (the exact Framer Motion recipes used across69the library). Match them precisely — the components must feel like siblings of70the existing ones.7172### 2. Scaffold the component file7374Create `components/library/<kebab-name>.tsx` using75`examples/component-template.tsx` as the starting point. Rules:7677- First line: `"use client"`.78- Export a single named function: `export function PascalName() { ... }`.79- No required props. If you add props, give every one a default.80- Keep it under ~120 lines. If it needs more, simplify the idea.81- Use Tailwind classes only (v4 — no config file). Follow the token palette.8283### 3. Make the motion excellent8485Pick the matching recipe from `references/animation-patterns.md`:8687- Pointer-driven 3D / glare → `useMotionValue` + `useSpring` + `useMotionTemplate`88- Magnetic / follow-cursor → spring-wrapped `x`/`y` motion values89- Count-up / progress → `animate()` + `useTransform` + `useInView`90- Enter/exit, stacks, toasts → `AnimatePresence` (+ `mode="popLayout"`/`layout`)91- Looping (marquee, shimmer, aurora) → `animate` prop with `repeat: Infinity`9293Tune springs like the library does: snappy interactions use94`{ stiffness: 220–300, damping: 15–20 }`; soft settles use lower stiffness.9596### 4. Register it in the orea registry9798Add the component to `components/library/registry.tsx`. This is the step that99makes it show up on the site. Follow `references/registry-workflow.md` exactly:1001011. Add the `import { PascalName } from "./kebab-name"`.1022. Append an `Entry` object to the `registry` array with `id`, `title`,103 `description`, `Component`, and a `code` template string.1043. The `code` string must be a faithful, standalone copy of the component's105 source (this is what users copy). Escape backticks and `${...}` as106 `\`` and `\${...}` inside the template literal.1074. Set `span: 2 | 3` only for wide demos (chat, command palette, marquee) and108 `pro: true` only if explicitly requested.109110### 5. Verify111112- The component compiles and renders centered in the preview tile.113- Toggling the card's code view shows source that matches the file.114- Motion runs at 60fps and settles (no perpetual repaint unless intentional).115- Reduced-motion users get a calm, non-jarring experience.116117## Quality bar / self-check118119Before declaring done, confirm every item:120121- [ ] `"use client"` + single named export + zero required props122- [ ] Renders a complete, self-explanatory demo at preview size123- [ ] Dark palette + one accent, matches `design-tokens.md`124- [ ] Motion uses the library's Framer Motion patterns and spring feel125- [ ] Keyboard + ARIA for anything interactive126- [ ] `prefers-reduced-motion` respected for decorative motion127- [ ] Cleaned up all effects/timers/animation controls128- [ ] Registered in `registry.tsx` with a matching `code` string129130## Reference files131132- `references/design-tokens.md` — colors, radii, spacing, typography, preview sizing133- `references/animation-patterns.md` — copy-ready Framer Motion recipes134- `references/registry-workflow.md` — exact steps + `code` escaping rules135- `examples/component-template.tsx` — starting scaffold