[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79TA2S6KFR25FPJEDA39YBA":3,"skill-same:01M79TA2S6KFR25FPJEDA39YBA":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79TA2S6KFR25FPJEDA39YBA","rate-limiting-architect",null,"Architect-level API protection — quota models and key selection, token bucket vs sliding window, where the limiter lives (edge vs app vs database), 429 contract and Retry-After, graceful degradation, and the abuse cases limits are actually for. Use when an API needs quotas or is being scraped\u002Fabused.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fapi-development-architect\u002Frate-limiting-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rate-limiting-architect\ndescription: Architect-level API protection — quota models and key selection, token bucket vs sliding window, where the limiter lives (edge vs app vs database), 429 contract and Retry-After, graceful degradation, and the abuse cases limits are actually for. Use when an API needs quotas or is being scraped\u002Fabused.\nlicense: MIT\ncompatibility: Any HTTP stack; Redis or an edge provider typical\nmetadata:\n  crusor-domain: website-architect\n  crusor-path: website-architect\u002Fapi-development-architect\u002Frate-limiting-architect\n  crusor-origin: original\n  crusor-sources: \"datatracker.ietf.org\u002Fdoc\u002Fdraft-ietf-httpapi-ratelimit-headers; cloud.google.com\u002Farchitecture\u002Frate-limiting-strategies-techniques\"\n  crusor-triggers: \"rate limit, rate limiting, throttling, throttle, quota, 429, abuse, scraping, backpressure, token bucket\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Rate Limiting Architect\n\nLimits exist so that **one client cannot degrade the service for everyone** —\nincluding your own retry storms.\n\n## When to use\n\n- Public or partner-facing APIs.\n- A client (or a bot) is degrading the service.\n- Expensive operations: exports, searches, AI calls, emails.\n\n## When NOT to use\n\n- Internal service-to-service traffic where backpressure and timeouts already\n  bound the work — adding quotas there just hides capacity problems.\n\n## Decision 1 — What you limit, and by whom\n\n| Dimension | Key |\n|---|---|\n| per user | authenticated subject id |\n| per IP | hashed address (behind a trusted proxy) |\n| per API key \u002F tenant | key id, with plan tiers |\n| per endpoint cost | weighted budget (exports cost 10× reads) |\n\n- Rate limit the **cost**, not just the request count: one export can equal 500\n  reads.\n- Anonymous traffic is keyed by IP **and** a coarse fingerprint; IP alone breaks\n  for shared NATs and proxies.\n- Never trust `X-Forwarded-For` without a configured trusted proxy chain.\n\n## Decision 2 — Algorithm\n\n| Algorithm | Behaviour | Use |\n|---|---|---|\n| fixed window | bursty at boundaries | simple, low value |\n| sliding window (log\u002Fcounter) | smooth | default for user quotas |\n| token bucket | allows burst up to capacity | APIs with bursty clients |\n| concurrency limit | caps in-flight | expensive endpoints |\n| queue + shed | admits then rejects | ingestion |\n\n- Default: token bucket per key per endpoint class, stored in Redis with atomic\n  increments (`INCR` + `EXPIRE`, or a Lua script).\n- Distributed limiter needs atomicity; local in-process counters multiply by the\n  instance count.\n\n## Decision 3 — Where it runs\n\n- Edge\u002FWAF for coarse abuse and DDoS (never the only limit).\n- Application middleware for per-user\u002Fper-tenant quotas (knows identity).\n- Per-operation guards for expensive work (exactly where cost is incurred).\n- Limits must degrade gracefully: reject early, before allocating work.\n\n## Decision 4 — The 429 contract\n\n- `429 Too Many Requests` with `Retry-After` (seconds) and rate headers\n  (`RateLimit-Limit`, `RateLimit-Remaining`, `RateLimit-Reset`).\n- The error body uses the same envelope as every other error, with a stable\n  code (`RATE_LIMITED`).\n- Limits are documented publicly: per plan, per endpoint class.\n- Clients must back off with jitter — publish that expectation.\n\n## Decision 5 — Fairness and abuse\n\n- Separate buckets for reads\u002Fwrites\u002Fexports so one heavy endpoint cannot starve\n  the rest.\n- Shadow-ban style soft limits for scrapers: slow, don't block, when the traffic\n  is plausibly human.\n- Cost-based limits for AI\u002FLLM calls with a hard daily budget per tenant.\n- Alert on limiter rejections: a spike is either an attack or your own retry\n  storm.\n\n## Failure modes at scale\n\n- Counter in process memory → effective limit = limit × instances.\n- Fixed windows allowing 2× burst at the boundary.\n- Limiter in front of an expensive job but after the queue → work already\n  enqueued.\n- 429 with no `Retry-After` → clients hammer immediately.\n- Retries without jitter turning a blip into an outage.\n\n## Verification receipts\n\n1. Limit table published: dimension, algorithm, thresholds, plan tiers.\n2. Load test proving rejection happens before expensive work.\n3. Distributed-consistency test across two instances.\n4. Client behaviour test: 429 honoured with backoff, no thundering herd.\n5. Alert on rejection rate and on limiter backend failure.\n","# Rate Limiting Architect\n\nLimits exist so that **one client cannot degrade the service for everyone** —\nincluding your own retry storms.\n\n## When to use\n\n- Public or partner-facing APIs.\n- A client (or a bot) is degrading the service.\n- Expensive operations: exports, searches, AI calls, emails.\n\n## When NOT to use\n\n- Internal service-to-service traffic where backpressure and timeouts already\n  bound the work — adding quotas there just hides capacity problems.\n\n## Decision 1 — What you limit, and by whom\n\n| Dimension | Key |\n|---|---|\n| per user | authenticated subject id |\n| per IP | hashed address (behind a trusted proxy) |\n| per API key \u002F tenant | key id, with plan tiers |\n| per endpoint cost | weighted budget (exports cost 10× reads) |\n\n- Rate limit the **cost**, not just the request count: one export can equal 500\n  reads.\n- Anonymous traffic is keyed by IP **and** a coarse fingerprint; IP alone breaks\n  for shared NATs and proxies.\n- Never trust `X-Forwarded-For` without a configured trusted proxy chain.\n\n## Decision 2 — Algorithm\n\n| Algorithm | Behaviour | Use |\n|---|---|---|\n| fixed window | bursty at boundaries | simple, low value |\n| sliding window (log\u002Fcounter) | smooth | default for user quotas |\n| token bucket | allows burst up to capacity | APIs with bursty clients |\n| concurrency limit | caps in-flight | expensive endpoints |\n| queue + shed | admits then rejects | ingestion |\n\n- Default: token bucket per key per endpoint class, stored in Redis with atomic\n  increments (`INCR` + `EXPIRE`, or a Lua script).\n- Distributed limiter needs atomicity; local in-process counters multiply by the\n  instance count.\n\n## Decision 3 — Where it runs\n\n- Edge\u002FWAF for coarse abuse and DDoS (never the only limit).\n- Application middleware for per-user\u002Fper-tenant quotas (knows identity).\n- Per-operation guards for expensive work (exactly where cost is incurred).\n- Limits must degrade gracefully: reject early, before allocating work.\n\n## Decision 4 — The 429 contract\n\n- `429 Too Many Requests` with `Retry-After` (seconds) and rate headers\n  (`RateLimit-Limit`, `RateLimit-Remaining`, `RateLimit-Reset`).\n- The error body uses the same envelope as every other error, with a stable\n  code (`RATE_LIMITED`).\n- Limits are documented publicly: per plan, per endpoint class.\n- Clients must back off with jitter — publish that expectation.\n\n## Decision 5 — Fairness and abuse\n\n- Separate buckets for reads\u002Fwrites\u002Fexports so one heavy endpoint cannot starve\n  the rest.\n- Shadow-ban style soft limits for scrapers: slow, don't block, when the traffic\n  is plausibly human.\n- Cost-based limits for AI\u002FLLM calls with a hard daily budget per tenant.\n- Alert on limiter rejections: a spike is either an attack or your own retry\n  storm.\n\n## Failure modes at scale\n\n- Counter in process memory → effective limit = limit × instances.\n- Fixed windows allowing 2× burst at the boundary.\n- Limiter in front of an expensive job but after the queue → work already\n  enqueued.\n- 429 with no `Retry-After` → clients hammer immediately.\n- Retries without jitter turning a blip into an outage.\n\n## Verification receipts\n\n1. Limit table published: dimension, algorithm, thresholds, plan tiers.\n2. Load test proving rejection happens before expensive work.\n3. Distributed-consistency test across two instances.\n4. Client behaviour test: 429 honoured with backoff, no thundering herd.\n5. Alert on rejection rate and on limiter backend failure.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"website-architect\u002Fapi-development-architect\u002Frate-limiting-architect","website-architect","original","datatracker.ietf.org\u002Fdoc\u002Fdraft-ietf-httpapi-ratelimit-headers; cloud.google.com\u002Farchitecture\u002Frate-limiting-strategies-techniques","rate limit, rate limiting, throttling, throttle, quota, 429, abuse, scraping, backpressure, token bucket","2026-10-30","Any HTTP stack; Redis or an edge provider typical","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fwebsite-architect\u002Fapi-development-architect\u002Frate-limiting-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill rate-limiting-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill rate-limiting-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill rate-limiting-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fapi-development-architect\u002Frate-limiting-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]