Build the Todo App
Use two prompts to generate the Todo module, then verify the generated UI and API.
Generate the Todo Module and Model
Mental model
You are not hand-writing the first CRUD layer in this tutorial.
You are describing the Todo app at a high level and letting SolidX generate the first working version of the module, UI, and API.
Once your agent is connected through the SolidX MCP server and solidctl start:dev is running, use these two prompts.
Prompt 1
Create a SolidX module named todo-management. Do not create models, fields, views, actions, menus, layouts, or any other metadata. Stop immediately after the module scaffold is created.Prompt 2
Inside todo-management, create a todoItem model with these fields:
- title: required short text
- description: long text
- dueDate: date
- priority: static selection with values low, medium, and high; default medium
- status: static selection with values pending, inProgress, and completed; default pendingTodo Model Overview
This is the model schema you are asking SolidX to generate with Prompt 2:
Prop
Type
That is enough to generate the first working version of the app.
Create Your First Todos in the Admin UI
- Open
http://localhost:3001. - Click the top-left menu icon at
Solid Core. - Switch to
Todo Management. - Open
Todo Item. - Start creating Todo items.
You should now see the generated Todo Item list view with standard create, edit, and delete controls available from the admin UI.
What SolidX Generated
List View
Generated with standard CRUD listing behavior for Todo items, including search and table-style browsing.
Form View
Generated so you can create and edit Todo items from the admin UI without building a custom form.
Tree View
Generated automatically as part of SolidX view scaffolding for the model.
Prop
Type
Why this is useful
This is the key payoff of SolidX: a very small prompt surface produces a usable admin module, CRUD API, and navigation wiring without manual boilerplate.
Visual File Map
Use this when exploring the repo
The tables above tell you what each generated layer does.
This file map gives you the fastest visual path to the actual generated files inside the project.
Verify the Generated API
Open Swagger at http://localhost:3000/docs.
Authenticate through POST /api/iam/authenticate.
Use:
{
"username": "sa",
"password": "Admin@3214$"
}Then:
- Copy the bearer token from the
accessTokenfield in the response. - Click
Authorize. - Paste the token.
- Call
GET /api/todo-item.
SolidX exposes generated REST routes in kebab-case, so the todoItem model appears under /api/todo-item.
Expected result
After authorizing in Swagger, GET /api/todo-item should return the Todo Item collection you generated.
If generation did not produce files
If the prompts return partial output or no module appears:
- verify
solidctl start:devis still running - verify the MCP client still has the installed SolidX server entry
- check the backend and MCP server logs for errors
- retry the module prompt, then the model prompt
Some Useful Generated Routes
Prop
Type
Prop
Type
Prop
Type
Summary
At this point, you have a generated Todo module, a working admin UI, usable CRUD API routes, and a clear file structure you can extend from here.
Continue to Next Steps for a few concrete ways to extend the generated app.