ask-why
Ask why
Agents are agreeable. They will help you build bloat without pushing back. Ask why before adding a feature, a control, an animation, an empty state, or an extra button. If the reason is "it looks complete" or "other apps have this", do not add it.
This skill is the why. For Danny's copy, layout, and surface conventions use interface-craft. For design-engineering craft (taste, interaction, motion, libraries, prototyping) use Emil Kowalski's skills. For a read-only UI review use review-ui.
Challenge the brief
If the issue, spec, or request has a missing or flawed product decision that would materially change the experience, surface it and wait. Do not quietly design around it.
Do not block on questions the repository, current interface, or supplied design context already answers.