premium uiux design architect

    1

    Converts product briefs into implementation-ready UI/UX specs including flows, tokens, and accessibility.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    premium uiux design architect

    Example session with this skill installed

    Design a spec for a mobile-first peer-to-peer equipment rental app for professional photographers. Focus on high-trust transactions and gear condition verification.

    • Read your context and instructions
    • Compiled the premium uiux design

    I have architected a complete design specification for "LensLease," a peer-to-peer marketplace focused on high-end camera gear. The spec prioritizes equipment safety, verification flows, and mobile-optimized interactions for users in the field.

    Design Specification — LensLease (P2P Rental)

    1. Product Overview

    A high-trust marketplace for professional photographers to rent out gear. Scope covers search, booking, verification, and handoff.

    2. Users & Goals

    • Primary Persona: Professional "Pro-sumer" photographers needing specific glass for a shoot.
    • Core Goal: Successful booking with verified insurance coverage.
    • Primary Metric: Booking conversion rate (search to paid).

    3. Visual Language

    Token TypeValue / SelectionRationale
    Primary Color#0066FF (Electric Blue)High contrast, professional, tech-forward.
    Success Color#10B981 (Emerald)Clear confirmation for high-value transactions.
    TypographyInter (Sans-serif)Neutral, highly legible for technical gear specs.
    Corner Radius6pxPrecise, professional, non-consumerist feel.
    Type Scale12, 14, 16, 20, 24, 32Clear hierarchy for dense equipment data.

    4. Critical Task Flow: Gear Verification

    1. Lister selects "Add Gear": Mobile camera opens immediately.
    2. Guided Photo Capture: Overlay guides for Front, Back, Serial Number, and Sensor.
    3. Condition Tagging: User selects from "Mint", "Good", "Used" with required text description of wear.
    4. AI Verification: System flags serial number discrepancies (Success/Error branch).

    5. Interaction Patterns

    • Loading State: Skeleton screens for gear results to reduce perceived latency on 4G/5G.
    • Empty State: "No gear found in your area" with a primary CTA to "Expand Search Radius."
    • Error State: Inline validation for insurance uploads with specific reason (e.g., "Expiry date passed").

    6. Accessibility

    • Contrast: All CTA buttons maintain 4.5:1 ratio against backgrounds.
    • Touch Targets: Minimum 44x44px for all mobile action items.
    • Screen Readers: Mandatory aria-label for all gear condition icons.

    Next steps

    1. Review the Gear Verification flow to ensure it matches your backend validation logic.
    2. Use the token table to initialize your Tailwind or CSS variable theme.
    3. Map the screen inventory to your frontend routing structure.

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

    About this skill

    The problem

    Developers often receive vague product briefs that lack technical depth, forcing them to make design and UX guesses during implementation. This leads to inconsistent interfaces, missed edge cases, and expensive rework when the "feel" doesn't match stakeholder expectations.

    What it does

    • Generates complete UX/UI design specifications from rough product ideas or feature lists.
    • Defines information architecture including screen inventories, sitemaps, and task flows.
    • Establishes concrete visual systems with type scales, color palettes, spacing, and component variants.
    • Specifies interaction patterns for loading, empty, and error states to prevent implementation gaps.
    • Includes accessibility baselines (WCAG) and responsive breakpoints for every screen.

    Why this beats prompting it yourself

    Generic prompts result in "modern and clean" boilerplate that lacks functional depth. This skill enforces a multi-phase diagnostic process that resolves TBDs and placeholders before they reach your code. It ensures every user-facing string, error state, and accessibility requirement is documented, so you spend time building instead of deciding.

    Use cases

    • Transforming a napkin-sketch product idea into a buildable technical design spec.
    • Creating a source-of-truth for a new feature to align frontend and backend teams.
    • Developing a design system foundation for a project without a dedicated UI/UX designer.
    • Auditing and documenting the flows for a complex SaaS dashboard redesign.

    Known limitations

    This skill produces high-fidelity text-based specifications and design systems, not visual Figma files or image exports. It requires a text-based brief to start.

    Produces text-based technical specifications and design tokens only. Does not generate image files, Figma boards, or live prototypes.

    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 any payment.

    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 1 month ago

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill generates comprehensive text-based design specifications, including sitemaps, interaction patterns, and design tokens, bridging the gap between a vague idea and a developer-ready technical document.

    While this skill does not output Figma or image files, it provides the precise structural and visual data—such as type scales, HEX codes, and component logic—needed to build or design the interface immediately.

    This skill is compatible with most major LLMs that support large context windows, as it processes detailed product briefs and outputs high-density technical specifications.

    The skill includes access to the core UI/UX architecture logic and any future version updates to ensure the design patterns stay current with modern accessibility and responsive standards.

    Simply provide a text-based product brief or feature list; the skill then initiates a multi-phase diagnostic process to resolve design gaps before generating the final spec.

    Yes, the skill includes a dedicated accessibility module that ensures your specifications meet WCAG baselines and define responsive breakpoints for all screen sizes.

    New in Frontend & Web Apps