agentleFS
nanoodlecomnanoodlecom/noodle-skills/skills/ui-mockup/SKILL.md

ui-mockup

Skill2 starsChanged 21 days agoMITView on GitHub

Render a UI mockup image from a one-line feature description — an LLM turns the description plus a style guide into a precise screenshot-style image prompt, then an image model renders it. Use to show the user what a screen could look like before writing any frontend code, or to settle "option A or option B" layout questions by rendering both.

  • Reads credentials

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never print the key.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

UI mockup

Runs the bundled nanoodle workflow workflows/ui-mockup.noodle-graph.json against the NanoGPT API: the feature description (Feature) and a product style guide (Style guide) are joined into a brief, an LLM turns the brief into one disciplined image prompt for a screenshot-style mockup (explicit layout regions, exact palette, short realistic labels, no lorem-ipsum walls), and an image model renders it (Mockup). Requires Node.js 22.23.4+, 24.22.1+, or 26.12.1+ and the nanoodle npm package (npx nanoodle fetches it).

Typical agent use: about to build or propose a screen, render the napkin sketch first, drop the file path in the conversation, and ask "like this?" before writing JSX.

API key

The run needs a NanoGPT API key. Use whichever is available:

  • NANOGPT_API_KEY already set in the environment — prefer this; no extra flags.
  • A .env file containing NANOGPT_API_KEY=... — pass --env-file <path> only when the key is not already in the environment. (With this CLI, --env-file overrides ambient NANOGPT_API_KEY.)

Never print the key.

Run

From this skill's directory (or prefix paths if running from elsewhere). Replace the Feature value with the screen being mocked:

npx nanoodle run workflows/ui-mockup.noodle-graph.json \
  --input "Feature=settings page: profile card, notification toggles grouped by channel, danger zone at the bottom" \
  --out ./mockup-out

Match the target product by overriding the style guide (a baked-in clean-SaaS default runs otherwise):

--input "Style guide=dark mode, near-black background, emerald primary, dense data tables"

Inspect the interface anytime with:

npx nanoodle inspect workflows/ui-mockup.noodle-graph.json

Inputs

KeyRequiredWhat to pass
FeatureyesThe screen to mock, one sentence of plain language
Style guideno (default baked in)The product's look: palette, spacing, light/dark, component vibe
System promptnoOverride the prompt-writer's instructions

Outputs

  • Media is saved under --out as Mockup.<ext> following the image MIME. Use the path the CLI prints on the Mockup: line — do not hard-code .png.
  • The stdout JSON summary carries the path in outputs.Mockup (and cost/balance).

Serve as an MCP tool

The same graph file works unchanged as a typed MCP tool — the agent gets a render-mockup tool it can call many times a day:

mkdir -p ~/noodles && cp workflows/ui-mockup.noodle-graph.json ~/noodles/render-mockup.json
claude mcp add nanoodle -- npx nanoodle-mcp --graphs ~/noodles --out ~/noodle-out

Cost

Each run costs about $0.04 in NanoGPT credit (the image step, nano-banana-2-lite, dominates; the prompt-writing LLM is a fraction of a cent). This is a napkin sketch, not marketing art — one fast, cheap render per question. Runs spend real credit — tell the user before running repeatedly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.