TheGoat395/Codex-Skills / skills/design-motion-principles
design-motion-principles
VerifiedMotion through Kowalski, Krehel and Jhey lenses.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.2 KB |
| agents/openai.yaml | config | 264 B |
| references/accessibility.md | markdown | 2.5 KB |
| references/anti-checklist.md | markdown | 13.4 KB |
| references/audit-checklist.md | markdown | 5.5 KB |
| references/creation-gotchas.md | markdown | 3.5 KB |
| references/demo-shell.html | other | 14.5 KB |
| references/emil-kowalski.md | markdown | 6.5 KB |
| references/jakub-krehel.md | markdown | 4.8 KB |
| references/jhey-tompkins.md | markdown | 6.1 KB |
| references/motion-cookbook.md | markdown | 18.3 KB |
| references/output-format.md | markdown | 18.0 KB |
| references/performance.md | markdown | 1.6 KB |
| references/report-template.html | other | 64.3 KB |
| workflows/audit.md | markdown | 12.7 KB |
| workflows/create.md | markdown | 4.4 KB |
references/jakub-krehel.md
View on GitHub# Jakub Krehel's Animation Principles
These are context-dependent interpretive defaults, not designer-authored authority or universal aesthetic rules. Apply the actual user direction, purpose, frequency, accessible state and measured consequence; purposeful artistic expression remains available.
Jakub Krehel is a design engineer known for his work at jakub.kr. His approach emphasizes **subtle production polish** — animations that enhance the experience invisibly, designed for real client work where users interact repeatedly.
This file is Jakub's **philosophy and decision frameworks** — the judgment for *how polished* and *how subtle* motion should be. Implementation code lives in `motion-cookbook.md` (cross-referenced below).
---
## Core Philosophy: Invisible Enhancement
> "The best animation is that which goes unnoticed."
His key question for any interaction: **"Is this subtle and polished enough for production?"**
Jakub's work embodies **refinement for production use**. His animations are:
- **Barely noticeable** — If users consciously notice the animation, it's probably too much
- **Production-ready** — Designed for real client work, not demos
- **Contextually appropriate** — Adapts to light mode, varied backgrounds, real content
- **Subtle over flashy** — The goal is to make interfaces feel smooth and responsive, not impressive
**The best compliment**: "This feels really nice" — not "cool animation!"
**The test**: If you remove the animation, do users feel something is missing? Good. If users comment "nice animation!" every time they see it? Too prominent.
---
## When to Apply Jakub's Mindset
- Production applications and client work
- Professional/enterprise interfaces
- When users will interact repeatedly (animations must not get tiresome)
- When accessibility and performance are critical
- When you need polish without distraction
---
## Signature Techniques (decision context — code in cookbook)
| Technique | When Jakub reaches for it | Cookbook |
|-----------|---------------------------|----------|
| Enter recipe (opacity + translateY + blur) | A selected meaningful entrance — blur can create a "materializing" feel more physical than fade alone | §1 |
| Subtler exits | Usually — exits don't need the same movement or attention as enters; the user is moving on | §1 |
| Spring animations (`bounce: 0`) | Production motion — smooth deceleration without overshoot; reserve `bounce > 0` for playful contexts | §2 |
| Shadows instead of borders | Light mode on varied backgrounds — shadows adapt via transparency where solid borders clash | §3 |
| oklch gradients | Any gradient — interpolates through perceptually uniform space, avoiding muddy midpoints | §3 |
| Blur as a signal | Materializing in/out — blur→sharp = entering focus, sharp→blur = losing relevance | §3 |
| Optical alignment | Buttons with icons, play buttons, asymmetric shapes — trust your eyes over math | §4 |
| Animated icon swaps (opacity + scale + blur) | Contextual icon changes (copy→check) — optional reinforcement when instant state changes are being missed | §5 |
| Shared layout via `layoutId` | Smooth FLIP transitions between different components (card→modal) | §6 |
| Targeted `will-change` | Specific properties about to animate — never global | see `performance.md` |
**Decision rules baked into the techniques:**
- Exits usually carry less weight; meaningful dismissal or directional continuity may justify a stronger exit.
- `bounce: 0` is the production default; bounce above zero reads as playful.
- Borders are fine in dark mode or when you want intentional hard edges.
---
## Common Mistakes (Jakub's Perspective)
- **Making enter and exit animations equally prominent** — Exits should be subtler
- **Using solid borders when shadows would adapt better** — Especially on varied backgrounds
- **Forgetting optical alignment** — Buttons with icons, play buttons, asymmetric shapes
- **Over-animating** — If users notice the animation itself, it's too much
- **Using the same animation everywhere** — Context should drive timing and easing choices
- **Ignoring hover state transitions** — Even small transitions (150-200ms) feel more polished than instant changes
---
## Jakub vs. Emil vs. Jhey
| Aspect | Jakub | Emil | Jhey |
|--------|-------|------|------|
| **Focus** | Subtle polish | Restraint & speed | Playful experimentation |
| **Key question** | "Is this subtle enough?" | "Should this animate?" | "What could this become?" |
| **Signature technique** | Blur + opacity + translateY | Frequency-based decisions | CSS custom properties |
| **Ideal context** | Production polish | High-frequency tools | Learning & exploration |
**When to use Jakub**: You've decided something should animate (passed Emil's gate) and need to make it production-ready and polished.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |