Build a ProductFrameworksSetup guidesClaude CodeGitHub 9 min
Explain the App You Vibe Coded
The 60-second build is the start of the conversation, not the end of it. If you can't explain your own app's request flow, database, and auth, you can't sell it, hire for it, or fix it under pressure.
the output
What you'll have when you're done
- A one-page product summary
- A component inventory
- A request-flow explanation
- A database summary
- An auth and permissions summary
- An AI-usage and cost summary
- A deployment summary
1 · the repository audit
Audit this repository and report: 1. What the product does, in one paragraph 2. Primary user 3. Frontend framework and main frontend directories 4. Backend framework and main backend directories 5. Third-party services and integrations 6. Where configuration and secrets are read from 7. Anything that looks unused or duplicated Cite the file paths that support each answer.
2 · trace the request flow
Trace exactly what happens when a user completes this action: [e.g. signs up / saves a record / purchases a subscription]. Walk through: the UI component → the client call → the route or function → any validation → the database write → what comes back → what the UI renders. Name every file involved.
3 · the database audit
Inspect the database configuration, migrations, and schema. List every table with its columns, relationships, and indexes. Explain what each table is for in plain English. Flag: missing constraints, tables with no access rules, and any column that stores sensitive data.
4 · the auth audit
Audit how authentication and authorization work here. Explain: how users create accounts, how sessions are maintained, where permissions are enforced (client, server, or database), which routes are protected, and what an unauthenticated user can reach. List anything enforced only in the UI — that's not enforcement.
5 · the AI-usage audit
Report on how this app uses AI: 1. Model provider 2. Model names and configuration 3. Where model calls occur (files and functions) 4. What data is sent to the model 5. Whether any user or customer data leaves the system 6. Retry, timeout, and failure handling 7. Roughly what a call costs and what drives that cost
6 · the deployment audit
Identify: hosting platform, build command, start command, environment variables required, where they're configured, how deploys are triggered, and what would break a deploy today.
7 · explain it to three audiences
Using only the verified audit above, explain this product to: (a) a non-technical customer, (b) an investor, (c) an engineer. For each, include: the problem, the user, how it works, what makes it defensible, and its current limitations. No jargon for (a).
Quiz yourself out loud
Where does the data live? How are permissions enforced? Which part genuinely uses AI? What external services does the product depend on? If you hesitate on any of these, re-run the matching audit.
Next guide
Build the First Version of Your App With AI