Tree view makerfrom plain language, free.
/ Example
(01)Prompt: The folder structure of a React app with components, pages, hooks and tests
treeView-beta
react-app/
public/
index.html
favicon.svg
src/
components/
Button.tsx
Modal.tsx
Navbar.tsx :::highlight ## shown on every page
pages/
Home.tsx
Profile.tsx
Settings.tsx
hooks/
useAuth.ts ## sign-in state
useFetch.ts
styles/
globals.css
App.tsx ## routes and layout
main.tsx
tests/
components/
Button.test.tsx
Modal.test.tsx
hooks/
useAuth.test.ts
setup.ts
package.json
tsconfig.json
vite.config.ts :::highlight ## build settings
README.md
/ Good for
(02)- Project folder layouts in a README
- Site maps and navigation
- Org charts and category trees
(03)
drop something in
1text, notes, whatever
it turns into a diagram
2usually in a few seconds
tweak it if you want
3export it and move on
/ Other diagram types
(04)- FlowchartSign-up, checkout and approval flows
- Sequence DiagramAPI requests across services
- Class DiagramObject-oriented designs and domain models
- State DiagramOrder and ticket lifecycles
- ER DiagramDatabase schema design
- User JourneyOnboarding and first-run experiences
- Gantt ChartProject and release schedules
- Pie ChartBudget and cost breakdowns
- Git GraphExplaining a branching strategy
- Mind MapBrainstorming and planning
- TimelineProduct and company history
- Requirement DiagramTracing requirements to components
- Quadrant ChartEffort and impact prioritisation
- C4 DiagramSystem context for new team members
- Sankey DiagramBudget and money flows
- XY ChartMonthly sales or sign-ups
- Block DiagramHigh-level system overviews
- Packet DiagramProtocol and file format documentation
- Kanban BoardSprint snapshots in a README or doc
- Architecture DiagramCloud infrastructure overviews
- Radar ChartComparing products or frameworks
- TreemapBudgets broken down by department
- Ishikawa DiagramRoot cause analysis after an incident
- Venn DiagramComparing products or roles