Frontend and backend
Ask PlutoAI to build the interface your users see and the logic that runs behind it
Every app has two halves. The frontend is what users see and interact with. The backend is what runs behind the scenes: storing data, handling requests, enforcing rules, and connecting to outside services. You build both the same way, by describing the outcome you want and letting the agent implement it.
Describe the outcome, not the implementation
Focus on what a screen should show, or what should happen and under what conditions. You do not need to specify how it is built.
When a user submits the signup form, create their account, send a welcome email, and start them on the free plan.
Building the interface
Describe the pages, components, and behavior you want.
Pages and navigation:
Add a settings page and link to it from the account menu in the top navigation.
Components and layout:
Create a card for each project showing its name, status, and last updated date, and arrange the cards in a responsive grid.
Forms and inputs. Describe the fields, what happens on submit, and how errors should be handled:
Add a contact form with name, email, and message fields. Validate the email, show an error under any invalid field, and show a confirmation after a successful submit.
A complete interface handles more than the ideal case. When it matters, ask for responsive behavior on mobile and desktop, loading states while data is fetched, empty states when there is no data yet, and error states when something goes wrong.
If your project already has a visual style, ask the agent to reuse it so new screens stay consistent.
Build the new reports page using the same layout, colors, and components as the existing dashboard.
Building the behavior
Describe what should happen on the server: the actions your interface calls, the data you keep, and the rules that protect it.
Server actions and APIs:
Add an endpoint that returns each project's task count so the dashboard can show it.
Data. Describe the information you need to keep and how the pieces relate:
Store projects and tasks. Each project has many tasks, and each task has a title, status, and assignee.
See Databases for how PlutoAI works with data.
Access rules. Describe who can do what:
Only the project owner can delete a project. Members can create and edit tasks but cannot delete the project.
See Authentication for sign-in and permissions.
Validation. Ask the agent to check input and handle failures so the app behaves predictably:
Reject a task with an empty title and return a clear error the form can display.
For outside services, connect them rather than assuming the agent can guess the details. See Connect your tools.
Backend changes affect data and access, so review them carefully and test the important flows before you deploy. See Testing.