More screenshots

    Works with the AI tools you already use

    CClaude CodeCCursorCCodex CLIGGitHub CopilotGGemini CLIVVS CodeWWindsurf+15 more

    Mobile-First Web UI Redesign Agent

    by Shandra

    1

    The skill does not merely shrink desktop screens or stack existing columns.

    Secure checkout via Stripe

    0 installsSecurity scanned

    See it in action

    You say

    Project name: UrbanNest Furniture Store

    Website or application type: Shopify e-commerce store selling premium furniture and home accessories

    Primary mobile users: Homeowners Interior-design enthusiasts Apartment renters Mobile shoppers arriving from Instagram, Pinterest, Google Shopping, and organic search

    Primary mobile tasks: Browse product categories Review product images Select materials and colors Check dimensions Confirm availability Review delivery information Add products to the cart Complete checkout Save products to a wishlist Contact customer support

    Primary conversion: Add a configured product to the cart and complete checkout

    Secondary conversions: Save to wishlist Request a material sample Contact support Join the newsletter

    Current desktop structure: Large multi-row header Mega navigation Two-column product pages Left-side category filters Four-column product grids Wide feature tables Side-by-side cart and order summary Large newsletter modal Persistent chat widget Desktop-oriented footer with six columns

    Current mobile problems: The desktop header is compressed into two crowded rows. The menu contains six nested levels. Search is hidden inside the menu. Product titles appear below an oversized image gallery. Variant selectors use small swatches with no text labels. The Add to Cart button appears after long product descriptions. A sticky chat widget covers the Add to Cart button. The filter drawer loses selected filters after closing. Product comparison causes horizontal page scrolling. The cart quantity controls are too small. Checkout errors appear above the visible viewport. The virtual keyboard covers the final form field and payment CTA. The newsletter modal is taller than the viewport. Desktop images are loaded on mobile. Large layout shifts occur while product media loads.

    Critical pages: Home Category Search Results Product Detail Product Comparison Cart Checkout Wishlist Contact Account

    Critical components: Header Navigation Drawer Search Product Gallery Product Card Variant Selector Price Availability Delivery Information Add to Cart Sticky Purchase Bar Filters Sorting Comparison Table Cart Item Checkout Form Newsletter Modal Chat Widget Footer

    Navigation depth: Six levels in the current desktop mega menu

    Forms: Newsletter Contact Material Sample Request Account Registration Checkout Address Payment

    Filters: Category Price Material Color Style Room Availability Delivery Time Rating

    Tables: Product dimensions Product comparison Order history

    Modals: Newsletter Image zoom Size guide Material information Cart confirmation

    Sticky elements: Desktop header Chat widget Cookie banner Mobile Add to Cart bar Checkout summary

    Required integrations: Shopify checkout Wishlist application Product reviews Search Chat Payment providers Shipping calculator

    Frontend stack: Shopify Liquid JavaScript CSS Selected custom web components

    Design system: Partial custom design system

    Current breakpoints: 768 pixels and 1024 pixels only

    Target devices: Small mobile Standard mobile Large mobile Tablet portrait Tablet landscape Desktop

    Browser support: Current and previous major versions of Safari, Chrome, Firefox, and Edge

    Accessibility target: WCAG 2.2 AA implementation review

    Performance target: Improve mobile loading stability and interaction responsiveness Do not claim specific scores before measurement

    Localization: English Spanish German Allow at least 35% text expansion

    Analytics: Shopify analytics Google Analytics Advertising pixels Current mobile events are incomplete

    Need output: Complete mobile-first redesign Content-priority map Navigation architecture Product-page redesign Category-page redesign Mobile filters Sticky Add to Cart Cart and checkout redesign Form behavior Modal behavior Accessibility Performance Analytics events Experiment roadmap Developer handoff Acceptance criteria Regression tests QA checklist Risk assessment

    Need variations: Commerce-Focused Mobile Redesign Editorial Premium Mobile Redesign Fast-Purchase Mobile Redesign

    Special constraints: Preserve premium brand positioning. Do not hide product dimensions. Do not hide delivery terms. Do not disable zoom. Do not use swipe as the only image control. Do not let sticky controls cover content. Do not invent shipping, payment, return, or availability rules.

    Your agent does

    === MOBILE-FIRST WEB UI REDESIGN ===

    Project: UrbanNest Furniture Store

    Product Type: Premium furniture and home-accessories e-commerce store

    Primary Mobile Conversion: Configure a product, add it to the cart, and complete checkout.

    === EXECUTIVE SUMMARY ===

    The current mobile experience is a compressed desktop store rather than a deliberately designed mobile purchasing journey.

    The most important redesign priorities are:

    1. Replace the crowded desktop header with a compact mobile header.
    2. Promote search outside the navigation drawer.
    3. Simplify the six-level mega menu into a drill-down mobile structure.
    4. Move product identity, price, variants, delivery context, and Add to Cart earlier.
    5. Replace unlabeled color swatches with accessible labeled selections.
    6. Introduce a safe sticky purchase bar after the inline CTA leaves view.
    7. Preserve filter state and applied-filter visibility.
    8. Replace page-level horizontal comparison with a mobile comparison model.
    9. Redesign checkout for virtual-keyboard safety.
    10. Resolve conflicts between Add to Cart, chat, cookie, and browser controls.
    11. Use responsive product media and reserve dimensions.
    12. Convert oversized desktop modals into mobile-appropriate patterns.

    === PRIMARY MOBILE TASK ===

    Primary User: Mobile shopper evaluating premium furniture

    Primary Task: Review the product, select a material and color, understand delivery conditions, and add the configured product to the cart.

    Entry Points:

    • Social advertisement
    • Product search
    • Category page
    • Saved product
    • Direct product link

    Success: A valid product configuration is added to the cart.

    Failure Risks:

    • Variant confusion
    • Hidden delivery information
    • Sticky-control collision
    • Lost selections
    • Unclear availability
    • Form obstruction
    • Slow media
    • Horizontal overflow

    === CONTENT-PRIORITY MAP ===

    Product Title: Priority 1 — Essential

    Mobile Position: Above the primary product media or immediately after the first media frame, depending on final visual validation.

    Price: Priority 1 — Essential

    Mobile Position: Near the title and selected variant.

    Variant Selection: Priority 1 — Essential

    Mobile Position: Before Add to Cart.

    Availability: Priority 1 — Essential

    Delivery Information: Priority 1 — Essential

    Primary CTA: Priority 1 — Essential

    Product Dimensions: Priority 2 — Supporting

    Mobile Position: Expandable details available before the lower marketing content.

    Materials and Care: Priority 2 — Supporting

    Reviews: Priority 2 — Supporting

    Brand Story: Priority 3 — Optional

    Related Products: Priority 3 — Optional

    Newsletter: Priority 4 — Deferred

    Decorative Editorial Content: Priority 4 — Deferred or reduced

    Repeated Benefit Blocks: Priority 5 — Remove when duplicative

    === BREAKPOINT STRATEGY ===

    Small Mobile: 0–479 pixels

    Standard Mobile: 480–767 pixels

    Tablet: 768–1023 pixels

    Desktop: 1024–1439 pixels

    Wide: 1440 pixels and above

    Validation Rule: Final breakpoints should be adjusted according to navigation pressure, product-card minimum width, form behavior, product-media layout, and content expansion.

    === MOBILE HEADER ===

    Structure:

    • Menu trigger
    • Centered or left-aligned logo
    • Search
    • Cart

    Optional: Account access inside the navigation drawer unless usage data supports direct header access.

    Height: Compact enough to preserve viewport space.

    Sticky Behavior:

    • Sticky after initial scroll
    • Reduced height in the scrolled state
    • Border rather than a heavy shadow
    • Correct anchor offset
    • Safe-area support
    • No content overlap

    Accessible Names:

    • Open Menu
    • Search
    • View Cart

    Cart Badge: Expose the cart quantity programmatically.

    === MOBILE NAVIGATION ===

    Navigation Type: Accessible drill-down drawer

    Level 1:

    • New
    • Furniture
    • Rooms
    • Collections
    • Inspiration
    • Sale
    • Support

    Level 2 Example: Furniture

    • Seating
    • Tables
    • Storage
    • Beds
    • Lighting
    • Accessories

    Behavior:

    • Dedicated back action
    • Visible current category
    • Internal scrolling
    • Persistent close action
    • Background interaction prevented
    • Focus moves into the drawer
    • Focus returns to the menu trigger after closing
    • Escape supported where appropriate

    Search: Placed in the header and repeated at the top of the drawer.

    Avoid: Displaying all six navigation levels simultaneously.

    === MOBILE PRODUCT-PAGE ORDER ===

    1. Breadcrumb or compact category context
    2. Product title
    3. Rating and review link
    4. Product media
    5. Price
    6. Financing context when verified
    7. Variant selection
    8. Availability
    9. Delivery or pickup information
    10. Inline Add to Cart
    11. Returns and trust summary
    12. Product overview
    13. Dimensions
    14. Materials and care
    15. Reviews
    16. Related products
    17. Editorial brand content

    === PRODUCT MEDIA ===

    Mobile Pattern: Full-width media gallery

    Controls:

    • Swipe
    • Visible Previous button
    • Visible Next button
    • Image counter
    • Thumbnail or compact selector
    • Full-screen image view
    • Zoom controls

    Critical Rule: Swipe must not be the only navigation method.

    Responsive Images:

    • Load mobile-appropriate sources
    • Preserve intrinsic dimensions
    • Use art direction where needed
    • Avoid loading all high-resolution desktop assets immediately
    • Lazy-load noninitial media

    Alternative Text: Describe meaningful product and variant information.

    Variant Synchronization: Selecting a material or color should update the relevant media without resetting the user's scroll position.

    === VARIANT SELECTOR ===

    Material Selector: Labeled options with material name and optional texture preview.

    Color Selector: Visual swatch plus visible or programmatically associated color name.

    Selected State:

    • Strong border
    • Check indicator
    • Text label
    • Programmatic selected state

    Unavailable State:

    • Visible Unavailable label
    • Explanation where needed
    • Not communicated through low opacity alone

    Price Change: Update price without causing layout shift.

    Image Change: Update product media while preserving context.

    Validation Error: Choose a material and color before adding this product to the cart.

    === INLINE ADD-TO-CART AREA ===

    Include:

    • Selected material
    • Selected color
    • Quantity
    • Price
    • Availability
    • Primary Add to Cart CTA

    Primary CTA: Add to Cart

    Secondary Action: Save to Wishlist

    Requirements:

    • Full-width primary button
    • Clear disabled reason
    • Loading state
    • Success state
    • Error recovery
    • Duplicate-submission prevention
    • Focus remains understandable after state changes

    === STICKY PURCHASE BAR ===

    Visible When: The inline Add to Cart section has scrolled outside the viewport and a valid product context exists.

    Contents:

    • Compact product or selected-variant summary
    • Price
    • Add to Cart

    Optional: Variant reminder when a required choice is missing.

    Hidden or Adapted When:

    • Virtual keyboard is open
    • Modal is active
    • Cart drawer is active
    • Cookie controls conflict
    • Checkout begins

    Layout: Reserve bottom space equal to the bar height.

    Safe Area: Include device bottom safe-area inset.

    Chat Conflict: Suppress or reposition the chat widget while the sticky purchase bar is active.

    Acceptance: The bar must not cover content, errors, form fields, footer controls, or browser zoom content.

    === CATEGORY PAGE ===

    Header:

    • Category title
    • Short description
    • Result count

    Controls:

    • Filter
    • Sort

    Applied Filters: Visible chips beneath the controls.

    Product Grid: Two columns on standard mobile when product content remains readable. One column on very narrow screens or for editorial products.

    Product Card:

    • Image
    • Product name
    • Price
    • Color count
    • Availability
    • Wishlist
    • Optional verified badge

    Avoid: Excessive card metadata and hidden product names.

    === FILTER SYSTEM ===

    Pattern: Full-screen mobile filter view

    Trigger: Filters — 3 Applied

    Sections:

    • Category
    • Price
    • Material
    • Color
    • Style
    • Room
    • Availability
    • Delivery Time
    • Rating

    Behavior:

    • Preserve selections
    • Show selected count
    • Show estimated result count when technically supported
    • Keep Apply and Clear actions reachable
    • Support internal scrolling
    • Restore focus to the trigger
    • Preserve product-list scroll context

    Primary CTA: Show Verified Result Count

    Secondary Action: Clear All

    Live Update: Use only when performance and user understanding remain acceptable.

    === SORTING ===

    Pattern: Accessible bottom sheet or compact select

    Options:

    • Recommended
    • Price: Low to High
    • Price: High to Low
    • Newest
    • Rating

    Recommendation Logic: Do not use Recommended unless the sorting logic is defined and approved.

    === PRODUCT COMPARISON ===

    Desktop: Full comparison table

    Mobile Strategy: Selected-product comparison

    Behavior:

    • Select two or three products
    • Show one feature group at a time
    • Keep product names visible
    • Allow product switching
    • Provide Previous and Next controls
    • Preserve complete specifications
    • Provide contained horizontal comparison only where relationships require it

    Groups:

    • Dimensions
    • Materials
    • Availability
    • Delivery
    • Care
    • Warranty when verified
    • Price

    Avoid: Page-level horizontal scrolling.

    === CART REDESIGN ===

    Cart Item:

    • Product image
    • Product name
    • Selected variant
    • Delivery estimate when verified
    • Quantity
    • Price
    • Remove
    • Save for Later

    Quantity Controls: Large touch targets with accessible labels.

    Order Summary:

    • Subtotal
    • Discounts
    • Shipping
    • Taxes where verified
    • Total

    Primary CTA: Proceed to Checkout

    Sticky Behavior: Use carefully and reserve space.

    Error State: Explain inventory or price changes without deleting the item.

    === CHECKOUT REDESIGN ===

    Recommended Structure: Clear sequential sections or a validated step flow.

    Sections:

    1. Contact
    2. Delivery Address
    3. Delivery Method
    4. Payment
    5. Review

    Form Rules:

    • Persistent labels
    • Correct autocomplete
    • Correct keyboard types
    • Data preservation
    • Inline errors
    • Error summary
    • Billing and shipping logic
    • No hidden charges
    • Review before final confirmation

    Virtual Keyboard:

    • Scroll the focused field above the keyboard
    • Keep errors visible
    • Adapt sticky order summary
    • Keep the payment action reachable
    • Avoid fixed elements covering the final fields

    Order Summary: Expandable but always provide access to the total.

    === MODAL TRANSFORMATIONS ===

    Newsletter Modal: Convert to an inline section, compact bottom sheet, or delayed mobile prompt.

    Do not show during checkout or active form completion.

    Image Zoom: Full-screen media view.

    Size Guide: Full-screen dialog or dedicated page with internal navigation.

    Material Information: Bottom sheet for concise content or dedicated page for complex information.

    Cart Confirmation: Compact drawer or inline confirmation that preserves product-page context.

    === FORM ARCHITECTURE ===

    Required:

    • Persistent labels
    • One-column flow
    • Logical field order
    • Appropriate input types
    • Autocomplete
    • Values preserved
    • Clear required status
    • Inline errors
    • Error summary for long forms
    • Save and resume where relevant
    • Reachable submit action

    Avoid:

    • Placeholder-only labels
    • Tiny helper text
    • Side-by-side address fields on narrow screens
    • Clearing fields after failure
    • Error messages only at the top

    === TOUCH REQUIREMENTS ===

    • Reliable control sizes
    • Adequate spacing
    • Clear selected states
    • Destructive actions separated from primary actions
    • No hover-only information
    • Non-gesture alternatives
    • Visible carousel controls
    • Accessible overflow menus
    • No tiny quantity or close controls

    === ACCESSIBILITY REQUIREMENTS ===

    • Semantic page structure
    • Logical heading hierarchy
    • Accessible navigation drawer
    • Visible focus
    • Keyboard support
    • Logical DOM order
    • Accessible variant names
    • Non-color availability states
    • Labeled filter controls
    • Filter focus restoration
    • Dialog focus management
    • Sufficient contrast
    • Browser zoom
    • Responsive reflow
    • Text enlargement
    • Reduced motion
    • Product-image alternative text
    • Touch-target review
    • Error summaries
    • Sticky-element collision testing
    • Virtual-keyboard testing

    === PERFORMANCE REQUIREMENTS ===

    Images:

    • Responsive sources
    • Mobile dimensions
    • Proper compression
    • Reserved aspect ratios
    • Lazy-loaded secondary images

    JavaScript:

    • Reduce noncritical scripts
    • Review chat, reviews, wishlist, and advertising integrations
    • Avoid heavy carousel libraries
    • Defer noncritical widgets

    Fonts:

    • Limit families and weights
    • Use appropriate loading behavior

    Layout:

    • Reserve product-media dimensions
    • Reserve sticky-bar space
    • Prevent late price or CTA shifts

    Mobile:

    • Do not load hidden desktop navigation or full desktop media unnecessarily
    • Test slow connections
    • Keep essential content and Add to Cart available early

    === CONTENT STRESS TESTS ===

    Test:

    • Long German product names
    • Long variant labels
    • Multiple delivery messages
    • Sale price and original price
    • Missing image
    • Unavailable variant
    • Twelve selected filters
    • No search results
    • Long checkout error
    • 200% zoom
    • 320-pixel viewport
    • Landscape mobile
    • Short viewport height
    • Virtual keyboard
    • Slow product-media loading

    === ANALYTICS EVENT MAP ===

    Event: mobile_menu_opened

    Properties:

    • entry_page
    • device_width_bucket

    Event: mobile_search_started

    Properties:

    • entry_page
    • acquisition_source

    Event: filter_opened

    Properties:

    • category
    • current_result_count

    Event: filter_applied

    Properties:

    • filter_count
    • result_count_bucket
    • category

    Event: product_variant_selected

    Properties:

    • product_id
    • variant_type
    • availability_state

    Event: sticky_add_to_cart_viewed

    Properties:

    • product_id
    • selected_variant_state

    Event: sticky_add_to_cart_clicked

    Properties:

    • product_id
    • selected_variant_state
    • scroll_depth_bucket

    Event: checkout_started

    Properties:

    • cart_size_bucket
    • device_type

    Privacy: Do not include names, addresses, payment information, private order details, email addresses, or sensitive customer data in analytics properties.

    === EXPERIMENT ROADMAP ===

    Experiment 1: Sticky Add to Cart

    Observation: The inline CTA appears after substantial product content.

    Hypothesis: A safe sticky purchase bar shown after the inline CTA leaves view will improve valid Add to Cart completion.

    Primary Metric: Mobile Add to Cart rate

    Guardrails: Variant-selection errors Accidental cart additions Page obstruction complaints

    Experiment 2: Search Placement

    Hypothesis: Keeping search visible in the mobile header will improve product discovery compared with menu-only search.

    Primary Metric: Search-to-product-view rate

    Experiment 3: Filter Experience

    Hypothesis: A full-screen filter view with applied counts will improve filter completion and product discovery.

    Primary Metric: Filtered product-view rate

    Guardrail: Filter abandonment

    Experiment 4: Checkout Keyboard Safety

    Hypothesis: Adapting sticky controls while the keyboard is active will reduce checkout form abandonment.

    Primary Metric: Mobile checkout completion

    === DEVELOPER HANDOFF ===

    Required Components:

    • MobileHeader
    • NavigationDrawer
    • MobileSearch
    • ProductGallery
    • VariantSelector
    • ProductPrice
    • DeliverySummary
    • AddToCart
    • StickyPurchaseBar
    • ProductCard
    • FilterTrigger
    • FilterView
    • AppliedFilterChip
    • SortControl
    • MobileComparison
    • CartItem
    • CheckoutForm
    • ErrorSummary
    • MobileDialog
    • BottomSheet

    Implementation Rules:

    • Use semantic DOM order.
    • Preserve filter and form state.
    • Reserve sticky-bar space.
    • Adapt sticky controls to the virtual keyboard.
    • Avoid page-level horizontal scrolling.
    • Provide gesture alternatives.
    • Load mobile-appropriate media.
    • Keep labels visible.
    • Maintain accessible focus behavior.
    • Verify all commerce rules before publication.

    === IMPLEMENTATION SEQUENCE ===

    1. Confirm primary mobile tasks and conversion path.
    2. Rebuild mobile header and navigation.
    3. Implement search.
    4. Reorder product-page content.
    5. Implement accessible product media.
    6. Implement variant selection.
    7. Implement inline and sticky Add to Cart.
    8. Implement category filters and sorting.
    9. Implement mobile comparison.
    10. Redesign cart.
    11. Redesign checkout.
    12. Replace desktop modals.
    13. Implement accessibility.
    14. Optimize performance.
    15. Add analytics.
    16. Complete device and browser QA.
    17. Launch prioritized experiments.

    === ACCEPTANCE CRITERIA ===

    Navigation:

    Given a keyboard or assistive-technology user opens the mobile navigation, when the drawer appears, then focus moves into the drawer, background content is unavailable, navigation is understandable, and focus returns to the menu trigger after closing.

    Variant Selection:

    Given a product requires material and color selection, when a mobile user chooses both options, then the selected states, availability, price, media, and Add to Cart readiness update without losing scroll context.

    Sticky Purchase Bar:

    Given the inline Add to Cart leaves the viewport, when the sticky purchase bar appears, then it displays the current price and action, reserves layout space, respects safe areas, and does not cover content.

    Filter Persistence:

    Given a user selects three filters, when the filter view closes and results update, then the selections remain visible, the applied count is correct, and the user's list context remains understandable.

    Checkout Keyboard:

    Given the virtual keyboard opens on the final checkout field, when the user enters payment or address information, then the field, validation message, and required action remain visible and reachable.

    Responsive Media:

    Given the page loads on a standard mobile connection, when the initial product view renders, then the primary image uses an appropriate responsive source, dimensions remain reserved, and secondary media does not delay the primary task unnecessarily.

    === REGRESSION TEST MATRIX ===

    Viewport Conditions:

    • 320-pixel mobile
    • 390-pixel mobile
    • Large mobile
    • Tablet portrait
    • Tablet landscape
    • Desktop
    • 200% zoom
    • Landscape mobile
    • Short-height mobile

    Navigation States:

    • Closed
    • Open
    • Deep navigation
    • Search active
    • Long labels
    • Cart badge

    Product States:

    • Default
    • Sale
    • Unavailable
    • Variant unavailable
    • Long title
    • Missing image
    • Multiple prices
    • Loading

    Filter States:

    • No filters
    • One filter
    • Many filters
    • No results
    • Network failure

    Checkout States:

    • Empty cart
    • Guest checkout
    • Signed-in checkout
    • Address error
    • Payment error
    • Inventory change
    • Price change
    • Keyboard active

    Accessibility Conditions:

    • Keyboard
    • Screen reader
    • Reduced motion
    • Zoom
    • Text enlargement
    • High contrast where supported

    === QA CHECKLIST ===

    Navigation:

    • Verify menu opening.
    • Verify drill-down levels.
    • Verify focus.
    • Verify scrolling.
    • Verify closing.
    • Verify search.
    • Verify cart badge.

    Product Page:

    • Verify title.
    • Verify images.
    • Verify controls.
    • Verify variants.
    • Verify price.
    • Verify availability.
    • Verify delivery.
    • Verify Add to Cart.
    • Verify sticky bar.

    Category:

    • Verify product cards.
    • Verify filters.
    • Verify sorting.
    • Verify applied chips.
    • Verify no-results state.

    Cart:

    • Verify quantities.
    • Verify variants.
    • Verify removal.
    • Verify totals.
    • Verify inventory changes.

    Checkout:

    • Verify autocomplete.
    • Verify keyboard types.
    • Verify errors.
    • Verify payment.
    • Verify review.
    • Verify virtual keyboard.
    • Verify total.

    Responsive:

    • Verify all target widths.
    • Verify orientation.
    • Verify zoom.
    • Verify long content.
    • Verify safe areas.
    • Verify no horizontal page scrolling.

    Accessibility:

    • Verify labels.
    • Verify focus.
    • Verify reading order.
    • Verify touch targets.
    • Verify dialogs.
    • Verify error summaries.
    • Verify gesture alternatives.

    Performance:

    • Verify image sizes.
    • Verify layout stability.
    • Verify font loading.
    • Verify script cost.
    • Verify slow network.
    • Verify interaction responsiveness.

    === RISKS ===

    Risk: Sticky controls collide with chat, cookies, or browser UI.

    Mitigation: Define component priority, reserve space, and suppress lower-priority controls during purchase tasks.

    Risk: Visual reordering conflicts with DOM order.

    Mitigation: Update semantic document order rather than relying on CSS order alone.

    Risk: Filter redesign loses selections.

    Mitigation: Use persistent filter state and test reopening, applying, clearing, and browser navigation.

    Risk: Product media remains too heavy.

    Mitigation: Use responsive sources, loading priorities, reserved dimensions, and mobile asset budgets.

    Risk: Mobile checkout errors remain difficult to discover.

    Mitigation: Use inline errors, an error summary, focus management, and keyboard-safe scrolling.

    === KNOWN LIMITATIONS ===

    • Checkout and payment behavior require live testing.
    • Shipping, availability, returns, and pricing require verification.
    • Accessibility requires implementation testing.
    • Mobile-browser behavior requires real-device validation.
    • Performance requires measured validation.
    • Analytics must be implemented and verified.
    • Experiment conclusions require sufficient evidence.
    • The redesign does not guarantee higher conversion, revenue, engagement, or retention.

    === FINAL PROFESSIONAL NOTE ===

    All business rules, prices, claims, analytics, support promises, payment behavior, shipping terms, account permissions, browser support, device support, and conversion statements must be verified before publication.

    The redesign is intended to improve mobile clarity, usability, accessibility, and conversion readiness. It does not guarantee higher conversion, engagement, revenue, retention, or search performance.

    What you get

    Audit mobile layouts for conversion leaks and navigation dead ends.Map desktop content to a mobile-first hierarchy based on task priority.Transform wide data tables into touch-friendly cards or accordion lists.Define sticky CTA behaviors that respect safe areas and virtual keyboards.

    About this skill

    Mobile-First Web UI Redesign Agent helps e-commerce stores, SaaS teams, agencies, local businesses, landing-page designers, product teams, no-code creators, and frontend developers transform desktop-oriented interfaces into clear, usable, accessible, and conversion-aware mobile experiences.

    The skill does not merely shrink desktop screens or stack existing columns. It rethinks the interface around mobile user priorities, narrow viewports, touch interaction, virtual keyboards, short attention windows, unstable network conditions, browser controls, device safe areas, and one-handed use.

    It begins by identifying the primary mobile users, their most important tasks, entry points, conversion goals, failure risks, current desktop structure, and critical mobile usability problems. It then creates a content-priority model that determines what remains immediately visible, what should be reordered, what can be progressively disclosed, what belongs in a drawer or detail screen, and what can be removed.

    The agent can redesign marketing websites, landing pages, e-commerce product pages, category pages, carts, checkout flows, SaaS dashboards, onboarding experiences, pricing pages, booking systems, lead-generation forms, account areas, analytics interfaces, customer portals, marketplaces, directories, local-business websites, membership products, AI applications, and enterprise web tools.

    It architects mobile navigation using compact headers, accessible drawers, bottom navigation, tab bars, drill-down menus, search-led navigation, workspace switchers, or role-based navigation. Each navigation system can include current-state behavior, labels, icons, focus management, scrolling, safe-area treatment, long-label behavior, responsive transitions, and keyboard interaction.

    The skill creates mobile CTA systems with one visually dominant primary action, strategically positioned inline actions, repeated actions where justified, and sticky bottom bars that reserve layout space, respect device safe areas, adapt when the virtual keyboard opens, and never obscure focused fields, validation errors, prices, or important content.

    It converts oversized desktop card systems into mobile-appropriate lists, compact cards, accordions, summary-and-detail layouts, full-screen detail views, grouped sections, or edge-to-edge panels. It preserves essential information and actions while reducing unnecessary visual density.

    For forms, the agent reorders fields according to task logic, converts multi-column structures into coherent mobile sequences, defines persistent labels, input types, autocomplete, mobile keyboard behavior, validation, error summaries, data preservation, save-and-resume behavior, progress indicators, sticky actions, and recovery after failed submission.

    It designs mobile filtering and sorting through filter chips, accessible drawers, full-screen filter views, progressive filters, applied-filter counts, persistent selection, result updates, clear actions, scroll restoration, focus restoration, and mobile-safe action placement.

    Wide tables and data grids are deliberately transformed through priority columns, contained horizontal scrolling, expandable rows, card views, compact lists, dedicated record screens, or task-specific responsive data grids. The chosen strategy is based on comparison needs, data relationships, row actions, editing, selection, accessibility, and user priorities.

    Desktop modals, drawers, and popovers are converted into mobile-appropriate full-screen dialogs, bottom sheets, dedicated pages, or inline disclosures. The skill defines focus entry, focus containment, dismissal, Escape behavior, internal scrolling, unsaved-change protection, keyboard adaptation, reachable actions, and background interaction prevention.

    For e-commerce, it can redesign mobile product media, variant selection, price presentation, availability, delivery information, trust content, reviews, Add to Cart behavior, sticky purchase bars, product filters, category cards, carts, and checkout flows.

    For SaaS applications, it can redesign application shells, dashboards, tables, action queues, forms, settings, navigation, filters, saved views, alerts, dense data, mobile record pages, and contextual actions without stacking every desktop component in the original order.

    For landing pages, it restructures hero sections, copy hierarchy, trust placement, CTA timing, form placement, section order, comparison content, pricing, FAQs, media, and performance so the mobile page communicates value earlier and avoids excessive scrolling before the primary action.

    The skill includes responsive breakpoint recommendations, mobile and tablet behavior, content-driven layout transitions, orientation handling, browser zoom, text enlargement, right-to-left support, localization expansion, narrow-screen testing, short-height testing, missing-content states, slow-loading states, and virtual-keyboard scenarios.

    Accessibility requirements include semantic structure, logical headings, accessible control names, visible focus, keyboard navigation, reading-order alignment, adequate touch targets, sufficient contrast, persistent labels, non-color state communication, gesture alternatives, modal focus management, zoom, reflow, reduced motion, alternative text, media captions, and sticky-element safety.

    Performance guidance covers responsive images, mobile-specific media, asset compression, font loading, JavaScript cost, third-party scripts, layout stability, lazy loading, animation cost, slow connections, interaction responsiveness, and avoiding hidden desktop assets on mobile.

    The skill can also create mobile UI audits, conversion-leak reports, responsive matrices, analytics event maps, experiment roadmaps, implementation sequences, developer handoffs, acceptance criteria, regression plans, QA checklists, risk assessments, and structured JSON specifications.

    It prioritizes preserved functionality, clear mobile hierarchy, touch usability, accessible interaction, recoverable workflows, mobile performance, conversion readiness, realistic implementation, and consistent brand quality.

    The core commercial promise is: transform desktop-heavy web interfaces into clear, touch-friendly, accessible, conversion-aware mobile experiences without losing essential functionality, hierarchy, or brand quality.

    How to install

    Drop the file into your AI Agent. Works with Claude, Cursor, ChatGPT, and 20+ more.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    Listedtoday

    Creator

    Shandra is a top-ranked AI prompt creator and premium agent skill builder with an established track record in the AI marketplace. She is recognized as a #1 Top Seller on PromptBase, where she has built a trusted catalog of specialized AI prompts and agent skills for creators, entrepreneurs, educators, marketers, digital product sellers, and business professionals. With over 3,500 AI products published, more than 3,400 sales, and 1,000+ five-star reviews, Shandra has become known for creating practical, polished, and commercially useful AI resources that help users save time, organize complex ideas, generate high-quality content, build digital products, and transform creative concepts into actionable workflows. Her Agensi store focuses on premium, ready-to-use agent skills designed for real-world productivity. Each skill is developed with clear instructions, structured workflows, professional formatting, practical use cases, setup guidance, examples, edge-case handling, and a strong emphasis on usability. Her work combines creative strategy, prompt engineering, documentation design, business thinking, and practical automation into reliable tools that users can apply immediately. Shandra’s mission is to create AI skills that feel professional, useful, and complete from the first use — not generic templates, but carefully built workflow systems that help users think better, work faster, and produce stronger results.

    Frequently Asked Questions

    Popular in Web & App UI Design