unknowns-design-directions
Skill2 starsChanged 4 months agoMITView on GitHub
Generate multiple incompatible product/UI/design directions so the user can discover taste by reaction. Use when the user says they have no visual taste, will know it when they see it, wants 3-4 directions, wants alternatives before committing, or needs an interactive review artifact for design choices.
In this repository11 other files it gives its agents.
- know-your-unknownsSkill
- unknowns-blindspot-passSkill
- unknowns-buy-in-docSkill
- unknowns-domain-bootstrapSkill
- unknowns-implementation-notesSkill
- unknowns-intervention-brainstormSkill
- unknowns-merge-quizSkill
- unknowns-mock-before-wireSkill
- 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 10
Create divergent options from the same content and constraints.
- Distinctive: line 18
Stop condition: the user has selected a direction or produced a combined direction brief.
- Distinctive: line 24
Use HTML when side-by-side visual review or selectable chips materially improves the decision.
≈ “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 Design Directions
Workflow
Create divergent options from the same content and constraints.
Return:
- 3-4 genuinely different directions, not minor theme variations.
- For each: intent, strengths, tradeoffs, what to steal, what to skip.
- A reaction capture loop: choose direction, steal details, reject details.
- A generated reply or next prompt that encodes the user's choices.
- Stop condition: the user has selected a direction or produced a combined direction brief.
Rules
Make options distinct in information density, layout logic, interaction model, and visual tone. Do not let all directions share the same skeleton.
Use HTML when side-by-side visual review or selectable chips materially improves the decision.
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.