Commercial UI/UX for Codex

    0

    Design, review and repair SaaS interfaces with clear workflows, complete states and accessible controls.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Commercial UI/UX for Codex

    Example session with this skill installed

    Use commercial-ui-ux to design a responsive B2B SaaS refund approval screen. Design specification only; do not write code. Users: support agents submit refund requests; finance approvers approve requests up to their authorized limit. Existing system: light neutral surfaces, blue primary actions, compact tables, 8px spacing, 8px radii. Keep that system. Include pending requests, amount/currency, reason, audit context, permission limits, loading/empty/error states, safe approval and rejection, and a mobile strategy. Use fictional data and state assumptions.

    • Read your context and instructions
    • Compiled the commercial ui ux

    Refund approval screen — design specification

    The screen helps support agents submit complete requests and finance approvers make traceable decisions. This is a design-only demonstration using fictional data; no interface was built or browser-tested.

    Roles and assumptions

    Support agents can create requests and view their own submissions; finance approvers can review requests within their assigned scope. Approval limits and permissions must come from the server. Amounts always display their currency; do not compare different currencies as if they shared one limit. Actual refund execution, customer notification and policy eligibility are separate backend decisions.

    Desktop structure

    Keep the existing app navigation. Use a page title, pending-count status and filters for status, currency and assignee above the compact table. Columns: request ID, customer reference, submitted time, amount/currency, reason, status and owner. Selecting a row opens a detail panel with the request, evidence, permission status and chronological audit trail. Keep approve/reject actions beside the relevant amount and reason. Avoid bulk approval for the initial design.

    Fictional example: RF-1042, customer DEMO-018, USD 120.00, duplicate charge, awaiting finance review. Example policy: an approver has a USD 500.00 limit. These are demonstration values, not a recommended refund policy.

    Main and recovery journeys

    1. Support creates a request with an order reference, amount/currency and reason. Show field errors beside the relevant input and preserve the draft when submission fails.
    2. Finance opens a pending request, checks the evidence, permission scope and decision history.
    3. Approve opens a confirmation with request ID, customer reference and exact amount/currency. A second explicit confirmation submits the decision; the server revalidates permission, limit and current request status.
    4. Reject requires a reason and shows the customer-facing consequences before confirmation. Preserve the reason on retry.
    5. If another approver changed the request, retain the local context and refresh the latest status before allowing another decision.

    State contract

    StateVisible behaviorAction behavior
    LoadingTable skeleton; retain page contextDecision controls unavailable
    No pending requestsExplain that the queue is clearOffer completed-history navigation
    No filter matchesShow selected filters and clear-filters controlPreserve the current filter choices
    Load failureError with retry; retain prior rows marked stale when availableBlock decisions based on stale details
    Missing evidenceIdentify the missing fields and responsible submitterRequest clarification rather than approve
    Outside permission/limitState the scope or currency-specific limitDisable approval and offer escalation
    SubmittingKeep details visible with a progress labelPrevent duplicate submissions
    ConflictShow that the status changed and who changed it if authorizedRequire refresh before another decision
    SuccessShow confirmed decision, actor and server timestampRemove pending actions; link to audit history

    Mobile and accessibility

    At 375px, replace the dense table with request cards that retain ID, amount/currency, status and primary detail action. Open request details as a full page with sections for evidence and history. A bottom action bar must reserve enough content space so it never covers errors or the last audit entry. At 768px, use a list plus details only if both remain readable; at 1280px, use the compact table and detail panel. Keyboard users can reach every filter and action; labels, field errors and focus states must remain visible. Status uses text and icon cues as well as color.

    Visual strategy and acceptance checks

    Use the existing neutral surfaces, blue action color, spacing and radius tokens. Reserve warning/error colors for actual risk; do not turn the page into a marketing layout. Verify text contrast, focus order, confirmation cancel/escape behavior, field-error association, stale-data blocking, duplicate-submit protection, permission revalidation and mobile content clearance. A developer and product owner must validate these checks against the real interface and refund policy before claiming completion.

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

    About this skill

    Build interfaces people can actually use

    Commercial UI/UX helps Codex design, review, repair and implement product interfaces around the user's job and business workflow. It is especially useful for SaaS dashboards, admin panels, forms, tables and mobile approval flows.

    What it does

    • Models users, roles, primary journeys and recovery paths before choosing visual styling.
    • Preserves existing information architecture, components, routes and design tokens during repairs.
    • Covers loading, empty, error, disabled, permission and protected-action states.
    • Defines responsive layouts, keyboard focus, field-level validation and accessible controls.
    • Infers a visual strategy from the product when no brand guide or reference is provided.
    • Routes to an industry matrix with 18 domains and 54 named scenario patterns. These are human-readable starting points, not 54 ready-made coded screens.

    Three ways to use it

    Design: request a workflow, screen specification and acceptance checklist. Review: request prioritized findings with user impact and suggested repairs. Implement or repair: work within your existing frontend stack and verify using your project's available checks.

    Package and version

    Free public core, version 0.1.0-rc.1 (release candidate). Includes SKILL.md, English/Chinese entry and product documentation, and separate English and Chinese versions of all nine supporting references (24 files total). The agent reads the appropriate language references and answers in your requested language.

    The skill contains Markdown guidance only. It does not install dependencies or run a background service. Coding tasks use the tools and permissions already available to your agent.

    Boundaries

    Output still needs human review and project-specific verification. This skill does not certify production readiness, accessibility compliance or legal, medical, financial or security compliance. It does not create logos or illustrations and does not support deceptive UI patterns.

    Source and documentation

    Release candidate 0.1.0-rc.1. Industry patterns are guidance, not ready-made components. No guaranteed compliance, conversion uplift or production readiness. Screenshot checks require browser/image tools; implementation requires access to the selected user project. If a connector cannot expose supporting docs, full reference-based behavior is unavailable.

    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

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    macOS

    Permissions

    Read Files
    Write Files
    Browser
    Network Access

    Design-only work can use the supplied brief without filesystem access. Reviewing an existing project requires reading only the user-selected files. Implementation additionally writes those files and may use a terminal for project checks and a browser for visual verification. No environment-variable harvesting, credentials or unrelated account access is required. External network access is optional for user-requested references or the project development workflow.

    Listed1 month ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions

    Yes. This listing contains the free public core, version 0.1.0-rc.1. The public source remains on GitHub.

    Designed for Codex / Codex CLI. Other SKILL.md-compatible agents must expose the supporting files; cross-agent behavior has not been independently verified.

    24 Markdown/version files: SKILL.md, bilingual entry/product documentation and separate English and Chinese versions of all nine supporting references. No executable runtime or background service.

    Yes. Provide the selected project files, user journeys and constraints. The skill prioritizes findings and preserves existing components, routes and design tokens during scoped repairs.

    Design-only work can use a supplied brief. Project review reads selected files; implementation can write them and use terminal/browser checks. External network access is optional; no unrelated service login or credentials are required.

    No. It guides accessibility and interaction checks; a human and the project tests must verify the real interface. The release candidate does not certify compliance or business outcomes.

    New in Frontend & Web Apps