New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

HTML Feature Mocks

by imbue-ai in imbue-ai/bouncer

Explores a feature idea through HTML mocks that match the project's existing UI, keeping every earlier version and logging each requested tweak in a context file.

AGPL-3.0Auto-check passedFrontend & Design

Install HTML Feature Mocks

skills CLI
$ npx skills add imbue-ai/bouncer --skill create-html-mock -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install imbue-ai/bouncer create-html-mock --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/imbue-ai/bouncer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-html-mock .claude/skills/create-html-mock && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
create-html-mock
GitHub stars
400
Token cost
~677 tokens
SKILL.md length
331 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Explores a feature idea through HTML mocks that match the project's existing UI, keeping every earlier version and logging each requested tweak in a context file.

  • Works in 4 steps: Understand the feature: Read the user's… → Propose a feature name: Based on the… → Create the feature folder automatically:… → …
  • Sketching a new feature as HTML before building it
  • SKILL.md covers Initial Setup, Creating the Mocks, During Iteration and User's Feature Description
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The agent first reads your description, flags inconsistencies or gaps and asks clarifying questions, then proposes a short hyphenated feature name of two or three words and confirms it with you. It creates a folder for that feature under docs and starts a mocks.context.md file with the original description, if one does not already exist.

Mocks go into a single HTML file that shows several labeled scenarios or states, each with a short description, inside a realistic application window built by reading the project's UI code, with realistic sample data. Earlier mocks are never deleted, since each iteration gets a new file such as mocks-v2.html, and each new file is opened in your browser. Every requested change is recorded in a UI Tweaks Log in the context file so requirements can be extracted from it later.

When your agent uses it

  • Sketching a new feature as HTML before building it
  • Showing several states of a UI change in one file
  • Keeping a log of design feedback to turn into requirements later

Example prompts

  • “Create HTML mocks for a bulk-archive feature in our inbox view.”
  • “Mock up an empty state and an error state for the new export dialog, matching our current UI.”
  • “Make a v2 of the mocks with the filter bar moved to the left, and log the change.”

Requirements

  • A project with UI code for the mocks to imitate
  • A browser to open the HTML files

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Understand the feature: Read the user's description provided below. Review for inconsistencies, gaps, or potential enhancements. If…
  2. Propose a feature name: Based on the description, propose a short 2-3 word feature name (lowercase, hyphenated). Confirm this name with…
  3. Create the feature folder automatically: Use mkdir -p docs/ to create the directory (this is safe if it already exists). Then create
  4. Initialize the context file (only if newly created) with this structure

What it can do on your machine

Read from SKILL.md and the folder at commit 1ed480c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

HTML Feature Mocks loads about 677 tokens when it runs. Until then it costs about 14 tokens; SKILL.md has 331 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~14
When it runs · the whole SKILL.md, loaded when a task matches
~677

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from imbue-ai/bouncer at commit 1ed480c, republished under its AGPL-3.0 licence (© imbue-ai). 331 words, ~677 tokens.

