api-design-principles
Skill8 starsChanged 5 months agoNo licenceView on GitHub
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
We split this skill into the rules it gives an agent
7 rules. 5 are common, 0 are distinctive, and 2 are very specific to this project.
5
Common
Most of the 25 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Other versions32 projects use a version of this.
Word for word · 2
- Bbar0n234/learnflow-ai★ 35100% same
- CodeWithBehnam/cc-docs★ 2100% same
Edited · 28
- coco-research/coco★ 79794% same
- jh941213/my-claude-code-asset★ 12693% same
- chendongqi/OPB-Skills★ 12596% same
- jh941213/ADLC-harness★ 12593% same
- jh941213/my-cc-harness★ 12593% same
- The-AIOS/aios★ 9396% same
- KhaledSaeed18/node-express-boilerplate★ 3694% same
- nilecui/SkillsBase★ 2796% same
- wpank/ai★ 1115% same
- xfstudio/skills★ 949% same
18 more not listed
Wrote their own version · 2
- myths-labs/muse★ 37same name
- kumaran-is/claude-code-onboarding★ 35same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use error-handling-patterns, tailwind-design-system and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
xfstudioSkillerror-handling-patterns
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
Also in 7 projects that use this
- xfstudioSkill
tailwind-design-system
Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
Also in 10 projects that use this
Aver005Skillpython-project-structure
Python project organization, module architecture, and public API design. Use when setting up new projects, organizing modules, defining public interfaces with __all__, or planning directory layouts.
Also in 3 projects that use this
xenitV1Skilldeployment-procedures
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
Also in 3 projects that use this
- Aver005Skill
python-design-patterns
Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use when making architecture decisions, refactoring code structure, or evaluating when abstractions are appropriate.
Also in 3 projects that use this
- +4 more from xfstudio
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-introspection-debuggingSkill
- backend-patternsSkill
- brainstormingSkill
- canary-watchSkill
- coding-standardsSkill
- context-budgetSkill
- councilSkill
- deep-researchSkill
- design-taste-frontendSkill
- dispatching-parallel-agentsSkill
- docker-patternsSkill
- executing-plansSkill
- fastapi-templatesSkill
- finishing-a-development-branchSkill
- frontend-designSkill
- frontend-patternsSkill
- full-output-enforcementSkill
- git-workflowSkill
- hookify-rulesSkill
- minimalist-uiSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- postgres-patternsSkill
- python-patternsSkill
- python-performance-optimizationSkill
- python-testing-patternsSkill
- receiving-code-reviewSkill
- redesign-existing-projectsSkill
- requesting-code-reviewSkill
- safety-guardSkill
- search-firstSkill
- security-reviewSkill
- strategic-compactSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- tdd-workflowSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- using-superpowersSkill
- vercel-react-best-practicesSkill
- verification-before-completionSkill
- verification-loopSkill
- web-design-guidelinesSkill
- writing-plansSkill
- writing-skillsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.