Site edit

Editors leave notes on the page; an agent makes the change; the editor ships it from an email. The developer sets it up once. This skill does that setup with the npm package @nuthinking/site-edit, which holds the widget and the server handlers, and the templates it ships for the workflows, the email script and the agent rules.

pins and notes on the page ──▶ GitHub issue ──▶ Claude Code makes the change ──▶ pull request
        ▲                                                                              │
        │                                                                              ▼
   notes on the preview ◀── email: screenshots, replies, Ship ◀── Vercel preview deployment

How each piece behaves, and why: references/how-it-works.md. Read it before installing, and whenever you explain the loop to the user. The settings only a human can make (GitHub App, secrets, Vercel, Resend): references/setup.md.

What it needs. A GitHub repository; a React site (the widget is React; Next.js App Router has a ready-made entry, other frameworks take two props); a host that deploys previews per branch and reports them as GitHub deployments (Vercel does); a Resend account for the email; a Claude subscription or API key for the GitHub Action. Without Vercel the editing and approval work, but the email script needs a GitHub deployment with a preview URL to screenshot.

Choose a mode