frontend-ui-prototype SKILL.md skillB
frontend-ui-prototype from neversight/learn-skills.dev is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add neversight/learn-skills.dev/frontend-ui-prototype@git:20260901.dd9531aPins git:20260901.dd9531a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- neversight/learn-skills.dev
- Path
data/skills-md/0furkancolak/frontend-ui-prototype/frontend-ui-prototype/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260901.dd9531a, committed Sep 1, 2026
- Size
- 22,232 bytes
- Repository stars
- 223
- License
- none declared
Build a question-driven, browser-testable frontend prototype with a single index.html and locally downloaded raster assets. Use when turning a product idea, existing app, repository, screenshot, or live URL into a landing page or UI prototype before production implementation. Inspect product truth, ask concrete intake questions, research and select a suitable DESIGN.md direction, decide how real screenshots, photography, generated imagery, or illustration should be used, then create…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Frontend UI Prototype Create a fast, disposable, visually credible prototype that helps the user make a design decision before production development. The default implementation is intentionally simple: ```text prototype/<slug>/ ├── index.html ├── DESIGN.md ├── Makefile └── assets/ # only when raster visuals are used ``` All page markup, styles, interactions, inline SVG, and prototype data belong in `index.html`. Do not create `src/`, `components/`, `package.json`, framework scaffolding, build configuration, or separate CSS/JS files unless the user explicitly requests a different delivery format. ## Core contract 1. Ask concrete questions before designing when required information is missing. 2. Inspect an existing product when one is available; treat it as product truth. 3. Research current references and appropriate `DESIGN.md` systems before coding. 4. Let the user select a design direction, unless they explicitly delegate the choice. 5. Decide the visual-evidence strategy: real product UI, photography, generated imagery, illustration, or no hero image. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_yeex72bpzh7ofmgq/0d8a506715a0ae122227b5def1765759703f4200b0ac3b8cd982088843ba34f3.json
Then /plugin install frontend-ui-prototype@markdownregistry-yeex72bpzh7ofmgq in Claude Code. It installs git:20260901.dd9531a, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add neversight/learn-skills.dev/frontend-ui-prototype@sha256:0d8a506715a0ae12The line at the top of this page pins the label git:20260901.dd9531a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_yeex72bpzh7ofmgq)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in neversight/learn-skills.dev/frontend-ui-prototype since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of frontend-ui-prototype from somewhere else? Ask it: where did my frontend-ui-prototype come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Sep 1, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/frontend-ui-prototype/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (22232 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
neversight/learn-skills.dev · 223 stars · license none declared · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yeex72bpzh7ofmgq GET https://markdownregistry.com/api/v1/resolve?ref=neversight/learn-skills.dev/frontend-ui-prototype GET https://markdownregistry.com/api/v1/blob/0d8a506715a0ae122227b5def1765759703f4200b0ac3b8cd982088843ba34f3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.