lofi-prototype
Skill1 starsChanged 8 months agoNo licenceView on GitHub
Build grayscale lo-fi interactive prototypes as single-file HTML apps. Use this skill whenever someone asks to prototype a flow, screen, interaction, or user journey — whether from a Figma file, sketch, Notion doc, Linear task, PRD, descriptive prompt, or any other input. Also trigger when someone says "prototype", "lo-fi", "low fidelity", "mockup", "interactive mock", "clickable prototype", "flow prototype", "screen prototype", or describes wanting to see how a multi-screen experience would feel on a phone. Even if they don't say "lo-fi" explicitly, if the request is about prototyping a mobile app flow, use this skill. Also trigger when someone says "sync this prototype to figma", "push to figma", "capture to figma", or "set up figma sync" on an existing prototype — the skill includes an opt-in Figma two-way sync workflow for longer-lived prototypes. The output is always a single self-contained HTML file with vanilla JS that feels like navigating a real app.
In this repository3 other files it gives its agents.
- figma-syncSkill
- hifi-prototypeSkill
- prototype-agentSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
31 rules. About 0 are common, 17 are distinctive, and 14 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.