More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    UI States & Edge Cases Designer

    1

    Generate comprehensive UI state specifications, microcopy, and transition logic for robust interface development.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    UI States & Edge Cases Designer

    UI States & Edge Cases Designer

    Example session with this skill installed

    Design the UI states for a 'Search' component in a React-based CRM. Users search for customers by name or ID. Handle loading, no results, and API timeout errors.

    • Read your context and instructions
    • Compiled the ui states

    I have mapped the UI states for the CRM Search component, focusing on user recovery and data persistence during network interruptions.

    Search Component Specifications

    State IDState NameTriggerUser-Visible ContentAvailable ActionsRecovery Behavior
    ST-01DefaultComponent MountEmpty search input, "Search by name or ID" placeholderInput text, SubmitN/A
    ST-02LoadingSearch SubmittedSkeleton list or progress spinnerCancel searchStop request on cancel
    ST-03SuccessData ReturnedResult list with count, highlighted termsView record, Edit, New searchN/A
    ST-04EmptyNo match found"No customers found for '[query]'", check spellingClear search, Try againReturn to Default
    ST-05Error (Timeout)Request > 10s"Connection timed out. Your search is saved."Retry, Contact SupportKeep query in input

    State Transition Map

    flowchart TD
        Default -- "Submit Query" --> Loading
        Loading -- "API Success" --> Success
        Loading -- "0 Results" --> Empty
        Loading -- "Timeout/Error" --> Error
        Error -- "Retry" --> Loading
        Empty -- "Clear" --> Default
    

    Microcopy & Accessibility

    • Success: "Found 12 customers matching 'Smith'."
    • Error: "We couldn't reach the server. Check your connection and try again."

    A11y: Use aria-live="polite" for the result count and aria-busy="true" during ST-02. Ensure the search button has a descriptive name during loading.

    Next steps

    1. Review the data preservation rule for the ST-05 Retry button.
    2. Confirm if partial name matches should trigger a "Did you mean?" state.
    3. Integrate these acceptance criteria into your Jira ticket.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    UX debt often starts with ignored edge cases. Developers frequently receive happy-path designs that lack specs for network failures, empty results, or permission hurdles. This skill forces those hidden states into the light, providing structured documentation for every interaction permutation.

    What it does

    • State Inventory mapping lists every component state from loading and success to partial-data and session-expiry.
    • Recovery design defines specific retry, cancel, and edit behaviors to prevent user dead-ends.
    • Microcopy generation provides actionable, empathetic error and success messaging that avoids technical jargon.
    • Accessibility auditing suggests focus management, status announcements, and color-independent status indicators.
    • Developer handoff generates acceptance criteria and transition rules to bridge the gap between design and implementation.

    How it works

    1. Scope definition identifies the feature, user goals, and target framework to set boundaries.
    2. State inventory maps components against a checklist of 15+ potential states like rate-limiting or stale data.
    3. Spec generation builds a detailed table for each state including triggers, visibility rules, and data preservation.
    4. Transition mapping creates Mermaid flowcharts to visualize how users move between success, error, and recovery paths.

    Frameworks & tools

    Works with any frontend framework including React, Vue, Svelte, or HTMX. Outputs structured Markdown and Mermaid.js diagrams for integration into Jira, GitHub, or internal wikis.

    Why this beats prompting it yourself

    Generic prompts often miss rare edge cases like "duplicate submission prevention" or "partial data results." This skill uses a systematic 10-step workflow and a rigorous state checklist to ensure no interaction path is forgotten.

    Use cases

    • Drafting error handling specs for complex multi-step forms.
    • Designing the "empty state" experience for new dashboard users.
    • Mapping re-authentication flows for expired sessions in secure apps.
    • Auditing existing components for accessibility and keyboard focus traps.

    Known limitations

    Does not generate functional code, Figma files, or visual assets. Logic is based on provided descriptions and assumes standard web/mobile interaction patterns.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.

    Does not generate functional code, Figma files, or visual assets. Logic is based on assumptions unless backend and API behaviors are explicitly provided.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 21 days ago

    Permissions

    Write Files
    Listed21 days ago

    What's inside

    Frequently Asked Questions

    This skill acts as a specialized UX architect, transforming basic designs into comprehensive technical specifications that cover edge cases like network failures, empty states, and permission errors that are often missed in standard design handoffs.

    You receive a structured documentation suite including state inventories, recovery behavior specs, microcopy for error messages, accessibility guidelines, and Mermaid.js flowcharts for visual logic.

    This skill is designed to work with any text-based AI agent that supports Markdown; the generated logic and specifications are framework-agnostic and compatible with React, Vue, Svelte, and more.

    No complex setup is required; once you add the skill to your agent, you simply provide your feature goals and target framework to begin the 10-step systematic state analysis.

    While this skill generates structured Markdown and Mermaid diagrams for Jira or GitHub, it focuses on design logic and specifications rather than generating functional code or visual Figma assets.

    New in Frontend & Web Apps