Build a form with your AI assistant

Describe the form you need and let Claude, ChatGPT, Gemini, or Copilot draft the whole thing as a file you import into Droplet.

Overview

The Droplet Form Creator is a skill: a folder of instructions your AI assistant loads so it knows how Droplet forms are built. It turns a plain-language description into a .drplt file with the fields, workflow steps, and notification emails already in place.

The skill works with Claude Code, claude.ai, ChatGPT, Gemini, GitHub Copilot, Cursor, and OpenAI Codex.

Install the skill

The Droplet Form Creator README has the complete, current steps for every tool.

Claude Code

Run these two commands. The plugin install also keeps the skill up to date.

/plugin marketplace add drplt/droplet-form-creator
/plugin install droplet-form-creator@droplet-forms

claude.ai

Download the latest skill zip. In Claude, open Customize, then Skills, then Create skill, then Upload a skill, and choose the zip.

Codex, Copilot, Gemini CLI, and Cursor

These coding tools read skills from a .agents/skills/ folder in your project. The README has the commands to copy the skill folder there.

ChatGPT and Gemini apps

On ChatGPT Business, Enterprise, and Edu plans, upload the skill zip under Plugins, then Skills, then Create. On other plans, create a Custom GPT with the skill instructions and reference files. In Gemini, create a Gem the same way.

Describe your form

Say what the form collects, who reviews it at each step, and who gets an email along the way. A short request works:

"Build a field trip request form that goes to the principal, then the transportation office, and emails the teacher when approved."

The assistant asks questions only when your request is ambiguous. Otherwise it builds the file and lists the assumptions it made.

Write a request that gets the form you want

The more of your process you describe up front, the fewer assumptions the assistant makes. Cover these points:

• Who fills it out. Say whether submitters sign in to Droplet, or whether parents and other people outside your organization use it too.

• What it collects. List the fields, which ones are required, and any that should appear only in certain cases, such as lodging details for an overnight trip.

• Who approves, in order. Name each step and how its approver is chosen: one fixed person, or someone looked up by school or department. Each step goes to one person, so when two people share a role, pick one and copy the other on an email.

• Which emails go out. Say who hears about each step, and who hears when the request is approved or denied.

• Datasets you already have. Name them, such as a school directory, so dropdowns and approver lookups use your real data.

• What you are replacing. Attach the paper form, a PDF, or a screenshot of the current process so the assistant matches your fields and wording.

A request that covers these points reads like this:

"Build a field trip request form for staff who sign in. Collect the trip date, destination, number of students, whether it is overnight, and whether a bus is needed. Send it to the principal of the teacher's school from our School Directory dataset, then to the transportation office only when a bus is needed. Email the teacher when it is approved or denied."

Import and finish

1. On the Forms page, click + Form and choose I have a .drplt file, then upload the file.

2. Replace the placeholders the assistant listed, such as dataset IDs, approver names and emails, the logo, and any webhook connection.

3. In the Workflow Editor, click Test and walk one submission through every step.

4. Publish the form.

For more on the form builder, see Create and edit a form.

Make changes after you import

Droplet cannot overwrite an existing form with a new .drplt file. Importing again creates a second, separate form. Once your form is in Droplet, bring later changes from your assistant in through the Code Builder, one piece at a time.

1. Ask your assistant for the complete updated text of each file it changed, not only the edited lines.

2. If the form is already published, click the version number and select New Draft so the live form stays untouched while you work.

3. In the form builder, click the ⋮ menu and select Code Builder.

4. Open the tab that matches the file, replace everything in it with the new text, and save.

5. Repeat for each changed file, then test the workflow again.

Each file the assistant writes has a matching Code Builder tab:

When you add, rename, or remove a field, update both the Form and Visibility tabs. The Visibility tab lists every field by its ID, so the two need to match.

FAQ