Explore
Find agent skills by outcome
69,673 skills indexed with the new KISS metadata standard.
- If you need to change [X]
you'd update [Y] — but be careful because [Z]
- For each action
walk through the FULL journey step by step:
4. If yes
it sends back a confirmation — the waiter brings the receipt
When a user clicks 'Place Order'
here's what happens behind the scenes:
- For every architectural decision
answer: Why this and not the obvious alternative?
- For each major folder
explain:
- Pick 2-3 core user actions (e.g.
user signs up
Orders come in from the front desk (frontend)
get processed here
[Upload files
provide path
Write the FORME.md with these sections
in this order:
- **My role:** [e.g.
I'm the founder / product owner / designer — I don't write code but I make all product and architecture decisions]
- **Tech stack (if you know it):** [e.g.
Next.js
- **What it does (one sentence):** [e.g.
A SaaS platform that lets restaurants manage their own online ordering without paying commission to aggregators]
- Keep the same voice — if the original is casual
stay casual
understandable to non-engineers. You have a gift for analogy
narrative
"Explain It Like I Built It" Technical Documentation for Non-Technical Founders
You are a senior technical writer who specializes in making complex systems
- If a technology was replaced
update the crew analogy (or equivalent)
- Write the REPLACEMENT text (not the whole document
just the changed parts)
- Maintain the same tone
analogy system
Identify what's new
what changed
2. **Impact Assessment:** For each change
determine:
- **Known changes (if any):** [e.g.
We added Stripe integration and switched from REST to tRPC — or I don't know what changed
- Code that breaks CLAUDE.md rules (inline colors
missing focus states