api-and-interface-design
Skill1 starsChanged 16 days agoNo licenceView on GitHub
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
76 other projects use a version of this, 62 of them edited; most edited versions we compared are an older text (32 of 58).
How people change it
Most projects run an older version: 32 of 58 add nothing and lack a rule this one has, most likely added since.
Of the 58 edited versions we compared: 19 keep every rule, 32 are an older text, 7 made changes of their own.
Not in older versions
- Never let the second caller through because the first "seems stuck". A stalled attempt whose fate is unknown is exactly when duplicating costs most.missing from 32 of 32
Rules people drop
- Never let the second caller through because the first "seems stuck". A stalled attempt whose fate is unknown is exactly when duplicating costs most.dropped by 6 of 7
- Use query parameters for filters:dropped by 5 of 7
- Don't mix patterns. If some endpoints throw, others return null, and others return
{ error }— the consumer can't predict behavior.dropped by 4 of 7 - Avoid forcing consumers to choose between multiple versions of the same dependency or API. Diamond dependency problems arise when different consumers need different versions of the same thing. …dropped by 4 of 7
- Be intentional about what you expose. Every observable behavior is a potential commitment.dropped by 3 of 7
- Don't leak implementation details. If users can observe it, they will depend on it.dropped by 3 of 7
- After designing an API:dropped by 2 of 7
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Most recently taken up by
- sirius-cc-wu/sirius-skillsedited, first seen Nov 16, 2026
- Alter-ai/skill-labedited, first seen Nov 15, 2026
- tkbk-online/skillsedited, first seen Nov 15, 2026
- dvy1987/agent-loomtheir own version, first seen Nov 15, 2026
- addyosmani/agent-skillsword for word, first seen Nov 14, 2026
- ishandutta2007/Awesome-Agent-Skillsedited, first seen Nov 8, 2026
Used with
Projects with it also use constraint-driven-development, observability-and-instrumentation and 10 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.
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 17 projects that use this
HK-hubSkillobservability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Also in 40 projects that use this
HK-hubSkilldeprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Also in 40 projects that use this
seikaikyoSkilldoubt-driven-development
對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。
Also in 47 projects that use this
skytiger6724Skillbrainstorm-experiments-existing
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Also in 4 projects that use this
skytiger6724Skillprioritize-assumptions
Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.
Also in 4 projects that use this
- +2 more from HK-hub
- +2 more from skytiger6724
Other versions76 projects use a version of this.
Word for word · 2
- addyosmani/agent-skills★ 118k100% same
- SanHsien/agent-skills★ 1100% same
Edited · 62
- ollaya-dev/ollaya★ 1.4k100% same
- shashankswe2020-ux/whoop-mcp★ 18199% same
- vinvcn/addyosmani-agent-skills-zh★ 4651% same
- jmxt3/gitscape.ai★ 3399% same
- sampleXbro/agentsmesh★ 2799% same
- jaskirat1616/grok-skills★ 22100% same
- ishandutta2007/Awesome-Agent-Skills★ 2199% same
- JPeetz/agent-skills★ 1787% same
- HK-hub/AgentSkills★ 699% same
- lza6/claw-code-tingfeng★ 599% same
52 more not listed
Wrote their own version · 12
- drvoss/everything-copilot-cli★ 49same name
- ddddjaak/ae-skills★ 4same name
- dvy1987/agent-loom★ 4same name
- bnalwalid/walidforge-skills★ 2same name
- codexskills/agent-forge★ 2same name
- GuillemRoca/agent-skills-android★ 2same name
- GodMaking/makecrew★ 1same name
- iancleary/skills★ 1same name
- juandelossantos/another-agent-skills★ 1same name
- subhash-arabhi/saas-playbook★ 1same name
2 more not listed
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.
In this repository134 other files it gives its agents.
- .claude/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .claude/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- ad-managerSkill
- adsSkill
- agent-reachSkill
- algorithmic-artSkill
- animation-performanceSkill
- ap-processorSkill
- brainstormingSkill
- brand-styleSkill
- build-agentSkill
- build-connectorSkill
- business-pulseSkill
- call-listSkill
- call-prepSkill
- call-summarySkill
- canva-creatorSkill
- canvas-designSkill
- cash-flow-snapshotSkill
- ci-cd-and-automationSkill
- close-monthSkill
- codebase-designSkill
- competitor-analysisSkill
- content-strategySkill
- context-engineeringSkill
- contract-reviewSkill
- copywritingSkill
- create-prdSkill
- crm-autopilotSkill
- croSkill
- customer-escalationSkill
- design-taste-frontendSkill
- differential-reviewSkill
- dispatching-parallel-agentsSkill
- documentation-and-adrsSkill
- draft-responseSkill
- drawio-skillSkill
- emil-design-engSkill
- executing-plansSkill
- exploratory-data-analysisSkill
- finishing-a-development-branchSkill
- frontend-designSkill
- grant-rfp-writerSkill
- grillingSkill
- grill-meSkill
- grow-pipelineSkill
- growth-pulseSkill
- gsap-coreSkill
- gsap-frameworksSkill
- gsap-performanceSkill
- gsap-pluginsSkill
- gsap-reactSkill
- gsap-scrolltriggerSkill
- gsap-timelineSkill
- gsap-utilsSkill
- handle-objectionSkill
- handoffSkill
- hiring-screenerSkill
- huggingface-datasetsSkill
- huggingface-gradioSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 5 are common, 1 is distinctive, and 1 is very specific to this project.
5
Common
Most of the 69 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
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 69 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

