Prompts
Add Feature
Prompts for creating new entities and features
TL;DR: Describe your feature, AI creates everything - database, API, UI.
Basic Feature
Simple Entity
Add [name] feature with fields: [field1], [field2], [field3]Example:
Add tasks feature with fields: title (required), description,
due_date, status (todo/in_progress/done)AI will create:
- Database table
- Validation schemas
- API endpoints (list, get, create, update, delete)
- List page with DataTable
- Navigation entry
Feature with Relations
One-to-Many (Child Entity)
Add [child] feature. Each [parent] has many [children].
Fields: [field1], [field2], [field3]Example:
Add invoice_items feature. Each invoice has many items.
Fields: description (required), quantity (number), unit_price (decimal)Reference to Another Entity
Add [name] feature with fields: [fields].
Add relation to [other_entity] (many [name] per [other_entity]).Example:
Add tasks feature with fields: title, description, due_date, status.
Add relation to clients (many tasks per client).
Show client name in task list.Feature Like Existing One
Copy Pattern
Add [name] feature, similar to [existing_feature].
Fields: [field1], [field2], [field3]Example:
Add products feature, similar to clients.
Fields: name, sku, price (decimal), stock_quantity (number),
category (use dictionary), active (boolean)Feature with Specific UI
With Filters
Add [name] feature with fields: [fields].
List page should have filters for [field1] and [field2].Example:
Add orders feature with fields: order_number, customer_name,
total (decimal), status (pending/processing/shipped/delivered), created_at.
List page should have filters for status and date range.With Card View
Add [name] feature with fields: [fields].
Support both table and card view on list page.
Card should show [key_fields].With Detail Page
Add [name] feature with fields: [fields].
Detail page should show all fields in sections:
- Basic Info: [fields]
- Details: [fields]
Related [children] as embedded list.Example:
Add projects feature with fields: name, description, status,
start_date, end_date, budget (decimal).
Detail page should show:
- Overview section: name, status, dates
- Budget section: budget, spent, remaining
Related tasks as embedded list at bottom.Complete Examples
CRM-style Feature
Add leads feature for tracking sales leads.
Fields:
- company_name (required)
- contact_name
- email
- phone
- source (website/referral/cold_call/event) - use dictionary
- status (new/contacted/qualified/proposal/won/lost)
- estimated_value (decimal)
- notes (textarea)
List page:
- Filters for status and source
- Sort by estimated_value
- Show status as colored badge
Detail page:
- Header with company name and status badge
- Contact section with email/phone
- Activity timeline (related activities)Inventory Feature
Add inventory feature for tracking stock.
Fields:
- sku (required, unique)
- name (required)
- description
- category - use dictionary
- quantity (number)
- min_quantity (number) - for low stock alert
- unit_price (decimal)
- location
List page:
- Search by sku and name
- Filter by category
- Highlight rows where quantity < min_quantity
- Export to CSV
Detail page:
- Stock info with quantity badge (red if low)
- Pricing section
- Stock history as related listWhat NOT to Specify
AI already handles these - no need to mention:
- File locations and structure
- Database migrations
- API route setup
- TypeScript types
- Organization scoping (organizationId)
- Basic CRUD operations
- Navigation menu entry