AddThisFeature

Newsletter Signup

Collect email addresses with proof that the person actually asked to hear from you.

simple Growth

What it adds

An email capture form with a confirmation step, stored consent metadata, and a working unsubscribe.

What your agent is told to do

5
  1. 1

    Place the capture box where it makes sense and keep it to one field plus a button. Ask for a name only if you will actually use it.

  2. 2

    Send a confirmation email containing a signed, expiring link and only mark the subscriber active when it is clicked. Store the source, the timestamp, and the address of the request alongside the subscription as the record of consent.

  3. 3

    Reuse the app's existing Email Verification mechanism for the confirmation link rather than writing a second token scheme, and route unsubscribes through the existing Email Preference Center if one exists.

  4. 4

    If the app already syncs contacts to an external marketing platform, make this feature feed that same pipeline instead of creating a second list that immediately diverges.

  5. 5

    Do not add the address to your sending list before confirmation. Sending to unconfirmed addresses is how a domain's sending reputation is destroyed, and it is difficult to recover.

Edge cases it handles

8
  • A misspelled common domain silently loses the subscriber forever. Validate the address format and warn on near-miss domains before storing, while still allowing the user to override.
  • Someone who signs up twice should see the same success message as a first-time signup. Telling them the address is already registered leaks who is on your list.
  • Unconfirmed opt-in links must expire after a defined window, and the pending record should be cleaned up rather than sitting in the table forever.
  • Every subscriber needs the source, exact timestamp, and consent context recorded. Without that you cannot answer a complaint or a regulator asking where the address came from.
  • An address that has unsubscribed must not be silently reactivated by a later form submission. Treat the resubscribe as a deliberate act requiring a fresh confirmation.
  • The unsubscribe link in every sent email must work without a login and must take effect immediately, not at the next send.
  • The form is a spam target. Rate-limit by address and by session so it cannot be used to send confirmation emails to arbitrary third parties.
  • Success and error states must be announced accessibly, and the form must not clear itself before the visitor has seen the confirmation message.

Definition of done

9
  • An address becomes an active subscriber only after a confirmation link is clicked.
  • Consent source, timestamp, and context are stored for every subscriber.
  • Confirmation links expire after a defined window and expired attempts explain what to do next.
  • A repeat signup returns the same success response as a first signup.
  • A previously unsubscribed address is not reactivated without a fresh confirmation.
  • Unsubscribe works from any sent email without a login and takes effect immediately.
  • The form is rate-limited and cannot be used to mail arbitrary addresses.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.