emil-design-engineering
- Repo stars 0
- Author updated Live
- Author repo sea-prototype-template
- Domain
- Design
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @lemu · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: emil-design-engineering
description: Design engineering principles and patterns for building polished, accessible web interfaces. Use…
category: design
runtime: no special runtime
---
# emil-design-engineering output preview
## PART A: Task fit
- Use case: Design engineering principles and patterns for building polished, accessible web interfaces. Use this skill when building UI components, reviewing frontend code, implementing forms, handling touch interactions, optimizing performance, or creating marketing pages. Triggers on: design engineering, UI polish, input fields, form validation, button states, touch devices, mobile UX, accessibility, a11y, keyboard navigation, aria labels, font rendering, typography, layout shift, z-index, animations, transitions, easing, hover effects, tap targets, iOS Safari, prefers-reduced-motion, marketing pages, landing pages, dark mode, theme switching, scrollbars, gradients, shadows, virtualization, preloading..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Quick Reference / Core Principles / 1. No Layout Shift” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Design engineering principles and patterns for building polished, accessible web interfaces. Use this skill when building UI components, reviewing frontend code, implementing forms, handling touch interactions, optimizing performance, or creating marketing pages. Triggers on: design engineering, UI polish, input fields, form validation, button states, touch devices, mobile UX, accessibility, a11y, keyboard navigation, aria labels, font rendering, typography, layout shift, z-index, animations, transitions, easing, hover effects, tap targets, iOS Safari, prefers-reduced-motion, marketing pages, landing pages, dark mode, theme switching, scrollbars, gradients, shadows, virtualization, preloading.”.
- **02** When the source has headings, the agent prioritizes “Quick Reference / Core Principles / 1. No Layout Shift” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Quick Reference / Core Principles / 1. No Layout Shift”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: emil-design-engineering
description: Design engineering principles and patterns for building polished, accessible web interfaces. Use…
category: design
source: lemu/sea-prototype-template
---
# emil-design-engineering
## When to use
- Design engineering principles and patterns for building polished, accessible web interfaces. Use this skill when build…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Quick Reference / Core Principles / 1. No Layout Shift” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "emil-design-engineering" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Quick Reference / Core Principles / 1. No Layout Shift
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Emil's Design Engineering Principles
A comprehensive guide for building polished, accessible web interfaces based on Emil Kowalski's design engineering practices.
Quick Reference
| Category | When to Use |
|---|---|
| Animations | Enter/exit transitions, easing, springs, performance |
| UI Polish | Typography, visual design, layout, colors |
| Forms & Controls | Inputs, buttons, form submission |
| Touch & Accessibility | Mobile, touch devices, keyboard nav, a11y |
| Component Design | Compound components, composition, props API |
| Marketing | Landing pages, blogs, docs sites |
| Performance | Virtualization, preloading, optimization |
Core Principles
1. No Layout Shift
Dynamic elements should cause no layout shift. Use hardcoded dimensions, font-variant-numeric: tabular-nums for changing numbers, and avoid font weight changes on hover/selected states.
2. Touch-First, Hover-Enhanced
Design for touch first, then add hover enhancements. Disable hover effects on touch devices. Ensure 44px minimum tap targets. Never rely on hover for core functionality.
3. Keyboard Navigation
Tabbing should work consistently. Only allow tabbing through visible elements. Ensure keyboard navigation scrolls elements into view with scrollIntoView().
4. Accessibility by Default
Every animation needs prefers-reduced-motion support. Every icon button needs an aria label. Every interactive element needs proper focus states.
5. Speed Over Delight
Product UI should be fast and purposeful. Skip animations for frequently-used interactions. Marketing pages can be more elaborate.
Decision Flowcharts
Should I Animate This?
Will users see this 100+ times daily?
├── Yes → Don't animate
└── No
├── Is this user-initiated?
│ └── Yes → Animate with ease-out (150-250ms)
└── Is this a page transition?
└── Yes → Animate (300-400ms max)What Easing Should I Use?
Is the element entering or exiting?
├── Yes → ease-out
└── No
├── Is it moving on screen?
│ └── Yes → ease-in-out
└── Is it a hover/color change?
├── Yes → ease
└── Default → ease-outCommon Mistakes
| Mistake | Fix |
|---|---|
transition: all |
Specify exact properties |
| Hover effects on touch | Use @media (hover: hover) |
| Font weight change on hover | Use consistent weights |
Animating height/width |
Use transform and opacity only |
| No reduced motion support | Add prefers-reduced-motion query |
| z-index: 9999 | Use fixed scale or isolation: isolate |
| Custom page scrollbars | Only customize scrollbars in small elements |
Review Checklist
When reviewing UI code, check:
- No layout shift on dynamic content
- Animations have reduced motion support
- Touch targets are 44px minimum
- Hover effects disabled on touch devices
- Keyboard navigation works properly
- Icon buttons have aria labels
- Forms submit with Enter/Cmd+Enter
- Inputs are 16px+ to prevent iOS zoom
- No
transition: all - z-index uses fixed scale
Reference Files
For detailed guidance on specific topics:
- animations.md - Easing, timing, springs, performance
- ui-polish.md - Typography, shadows, gradients, scrollbars
- forms-controls.md - Inputs, buttons, form patterns
- touch-accessibility.md - Touch devices, keyboard nav, a11y
- component-design.md - Compound components, composition, props API
- marketing.md - Landing pages, blogs, docs
- performance.md - Virtualization, preloading, optimization
Decide Fit First
Design Intent
How To Use It
Boundaries And Review