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 |
workflows/create.md
View on GitHub# Workflow: Create Mode
Build interactive components with purposeful motion. Light discovery, then generate against the cookbook.
## Required Reading
Read before generating:
1. `references/motion-cookbook.md` — read the sections for the selected effect; other recipes stay unloaded
2. `references/accessibility.md` — `prefers-reduced-motion` is mandatory in everything you generate
3. `references/creation-gotchas.md` — Common implementation failure modes when writing motion; self-check against these
---
## STEP 1: Light Discovery
Establish two things — project context and designer weighting — before generating. Infer from available context first.
### Infer First, Ask Second
Check what you can already see:
- **The request** — what component, what interaction, what stack (React / Framer Motion / CSS / HTML)?
- **Applicable project instructions, package.json and affected components** — project type and existing animation conventions; reuse unchanged context
### Propose Context + Weighting
Map the project type to a perspective weighting using the Context-to-Perspective Mapping table in SKILL.md. State your inference in one short block:
```
Building: [what — e.g. "a notification toast, React + Framer Motion"]
Project context: [inferred — e.g. "productivity SaaS dashboard"]
Proposed weighting: Primary [Designer] · Secondary [Designer]
```
Use current user direction and adequate existing context without asking again. State reversible assumptions and proceed. Ask only when a consequential missing choice actually blocks implementation; weighting itself is not an approval boundary.
---
## STEP 2: Load Weighted Knowledge
Based on the context-supported weighting, read the relevant designer file(s):
- **Read `references/emil-kowalski.md`** if Emil is primary/secondary — restraint, the frequency rule, when NOT to animate
- **Read `references/jakub-krehel.md`** if Jakub is primary/secondary — production polish judgment, subtlety bar
- **Read `references/jhey-tompkins.md`** if Jhey is primary/secondary — playful expression, what motion could become
The designer files give you the **judgment** (should this animate, what feel). The cookbook gives you the **code**.
If the component involves complex or numerous animations, also read `references/performance.md`.
---
## STEP 3: Generate
Build the component. Apply, in order:
1. **The frequency gate (Emil)** — Should this animate at all? High-frequency or keyboard-initiated interactions get minimal or no motion. Decide before adding anything.
2. **Recipes from the cookbook** — Use the weighted designer's patterns. Choose instant, opacity-only or movement to fit the purpose. Blur is optional and measured. Exits usually carry less visual weight; choose easing/springs for the actual brand and behavior.
3. **Accessibility** — Every animation ships with `prefers-reduced-motion` handling, in the same code. No exceptions, no follow-up.
4. **Performance** — Prefer transform/opacity; filter/clip effects can paint and must be measured. Use measured layout/FLIP or bounded size animation when it serves content flow; avoid layout thrash.
5. **Context-appropriate timing** — Use the weighted ranges as starting points: under 300ms for frequent productivity actions, 200–500ms for some transitions, longer expressive scenes when earned. The actual brief, interruption, preference and measured consequence control.
---
## STEP 4: Self-Check
Check applicable implementation risks from `references/creation-gotchas.md`. Run and inspect the affected interaction, including rapid reversal, keyboard/focus and reduced motion; repair observed defects and repeat the affected check. A matching code pattern alone is not a defect. If runtime inspection is unavailable, state that boundary and complete feasible source checks.
Then briefly tell the user the motion decisions you made and why — which designer weighting drove the timing, easing, and whether something was deliberately left un-animated.
---
## Success Criteria
- [ ] Context and weighting grounded in user direction or available evidence
- [ ] Frequency gate applied — motion is purposeful, not decorative-by-default
- [ ] Recipes drawn from the cookbook, matched to the designer weighting
- [ ] `prefers-reduced-motion` handled in all generated motion
- [ ] Rendering cost measured where needed; layout/effect exceptions justified
- [ ] Code self-checked against creation-gotchas.md
- [ ] Motion decisions explained to the user
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: 322k | 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 |