Command palette
Every appbricx app already has a Cmd/Ctrl+K palette that jumps to pages and records. This component adds the part people act with: a visible search bar (so it works on touch screens) that opens a palette with server-side search over one or two of your tables, then actions on the record you pick: open it, move its status to the next stage, or delete it, each only when the role may. Quick create makes a new record from the palette with just its title and required fields, and you can list your own shortcuts to pages. Press / anywhere on the page to open it.
What it adds to your app
Component CommandBar (props: entity, titleField, fields, detailRoute, entity2, pages). A Quick actions page for the role you choose.
Pages
/quick-actionsQuick actions (‹page_role›)
Components
CommandBarA search bar that opens a command palette (also with /): find ‹entity› records on the server, create one in place, move its status on, open or delete it, and jump to pages; works on phones
Set it up
It merges into the contract of an app you already have. Nothing is overwritten: a name you already use is refused until you pass a prefix.
- Pick the project
Use the button above, or ask your coding agent with the Appbricx MCP server connected (quickstart).
- Point it at your tables and roles
Leave out the ones with defaults; a wrong one is refused with the options your app has.
Param What it is Example entityThe table whose records the palette finds and acts on. jobentity_2Optional: a second table to search alongside it. Optional. customerpage_roleThe role the Quick actions page is for. Optional. staff - Preview, then apply to dev
A dry run shows the diff and the check report; applying it changes your dev environment only.
- Deploy
When dev looks right, deploy. Production gets a snapshot first, so you can roll back.
Use it with your coding agent
The agent reads the template, runs a dry run, shows you the diff and applies it.
Add the Command palette template (slug "command-palette") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (entity: table to search; entity_2: second table (optional); page_role: who sees quick actions).{
"tool": "use_template",
"arguments": {
"slug": "command-palette",
"project_id": "<your project id>",
"params": {
"entity": "job",
"entity_2": "customer",
"page_role": "staff"
},
"dry_run": true
}
}appbricx templates use command-palette --param entity=job --param entity_2=customer --param page_role=staff --dry-runGoes well with
Kanbo
Team project board with drag-and-drop cards, checklists, comments and my work.
AI chat panel
A private AI assistant inside your app that answers from the records each person is allowed to see, with saved conversations.
Overdue alerts
Each morning, flags rows past their due date, tells the person assigned and sends the team a list.