See how ChatGPT and Claude describe your product. Find the gaps, then fix them.
AI tools read your code but not the decisions behind it. They fill gaps with competitor patterns and wrong positioning. gist.design is a structured file that captures design decisions, positioning, and boundaries so AI tools get it right.
| Without gist.design | What prevents it |
|---|---|
| AI coding tool builds auto-execute when you designed for user approval | Design Decisions: "chose X over Y because Z" |
| AI fills gaps with competitor patterns your product deliberately avoids | Not This: explicit boundaries on what this is not |
| LLM recommends your product to the wrong audience | Positioning: who it's for and who it's not for |
| LLM describes your product as a clone of a competitor | Positioning: vs comparisons with honest differences |
Two ways to create the same file.
Three steps. One file that fixes how AI understands your product.
62%
45%
58%
Gaps found
See how ChatGPT, Claude, and Perplexity describe your product from your website alone. Find where they guess wrong, miss features, or confuse you with a competitor.
@Docs → Add new doc → paste your gist.design URL
Install the gist-design skill to generate files natively, or drop one in your repo root.
Place file in repo root
Paste URL or upload file for accurate product recommendations
Figma MCP gives structure. gist.design gives intent. Together they produce accurate implementation.
They're complementary. Use both.
llms.txtA README for LLMs. Features, links, how to use it.
“Acme is a project management tool with kanban boards.”
gist.designPositioning, boundaries, and design rationale. Stops LLMs from getting your product wrong.
“Not for enterprise. No Gantt charts by design. Chose manual scheduling because teams want control.”
What makes a gist.design file useful.
“We chose X over Y because Z” is useful. “The button is blue” is not.
3-tier badge next to each suggestion
“uses confidence visualization”
“Confidence scores appear as a 3-tier badge next to each suggestion,” not “uses confidence visualization.”
What it's NOT prevents AI from filling gaps with competitor patterns.
One file per significant feature. Keeps each file focused and useful.
The tool handles the format. You handle the thinking.
| Topic | Details |
|---|---|
| robots.txt | Crawlers — What can you access? |
| sitemap.xml | Search engines — What pages exist? |
| llms.txt | LLMs — What does this product do? |
| gist.design | LLMs — How should you talk about this product? Positioning, boundaries, audience, design rationale |
| File placement | /gist.design in the project root, or /features/[name]/gist.design for multi-feature products |
| Spec | Open for community input. Pattern research at aiuxdesign.guide |