intern dev
Commit Plan Prompt
Copy
Write me a COMMIT_PLAN.md where you write each commit with feat: ui: ux: chore: Make sure that each commit is iterative. Don't make a single commit adding all the dependencies or schemas. Only commit and push the schemas as you go. An example commit is like: feat: add filter functionality Bad commit is: chore: initialize express backend with typescript - Initialize package.json - Install dependencies: - express, cors, helmet, dotenv - typescript, ts-node, @types/express, @types/node - @supabase/supabase-js Why this is bad: This commit installs all dependencies upfront before they're needed. Supabase, express, cors, etc. should each be added in the commit where they're actually used. For example, add @supabase/supabase-js only when you implement the database connection, add cors when you implement CORS handling. This keeps commits focused and makes it clear why each dependency was added.