API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
Ask your Agent
Use this Skill: https://skilld.dev/gh/davila7/claude-code-templates/api-patterns
This session only. Nothing lands on disk.
≈144 tokens on demand. Your agent reads this file only when SKILL.md points to it.
Choose auth pattern based on use case.
| Pattern | Best For |
|---|---|
| JWT | Stateless, microservices |
| Session | Traditional web, simple |
| OAuth 2.0 | Third-party integration |
| API Keys | Server-to-server, public APIs |
| Passkey | Modern passwordless (2025+) |
Important:
├── Always verify signature
├── Check expiration
├── Include minimal claims
├── Use short expiry + refresh tokens
└── Never store sensitive data in JWTSource: SKILL.md on GitHub
The skill provides comprehensive API design and security documentation along with a Python-based endpoint validator. It is generally well-constructed but contains a potential surface for indirect prompt injection because the validation script analyzes untrusted project files.
No alerts
Risk: LOW · No issues
10/12 files flagged
Score: 93/100 · 2 sections analyzed
Signed by skilld at 1deb97c. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub 13 hours ago.