REST and GraphQL API design principles for building scalable, developer-friendly APIs.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add wshobson/agents --skill api-design-principlesCompatible with
Supported agents
Covers resource-oriented REST patterns including HTTP method semantics, URL design, pagination, filtering, and error handling with consistent status codes
Includes GraphQL schema-first development with type definitions, resolver patterns, Relay-style pagination, and DataLoader implementation for N+1 prevention
Provides versioning strategies (URL, header, query parameter) and HATEOAS patterns for hy
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionapi-design-principlesExecute the skills CLI command in your project's root directory to begin installation:
epx add wshobson/agents --skill api-design-principlesFetches api-design-principles from wshobson/agents and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/api-design-principles
Restart Cursor to activate api-design-principles. Access via /api-design-principlesin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
frontend-design
anthropics/claude-code · Frontend · tag: design
poster-design-generation
eachlabs/skills · Frontend · tag: design
frontend-design
buildermethods/design-os · Frontend · tag: design
mobile-design
vudovn/antigravity-kit · Frontend · tag: design
pencil-design
chiroro-jr/pencil-design-skill · Frontend · tag: design
ui-animation
mblode/agent-skills · Frontend · same category
api-design-principles reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: api-design-principles is focused, and the summary matches what you get after install.
api-design-principles reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for api-design-principles matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in api-design-principles — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend api-design-principles for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added api-design-principles from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend api-design-principles for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
api-design-principles fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in api-design-principles — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 65