القائمة
Apply Emil Kowalski-style UI polish: interaction details, component feel, animation restraint, and invisible product quality. Uses progressive disclosure instead of long design essays.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Apply Emil Kowalski-style animation guidance for web interfaces: purposeful motion, correct easing, interruptibility, performance, reduced motion, and interaction feel.
Implement the requested change on the current branch using the best available contract: issue, architecture, user request, or repo evidence. Does not require /architect or /review to have run. Hands naturally to /test.
Triage and address PR review comments. Uses available issue/architecture/context when present, keeps evidence in .context/address.md, and does not require prior workflow phases.
Derive the smallest correct architecture from user intent, repo facts, and available workflow evidence. Writes the full architecture to .context/architecture.md and returns only the decision, tradeoff, risk, and next action.
Review the current PR for correctness, tests, maintainability, security, standards, and prior-findings risk. Keeps reviewer detail in .context/code-review.md and posts concise actionable GitHub review comments.
Reproduce, root-cause, and fix a bug with the smallest verified change. Writes investigation evidence to .context/debug.md and hands naturally to /test.
| name | emil-design-eng |
| description | Apply Emil Kowalski-style UI polish: interaction details, component feel, animation restraint, and invisible product quality. Uses progressive disclosure instead of long design essays. |
Read the shared contracts before output: ../_shared/operator-output.md, ../_shared/attention-budget.md, ../_shared/evidence-record.md, ../_shared/state.md, ../_shared/cognitive-load.md, ../_shared/collaboration.md.
Improve how an interface feels by fixing concrete friction, timing, hierarchy, feedback, and interaction details.
UI code, screenshot, component, interaction, animation, or user request for polish/design engineering.
Existing UI implementation, screenshots/browser state, component library conventions, animation references when needed.
.context/design-eng.md for audit notes and rejected polish ideas.context/session-state.md for substantial work.context/design-eng.md; keep chat to the highest-impact fixes.When reviewing UI, use a compact table only if it improves scanning:
| Before | After | Why |
|---|---|---|
<issue> | <change> | <reason> |
Respect the attention budget: no more than eight rows in chat.
Return the design decision or implemented polish, up to three evidence bullets, remaining risk, and next action. For pure review, include only the top issues in chat and write the rest to .context/design-eng.md.
Stop if the UI cannot be inspected, the target audience/workflow is unknown and materially changes the design, or verification cannot run for a risky interaction.