agentleFS
iamneilrobertsiamneilroberts/shadetree-ai/.claude/skills/mock/SKILL.md

mock

Skill9 starsChanged 46 days agoMITView on GitHub

Build a UI design mockup for shadetree-ai as ONE self-contained HTML file (several variations behind a view-switcher, example data only) and publish it to https://mock.fuxed.org/<slug>/. Never use Artifacts for mockups in this repo. Triggers on `/mock`, "mock up", "design options for", "show me alternatives".

7 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions7 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 7

    1. vide/matedroid★ 86same name
    2. iamneilroberts/claude-skills★ 26same name
    3. Pradnyeshp/Claude-Skills★ 2same name
    4. ilamanov/skills★ 1same name
    5. junho5400/cramcode★ 1same name
    6. gustaferiksson/skills★ 0same name
    7. Holojerm/drawthesystem★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start from the real console look (src/obd_reader/web/console.html, docs/summaries/console-stages-1-3.md) when mocking the console.

    line 15
  2. Distinctive:

    Do not ship generic AI-default design.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

mock: build and host design variations (shadetree-ai)

Mockups never go to Artifacts here. They are single HTML files hosted on fuxed.org (public, no login, unlisted, noindex).

Steps

  1. Interview only what you cannot infer: what screen, how many variations, what dimension varies, light/dark. Start from the real console look (src/obd_reader/web/console.html, docs/summaries/console-stages-1-3.md) when mocking the console.
  2. Build from template.html in this folder (view-switcher with URL-hash deep links, no dependencies).
    • One file; inline all CSS and JS; no remote fonts, scripts or images (it must render from disk and offline).
    • Scope each variation's CSS under its #id. Label it a mockup. Work at 400 px width.
    • Example data only, marked SIMULATED. No VINs, transcripts, plates, names or places.
    • Do not ship generic AI-default design; make deliberate colour, type and layout choices for the subject.
  3. Publish: .claude/skills/mock/deploy-mock.sh put <slug> /tmp/mock-<slug>.html prints https://mock.fuxed.org/<slug>/. Same slug overwrites; delete <slug> removes; list shows what is up. Append #v2 to deep-link a variation.
  4. Give the user the URL as a fenced block. Port an approved design into the repo in a worktree, as a separate task.

Notes

  • Hosting is a Cloudflare Worker with static assets (shadetree-mocks) on the custom domain mock.fuxed.org; the deploy needs wrangler logged in.
  • Files are staged in ~/.local/share/shadetree-mocks/site/ (outside the repo).

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.