Loading...
Loading...
Found 7 Skills
Usability heuristics and principles based on Steve Krug's "Don't Make Me Think" and Jakob Nielsen's 10 heuristics. Use when you need to: (1) audit a UI for usability problems, (2) identify why users are confused or frustrated, (3) simplify navigation and information architecture, (4) conduct heuristic evaluations, (5) prioritize UX fixes by severity, (6) review designs before development, (7) improve form usability, (8) validate that interfaces follow established UX principles.
Design Sprint methodology based on Jake Knapp's "Sprint" (Google Ventures). Use when you need to: (1) validate product ideas in 5 days instead of months, (2) rapidly prototype and test solutions, (3) answer critical business questions quickly, (4) align teams on product direction, (5) de-risk product development before building, (6) test multiple concepts with real users, (7) make fast strategic decisions through structured process.
Unit tests for Spring Security with @PreAuthorize, @Secured, @RolesAllowed. Test role-based access control and authorization policies. Use when validating security configurations and access control logic.
Design Thinking methodology for human-centered innovation. Covers the 5-phase IDEO/Stanford d.school approach (Empathize, Define, Ideate, Prototype, Test) with workshop facilitation and exercise templates.
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", or "de-risk before building". Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done. Trigger with 'design', 'sprint'.
Use when you want to verify a site works by having agents act as real users completing common tasks — browsing, subscribing, purchasing, searching. Each agent has a goal and clicks through the real flow using browser MCP tools.
Validación con usuarios reales sobre RumIAndo: prepara la sesión desde el contrato de la ficha (qué hipótesis se testean, con qué prototipo, con quiénes), guía la conducción (mirar sin ayudar, no vender), y registra TODO en RumIAndo — sesión de validación, hallazgos tipados (ux/funcional/tecnico/bloqueante), decisiones (aceptar/rechazar/iterar/derivar) — cerrando el loop: procesa las decisiones a transiciones de ficha. Usar cuando una ficha/fichero en PARA_VALIDAR se testea con productores/técnicos/usuarios, y también para registrar a posteriori una sesión que ya ocurrió. NO es QA técnico (wachi-qa) ni review interno (wachi-validacion-interna).