Building apps with your Agent

On this page

When you ask your Agent for a dashboard, a report, a form, a planner or an internal tool, it builds the app with the PH App Kit. You don't need to ask for it. The app gets the Performance Hub look, follows your light or dark choice, and works with Performance Hub's keyboard shortcuts from the first version.

The kit is what makes apps from different Agents, and from different people, look like one product. A clinic's booking dashboard, a school's excursion tracker and a warehouse's delivery board all share the same fonts, colours, tables, forms and charts.

What the Agent builds with the kit

The kit is for software people work in:

  • Dashboards and reports
  • Lists, records and detail pages
  • Forms and settings screens
  • Planners, calendars and boards
  • Admin screens and internal tools

It isn't used for public websites or design-led pages, such as a landing page, a menu, an event invitation or a portfolio. For those your Agent designs the look freely. If a request could be either, your Agent asks whether people will mostly use the page or look at it.

How the Agent starts

Your Agent starts from a ready-made starter instead of a blank page. It picks one to suit the job:

StarterGood for
StaticDashboards and reports over files or data the Agent generates. The fastest to build and open.
ServerApps that need logic, a database, scheduled data or form submissions.
ReactRich apps with many views, forms and live state.

Each starter comes with the kit already wired in and a sample page with loading, empty and error states, so a new app never opens to a blank screen. If you ask for a calendar, a rich text editor, a map, a data grid or a drag-and-drop board, the Agent adds that optional module. See Calendar, Rich text editor, Maps, Data grid and Drag and drop.

To add the kit to an app you already have, ask the Agent to bring it up to the App Kit standard. It adds the kit's stylesheet and script to your pages, and the optional modules your pages need.

The two tools behind it

Your Agent uses two tools from its app skill. You never run them yourself.

ToolWhat it does
ph-app-kitCreates a new app from a starter, adds the kit to an existing app, and adds the optional modules (calendar, rich text editor, maps, data grid, drag and drop)
ph-app-checkChecks a running app, as described below

How the Agent checks its work

Before your Agent hands an app over, it checks it, and it checks again after every change to the screens. The check opens the running app in a browser, in light and dark mode, at desktop and phone width, and saves a screenshot of each. You don't see the report unless something can't be fixed. If it can't, your Agent tells you in plain words what you would notice.

The check looks atWhat it catches
The page itselfMissing title, language or phone-friendly settings, and files that don't load
The kitThe App Kit stylesheet isn't linked
AddressesLinks that only work from the top of a site, or scripts, styles and fonts from third-party sites
ErrorsErrors in the browser, and requests that fail
Light and darkA screen that looks the same in both, because colours are fixed instead of taken from the kit
Performance HubThe app doesn't follow a theme change straight away, doesn't pass on Performance Hub shortcuts, or never tells Performance Hub it has loaded
LayoutSideways scrolling on a phone or a wide desktop screen
SpeedA slow first screen, or too much JavaScript on first load
AccessibilityProblems that make the app hard to use, such as low contrast or inputs without labels
WordingEmoji in the interface

The Agent fixes every failure. It also fixes warnings when that is quick.

Asking for an app

Describe who uses the app and what they need to do. You don't need to mention the kit or how it should look. For example:

  • "A page for our physiotherapy clinic that shows today's appointments by practitioner, with a way to mark someone as arrived."
  • "A delivery board for the warehouse that shows each loading dock, what's waiting and which trucks are late."
  • "A school excursion tracker with a calendar, a permission slip checklist and a list of students who haven't replied."
  • "A café roster with a week view, drag and drop to move shifts, and a printout for the kitchen."
  • "A stock list for the retail store with search, inline editing and CSV export."

Review the first version in the side menu or the Published Apps tab, then ask for changes in plain words: "Move the filters above the table", "Show last month's total next to this week's". See Published Apps for where your apps appear and who can open them.

What stays the same for every app

  • Light and dark. The app follows your choice in Performance Hub. It has no theme switch of its own inside Performance Hub.
  • Shortcuts. Search, the Agent, help and the light and dark switch work while you're in the app.
  • Wording. Sentence case, Australian spelling, buttons that say what they do and error messages that say what to do next.
  • Phone and desktop. Screens fill a wide window and collapse neatly on a phone.
  • No blank screens. Every view shows a loading state, an empty state with a next step, or an error with a Try again button.