Understand your app without reading code.
Faundr maps your project: the screens, the logic, the data, and what uses what. Ask in plain language, like “what breaks if I change shipping?”, and get an answer with the exact file and line for every spot.
Editing your app blind. When one change touches more than you think.
Change one thing, break another.
You ask for a small shipping tweak. Quietly, the cart and orders stop adding up.
With the map
- See what depends on a part before you change it
- Ripple effects, two levels deep
- Exact file and line for every hit
No idea where anything lives.
Your app grew fast with AI, and now you can’t say which file handles login or what each folder is for.
With the map
- Your app, grouped into named areas
- Screens, logic, and data side by side
- How two parts connect, in one sentence
Your AI rereads everything.
Every session, it opens file after file to get its bearings. That burns tokens, and sometimes it edits the wrong spot.
With the map
- The map loads at the start of every session
- The right snippets and who uses them
- Updates itself on every edit
Ask about your app in plain language. Answers point to the exact file and line.
Type /faundr:map followed by your question, the way you’d say it out loud. You get an answer in everyday terms that shows where everything lives, so you can double-check it or ask for a change in the right spot.
you › /faundr:map what breaks if I change how shipping is calculated?
● Shipping is calculated in one place and used in two: the Cart shows the price to the customer, and the Orders server saves it at checkout. If you change the rule, check both. The confirmation email reads the saved amount, so it’s unaffected.
- src/lib/shipping.ts:12
- src/routes/cart.tsx:48
- src/server/orders.ts:31
The AI checks everything that depends on it, up to two levels deep.
Your app, mapped the way it actually works. No code required.
Faundr reads your project and groups code that works together into areas: screens on one side, logic in the middle, data on the other. Click an area to see what’s inside and what it connects to, in one sentence.
Screens
UI components
Entry points (APIs and plugins)
Logic
Data
Docs and technical files stay hidden until you need them.
Area
Shop
3 screens · 2 components
What’s inside
- index.tsx
- product.tsx
- cart.tsx
- Cart.tsx
- ProductCard.tsx
Connects to
Shop calls 2 Shipping functions (calculateShipping and freeShipping).
Generated from the map with no AI and no cost. For more detail, Explain copies a prompt your AI can dig into.
Your plan, next to what’s actually built. Code that doesn’t fit gets flagged too.
Ask your agent to "draw the project architecture" and it maps out the parts and how they connect. Every session, Faundr checks the code to see what’s built, what’s still planned, and which new folders don’t fit anywhere.
Coupon
Planned · A coupon field in the cart. Planned, no code yet.
Off plan (5)
Code folders that don’t belong to any part of the diagram. Your agent flags them in the terminal and suggests where they belong. Off plan on purpose, like one-off scripts? Mark it, and it stops being flagged.
- src/lib/promo3 files
- src/routes/admin2 files
Auto-place new folders
Off: the agent suggests a part and waits for your approval.
A map that never goes stale. Zero upkeep.
Built once, then kept current with every edit. Your AI uses it to find its way around, and you use it to understand your app.
Once
Build the map
Run /faundr:map. It scans your project and sends the map to your dashboard.
On every edit
Stays in sync
Change a file and the map follows. Your status line shows "graph up to date".
Before changes
The AI checks first
It looks up what depends on a part in a single step.
Every session
Architecture check
What’s built, what’s planned, and what’s fallen outside the diagram.
Supported languages
The map reads the code of each language on its own, with nothing to install. HTML, CSS and Docker files don’t have functions to connect, so they stay off the map.
- JavaScript & TypeScript
- React Native
- Vue
- Angular
- Svelte & Astro
- Python
- Flutter & Dart
- PHP
- Go
- Java
- Kotlin
- C#
- Rust
- C
- C++
Your AI knows how to code. With the map, you both know where things are.
On its own, your agent rediscovers your project every session, and you rely on it to know what exists. With the map, you’re both looking at the same picture.
FAQ
Do I need to code to use the map?
No. Areas have names, connections read as sentences, and you ask questions in plain language. You only see code if you open the Code tab.
Does it use tokens?
Building and updating the map runs locally with no AI, and the sentences that explain how two parts connect are free too. Only questions (/faundr:map followed by your question) and the architecture diagram use tokens from your own AI plan.
Does the map go stale?
No. It updates every time a file changes, and your terminal status line shows "graph up to date" or "graph updating".
What if the map gets a connection wrong?
The map keeps what it read directly in the code separate from what it inferred, say, from a name. Inferred links are marked as likely, and the AI checks the file before explaining them.
Can I leave folders out?
Yes. List them in a .faundrignore file at the project root, in the same format as .gitignore. Third-party code and generated files stay out of the map and the checks.
Does it work on projects that predate Faundr?
Yes. Run /faundr:map in your project folder, then /faundr:inventory lists what the app already does, based on the map.