188건 · 관련도순
Review web interface code against the latest Web Interface Guidelines to identify issues in design, usability, and accessibility. Specify files or a file pattern, and receive concise findings with file names and line numbers.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn interviews, surveys, usability notes, and customer feedback into shared themes, user groups, and prioritized recommendations. Findings include supporting quotes and participant counts, helping teams connect research evidence to concrete product improvements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan user research by matching methods to study goals and explaining participant numbers and confidence. Synthesize tagged observations into recurring findings, distinguish isolated anecdotes, and organize evidence so research results can be found and reused.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Examine feature ideas for existing products to uncover risky assumptions about customer value, usability, business support, and technical feasibility. Consider product, design, and engineering perspectives, then record potential failures, confidence levels, and suggested ways to test each assumption.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Refine a working feature through browser feedback from the user. Collect observations through typed comments or live speech and drawing, apply focused usability fixes, and save the changes in local commits.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review web interface code against the latest Web Interface Guidelines to identify issues in design, usability, and accessibility. Specify files or a file pattern, and receive concise findings with file names and line numbers.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit a website’s technical foundations for search engines and AI services. Check crawler access, indexing, security, mobile usability, speed, and server-rendered content, then produce a scored Markdown report with prioritized findings.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn interviews, surveys, usability notes, and customer feedback into shared themes, user groups, and prioritized recommendations. Findings include supporting quotes and participant counts, helping teams connect research evidence to concrete product improvements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore a web application as a user to find bugs and usability problems. Produce a structured report with reproducible steps, screenshots, and videos for interaction issues, giving responsible teams clear evidence to investigate.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Reviews APIs and configuration designs for choices that make security mistakes easy. Checks unsafe defaults, confusing parameter types, and hidden failures, then validates whether misuse creates a real vulnerability and assigns severity.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review a product experience by walking through its steps and capturing screenshots. Produces an illustrated assessment of usability, design, and accessibility risks, with findings tied to specific screens and clear limits on what was checked.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Research current user problems with a named digital product using public sources and permitted internal sources. Group evidence into usability issues, rank their importance, and produce a concise brief with citations and recommended improvements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review websites, apps, screenshots, or design code for redundant decoration, generic patterns, and usability defects. Receive prioritized findings tied to specific evidence, with removal or small corrections that preserve the interface’s existing design direction.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit the journey from a search result to a page’s intended action. Review titles, search intent, speed, readability, calls to action, and mobile usability to identify problems behind low click rates or weak conversions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize multi-agent reviews with defined roles for bugs, architecture, integration, and usability. Designed for local Codex workflows with vibe, it combines findings by severity into a shared set of keep, simplify, or remove decisions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write realistic usability task scenarios with success criteria and facilitation notes. Use when you have a study and need the tasks. For the surrounding study design, use `usability-test-plan` (design-research).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Use when planning the study as a whole. For writing the task scenarios inside it, use `test-scenario` (prototyping-testing).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts. Use when the user wants to prototype, wireframe, map a user flow, or plan/run usability testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided journey from a live website that underperforms to a prioritized, evidence-backed backlog of conversion, usability, message, and speed fixes - each shipped as a testable experiment. Orchestrates eight skills phase by phase - cro-methodology, ux-heuristics, refactoring-ui, web-typography, storybrand-messaging, high-perf-browser, made-to-stick, design-everyday-things - asking the user questions at every decision point and recording results in the project docs/ folder (WEBSITE.md, DESIGN.md, IMPROVE-WEBSITE-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a landing page that isn't converting, diagnose why visitors leave, audit for clarity and usability, or says 'the homepage feels off but a redesign didn't help'. No site yet, create-website; converts but needs traffic, grow-website; if the friction is in a product app, not the marketing site, improve-app; if one specific flow leaks, conversion-optimization. For one framework in isolation, invoke that skill directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "outcome over output", "design studio method", "assumption mapping", "lightweight research", "too much design documentation", or "get the team designing together". Also trigger when reducing design-documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
UX research and design toolkit covering persona generation, journey mapping, usability testing, and research synthesis. Use for user research, persona creation, journey mapping, or design validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus usability observations through a UX lens reported separately from defects. Deeper than $smoke-test. Use when the user asks to "exploratory test", "test thoroughly", "test all scenarios", "deep test", "test edge cases", "test everything", "break it", "find bugs by testing", "test usability", or "check the UX while testing".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus usability observations through a UX lens reported separately from defects. Deeper than /smoke-test. Use when the user asks to "exploratory test", "test thoroughly", "test all scenarios", "deep test", "test edge cases", "test everything", "break it", "find bugs by testing", "test usability", or "check the UX while testing".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.