Acerca de este Skill
UI engineering workflows for recording and applying evidence-based design guidance.
Por qué lo elegimos
The selected workflow produces a design-system document grounded in actual project or rendered-site evidence.
Skills de esta colección
5 skills- Ver →
Baseline UI
Quickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.
- Ver →
fixing-accessibility
Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.
- Ver →
fixing-motion-performance
Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance.
- Ver →
Improve UI
Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.
- Ver →
Create DESIGN.md
Create an evidence-based DESIGN.md from a product repository or a rendered public website.
Para qué sirve
- Document a product’s design language for a coding agent.
Antes de usarlo
- Use a coding agent with access to the source project or a browser-rendered public page.
Fuentes y referencias
Las fuentes originales se enlazan a continuación. Los puntos de partida prácticos son sugerencias editoriales de SkillHey.