Skip to content

Build with an AI agent

Coding agents, such as Claude Code and Codex, can build complete Adapt applications. The agent skills that Adaptkit installs teach them the platform’s rules: how to structure an application, keep credentials safe, protect endpoints, test, and publish. You do not have to repeat those rules in your prompts.

  1. Install Node.js 24 and Adaptkit:

    Terminal window
    npm install --global @mochabug/adaptkit@latest
  2. Install the skills at the root of your Git repository, and commit them:

    Terminal window
    adaptkit skill
  3. Optional: to let the agent test in the emulator, install Docker and mkcert, and run adaptkit emulator setup once yourself. It can ask for your administrator password.

You The agent
Describe what to build. Proposes a structure, and asks about anything unclear.
Approve the structure. Creates the project with Adaptkit, and writes the code.
Enter credentials in the service settings. Defines the services. It never needs to see your secrets.
Give OAuth2 consent in your browser. Starts the consent, and gives you the link.
Review the result. Tests, documents, and audits its work.
Sign in when you publish. Prepares the release, and runs the publish script.
  1. Describe the application. Say “Adapt app” so that the agent picks the skill, or invoke it: /adapt-app in Claude Code, $adapt-app in Codex.

    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 the ticket ID, and completes.
  2. Review the structure. Before it creates any files, the agent proposes the folder and name, the vertices, their signals, and their pages and settings. It waits for your answer. Changes are cheapest now.

  3. Follow along. The agent creates the project with adaptkit init, writes the code, and checks the pages with the development server. Ask for screenshots.

  4. Add credentials. Enter API keys and secrets in the emulator’s Services page. Never paste them into the chat or the code.

  5. Let it test. The agent runs the unit tests and the build. Then it tests the application in the emulator with the adapt-emulator skill.

  6. Review and publish. Check the result, then ask the agent to publish. You complete the sign-in.

For anything bigger than one vertex, write a brief, in the chat or in a file that you point the agent to. Answer these questions:

  • Vertices: Which steps do users place in a project? What does each one do?
  • Signals: What does each vertex receive and send? When does it finish? Which errors must the flow handle?
  • Pages: Does a vertex show a page while it runs? Which settings does it need?
  • Services: Which APIs does it call? Who owns the credentials: you, or each user?
  • Access: Is anything public?
  • Details: Size limits, languages, and styling.
ticket_form/brief.md
# Support tickets
## Ticket form vertex
- Shows a form: name, email, subject, message, and an optional attachment of up to 5 MB.
- Settings: the page heading, the ticket categories, and the colors.
- On submit: create a ticket, send `created` with the ticket ID, and complete.
- If the helpdesk rejects the ticket, send `failed` with the reason.
## Services
- Helpdesk API key at api.helpdesk.example. Each user brings their own key.
## Access
- Nothing is public except the form page itself.
  • Structure: the vertices, signals, and transmitter modes match what you agreed.
  • README.md explains the application to its users, with no developer details.
  • Developer notes, such as DEVELOPMENT.md, cover setup, design, and tests. Ask for them.
  • Endpoint audit: each endpoint, who may call it, and how it checks the caller. See Endpoint security.
  • Test record: what was tested, where, and what was not.
  • No secrets in the code, the pages, or the logs.

Put your conventions in a project instructions file, such as AGENTS.md or CLAUDE.md:

AGENTS.md
- Put each Adapt application in its own folder at the repository root.
- Make every page of a Browser vertex stylable in the vertex settings.
- Write developer notes in DEVELOPMENT.md.
- Send screenshots of each page while you build it.

Do not edit the skill files. adaptkit skill replaces them.

Ask for changes in the same way. Changes to services, the settings format, stored data, or vertex names affect people who already use your application. Before you release one, ask the agent what users must reconfigure. See Update a published application.

For more prompts, see Prompt examples.