Skip to content

Prompt examples

These prompts work with any coding agent that has the Adapt agent skills. Change the names and details to fit your application.

Create an Adapt app in ticket_form/. It has one vertex that shows a support form
while it runs. When a visitor submits the form, the vertex creates a ticket with
the Helpdesk API, sends "created" with the ticket ID, and completes.
Create an Adapt app in ticket_form/ from ticket_form/brief.md.
Propose a structure for an Adapt app that sends invoices from our billing system.
Don't create any files yet.

The agent always proposes a structure and waits for your approval before it creates files. The last prompt stops there, so you can compare designs.

Add a vertex "ticket_status" to ticket_form/. It receives a ticket ID and sends
the ticket's status. It has no page.
Give the "greeting" vertex in hello_world/ a settings page where users set the
page heading. The vertex can run only when the heading is set.
The ticket_form vertex must call https://api.helpdesk.example. Each user has their
own API key, sent as "Authorization: Bearer <key>".

The agent adds a service. Users enter their key in Adapt, and your code never sees it.

Let users connect their Google Calendar with OAuth2. We own the OAuth client.
Use the smallest scopes that can read free/busy times and create events.
The payment provider calls a webhook when a payment changes. Verify each call with
the provider's signature, and send "paid" from the session that created the payment.
Make the booking page stylable in the vertex settings: colors for the light and the
dark theme, the corner radius, and the font.
Start the development server, and send me screenshots of both pages in the light
and the dark theme, at phone and desktop widths.
Test ticket_form/ in the emulator. Run the vertex with test signals, check the
outputs, check that the API rejects missing and invalid tokens, and measure the
resource use.
Test the payment webhook end to end through an ngrok tunnel to the emulator.
Audit every endpoint of ticket_form/, and write the results to DEVELOPMENT.md.
Prepare release 1.1.0 of ticket_form/. Set the organization to <your organization ID>,
run the tests and the build, and publish.
I want to rename the "api_key" service in ticket_form/ to "helpdesk". Before you
change anything, tell me what happens to the settings of users who update.

For the last prompt, the agent compares the old and new definitions, and lists which settings carry over, which reset, and what users must do. See Update a published application.