Source profileQuality 70/100

nexu-io/open-design/skills/emilkowalski-motion/SKILL.md

emilkowalski-motion

Motion-design follow-up skill inspired by Emil Kowalski's animation guidance. Use after an interface exists to add tasteful micro-interactions, state transitions, and page motion with product-grade restraint.

Source repository stars: 91,167
Declared platforms: 0
Static risk flags: 0
Last source update: 2026-08-25
Source checked: 2026-08-25

Decision Compatibility Install Workflow Permissions Evidence Source FAQ

Decision brief

What it does: where it fits

Use this skill after a design artifact already exists. The goal is to make the interface feel alive without turning it into a motion demo.

Best for

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

npx skills add https://github.com/nexu-io/open-design --skill "skills/emilkowalski-motion"

Safe inspection promptEditorial

Inspect the Agent Skill "emilkowalski-motion" from https://github.com/nexu-io/open-design/blob/edfa6b5f447e95cb120eae030f03baba00dc34de/skills/emilkowalski-motion/SKILL.md at commit edfa6b5f447e95cb120eae030f03baba00dc34de. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
Workflow
1. Inspect the current HTML, component, or selected page element before adding animation. 2. Pick the smallest set of motion moments that clarify state or hierarchy: - entry reveal for the primary content - hover / active feedback for important controls - transition between UI s…
Inspect the current HTML, component, or selected page element before adding animation.Pick the smallest set of motion moments that clarify state or hierarchy:entry reveal for the primary content
02
Implementation Notes
For plain HTML, CSS keyframes and small JavaScript observers are enough.
For plain HTML, CSS keyframes and small JavaScript observers are enough.For React or framework code, use the local stack already present in the repo.If GSAP is available and the motion needs sequencing, pair this with gsap-core, gsap-timeline, or gsap-scrolltrigger.
03
Motion Rules
Default UI transitions should feel quick and useful: 140-220ms for most controls.
Default UI transitions should feel quick and useful: 140-220ms for most controls.Larger page reveals can be slower, but must not block reading.Avoid endless decorative loops unless they communicate status or progress.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	70/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	91,167	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: nexu-io/open-design
Skill path: skills/emilkowalski-motion/SKILL.md
Commit: edfa6b5f447e95cb120eae030f03baba00dc34de
License: Apache-2.0
Collected: 2026-08-25
Default branch: main

View the original SKILL.md

Emil Kowalski Motion Follow-Up

Use this skill after a design artifact already exists. The goal is to make the interface feel alive without turning it into a motion demo.

Workflow

Inspect the current HTML, component, or selected page element before adding animation.
Pick the smallest set of motion moments that clarify state or hierarchy:
- entry reveal for the primary content
- hover / active feedback for important controls
- transition between UI states
- scroll reveal only when it helps the story
Prefer transform and opacity. Avoid animating layout properties such as top, left, width, or height.
Use one motion language across the artifact. Do not mix unrelated easings, durations, or physics.
Add prefers-reduced-motion fallbacks for any automatic or scroll-linked motion.
Keep copy, data, and layout intent intact unless the user explicitly asks for a redesign.

Motion Rules

Default UI transitions should feel quick and useful: 140-220ms for most controls.
Larger page reveals can be slower, but must not block reading.
Avoid endless decorative loops unless they communicate status or progress.
Do not add custom cursors, noisy particle effects, or motion that competes with content.
Stagger only small groups. Long staggered lists make interfaces feel slow.

Implementation Notes

For plain HTML, CSS keyframes and small JavaScript observers are enough.
For React or framework code, use the local stack already present in the repo.
If GSAP is available and the motion needs sequencing, pair this with gsap-core, gsap-timeline, or gsap-scrolltrigger.
Always clean up observers, timers, and animation instances.

Frequently asked questions

What to verify before installation and use

What does the emilkowalski-motion source document cover?

Use this skill after a design artifact already exists. The goal is to make the interface feel alive without turning it into a motion demo.

How do I install emilkowalski-motion?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "skills/emilkowalski-motion". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing

Computed 10014,671

prowler-cloud/prowler

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance

Computed 100147

oaustegard/claude-skills

featuring

Generate hierarchical _FEATURES.md files that describe what a codebase DOES from a user/consumer perspective, anchored to source symbols via tree-sitting. Supports large complex codebases through feature-driven decomposition into sub-feature files. Uses a multi-pass synthesis: orientation → detail → overview rewrite. Use when someone says "what does this do", "document features", "feature inventory", "_FEATURES.md", or needs to understand a codebase's purpose before modifying it. Complements tre

Computed 9931,651

HKUDS/Vibe-Trading

strategy-generate

Create, modify, and optimize quantitative trading strategies, then backtest and evaluate them.

Computed 9980

vasilyu1983/AI-Agents-public

qa-testing-ios

Guides iOS testing with XCTest, XCUITest, Swift Testing, simctl, and xcresult. Use when choosing destinations, controlling flakes, or parsing test artifacts for native apps.