Overview
A focused VS Code extension for turning a described layout into a file tree, previewing it, and materialising folders and stub files into the workspace. It has picked up 29k+ marketplace downloads and strong reviews. The goal is a boring, predictable utility: strict validation, no silent overwrites, and a workflow that matches how people already structure repos.
/ Scope
- VS Code extension API
- Tree schema & parsing
- Preview webview + filesystem writer
- Marketplace release & updates
Highlights
01
Preview-first file tree generation
02
Safe, conflict-aware writes to the workspace
03
29k+ downloads on the marketplace
/ Tracks
- Product
- Open source
The Problem
New projects repeat the same folder patterns — components, hooks, tests — and it is easy to miss a convention or clobber an existing file. I wanted a small tool that helps you design the tree first, then apply it carefully.
Approach
The extension works from a strict, parseable tree format: describe the shape you want, see it in a preview, and only then write to disk. Parsing rejects malformed trees instead of guessing, and the file writer is conflict-aware so existing work is not overwritten by accident.
Key Decisions
- 01
Strict tree schema
Output must match a known structure. If validation fails, the user gets a clear error — no half-written directories.
- 02
Preview before write
A webview shows the tree before any filesystem change. Reduces 'oops' moments in real repos.
- 03
Small command surface
Shipped with a minimal set of commands and settings so the extension stays easy to support and to explain in the listing.
Challenges & How I Solved Them
Robust parsing
/ Problem
Early builds had to tolerate noisy input (fences, indentation drift) while still ending in a single validated tree.
/ Solution
Strip and normalise, then run a strict structure check. Bad input fails loudly.
Preserving existing work
/ Problem
Re-running the flow could touch files users had already edited.
/ Solution
Default to skipping existing files; opt-in renames with an explicit suffix when the user wants it.
Outcomes
- 29,000+ downloads on the VS Code Marketplace
- 5.0 rating across active reviews
- Steady adoption with a narrow, predictable UX
What I Learned
- 01
Utilities that respect the repo on disk outrank flashy demos in the long run
- 02
Strict validation is a feature when anything can write to the workspace
- 03
Marketplace success tracks clarity in the listing (title, screenshots, what it does in one line)
Tech Stack
Next Steps
- Reusable project-shape presets (save and recall)
- Smarter defaults per stack (e.g. Next.js vs. Nest layout hints)