Add Persistent Rate Limiting to Existing App

About this workflow

Integrate a real, persistent rate limiting system into the current application.

What happens when you run it

1. 1
   Determine the app's language/framework and locate the main request handling file to know where to inject rate limiting.

   Runs flow-rate-limiting-1-identify-stack-and-request-entry-point-320b10 on Claude Sonnet 4.6
2. 2
   Select a library that supports external storage (Redis) and add it to the project.

   Runs flow-rate-limiting-2-choose-and-install-a-persistent-rate-limiting-libra-2af37d on Claude Sonnet 4.6
3. 3
   Configure Redis connection and export a store that the rate limiter can use.

   Runs flow-rate-limiting-3-create-a-persistent-store-configuration-d5113f on Claude Sonnet 4.6
4. 4
   Apply the rate limiting middleware to all API routes (or selected ones).

   Runs flow-rate-limiting-4-integrate-middleware-into-the-request-pipeline-bbe178 on Claude Sonnet 4.6
5. 5
   Allow dynamic adjustment of limit values without code changes.

   Runs flow-rate-limiting-5-persist-rate-limit-settings-in-the-database-3474a5 on Claude Sonnet 4.6
6. 6
   Make the rate limiter fetch limit values per route from the database instead of hard‑coded values.

   Runs flow-rate-limiting-6-update-middleware-to-read-limits-from-db-f46955 on Claude Sonnet 4.6
7. 7
   Verify that the limit is enforced and respects DB‑configured values.

   Runs flow-rate-limiting-7-write-end-to-end-tests-for-rate-limiting-7b9d98 on Claude Sonnet 4.6
8. 8
   Confirm rate limiting works in a live environment.

   Runs flow-rate-limiting-8-deploy-and-manually-verify-in-staging-fe1030 on Claude Sonnet 4.6

Best for

• •Recurring tasks you currently copy-paste between tools.
• •When a single prompt isn't enough — you need a chain where output(n) feeds prompt(n+1).
• •Fork and adapt if your inputs differ materially from the author's use case.

Models used