grill-design
Skill170 starsChanged 3 months agoMITView on GitHub
Converge on a frontend look through rounds of prototypes and grilling verdicts. Use when the user wants to iterate on UI/visual taste against concrete variants, or a wayfinder prototype ticket names this skill.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- craigcossairt/trellistheir own version, first seen Nov 6, 2026
- phatysddev/skillstheir own version, first seen Oct 9, 2026
- qduc/claude-skillstheir own version, first seen Jul 26, 2026
- Xuan0629/shared-skillstheir own version, first seen Jul 5, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- phatysddev/skills★ 8same name
- craigcossairt/trellis★ 5same name
- Xuan0629/shared-skills★ 2same name
- qduc/claude-skills★ 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-toolsSkill
- cmuxSkill
- code-storySkill
- development-workflowSkill
- grilling-frontend-prototypingSkill
- find-standardsSkill
- flashlightSkill
- sandcastleSkill
- test-a-skillSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
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
- Very specific: line 6
Run a /grilling session, using the /prototype skill — each question is asked with prototypes, not words:
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
Run a /grilling session, using the /prototype skill — each question is asked with prototypes, not words:
- Each round, build 5 radically different prototypes of the current design question into one live mocked app: one standalone HTML file (Artifact tool), updated in place each round.
- A floating bottom-right draggable picker names each design; ←/→ arrows switch between them, restyling the mocked app live. When the design has meaningful states (an inbox: full vs empty), add picker buttons that toggle the mock between them.
- The grilling walks down the visual design tree, each verdict zooming in one level: the overall design, then component groups, then individual components — until the user has designed the entire feature in detail.
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.