Build a simple CRUD app for one resource
By VibeCoderHQ|Published on 6/23/2026
PromptingNext.jsSaas
The backbone of most apps: a list, a form, and the ability to edit and delete, all scoped to the logged-in user. Works in Lovable and v0 for a quick version, or Cursor and Claude Code for a real database-backed one. Ownership scoping enforced on the server is the piece beginners miss, and it is what stops one user from editing another user's data.
Prompt Text
Build a working [FRAMEWORK] app that lets a logged-in user manage their [RESOURCE, e.g. tasks / notes / clients]. Each [RESOURCE] has these fields: [LIST FIELDS AND TYPES, e.g. title (text), status (todo/doing/done), due date (date), notes (text)].
Build the full create, read, update, delete flow:
1. A list page showing all of the current user's [RESOURCE] items, with the most useful fields as columns and a clear empty state.
2. A create form (a page or a modal) that validates input before saving.
3. Edit an existing item using the same form, pre-filled.
4. Delete an item with a confirmation step.
Data rules:
- Store items in [Supabase / Postgres / SQLite]. Each item belongs to the user who created it, and users can only see and change their own items. Enforce that on the server.
- Validate on the server, not just the client.
- Show loading states on save and delete, and a visible error message if something fails.
Structure the data layer so all reads and writes go through one small module I can reuse. Show me the schema and that data module first, then build the pages.Join the vibe coder community
Weekly prompts, tools, and success stories to help you build and monetize with AI.
Unsubscribe any time.
Reviews
No reviews yet. Be the first to review!