Fog show
Resolve taste the user can't verbalize by showing contrasting throwaway artifacts. Use when a FOG.md item is tagged → show, or the requirement is look, feel, or tone the user will only recognize on sight.From its SKILL.md
npx -y skills add leoncuhk/defog --skill fog-showAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 273 tokens by cl100k_base, as published. Nobody here has run it
Fog Show
Never ask the user to verbalize taste — "what does modern mean to you?" produces noise. Show, and read the reaction.
One decision per round: one axis a reaction can be attributed to, every other property held constant. Produce 3–5 variations that are wildly different, not shades — if you can't name a plausible user who would react differently to two of them, replace one. Note the belief each bets on ("this one bets density beats whitespace") in the filename or your notes — never inside the artifact, so the reaction is to the artifact, not the thesis.
Cheap and disposable: visual → one self-contained HTML file, fake data, no wiring; approaches → a one-screen sketch each (the idea, what it optimizes for, its sharpest tradeoff).
The deliverable is a sentence, not the artifact: "you consistently rejected X, so the real requirement is Y." Write it to the ledger as resolved — it is now spec — and delete the probes; the sentence is the only survivor. Reactions that reveal new unknowns become Open items with resolvers.
If nothing lands, the decision space was framed wrong: derive the new axis from the rejection reasons — when every rejection complains about the same non-axis property, that property is the real decision — and rerun.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.