emil-design-eng

Files (8)

• LICENSE
• SKILL.md
• component-lessons.md · references/
• components.md · references/
• motion-decisions.md · references/
• performance-and-accessibility.md · references/
• stagger-and-debugging.md · references/
• transforms-and-gestures.md · references/

SKILL.md (first lines)

# Emil-inspired design engineering

Use this specialist perspective when explicitly requested or when a focused component detail needs it. It interprets publicly discussed design principles; it is not authored or endorsed by Emil Kowalski. Keep the project's established system and the user's requested scope.

Prioritize responsive feedback, origin-aware popovers, interruptible transitions, and touch/hover distinctions. Frequent interactions usually benefit from restrained or instant feedback. Duration, easing, blur, scale, and stagger are choices to test, not universal defects or acceptance rules. Do not delay keyboard operation or focus for motion.

Read only the relevant reference:

- [Motion decisions and springs](references/motion-decisions.md): deciding whether and how to animate.
- [Component polish](references/components.md): buttons, popovers, tooltips, interruption, and entry.
- [Transforms, clipping, and gestures](references/transforms-and-gestures.md): geometric or drag details.
- [Performance and accessibility](references/performance-and-accessibility.md): rendering cost, reduced motion, and touch handling.
- [Component lessons](references/component-lessons.md): Sonner-inspired defaults and adoption details.
- [Stagger and debugging](references/stagger-and-debugging.md): diagnosing timing or coordinating a sequence.

Reduced-motion users must retain all content and functionality. Decorative duplicates must be hidden from accessibility APIs and removed from focus order. Test changed behavior with keyboard, pointer, touch where relevant, and reduced motion. Check current official docs for version-dependent APIs and performance claims.

For review-only work, report evidence and the smallest useful recommendation without editing. A before/after comparison can clarify several changes; a focused answer can be prose. For implementation, make the authorized change and verify it. Do not replace a concrete request with an introductory greeting or a required format.

From AbdelazizMoustafa10m/skills-for-agents, MIT.

More from AbdelazizMoustafa10m/skills-for-agents