Download SKILL.mdSave it as .claude/skills/create-html-mock/SKILL.md (or your agent's skills folder).
name
create-html-mock
description
Create HTML mocks for a new feature idea
disable-model-invocation
true
argument-hint
[feature description]

Create HTML Mock

You are helping the user explore and refine a feature idea through HTML mocks.

Initial Setup

  1. Understand the feature: Read the user's description provided below. Review for inconsistencies, gaps, or potential enhancements. If anything is unclear or ambiguous, ask clarifying questions before proceeding.

  2. Propose a feature name: Based on the description, propose a short 2-3 word feature name (lowercase, hyphenated). Confirm this name with the user before proceeding.

  3. Create the feature folder automatically: Use mkdir -p docs/<feature-name> to create the directory (this is safe if it already exists). Then create:

    • docs/<feature-name>/mocks.context.md - for tracking context (only if it doesn't already exist)

  4. Initialize the context file (only if newly created) with this structure:

    markdown
    # <Feature Name> - Mock Context

## Original Description
<paste the user's original description here>

## Clarifying Q&A
<record any clarifying questions and answers here>

## UI Tweaks Log
<record all UI feedback and tweaks requested during iteration>

Creating the Mocks

  1. Generate HTML mocks that demonstrate the feature:

    • Make sure it matches the look and feel of the project's existing UI
    • In a single html file, create multiple mocks showing the various requested scenarios/states
    • Label each one, and also provide a short description of the scenario it is demonstrating
    • Always show the new UI elements within the context of a realistic application window. Don't guess at what the app looks like. Read the UI code and create a close approximation.
    • Include realistic sample data

  2. Never delete previous mocks: Always create a new file for each iteration (e.g., mocks.html, mocks-v2.html, mocks-v3.html, or use descriptive names). Previous mock files must be preserved.

  3. Always open the HTML file: After writing a mock file, always run open <path-to-file> to open it in the user's browser.

Show full SKILL.md (77 more words)Show less

During Iteration

As the user provides feedback on the mocks:

  1. Log every UI tweak: Whenever the user requests a change to the mocks, update the "UI Tweaks Log" section in mocks.context.md with:

    • What was requested
    • What was changed

    At the end of each response where you make changes, note: (Logged: [brief description of change])

  2. Keep the context file current: This log will be used later to extract requirements, so be thorough.

User's Feature Description

$ARGUMENTS

© imbue-ai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/create-html-mock of imbue-ai/bouncer.

Open the folder on GitHubat commit 1ed480c

Compare with similar skills

HTML Feature Mocks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

HTML Feature Mocks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
HTML Feature Mocks this skillimbue-ai/bouncer400—~677Automated safety check: PassAGPL-3.0
Product Design Workflow BundleXiaomiMiMo/MiMo-Code14k—~721Automated safety check: PassMIT
Prototypeplugin87/ux-ui-agent-skills1.5k—~614Automated safety check: PassMIT
Product Designerborghei/Claude-Skills881—~3.1kAutomated safety check: PassMIT
Prototype to Figmaalima-max/prototype-to-figma-skill140—~7.8kAutomated safety check: PassMIT
LobeHub UX Checklistslobehub/lobehub83k—~2.6kAutomated safety check: PassCustom licence

Similar skills

  • Product Design Workflow Bundle

    XiaomiMiMo/MiMo-Code

    Entry point to a bundle of product design workflows covering context, research, audits, ideation, URL or image to code, design QA and sharing a prototype.

    14k GitHub stars~721 tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed

  • Prototype

    plugin87/ux-ui-agent-skills

    Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts.

    1.5k GitHub stars~614 tokensUpdated today
    Frontend & DesignAuto-check passed

  • Product Designer

    borghei/Claude-Skills

    Product design across UI/UX, design systems, prototyping, and user research.

    881 GitHub stars~3.1k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • Prototype to Figma

    alima-max/prototype-to-figma-skill

    Converts a working code prototype into a structured Figma file with one frame per interaction state, mapped to your design system and annotated with transitions.

    140 GitHub stars~7.8k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check passed

  • LobeHub UX Checklists

    lobehub/lobehub

    Applies LobeHub's four design values and per-module interaction checklists when building or reviewing user-facing flows, covering behavior over time rather than visual style.

    83k GitHub stars~2.6k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Design Critique

    mohitagw15856/pm-claude-skills

    Give structured, constructive feedback on any design using UX frameworks.

    1.4k GitHub stars~1.5k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from imbue-ai/bouncer

  • Implementation Plan Writer

    imbue-ai/bouncer

    Turns a feature's goals, requirements and architecture documents into a set of self-contained task files that a developer with no project context can follow.

    400 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Requirements From HTML Mocks

    imbue-ai/bouncer

    Turns an HTML mock iteration session into a requirements document that describes only user-facing behavior.

    400 GitHub stars~410 tokensUpdated yesterday
    Auto-check passed

  • Execute Implementation Plan

    imbue-ai/bouncer

    Works through the task files of a feature's implementation plan one at a time, with a TODO list and a verification step and commit for each task.

    400 GitHub stars~425 tokensUpdated yesterday
    Auto-check: warnings

  • Architecture Document Writer

    imbue-ai/bouncer

    Writes an architecture document for a feature from its goals and requirements, after asking questions and studying the existing codebase.

    400 GitHub stars~335 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about HTML Feature Mocks

What does HTML Feature Mocks do?

Explores a feature idea through HTML mocks that match the project's existing UI, keeping every earlier version and logging each requested tweak in a context file. The agent first reads your description, flags inconsistencies or gaps and asks clarifying questions, then proposes a short hyphenated feature name of two or three words and confirms it with you.md file with the original description, if one does not already exist.

When should I use HTML Feature Mocks?

HTML Feature Mocks fits situations like: sketching a new feature as HTML before building it; showing several states of a UI change in one file; keeping a log of design feedback to turn into requirements later.

How do I install HTML Feature Mocks in Claude Code?

Run `npx skills add imbue-ai/bouncer --skill create-html-mock -a claude-code`. Or copy the skill folder (.claude/skills/create-html-mock in imbue-ai/bouncer) into .claude/skills/create-html-mock in your project. Claude Code loads it when a task matches its description.

How do I install HTML Feature Mocks in Codex?

Run `npx skills add imbue-ai/bouncer --skill create-html-mock -a codex`. Or copy the skill folder (.claude/skills/create-html-mock in imbue-ai/bouncer) into .agents/skills/create-html-mock in your project. Codex loads it when a task matches its description.

Can I use HTML Feature Mocks in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add imbue-ai/bouncer --skill create-html-mock -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-html-mock, .gemini/skills/create-html-mock, .github/skills/create-html-mock and .opencode/skills/create-html-mock in your project.

What does HTML Feature Mocks need to run?

SKILL.md names no scripts, command-line tools or credentials: HTML Feature Mocks is instructions for the agent only. Our summary lists: A project with UI code for the mocks to imitate; A browser to open the HTML files.

Does HTML Feature Mocks access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is HTML Feature Mocks safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does HTML Feature Mocks use?

HTML Feature Mocks is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does HTML Feature Mocks use?

About 677 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to HTML Feature Mocks?

Skills that share tags, products or a category with HTML Feature Mocks: Product Design Workflow Bundle (XiaomiMiMo/MiMo-Code, 14k stars), Prototype (plugin87/ux-ui-agent-skills, 1.5k stars), Product Designer (borghei/Claude-Skills, 881 stars) and Prototype to Figma (alima-max/prototype-to-figma-skill, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains HTML Feature Mocks?

imbue-ai (a GitHub organization) maintains it in imbue-ai/bouncer, which has 400 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

Source: imbue-ai/bouncer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.