Motion Inspection
Inspect rendered UI motion frame by frame: start, mid, end, interrupt, and reduced-motion. Reverse-engineer unnamed animation into families/patterns from motion-families.md. Trigger for “inspeksi animasi”, “frame by frame”, “kenapa animasinya aneh”, “jelaskan transisi”, or reverse-engineer motion. Implementing new motion stays on motion; decorative spam stays on anti-slop-design.
Install
/plugin marketplace add sukirman1901/frontend-expertThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sukirman1901/frontend-expert --skill motion-inspectiongit clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/motion-inspection ~/.claude/skills/motion-inspectionPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Motion Inspection ## Overview Source duration is not proof. Play the animation (or mark **Not verified**). Name what it actually does at start / mid / end, whether it can be interrupted, and whether reduced-motion was observed. Then map it to catalog families/patterns. ## When to use - Explain, debug, or audit existing transitions - “Kenapa animasinya aneh” / frame-by-frame / reverse-engineer motion - `/design` on animated UI when claims depend on how it *plays* - Naming a mystery transition before changing it ## When to skip - Implementing new motion from a named pattern → `motion` - Decorative stack / motion spam as a visual tell → `anti-slop-design` (then inspect leftovers here) - Press-scale / duration heuristics on a new control → `polish` + `motion` - Comparing layout directions → `prototype` - WCAG classification of the target → `accessibility` ## MUST | Rule | Detail | |------|--------| | **Rendered** | Play or step the motion; do not pass from CSS/`transition` text alone | | **Not verified** | If it was not played, say so — never “smooth” / “perfect” | | **Beats** | Record start, mid, end, interrupt (click/focus/route away), reduced-motion | | **Name it** | Map to ≤2 families and named patterns in `motion-families.md` | | **Meaning** | If the only cue is motion, that is a defect — hand copy/a11y owners | | **Fix via `motion`** | Inspection does not ship a new stack; implementation follows `motion` | ## Workflow
Details
- Skill name
motion-inspection- Repository
- sukirman1901/frontend-expert
- Path
skills/motion-inspection/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Motion Inspection skill do?
Inspect rendered UI motion frame by frame: start, mid, end, interrupt, and reduced-motion. Reverse-engineer unnamed animation into families/patterns from motion-families.md. Trigger for “inspeksi animasi”, “frame by frame”, “kenapa animasinya aneh”, “jelaskan transisi”, or reverse-engineer motion. Implementing new motion stays on motion; decorative spam stays on anti-slop-design.
How do I install the Motion Inspection skill?
Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Motion Inspection popular?
It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.
Related skills
Accessibility
9sukirman1901/frontend-expert
Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.
Anti Slop Code
9sukirman1901/frontend-expert
Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.
Anti Slop Design
9sukirman1901/frontend-expert
Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.
Performance
9sukirman1901/frontend-expert
Optimize frontend Core Web Vitals (LCP, INP, CLS) and loading/rendering/network. Use when the UI feels slow, images/fonts/bundles need work, or during design audits that touch performance — phrases like "lemot", "optimize", "LCP", or "Core Web Vitals" without requiring a slash command.
Motion
9sukirman1901/frontend-expert
Purposeful UI motion by family/pattern — shell defaults (fade, drawer, press) plus marketing vocabulary (reveal, scroll, text, carousel, hero, …). Hand-roll CSS/Motion/GSAP from named patterns. Use for animation requests, landings, marquees, parallax, text reveal, and light defaults on /ui shells — not token-only tweaks.
Polish
9sukirman1901/frontend-expert
Polish micro-details that make UI feel better — optical alignment, tabular nums, text-wrap, interruptible transitions, press feedback, hit areas, no transition:all. Use when building/reviewing UI polish, "feels off", "rapihin detail", hover/press feedback, or after anti-slop-design. Structural layout, radius language, and WCAG conformance belong to other owners.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.