More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Frontend UI Design System — Tokens, Components & QA

    1

    Make shared controls consistent across screens. Consolidate tokens and component states, then check the views they affect.

    Free

    12 usesSecurity scanned
    Frontend UI Design System — Tokens, Components & QA

    Frontend UI Design System — Tokens, Components & QA

    Example session with this skill installed

    Synthetic workshop example; no live booking or customer data.

    Use the supplied before/index.html and before/styles.css. Browse, Details and Checkout use three different primary-button styles; the stylesheet also removes the focus outline.

    Keep the supplied Twilight palette and typefaces. Implement one shared primary-button variant across those three views. Include disabled and loading examples, visible keyboard-focus styling, compact/wide layout rules and reduced-motion handling. Report the files changed and the checks you actually ran. Leave browser and booking behaviour unverified when they have not been exercised.

    • Read your context and instructions
    • Compiled the frontend ui design
    • Generated the UI component

    Shared button implemented

    The three journey actions now use .button.button--primary. Their labels still describe the local action: “Reserve a seat” in Browse and Details, then “Confirm booking” in Checkout.

    BeforeShared rule now in the source
    Three unrelated colours, padding values and corner shapesOne action colour, spacing rule and control radius
    button:focus removes the outlineA separate 3px focus-visible outline
    Only the default button is representedNative disabled and disabled/loading examples; loading includes aria-busy
    Each section defines its own treatmentAll three views consume the same primary variant

    Files: after/index.html, after/styles.css, and local font assets with their licence notices.

    Agensi file preview: The index.html card labelled “TSX · React component” is Agensi’s preview, not a retained example output or runtime proof. This example changed and inspected local HTML/CSS fixture source; React delivery and browser execution were not verified.

    Checked in source: all three journey buttons use the shared variant; no inline style overrides remain; focus, disabled, loading, label wrapping, compact/wide layout and reduced-motion rules are present. The nine recorded source checks passed. The specified solid action/background colour pair calculates to 9.58:1; that calculation does not certify the whole interface.

    Still to inspect: rendered compact/wide layout, overflow, keyboard order and visible focus, hover/disabled/loading appearance, and state transitions. No browser check or live booking was run.

    Next step: render this slice in the target project and inspect those states before extending the shared rule to the remaining screens.

    index.html

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    A button changes colour from one screen to the next. Keyboard focus disappears in one view. A new page adds another exception to maintain.

    Frontend UI Design System helps your coding agent turn those differences into shared rules that the next screen can reuse. Give it your project, the affected views and the brand you already use. It inspects existing patterns, connects each proposed rule to a product need, and applies the change to a representative part of the interface when implementation is requested.

    Carry one decision across the interface

    • Define colour, type and spacing roles that serve repeated needs.
    • Give components meaningful variants and applicable focus, disabled, loading, empty and error states.
    • Check consumers of a changed token or component, including affected views beyond the first screen.

    You receive the shared rules, the component changes and a handoff showing which views and states were inspected. That gives the next contributor something specific to extend.

    Use it for a new UI system or drift across an existing app. Guidance can start from a brief; implementation needs project access, and rendered checks need a runnable preview and browser. The work follows your brand. User preference and accessibility certification require separate evidence.

    Start with one repeated control across two or three views.

    Rendered layout and interaction claims need an actual runnable preview and inspection. Screenshots or source checks do not establish user preference, field usability or accessibility certification. Guidance can start from a brief; code changes need project access and its normal tools. No component library or Figma import is included. Agensi’s generated-file card is a platform preview; it does not establish a retained React output or runtime proof for this HTML/CSS source example.

    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

    12 uses

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 25 days ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Browser

    Project source and design files only when the user asks for implementation or review. No external account, credentials, network access, or environment variables are required by the skill.

    Listed1 month ago
    Updated25 days ago

    What's inside

    Frequently Asked Questions

    No. A brief can supply the audience and task for a new system. For an existing app, the workflow starts with its tokens, components and established brand.

    A compact map from product needs to shared rules, component behaviour and inspected views. When you request implementation and provide project access, your agent applies a representative slice and reports the changes and checks.

    The package contains a workflow for your agent. It uses the project and tools you provide; it does not supply a ready-made component library or import a Figma file.

    It can define rules and inspect source, then name the precise layouts and interaction states still unverified. Source checks are not reported as browser results.

    New in Frontend & Web Apps