UI/UX, logos, slides, and image generation (7.4K skills)
Choose measures that connect design decisions to user experience and business outcomes. Define what each measure means, how and where to collect it, its target, review frequency, and owner so teams can assess changes consistently.
Organize a site's or app's content into clear categories, labels, and relationships. Create sitemaps and content models, descriptions of content types and their connections, to help teams plan navigation and check whether users can find information.
Write realistic tasks for usability tests, where participants try to achieve goals using a product. Define success criteria, observation points, and follow-up questions while avoiding wording that gives away the interface steps.
Create clear design principles that help a team resolve recurring disagreements. Each principle includes a rationale, examples, a counterexample, and trade-offs, with priorities that guide decisions when principles conflict.
Design a first-use experience that guides new users from signup to a meaningful action. Plan setup steps, contextual guidance, empty screens, and sample data, with measures for understanding where users get stuck or leave.
Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.
Design a search experience covering query input, suggestions, result layouts, filters, and helpful responses when nothing matches. It also identifies search metrics that reveal missing content, weak rankings, and places where users struggle to find information.
Use the Von Restorff Effect, where an item stands out because it differs from its surroundings, to emphasize one important action or detail. It guides button, pricing, and notification design while checking that emphasis remains accessible.
Compose interfaces so people notice key content and actions first. Use text size, weight, color, spacing, position, and grouping to establish clear levels of importance and make pages easier to scan.
Describe complex interface behavior with state machines: explicit states and rules for moving between them. Map events, conditions, and actions for forms, authentication, and data loading to expose edge cases and prevent contradictory states.
Evaluate interface decisions against patterns users already know from other products. Identify strong expectations, assess the learning cost of changing familiar interactions, and determine when a different approach is justified by the task or user testing.
Adapt an existing light palette into a dark interface by adjusting surface brightness, text contrast, and color saturation. Covers images, logos, accessibility checks, and automatic or manual switching between light and dark modes.
Create a spacing scale from a base unit and define where each value belongs. Standardize padding, vertical and horizontal gaps, and spacing adjustments for compact data views or more spacious reading layouts.
Define a page layout grid with columns, gaps, outer margins, and rules for different screen widths. Plan card layouts, sidebars, and content containers, and document the specifications developers need to keep pages consistent.
Use shared colors, shapes, sizes, and styles to show which interface elements belong together, even across a page. Establish consistent visual rules for controls, categories, and charts, with additional cues so meaning does not depend on color alone.
Specify a single interface interaction for engineering handoff, such as a toggle or swipe action. Define its trigger, behavior, feedback, timing, repetition, and accessibility considerations so the intended response is clear.
Develop several solutions to the same problem by varying user steps, starting points, or decisions shared with the system. Keep concepts equally detailed so teams can explore meaningful alternatives before refining a single direction.
Design the most emotionally intense moment and the ending of a user journey, which shape how people remember it. Apply this approach to purchase confirmations, first results, milestones, and recovery after errors.
Define a screen’s structure before visual design by organizing content priorities, component placement, and behavior notes. Create wireframe specifications that cover different screen sizes, content requirements, and states such as loading or errors.
Map how people move through a product to complete a task. Create diagrams covering screens, actions, decisions, error recovery, and background processes so the paths through a feature are clear.
Design navigation that fits a product’s structure and user tasks. Choose tabs, sidebars, menus, and breadcrumbs, then define clear labels and selected states so people understand where they are and how to move between sections.
Group related interface elements with shared backgrounds, borders, or containers. Apply the Law of Common Region, a visual grouping principle, to clarify cards, forms, and panels while avoiding unnecessary borders and excessive nesting.
Apply closure, the tendency to mentally complete partial shapes, to simplify icons and interface boundaries. Use spacing, alignment, and partial lines to convey structure, while identifying where full borders remain necessary.
Review interfaces against Nielsen's ten usability principles and relevant domain criteria without recruiting participants. Document where problems occur, rate their severity from zero to four, and suggest improvements so teams can prioritize fixes before user testing.