More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Signal UI UX Studio

    1

    One self-contained UI/UX skill: Signal design system, navigation, accessibility, motion, data integrity and rendered verification.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Signal UI UX Studio

    Example session with this skill installed

    Build a Signal inventory screen with long Vietnamese names; keep ownership unknown while refreshing, preserve the current route and verify keyboard navigation.

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

    Working neutral UI, source changes, bounded positive/negative fixture results, screenshots, source hashes and explicit native/backend limitations.

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

    About this skill

    Six UI/UX capabilities in one agent skill. Design interfaces from the original Signal ink/bone/orange foundation, preserve host navigation and data contracts, implement keyboard and focus behavior, respect motion preferences, handle stale responses and uncertain writes, and verify rendered outcomes.

    Includes an original offline seven-surface gallery, pure state helpers with executable regression tests, a local-only browser runner and four licensed OFL fonts. Each module is loaded only when relevant. No Observer runtime, account or API key is required.

    Marketplace files use standard JavaScript ESM. A no-download font preparer reconstructs the four checked font assets from bundled data; all notices and hashes are included. Instructions and helpers are reusable on web and React Native adapters; the included rendered fixture is web.

    The gallery and acceptance examples are browser fixtures. React Native adapters, TalkBack/VoiceOver, OS keyboard/insets, native optical material quality, FPS and real backend/account behavior need separate target-platform evidence. Custom composite widgets, shadow DOM and iframe focus need host-specific integration. This is not a universal accessibility or security certification.

    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 15 days ago

    Requires

    Node.js 22.12+
    Playwright
    Google Chrome or Microsoft Edge

    Permissions

    Terminal / Shell

    File Scopes

    The
    user-selected
    application
    or
    local
    skill
    folder
    Its
    explicitly
    selected
    fixture
    and
    artifact
    output
    directories

    No external account/API or dependency download. Font preparation creates only four fixed verified local font files. Serving and browser QA use owned loopback fixtures and fresh browser contexts. Does not change agent trust/settings.

    Listed16 days ago

    What's inside

    Frequently Asked Questions

    No. This is one $10 one-time skill containing all six modules.

    It includes portable state helpers, platform recipes and an original web starter. Integrate them into the host components and verify the actual native application separately.

    No. Prepare the four bundled verified fonts locally, then serve the fictional gallery offline. Browser QA requires a preinstalled compatible Playwright and Chrome/Edge.

    No. Checks apply to named fixtures and evidence. Screen readers, native performance, custom widgets and real backend behavior require their own acceptance.

    New in Mobile Development