Modeling your data

Good data models make every later feature cheaper. Before prompting, write down your nouns (user, booking, service) and the relationships between them (a booking belongs to one user and one service). That sentence-level model is exactly what the agent needs. Prefer boring, explicit structures: separate tables per noun, real foreign keys, timestamps on everything. Clever denormalization is a problem you are lucky to have later. When requirements change, migrate — do not mutate blindly. Ask the agent for a migration that preserves existing data, and test it against a copy before running it on production. Your future self sends thanks.