What should the prompt tell Claude Code to read?

Point it to CLAUDE.md or other repository instructions, package scripts, and the current form route or component before editing.

Should Claude Code store the endpoint in a secret variable?

No. The public form slug is browser-visible by design. Only protected access keys, webhook secrets, and provider credentials require server-side secret storage.

Which checks should Claude Code run?

Use the repository's declared formatter, typecheck, tests, and production build, plus a focused diff review. Command names differ by project.

Why test an invalid endpoint?

It proves the generated failure state works, announces the error, and preserves the visitor's message instead of covering only the happy path.

Does Form Plume work with Claude Code?

Yes. Form Plume gives you one endpoint that works from your project. Start with the quickstart docs, then drop the endpoint into your form.

Where do Claude Code form submissions go in Form Plume?

Submissions are stored in your Form Plume dashboard, sent to your email, and can trigger integrations like webhooks, Slack, Discord, Google Sheets, Mailchimp, and ActiveCampaign. See the feature overview for the full flow.

Can I try Form Plume before wiring it into my project?

Yes. You can create an endpoint on the free plan, test it from localhost, preview, or a staging URL, and upgrade only when your form volume or team needs grow. Compare limits on pricing or ask a question on the contact page.

New:Build with AI agents

Ask Claude Code to connect your form to a real backend.

Claude Code wires the existing interface. Form Plume receives the submissions, emails them to you, stores them, blocks spam, and powers downstream automation.

Free foreverNo credit cardPublic endpoint for the existing form

claude prompt

# Repository-aware Claude Code task
Read CLAUDE.md and package.json.
Find the current form before editing.
Preserve its framework and styles.
Run the real project checks.
Show the diff and any residual risk.

The full guide

A bounded task for the real repository.

Make Claude Code inspect first, implement narrowly, and prove the visitor-facing behavior before you ship.

Claude Code works inside an existing project and can read files, edit them, and run commands. It is not the form host. Give it a bounded implementation job, make it follow the repository's CLAUDE.md and existing scripts, then inspect the diff before shipping.

1
Create your Form Plume accountStart free and give your Claude Code form a hosted endpoint for email, submissions, spam filtering, uploads, integrations, and webhooks.Start free
2
Create the form and copy the endpointCopy the endpoint URL from Form Plume. It looks like https://api.formplume.com/f/your-slug
3
Connect it inside Claude CodeReview the patch and command output, then exercise success and failure states from the built application. Send one test submission from the real Claude Code app or preview environment and confirm it reaches Form Plume.

A repository-aware prompt

Find the existing contact form and connect it to this public Form Plume endpoint:
https://api.formplume.com/f/your-public-slug
 
Read CLAUDE.md, package.json, and the relevant route/component before editing.
Preserve the current framework, validation, accessibility, and styling. Use a native
POST form when it fits the current UX, otherwise send FormData with the project's
existing client-side pattern. For fetch, add inline pending, success, and error feedback
and preserve values after an error. For native POST, verify hosted result navigation. Do not create a server route, database, or new dependency just
for delivery. Do not expose access keys, webhook secrets, SMTP credentials, or any
server-only variable. Run the repository's existing formatting, typecheck, tests, and
production build. Finally show the diff summary and list every command and result.

Use plan-first language for an unfamiliar repository: ask Claude Code to identify the form, proposed files, and verification commands before it edits. That makes it easier to catch a mistaken framework assumption early.

Review the patch in two passes

First review scope: did Claude Code change only the form and a relevant test? Then review behavior: named controls, accessible messages, non-2xx handling, and no data loss after failure. git diff --check catches whitespace damage, while the project scripts catch framework errors.

git diff --check
git diff --stat
pnpm typecheck
pnpm test
pnpm build

Those are examples, not universal commands. Claude Code should derive the actual package manager and scripts from the repository. If it reports a skipped check, resolve that explicitly rather than treating the implementation as fully verified.

The security boundary

The endpoint URL contains a public form slug and can live in markup or browser JavaScript. A protected-form access key, webhook signing secret, email-provider key, or deployment credential cannot. An .env value bundled into client code is still visible to visitors.

Permission prompts are a checkpoint, not proof that a command is appropriate. Read broad install, delete, deploy, or Git commands before approving them. A contact-form edit should not need destructive operations.

Test what a visitor experiences

Run the discovered format, type, test, and build scripts.
Submit valid input and verify Form Plume stored it and sent the expected notification.
Use an invalid slug. For fetch, confirm the page announces an inline error without clearing the message. For native POST, confirm the hosted error navigation.
Restore the slug and retest from the production hostname, especially when allowed domains are configured.

For framework specifics, follow the page Claude Code discovers, such as Next.js, Astro, or plain HTML. See the equivalent workflows for Cursor, Windsurf, and Codex.

Primary sources

FAQ

Claude Code questions
before the patch lands.

Yes. It can inspect the repository, edit the relevant files, and run commands. The prompt should require it to preserve the detected framework and existing conventions.

One line. Zero backend.

The form backend you don’t have to build.

Free foreverNo credit cardSet up in under a minute