Writing Prompts for AI Smartoo Assistant

Smartoo Assistant is your AI-powered development partner. It can generate a fully functional app from a simple description, but it works best when you give it clear instructions.

Think of Smartoo Assistant like a talented new employee. It has all the technical skills to build anything, but it doesn't know your business yet. It relies on you to explain how your team works, who needs access to what, and what "success" looks like.

This guide will teach you how to write prompts that get you 90% of the way there in the very first draft.

The 5 ingredients of a perfect prompt

You don't need to speak code to get a great result. You just need to describe your business process clearly. To build a robust app from the start, try to include these five elements in your prompt:

1. Users & Roles

Who is this app for?

Define who will log in and what they are allowed to do.

Example: "I need an app for Project Managers (who can see everything) and Freelancers (who can only see their own tasks)."

2. The "Things" You Track (Objects)

What are the main nouns in your workflow?

These become the data tables in your app.

Example: "We need to track Projects, Tasks, Invoices, and Clients."

3. Key Details (Fields)

What information do you need for each item?

List the specific data points that matter to you.

Example: "For every Task, I need to know the Priority, Due Date, Status, and Attached Files."

4. Relationships

How do the items connect to each other?

Help the AI understand the structure of your data.

Example: "A Client can have many Projects, and each Project contains many Tasks."

5. Workflow & Logic

What happens when data changes?

Describe the automation or rules you need.

Example: "When a task is marked 'Done', email the manager. Only Admins can delete invoices."

Prompt template

Struggling to start? Copy this template, fill in the brackets, and paste it into Smartoo Assistant:

"Build a [App Type, e.g., CRM] for [Target Audience].

Data to track:

• [Object 1]: include fields for [list key fields]
• [Object 2]: include fields for [list key fields]

How they connect: [Describe relationships, e.g., A Project has many Tasks]

Workflow Rules:

• [Rule 1, e.g., When X happens, do Y]
• [Rule 2, e.g., Only Managers can approve Z]

Permissions:

• [Role A] can view/edit everything.
• [Role B] can only view their own records."

Real-world examples

Here is how to apply the formula above to common business scenarios.

Scenario A: Internal Project Management

The Prompt:

"Build a project tracking app for a marketing agency. We need to track Projects and Tasks.

• Projects have a name, client, budget, and deadline.
• Tasks belong to a project and have a status, assignee, and priority.
• Rules: When a task is marked 'Urgent', send an alert to the Project Owner.
• Permissions: Admins see all projects; Team Members only see tasks assigned to them."

Why this works: It clearly defines the hierarchy (Tasks belong to Projects) and sets strict security rules immediately.

Scenario B: Client Portal

The Prompt:

"Create a secure client portal for a consulting firm. Track Clients, Deliverables, and Invoices.

• Workflow: When I upload a Deliverable, the Client should be notified via email.
• Permissions: It is critical that Clients can only see their own data. They should not see other clients' names or invoices."

Why this works: It explicitly addresses privacy concerns ("only see their own data"), ensuring the AI sets up the correct database permissions from the start.

Scenario C: Approval System

The Prompt:

"Build an expense approval app. Employees submit Requests with an amount, category, and photo of the receipt.

• Workflow: If the amount is under $50, auto-approve it. If it is over $50, change status to 'Pending Approval' and notify the Manager.
• Statuses: Use specific statuses: Draft -> Submitted -> Approved -> Rejected."

Why this works: It gives the AI precise logic to build automation, rather than just asking for a generic "approval process."

Pro-tips for better results

• Define Your "Done": Don't just say "make it modern." Instead, say "I need a Dashboard view for managers and a simple List view for mobile users."
• Be Specific with Statuses: Generic apps use "Open/Closed." Custom apps use your real language, like "New Lead > Contacted > Negotiation > Closed Won." Tell the AI your specific terminology.
• Start Simple: You can always refine the app later. It is often better to prompt for the core features first ("Just the project tracker") and add complexity ("Now add a chat feature") in a second prompt.