aakashns

Author here. I've shipped multiple Next.js projects to production with LLMs writing over 90% of the code, and this post outlines a project structure that aids LLMs and doesn't trip them up.

TL;DR: Keep it flat, obvious and simple. 7 top-level folders (app, components, database, emails, functions, lib, public) instead of deep nesting. Explicit server/client separation. Everything has one obvious place to live.

Happy to answer questions about working with LLMs on larger codebases or specific patterns I've found useful.

I created this template because I couldn't find any resources to run ClojureScript on Cloudflare Pages (one of the fastest and cheapest deployment options available today).

We do have a checkout flow, and yes, that page is visited by a very small number of users. However, you don't actually think I deleted the checkout flow, do you?

Haha, thanks! Yes, as I've said in the post, the idea is the migrate the codebase to a new stack quickly, and add back some features.

Our situation is a bit unique, because we're currently a two person company. I'm familiar with the product, our users, and the codebase, which allowed me to move quickly. This probably wouldn't work at a larger organization.