Rate limiting

Skill soden46/syarif-laravel-ai-skills/skills/rate-limiting

Laravel guidance to apply per-user and per-route limits with RateLimiter and throttle middleware; use backoffs and headers for clientsFrom its SKILL.md

Install

npx -y skills add soden46/syarif-laravel-ai-skills --skill rate-limiting

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 344 tokens by cl100k_base, as published. Nobody here has run it

Rate Limiting

Use this skill when a Laravel task involves rate limiting.

This skill is adapted to the personal Laravel standards in this repository. It maps the public rate-limiting topic from jpcaparas/superpowers-laravel into the local rate-limiting catalog without copying third-party skill body text.

Syarif Defaults

Follow Laravel conventions before introducing custom abstractions.
Prefer project-local patterns when they are explicit and tested.
Keep controllers focused on HTTP orchestration.
Put validation, authorization, transactions, side effects, and integrations at clear boundaries.
Keep client names, credentials, internal URLs, provider secrets, and project-specific business rules out of reusable standards.
Verify important behavior with the smallest meaningful tests and quality checks.

Workflow

Detect the Laravel version, PHP version, runner, package manager, and existing project conventions.
Identify the smallest local skill set that overlaps this topic.
Implement or review the change using Laravel-native APIs first.
Add abstractions only when they reduce real complexity or protect a meaningful boundary.
Run targeted tests and available quality checks before handoff.

Checkpoints

Authorization and validation boundaries are explicit.
Query shape, transactions, queues, cache, files, and external calls are intentional when touched.
User-facing behavior has feature, unit, browser, or integration tests at the right level.
Logs and errors are useful without exposing secrets or unnecessary personal data.
Documentation or proposals avoid importing source-project names or one-off business rules.

Related Skills

using-laravel-standards
architecture
testing
security

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most apis services skills give in 344 tokens

Counted across 448 of the 471 authors here whose files we hold, read 2026-09-06

Use HTTP status codes semanticallyin 25 of 448, across 11 files
Return 201 with a Location header on createin 24 of 448, across 9 files
Name resources plural, lowercase, kebab-casein 23 of 448, across 9 files
Configure rate limiting with limit headersin 22 of 448, across 8 files
Paginate list endpoints with cursor or offsetin 21 of 448, across 10 files
Version APIs in the URL pathin 21 of 448, across 11 files
Validate request input with a schemain 21 of 448, across 7 files
Add pagination to all list endpointsin 18 of 448, across 15 files
Match HTTP method to the operationin 12 of 448, across 6 files
Return 400 or 422 with field-level detailsin 12 of 448, across 2 files
Check ownership before returning resourcesin 12 of 448, across 2 files
Limit query depth and complexityin 12 of 448, across 7 files

Said here and by no other author read

Apply per-user and per-route limits.
Use backoffs and headers for clients.
Use Laravel-native APIs first.
Follow Laravel conventions before custom abstractions.
Detect Laravel and PHP versions and project conventions.
Keep controllers focused on HTTP orchestration.

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.