More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    clickable html prototype

    1

    Build portable, single-file HTML clickable prototypes with built-in state management and stakeholder QA tools.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    clickable html prototype

    Example session with this skill installed

    Build a single-file HTML clickable prototype for any product or flow. Stakeholders open it, click through, and react. No design tool, no build step, nothing to install.

    • Read your context and instructions
    • Compiled the clickable html prototype
    • Generated the UI component

    I have created the initial prototype file. It includes the core navigation logic, a state object initialized for trial tracking, and the two primary screens required to prove your claim.

    pay-flow-trial-check-prototype.html

    <!-- 
    HANDOFF: Resume with 'read the handoff note in this html and continue'.
    FILE: pay-flow-trial-check-prototype.html
    PREFIXES: p- (plan), c- (checkout)
    FUNCTIONS: go(id), buildPlan(), buildCheckout()
    -->
    <!DOCTYPE html>
    <html>
    <head>
        <style>
            :root { --primary: #2563eb; --bg: #f8fafc; }
            body { font-family: sans-serif; margin: 0; background: var(--bg); }
            .page { display: none; height: 100vh; width: 100%; }
            .page.active { display: flex; flex-direction: column; align-items: center; justify-content: center; }
            .card { background: white; padding: 2rem; border-radius: 8px; shadow: 0 4px 6px -1px rgb(0 0 0 / 0.1); }
            .btn { background: var(--primary); color: white; padding: 0.5rem 1rem; border: none; border-radius: 4px; cursor: pointer; }
            .qa-panel { position: absolute; left: calc(100% + 20px); top: 0; width: 200px; background: #333; color: white; padding: 10px; font-size: 12px; }
        </style>
    </head>
    <body>
        <div id="p-select" class="page active">
            <div class="card">
                <h1>Select a Plan</h1>
                <p>7-day free trial, then $29/mo.</p>
                <button class="btn" onclick="go('c-pay')">Start Trial</button>
            </div>
        </div>
        <div id="c-pay" class="page">
            <div class="card">
                <h1>Checkout</h1>
                <p><strong>Total today: $0.00</strong></p>
                <p style="color: #d97706;">First charge: August 20, 2024</p>
                <button class="btn" onclick="alert('Trial started')">Confirm</button>
            </div>
        </div>
    
        <script>
            let S = { trialDays: 7, plan: 'pro', firstCharge: '2024-08-20' };
            function go(id) {
                document.querySelectorAll('.page').forEach(p => p.classList.remove('active'));
                document.getElementById(id).classList.add('active');
            }
        </script>
    </body>
    </html>
    

    Next steps

    1. Open the file in a browser to verify the flow from plan selection to checkout.
    2. Add the QA_PANEL controls to toggle different trial lengths or charge dates.
    3. Update the internal Guide overlay with the specific conversion claim details.

    pay-flow-trial-check-prototype.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

    Stop wasting time in design tools or complex dev environments when you just need stakeholder buy-in. This skill produces single-file, self-contained HTML prototypes that work anywhere with zero dependencies. It builds high-fidelity, clickable flows that users can actually test, allowing you to validate claims before writing production code.

    What it does

    • Single-file delivery creates portable HTML files with inline CSS, JS, and base64 images that survive being emailed.
    • State management implements a global S object to handle complex logic like trial countdowns, plan tiers, and storage caps.
    • Interactive navigation manages a real history stack with go(id) and goBack() functions alongside keyboard navigation.
    • QA panel integration builds an absolute-positioned sidebar for stakeholders to force-toggle edge cases during meetings.
    • In-file documentation maintains a handoff comment and guide overlay to track decisions, fix logs, and "why" notes.
    • Resilient architecture uses a NAV_TREE and standardized builders to ensure structural changes don't break journey flows.

    How it works

    1. Initialize by copying the provided starter skeleton or reading an existing prototype file to understand its current state.
    2. Define the argument by identifying the specific claim the prototype proves and the primary screens required to show it.
    3. Build or extend screens using <div class="page"> structures, wiring interactions to the go() function and state object.
    4. Update the guide by recording specific stakeholder quotes and dated changes directly into the file's internal memory blocks.

    Frameworks & tools

    The skill produces vanilla HTML5, CSS3, and JavaScript. It uses Node.js for syntax checks and base64 encoding for image assets.

    Why this beats prompting it yourself

    Standard LLM prompts often produce disconnected snippets or fragile code that breaks when the file grows. This skill enforces a strict state machine, standardized navigation logic, and internal memory blocks that prevent the "forgetting" common in long sessions.

    Use cases

    • Validate a specific UX hypothesis with a non-technical decision maker.
    • Model complex monetization "exit paths" like downgrades and lapsed trials.
    • Create a portable sales demo that works offline or via email attachment.
    • Side-by-side comparison of "as-is" versus "redesign" concepts in one file.

    Known limitations

    The skill prioritizes a single-file budget. If assets exceed 2MB, it replaces screenshots with rebuilt components rather than splitting files.

    Limited to single-file HTML outputs under 2MB. Requires base64 encoding for images. High-fidelity components are prioritized over screenshots to maintain file size constraints.

    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 today

    Permissions

    Read Files
    Listedtoday

    What's inside

    Frequently Asked Questions

    The skill generates a single, self-contained HTML file containing all necessary CSS, JavaScript, and assets. This makes it easy to share via email or Slack without needing a hosting environment or external dependencies.

    Unlike static mockups, this skill implements a global state object and a navigation tree. This allows you to simulate complex logic like trial expirations, user permissions, and multi-step workflows that react to user input.

    The skill includes a built-in QA panel that stays with the file. This allows stakeholders to instantly toggle between different user states or edge cases during a live demo without manually resetting the prototype.

    This skill is compatible with any AI agent capable of writing and editing code, such as ChatGPT, Claude, or specialized IDE agents. It provides a standardized framework that helps the agent maintain consistency as the project grows.

    To keep the file portable and under the 2MB recommendation, the skill uses vanilla HTML5/CSS3 and base64-encoded assets. If a prototype becomes too large, it automatically switches to rebuilding UI components with code rather than using heavy image files.

    New in Frontend & Web Apps