Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →wshobson/api-design-principles
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers.
Passed 24 of 24 test cases with the skill, and 23 of 24 without it.
1 fixed23 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
A team starting a new backend service wants to skip writing a GraphQL schema file and instead auto-generate GraphQL types dynamically from their TypeORM entities at runtime. What schema design strategy should be followed instead?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends schema-first development by defining schema types before implementing resolvers. | Missed | Passed |
The instructions your model reads when the skill loads.
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time.
Resource-Oriented Architecture
HTTP Methods Semantics:
GET: Retrieve resources (idempotent, safe)POST: Create new resourcesPUT: Replace entire resource (idempotent)PATCH: Partial resource updatesDELETE: Remove resources (idempotent)Schema-First Development
test cases passed, vs 23 / 24 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.