Loading...
Loading...
Found 5 Skills
Audits web UI quality across accessibility, interaction, forms, typography, navigation, layout, performance, motion, and microcopy. Use when reviewing or refining frontend UI before merge or release, or when the user asks for a UI, UX, or accessibility audit.
Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features.
Frontend and visual QA for responsive surfaces, screenshots, text fit, hierarchy, and interaction states.
Review existing UI against the project's design context, accessibility expectations, responsive behavior, interaction quality, and high-confidence production rules. Use for UI audits, design QA, frontend review, accessibility review, consistency checks, or requests to find and safely fix visual defects. Trigger for requests such as "review this UI", "audit this page", "find design issues", "check responsiveness", or "fix obvious UX problems". Use 21st-ui-build when the request is primarily to create new UI.
QA funcional de front de la fábrica Perennia x Ruuts. Prueba una app web como un usuario real exigente con NUESTRO motor (agent-browser) y NUESTRO arranque local (portless / npm run dev) — toca todos los botones, llena forms con casos vacío/inválido/edge, recorre flujos, verifica estados (empty/loading/error/overflow), mira la consola tras cada interacción, prueba responsive, con screenshot por hallazgo. Calcula un health score 0-100, triagea por severidad, arregla en source con commits atómicos y re-verifica. Use cuando el usuario diga "qa", "probá la app", "testeá esto", "buscá bugs", "qa funcional", "/wachi-qa", o cuando diga que un feature está listo o pregunte "¿esto anda?". Para modo solo-reporte (no arregla) usar el flag --report-only.