agentleFS
aaronfloreyaaronflorey/agent-skills/skills/php-saloon/SKILL.md

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.

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
  1. Distinctive:

    Use this skill when building or debugging PHP API integrations and SDKs with Saloon, including connectors, requests, authentication, …

    line 11
  2. Very specific:

    Start with references/standalone-sdk-guidance.md and references/building-sdks.md.

    line 17
  3. Very specific:

    Always use strongly typed DTOs for responses.

    line 19
  4. Distinctive:

    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.

    line 20
  5. Distinctive:

    Add docblocks anywhere generics are required.

    line 22
  6. Distinctive:

    If the API supports authentication, add it.

    line 23
  7. Distinctive:

    Always support pagination if the API supports it.

    line 24
  8. Distinctive:

    Always add rate limiting.

    line 25
  9. Distinctive:

    Add custom exceptions, with a base SDK exception plus specific exceptions for common failures.

    line 28
  10. Distinctive:

    Put the request and response on exceptions so developers can inspect them.

    line 29
  11. Distinctive:

    Always write tests without hitting the real API.

    line 30
  12. Distinctive:

    Keep Laravel support optional and isolated in its own namespace.

    line 34
  13. Distinctive:

    Add the Laravel plugin as an optional dependency.

    line 35
  14. Very specific:

    Use spatie/laravel-package-tools for package wiring.

    line 38
  15. Very specific:

    Read references/index.md for the full page-by-page map.

    line 42
  16. Very specific:

    Read references/standalone-sdk-guidance.md before designing a standalone client or package.

    line 43
  17. Very specific:

    Read references/connectors.md, references/requests.md, and references/sending-requests.md before writing core Saloon code.

    line 44
  18. Very specific:

    Read references/data-transfer-objects.md, references/middleware.md, references/building-sdks.md, and references/laravel-integration.md …

    line 45
  19. Very specific:

    Read references/testing.md, references/handling-failures.md, and references/handling-rate-limits.md before shipping production integrations.

    line 46

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.md and references/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/Serde for 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-pro skill 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-tools for package wiring.

References

  • Read references/index.md for the full page-by-page map.
  • Read references/standalone-sdk-guidance.md before designing a standalone client or package.
  • Read references/connectors.md, references/requests.md, and references/sending-requests.md before writing core Saloon code.
  • Read references/data-transfer-objects.md, references/middleware.md, references/building-sdks.md, and references/laravel-integration.md before building an SDK package.
  • Read references/testing.md, references/handling-failures.md, and references/handling-rate-limits.md before shipping production integrations.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.