design-engineering — Claude Code skill for UI design and installation
The design-engineering skill guides interface animation choices and UI reviews. Use it when refining a component, transition, modal, or other interactive state.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat design-engineering does
The skill lays out a sequence for motion decisions: decide whether movement is needed, identify its purpose, then choose easing and duration. Frequency matters. It recommends keeping keyboard-triggered actions animation-free, while occasional surfaces such as modals can use standard transitions. That distinction matters for command palettes and other repeated actions.
Its guidance covers CSS easing curves, springs for gestures, and explicit component states such as :active and focus-visible. It also calls for honoring prefers-reduced-motion and keeping spacing and type scales consistent.
For UI code reviews, the required output is one Markdown table with Before | After | Why columns. To install through the Claude Code marketplace, run both commands in order.
What it helps with
- choose easing for a menu or state transition
- set an animation duration for a component
- add press feedback to an interactive control
- review UI code in a consistent table format
- account for
prefers-reduced-motion
Example prompts for the agent
- Review this component and suggest changes to its motion and interaction states.
- Add a transition to this drawer and choose suitable easing and timing.
- Should this keyboard-triggered action animate? Review the interface behavior.
How to install design-engineering
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowThis installs the whole pro-workflow plugin with all its skills
2Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill design-engineering -a claude-code3Manually: put the files in place
~/.claude/skills/design-engineering/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/design-engineering/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill design-engineering -a codex2Manually: put the files in place
.agents/skills/design-engineering/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill design-engineering -a cursor2Manually: put the files in place
.cursor/skills/design-engineering/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rohitg00/pro-workflow skills/design-engineering2Manually: put the files in place
.github/skills/design-engineering/SKILL.md1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill design-engineering -a gemini-cli2Platform CLI
gemini skills install https://github.com/rohitg00/pro-workflow --path skills/design-engineeringManually: put the files in place
.devin/skills/design-engineering/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about design-engineering
How do I install design-engineering in Claude Code?
Run these commands in order: /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow.
What does the design-engineering skill do?
It guides decisions about UI motion, easing, timing, and component states, and helps review interface code. Reviews use a single Markdown table.
What format should a UI review use?
Use one Markdown table, with one row per issue and the columns Before | After | Why.
Source text
SKILL.md · MIT
--- name: design-engineering description: Apply interface craft when building or reviewing UI - motion, easing, timing, springs, component feel, and visual foundations. Use when building a component, animation, transition, hover or press state, modal, drawer, toast, or when polishing an interface so it feels right. Says "make this feel better", "add an animation", "polish the UI", "review this component". --- # design-engineering In a world where most software works well enough, feel is the differentiator. Most of what makes an interface feel right is detail the user never consciously notices - the aggregate of small correct choices. Build for that aggregate. ## Motion decision framework Answer these in order before writing any animation. ### 1. Should it animate at all? The deciding factor is frequency. The more often a user sees it, the less it should move. | How often the user sees it | Decision | |----------------------------|----------| | 100+ times/day (shortcuts, command palette) | No animation, ever | | Tens of times/day (hover, list nav) | Remove or drastically reduce | | Occasional (modals, drawers, toasts) | Standard animation | | Rare or first-time (onboarding, celebration) | Room for delight | Never animate a keyboard-initiated action. It repeats all day; animation makes it feel slow and disconnected from the keypress. ### 2. What is the purpose? Every animation needs an answer to "why does this move?" Valid ones: spatial consistency (enters and exits the same edge), state change, feedback (a press that confirms the interface heard you), or preventing a jarring appear/disappear. "It looks cool" is not a purpose for anything the user sees often. ### 3. What easing? - Entering or exiting -> `ease-out` (fast start, feels responsive). - Moving or morphing on screen -> `ease-in-out`. - Hover or color change -> `ease`. - Constant motion (marquee, progress) -> `linear`. Never use `ease-in` for UI. It delays the first moment of movement - exactly when the user is watching - so a 300ms `ease-in` dropdown feels slower than a 300ms `ease-out` one. The built-in curves are weak; use stronger custom ones: ```css --ease-out: cubic-bezier(0.23, 1, 0.32, 1); /* UI interactions */ --ease-in-out: cubic-bezier(0.77, 0, 0.175, 1); /* on-screen movement */ --ease-drawer: cubic-bezier(0.32, 0.72, 0, 1); /* iOS-like drawer */ ``` ### 4. How fast? | Element | Duration | |---------|----------| | Button press feedback | 100-160ms | | Tooltip, small popover | 125-200ms | | Dropdown, select | 150-250ms | | Modal, drawer | 200-500ms | Keep frequent, interactive UI under 300ms; the modal and drawer range above (up to 500ms) is the deliberate exception for occasional, first-time surfaces. Perceived speed is real: a faster spinner makes a load feel faster at the same load time, and an instant tooltip after the first one makes a whole toolbar feel quick. ## Springs Springs settle on physics, not a fixed duration, so they feel alive and, unlike CSS keyframes, keep their velocity when interrupted. Reach for them on drag and gesture interactions the user can reverse mid-motion, and on decorative, mouse-tracked motion. Keep bounce subtle (0.1 to 0.3) and usually absent - save it for drag-to-dismiss and playful moments, not functional UI. ## Component feel - **Press feedback.** Any pressable element gets `transform: scale(0.97)` on `:active` with a ~160ms `ease-out` transition. Subtle (0.95 to 0.98); it makes the interface feel like it is listening. - **Never animate from `scale(0)`.** Nothing real appears from nothing. Start at `scale(0.9)` or higher plus opacity so the entrance has shape. - **Scale from the trigger.** Popovers and dropdowns scale from their origin, not their center. Modals stay centered. - **Respect `prefers-reduced-motion`.** Drop or shorten non-essential motion. ## Visual foundations - One spacing scale, one type scale. Consistency reads as intent; ad-hoc values read as noise. - Restrained color: a small palette with clear roles beats many accents. - Make every interactive state explicit - hover, active, focus-visible, disabled. A control with no states feels dead. ## Review format When reviewing UI code, output a single markdown table, one row per issue, with `Before | After | Why`. Do not use separate "Before:" / "After:" lines. | Before | After | Why | |--------|-------|-----| | `transition: all 300ms` | `transition: transform 200ms ease-out` | Name exact properties; avoid `all` | | `transform: scale(0)` | `scale(0.95); opacity: 0` | Nothing appears from nothing | | `ease-in` on a dropdown | strong `ease-out` | `ease-in` reads as sluggish | | no `:active` state | `scale(0.97)` on `:active` | Presses must feel responsive |
© Rohit Ghumare · MIT · rohitg00/pro-workflow