# One prompt. Your AI tool builds the signing flow.

> Vibe coding your own e-signature or clickwrap flow? Choose use cases, regions, and stack. Get a prompt for Cursor, Claude Code, v0, or Lovable, then test your integration against measurable rules.

Source: https://esigncomply.com/product/prompt-generator

Prompt generator

You're vibe coding a clickwrap or a signing page. Choose your use cases, signers, documents, and stack, then paste the generated prompt into Cursor, Claude Code, v0, Lovable, Bolt, or Replit.

[Generate a prompt](https://esigncomply.com/signup) · [Read the quickstart](https://esigncomply.com/docs/quickstart)

## What you choose

Select use cases, signer types, and your stack. Combine U.S. Federal, EU, UK, and Switzerland packs in any combination.

Jurisdiction packs

Federal · EU · UK · CH

Paste into

Cursor · Claude Code · v0 · Lovable · Bolt · Replit

### What the prompt contains

It describes the steps our recording service requires and checks. It lists the duties you build under "Your obligations" and suggested practices under "Recommendations." It also tells your tool which material to send us.

`esigncomply-prompt.md`

\## Required for the record

The steps our recording service requires and checks.

\## Your obligations

Duties the law places on your company, listed for your tool to build.

\## Recommendations

Suggested practices. Your tool asks you before applying one that changes the product.

\## What you can send us

Optional reports you can file. Each is sealed on receipt.

Only the first heading is checked by Esign Comply.

## Build from the session

The prompt tells your tool to pass the customer's signer-state data as `signer.region`, never to infer it from IP, and to use the session's `applied_jurisdictions`, `rules_fired`, `required_strings`, and `required_steps`.

Choose automatic, strictest, or explicit application. Use `POST /v1/jurisdictions/resolve` to preview the result without creating a session.

POST /v1/sessions

- `signer.region`: The signer's state, passed from your own data. Never inferred from IP.
- `applied_jurisdictions`: The packs the session applied.
- `rules_fired`: The rules that fired.
- `required_strings`: The wording the ceremony must show.
- `required_steps`: The exact steps the profile and signer need.

Application · automatic · strictest · explicit

## Keep recording as guidance changes

State and country rules and notices change often. We publish them as dated guidance releases.

### Recording keeps working

Updates do not break an existing recording integration, and adding or removing a state does not require a code change to keep recording.

### New rules start as advisories

New blocking rules, steps, and required facts start as advisories for existing profiles and do not block until you adopt them.

### Notices where you work

We send notices in the dashboard, by email and webhook, and through the API and a public changelog feed. Each release says whether to regenerate your prompt.

Conformance checker

### Check before you ship

Run the conformance checker over your test records. Each finding names the rule, what was measured, and the fix.

[Ceremony SDK and conformance checks](https://esigncomply.com/product/ceremony-sdk)

API

### Also available as an API

`POST /v1/prompts/generate` returns the same prompt for scripts and CI.

[API reference](https://esigncomply.com/docs/api)

## Paste a prompt. Ship the flow. Keep the receipt.

[Get started](https://esigncomply.com/signup) · [Documentation](https://esigncomply.com/docs)

Free plan: 10 live signatures a month and a full test mode. No card required.

---

Every page on esigncomply.com has a Markdown version at the same URL plus `.md` (the home page is `https://esigncomply.com/index.md`). https://esigncomply.com/llms.txt lists them.
