Claude Code API Patterns Skill for REST, GraphQL, and tRPC Decisions
Compare clients, query shapes, type sharing, and maintenance costs before selecting an API style. The pinned skill includes separate reading for REST, GraphQL, and tRPC.
中文Install in Claude Code
Use Claude Code with the full pinned skill and confirmed client requirements. Bring concrete reads or writes and a list of consumers.
- Get the complete `cli-tool/components/skills/development/api-patterns` directory from the pinned GitHub checkout.
- Copy it under the target project's `.claude/skills/`. Confirm `.claude/skills/api-patterns/SKILL.md`, open Claude Code at the project root, and call `/api-patterns`.
Example task
Pick an interface for a fictional book catalog. A website and two external tools need a list and lookup by ID. Fields are stable and custom nested queries are unnecessary.What to check
Explain the choice in terms of clients and data shape. If proposing REST, outline list and detail boundaries and when to revisit the decision.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should familiarity with the language determine the API style?
Check the number of clients, their query shapes, type sharing, and evolution cost. Validate the choice against representative calls.