Next step · What to do next

Protect forms and sign-in from floods (rate limits)

What you may see

Bots or one person can send too many requests

Why this step

Anything public that costs money or can be guessed (forms, sign-in, email sending, paid AI calls) needs a limit per person and per time.

Before you start

Which actions are public and which cost money?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Protect forms and sign-in from floods (rate limits)

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
Anything public that costs money or can be guessed (forms, sign-in, email sending, paid AI calls) needs a limit per person and per time.

DO THESE STEPS, IN THIS ORDER
1. List the public actions and propose a sensible limit for each (for example sign-in attempts, form sends, password resets, paid calls).
2. Implement limits on the server keyed by address and by account, with a clear friendly message and a wait time; store counters in a shared place that works on serverless hosts.
3. Make sure honest users behind a shared address are not blocked too easily, and log blocked attempts without personal data.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- Repeating an action quickly beyond the limit is refused with a clear message, and normal use is unaffected.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not rely on limits in the browser only.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

List the public actions and propose a sensible limit for each (for example sign-in attempts, form sends, password resets, paid calls).
Implement limits on the server keyed by address and by account, with a clear friendly message and a wait time; store counters in a shared place that works on serverless hosts.
Make sure honest users behind a shared address are not blocked too easily, and log blocked attempts without personal data.

Do not do this

Do not set limits so low that customers are blocked.
Do not rely on limits in the browser only.

Try another entry