Loading...
Loading...
Found 80 Skills
Create helpful, actionable zero-content states
Determine what UI element draws attention first, second, third using size, weight, color, and de-emphasis strategies
Evidence-first design review of a PR's UI. Walks the changed screens in a real browser, performs the user's tasks, and posts findings ranked by user impact, each with evidence, a pattern, a trade-off and an acceptance criterion.
Помогает разобрать продуктовую или UX-задачу до проектирования решения: увидеть скрытое предположение, отделить образ продукта от модели и технологии, найти наиболее ценный вопрос или следующий шаг. Использовать, когда нужно придумать или обсудить фичу, экран, флоу, редизайн, концепт, принцип интерфейса или продуктовую стратегию; когда запрос сразу предлагает решение; когда варианты кажутся одинаково возможными; или когда нужен требовательный дизайн-консультант. Не использовать для исполнения уже согласованного решения, точечной визуальной правки или технической реализации без продуктовой развилки.
Guided journey from a shipped app that works but feels rough to a product that fits the job, flows without friction, reads clearly, and persuades honestly. Orchestrates nine skills phase by phase - jobs-to-be-done, ux-heuristics, design-everyday-things, refactoring-ui, microinteractions, made-to-stick, influence-psychology, high-perf-browser, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (CUSTOMER.md, DESIGN.md, POSITIONING.md, IMPROVE-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a clunky product, cut UX friction, sharpen in-app copy and prompts, or says 'the app works but feels rough'. Do not use for code, tests, or production hardening - use improve-code-quality (fresh prototype) or remove-technical-debt (aged codebase); no app yet, create-app; needs growth loops, grow-app; marketing-site friction, improve-website. For one framework in isolation, invoke that skill directly.
Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone
Apply Jakob's Law — users expect your product to work like the others they already use. Use when deciding whether to innovate on a familiar pattern. For OS-mandated conventions specifically, use `platform-conventions` (ui-design).
Use when auditing an existing product, app, or feature across all four Product Judgement scales: screen structure (Focal), multi-screen journeys (Compass), relationship value and retention (Flywheel), and memorable moments (Soul). Run for a holistic app audit, cross-scale critique, or prioritized UX review using a codebase, live product, prototype, Figma/Paper frames, screenshots, or a description. Prefer a codebase because it exposes behavior, state, and lifecycle context. Do not use for a single-screen, single-flow, or single-stage review; invoke the corresponding Skill instead, or for implementation, design-system analysis, visual styling, animation implementation, research, or analytics.
UI density — how much information and how many features appear at once — should match the primary platform and user type. Desktop supports dense, feature-rich interfaces; mobile requires focused, reduced layouts. Enterprise power users tolerate higher density than occasional users. Use when designing data tables, dashboards, toolbars, or adapting a desktop product for mobile.
Apply an emotional resonance lens to a UI that is technically correct but flat, prescribing changes at the copy, motion, and interaction layer. Use when a design tests fine but lands cold. For the polish-perception argument, use `aesthetic-usability` (ui-design).
UI should make it immediately clear where the user is, what context they are operating in, and what their actions will affect. Use lines, regions, colour areas, breadcrumbs, and scope labels to communicate hierarchy and context — especially in deep navigation structures or multi-section layouts.
Проверить, понятно ли пользователю, что произошло после действия, и предусмотрены ли состояния загрузки, пустоты и ошибки. Использовать при реализации сохранения, копирования, удаления, отправки, загрузки и синхронизации; при создании экранов с асинхронными данными; и при разборе интерфейса, который кажется неотзывчивым или непонятным. Не использовать для визуальной полировки и эстетики.