php-saloon
Skill2 starsChanged 7 months agoMITView on GitHub
Use this skill when building or debugging PHP API integrations and SDKs with Saloon, including connectors, requests, authentication, request bodies, testing, pagination, Laravel integration, and Saloon plugin workflows.
In this repository26 other files it gives its agents.
- other/AGENTS.mdAGENTS.md
- beamng-modsSkill
- bootstrap-vueSkill
- charmbraceletSkill
- depsdotdevSkill
- find-domainSkill
- github-cliSkill
- go-cobraSkill
- goreleaserSkill
- go-viperSkill
- kasettoSkill
- laravel-actionsSkill
- lefthookSkill
- miseSkill
- pelican-panel-pluginsSkill
- php-monorepo-builderSkill
- prd-todo-slicerSkill
- prd-to-kandev-tasksSkill
- qodo-mergeSkill
- release-pleaseSkill
- rewrite-in-goSkill
- shieldsioSkill
- skill-researcherSkill
- skill-scoutSkill
- taskfileSkill
- website-visual-testingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 11 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use this skill when building or debugging PHP API integrations and SDKs with Saloon, including connectors, requests, authentication, …
- Very specific: line 17
Start with references/standalone-sdk-guidance.md and references/building-sdks.md.
- Very specific: line 19
Always use strongly typed DTOs for responses.
- Distinctive: line 20
If a request needs more than 2 or 3 parameters, or a DTO materially improves DX, use a typed DTO instead of a long parameter list.
- Distinctive: line 22
Add docblocks anywhere generics are required.
- Distinctive: line 23
If the API supports authentication, add it.
- Distinctive: line 24
Always support pagination if the API supports it.
- Distinctive: line 25
Always add rate limiting.
- Distinctive: line 28
Add custom exceptions, with a base SDK exception plus specific exceptions for common failures.
- Distinctive: line 29
Put the request and response on exceptions so developers can inspect them.
- Distinctive: line 30
Always write tests without hitting the real API.
- Distinctive: line 34
Keep Laravel support optional and isolated in its own namespace.
- Distinctive: line 35
Add the Laravel plugin as an optional dependency.
- Very specific: line 38
Use spatie/laravel-package-tools for package wiring.
- Very specific: line 42
Read references/index.md for the full page-by-page map.
- Very specific: line 43
Read references/standalone-sdk-guidance.md before designing a standalone client or package.
- Very specific: line 44
Read references/connectors.md, references/requests.md, and references/sending-requests.md before writing core Saloon code.
- Very specific: line 45
Read references/data-transfer-objects.md, references/middleware.md, references/building-sdks.md, and references/laravel-integration.md …
- Very specific: line 46
Read references/testing.md, references/handling-failures.md, and references/handling-rate-limits.md before shipping production integrations.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
php-saloon
Use this skill when building or debugging PHP API integrations and SDKs with Saloon, including connectors, requests, authentication, request bodies, testing, pagination, Laravel integration, and plugin workflows.
Rules
Standalone API Clients
- Start with
references/standalone-sdk-guidance.mdandreferences/building-sdks.md. - Build the SDK around a Saloon
Connector, and keep it easy to expand with resource classes, request classes, and strongly typed DTOs. - Always use strongly typed DTOs for responses. Prefer
github.com/Crell/Serdefor response DTO serialization. - If a request needs more than 2 or 3 parameters, or a DTO materially improves DX, use a typed DTO instead of a long parameter list.
- Everything must be strongly typed. Follow the nearby
php-proskill for PHP typing expectations when it is available. - Add docblocks anywhere generics are required.
- If the API supports authentication, add it. Let developers pass strongly typed auth details instead of loose arrays.
- Always support pagination if the API supports it.
- Always add rate limiting.
- Support caching as an optional dependency, and let developers pass their own cache implementation.
- Let developers register their own middleware.
- Add custom exceptions, with a base SDK exception plus specific exceptions for common failures.
- Put the request and response on exceptions so developers can inspect them.
- Always write tests without hitting the real API.
Laravel Support
- Keep Laravel support optional and isolated in its own namespace.
- Add the Laravel plugin as an optional dependency.
- Implement a facade and config.
- Auto-wire the SDK through a wrapper class that applies optional concerns like auth, caching, and middleware composition.
- Use
spatie/laravel-package-toolsfor package wiring.
References
- Read
references/index.mdfor the full page-by-page map. - Read
references/standalone-sdk-guidance.mdbefore designing a standalone client or package. - Read
references/connectors.md,references/requests.md, andreferences/sending-requests.mdbefore writing core Saloon code. - Read
references/data-transfer-objects.md,references/middleware.md,references/building-sdks.md, andreferences/laravel-integration.mdbefore building an SDK package. - Read
references/testing.md,references/handling-failures.md, andreferences/handling-rate-limits.mdbefore shipping production integrations.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

