new-integrator

Scaffold a new integrator

Scaffold a new integrator named $name under contracts/integrators/<name>/. This is a guided multi-step workflow that follows CONTRIBUTING.md. At every step, default to the convention and soft-warn on deviation — never hard-block.

Step 0 — Preconditions

Run these and abort with a clear message if any fail:

• Confirm CWD is the payment-integrators repo: read package.json and check "name": "@p2pdotme/payment-integrators". If not, tell the user "this skill only runs inside the payment-integrators repo" and stop.
• Confirm git status is clean OR the only diff is untracked .claude/. If there are unstaged changes, ask the user to commit or stash before continuing.
• Confirm the canonical template exists at contracts/templates/MyIntegrator.sol. If not, the repo is in an unexpected state — abort.

Step 1 — Resolve the name

If $name is empty, ask: "What's the integrator name? Use kebab-case for the directory (e.g. acme-checkout → contracts/integrators/acme-checkout/)."

Derive these three forms and confirm with the user:

Form	Example for acme-checkout	Used where
kebab	acme-checkout	directory, filenames, deploy script
Pascal	AcmeCheckout	Solidity contract name (AcmeCheckoutCheckoutIntegrator ← yes, doubled — see warn below)
display	Acme Checkout	docs page title, PR title

Soft-warn if the user-supplied name doesn't match ^[a-z][a-z0-9-]{1,30}$. The convention is lowercase kebab; warn but accept anything that's a valid filesystem identifier.

Naming convention for the Solidity contract: <Pascal>CheckoutIntegrator.sol. If Pascal already ends in Checkout (e.g. LotPotCheckout), the contract name would double up (LotPotCheckoutCheckoutIntegrator) — warn the user and offer to drop the suffix to <Pascal>Integrator.sol instead.

Step 2 — Gather four facts

Ask the user, one question at a time, with sensible defaults. Show the default in [brackets] and accept enter-to-confirm.