kinwisenz-devops/ui-ux-designer

Use when checking or designing for accessibility on mobile, tablet or desktop: touch target size, contrast, text scaling, screen readers (VoiceOver, TalkBack), keyboard and switch use, reduce motion, WCAG 2.2 criteria, or an accessibility checklist for a design. Do not use for general visual styling (visual-design-system), legal compliance claims, or writing accessibility code for a framework.

Use when laying out a screen, setting spacing and grids, handling notches and safe areas, adapting a phone design to tablet, foldable or desktop, choosing breakpoints or size classes, or fixing a layout that breaks with large text or rotation. Covers hierarchy, grouping, safe areas, edge-to-edge, size classes and reflow. Do not use for navigation structure (navigation-and-flows), colour and type (visual-design-system) or writing layout code.

Use when designing forms and input, validation, error messages, alerts and confirmations, loading, empty and error states, buttons, haptics, toasts, microinteractions or motion, or login and sign-up screens. Do not use for navigation structure (navigation-and-flows), colour and type (visual-design-system) or a full accessibility audit (accessible-design).

Use when starting or scoping a mobile app or responsive product, deciding what to build first, writing a design brief, planning user research, reducing clutter, designing onboarding, or asking how people use phones in real life. Covers research first, one primary action, feature prioritisation, mobile constraints (interruptions, one hand, weak signal) and onboarding. Do not use for screen layout (adaptive-layout-and-spacing), navigation choice (navigation-and-flows) or reviewing an existing UI (ux-review-and-testing).

Use when choosing or reviewing app navigation (tab bar, bottom navigation, hamburger menu, sidebar, rail), structuring information architecture, designing sheets, modals and dialogs flows, back behaviour, search, gestures or a multi-step flow such as checkout or sign-up. Do not use for form fields and messages (interaction-feedback-and-forms), screen spacing (adaptive-layout-and-spacing) or documenting site maps (ux-documentation-and-handoff).

Use when a task is about designing, reviewing or documenting a user interface or user experience for a phone app, tablet or responsive site, or when it is unclear which UI or UX skill applies. Routes mobile-first design work (UX principles, layout, navigation, feedback and forms, visual design, accessibility, documentation, review) to focused skills and enforces shared guardrails. Do not use for writing framework code (CSS, React, Flutter, native), brand strategy, or back-end work.

Use when writing UX documentation for an app: personas, user flows, site maps, wireframe and prototype notes, a style guide, component state specs, design principles, or a developer hand-off pack. Do not use for choosing the design itself (the design skills), for running usability tests (ux-review-and-testing) or for software documentation such as a README.

Use when asked to review, audit or critique an existing screen, flow or prototype for usability, run a heuristic evaluation, plan or analyse a usability test, or produce a ranked UX findings report. Do not use for designing a screen from scratch (the design skills), writing hand-off documents (ux-documentation-and-handoff) or a formal accessibility conformance claim (accessible-design).

Use when choosing or reviewing typography, type scale, colour palette, dark mode, icons, imagery, elevation, a spacing scale, design tokens or a style guide for a mobile or responsive product. Do not use for a full accessibility audit (accessible-design), screen layout (adaptive-layout-and-spacing) or brand strategy and illustration.