Name your entities — they become your tables
3 min
Entities mentioned in your description become Prisma models. Be specific.
When you say "a CRM with contacts and deals", the planner maps Contact and Deal to Prisma models. Each model gets its own CRUD routes, admin pages, and (optionally) audit log + notification subscriptions.
Good entity-naming patterns:
- Use singular, capitalised names: Contact, Deal, Invoice, Project. - Mention relationships explicitly: "each Deal belongs to a Contact" or "a Project has many Tasks". - Mention required fields: "Contact has name, email, company".
Example: "Build a project tracker. Each Project has a name, status (active/done/archived), and owner. Each Project has many Tasks. Each Task has a title, due date, and assignee."
The planner emits Prisma schema fragments for both models, the foreign-key relationship, and CRUD pages for each. The status field becomes an enum.
Live recipes need the desktop
This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.