Every SvelteKit project I have worked on hits the same wall around the twentieth route. The app runs fine, but nobody can answer a simple question anymore: where does this file go? Business logic slips into +page.server.ts, a utils.ts grows to 600 lines, and one day you find a database client imported straight into a component.
There is a lot of advice out there about folder structure, but most of it is either a beginner tutorial or a single opinionated layout presented as the only right answer. Real projects are messier than that. A structure that is perfect for a three route side project is wrong for a forty engineer platform, and the reverse is also true.
So I built a Claude skill that treats project structure the way a senior architect would: it asks about your scale and team, explains tradeoffs instead of handing down rules, and never pretends there is one correct layout.
What it does
The skill works in two modes.
