unknowns-mock-before-wire
Skill2 starsChanged 4 months agoMITView on GitHub
Build a throwaway mock or prototype before wiring production code. Use when UI layout, interaction, scope, placement, or flow is ambiguous and the user wants to react to fake data, a clickable HTML artifact, or a prototype before implementation.
In this repository11 other files it gives its agents.
- know-your-unknownsSkill
- unknowns-blindspot-passSkill
- unknowns-buy-in-docSkill
- unknowns-design-directionsSkill
- unknowns-domain-bootstrapSkill
- unknowns-implementation-notesSkill
- unknowns-intervention-brainstormSkill
- unknowns-merge-quizSkill
- unknowns-reference-mapSkill
- unknowns-spec-interviewSkill
- unknowns-tweakable-planSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 19
Stop condition: the user has answered the layout/scope questions or approved the direction.
- Distinctive: line 23
Keep prototypes disposable.
- Distinctive: line 25
Use one self-contained HTML file when clickable review is valuable.
≈ “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.
Files
Unknowns Mock Before Wire
Workflow
Probe the interaction without touching production code.
Return:
- The decision the mock is meant to test.
- A fake-data artifact or precise prototype description.
- The intentionally fake parts and non-goals.
- Open questions the mock should answer.
- A reply template that captures placement, scope, and interaction decisions.
- Stop condition: the user has answered the layout/scope questions or approved the direction.
Rules
Keep prototypes disposable. Avoid adding dependencies or integrating with real app state unless the user explicitly asks. The artifact should reduce uncertainty before implementation, not become implementation.
Use one self-contained HTML file when clickable review is valuable.
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.