MicrosoftKnown publishermicrosoft/frontier-ghcp-ttt-rvas/sessions/session-m3-05-agent-skills-ecosystem/lab/solution/skills-project/.github/skills/api-design/SKILL.mdapi-design
Skill3 starsChanged 54 days agoMITView on GitHub
Use for creating or reviewing REST routes under src/api/ when acceptance criteria, a reviewer, and a verified focused test command are available. Do not use for documentation, UI, deployment, or generated clients.
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 164 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
If any precondition is missing, stop and report the missing item.
- Distinctive: line 20
Read the target route and adjacent tests.
- Distinctive: line 25
Run the checked focused test command.
- Very specific: line 37
Stop when the task is outside src/api/.
- Distinctive: line 38
Stop when acceptance criteria, a reviewer, or the test command is missing.
- Distinctive: line 39
Do not add a dependency, call a network service, or change deployment files.
- Distinctive: line 40
Do not replace a failed command with a manual success claim.
“Common” is measured: kept by at least 6 in 10 of the 164 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.
Files
API design
Preconditions
- The task names one REST route under
src/api/. - Acceptance criteria define success and failure behavior.
- A human reviewer is assigned.
- The repository has a focused test command that has been checked.
If any precondition is missing, stop and report the missing item. Do not infer a repository convention or claim that validation ran.
Procedure
- Read the target route and adjacent tests.
- Map each acceptance criterion to a result that shows success or failure.
- Preserve the repository's current response and error shapes.
- Validate input at the route boundary.
- Make the smallest route and focused-test change.
- Run the checked focused test command.
- Report changed files, test output, and unresolved gaps.
- Request human review.
Validation
The run is complete only when the focused test command passes and the reviewer can trace every assertion to an acceptance criterion. If the command fails, show the failure and do not report success.
Failure behavior
- Stop when the task is outside
src/api/. - Stop when acceptance criteria, a reviewer, or the test command is missing.
- Do not add a dependency, call a network service, or change deployment files.
- Do not replace a failed command with a manual success claim.
Maintenance
Owner: training-maintainers
Review this skill when route conventions, test commands, or supported skill frontmatter change. Use the same procedure as a manual checklist when a client approved for use cannot load the skill.
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- affaan-m/ECC★ 246ksame name
- authgear/authgear-server★ 2.1ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
- Aaronontheweb/dotnet-skills★ 1.2ksame name
- epam/ai-dial-chat★ 502same name
- loulanyue/awesome-claude-notes★ 272same name
- KbWen/agentic-os★ 224same name
- DevelopersGlobal/ai-agent-skills★ 216same name
- kid-sid/claude-spellbook★ 190same name
- margelo/react-native-skills★ 172same name
182 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.
Used alongsideProjects with it also use everything-claude-code, everything-claude-code-conventions 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.
InfopibeSkilleverything-claude-code
Also in 9 projects that use this
mryeastcodeSkilleverything-claude-code-conventions
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Also in 8 projects that use this
tpavanipradeepSkillnextjs-turbopack
Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.
Also in 15 projects that use this
- InfopibeSkill
investor-materials
Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
Also in 21 projects that use this
CodeWithBehnamSkilldmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
Also in 16 projects that use this
Indium-AI-LabsSkilldata-pipeline-design
Design batch or incremental ETL and ELT pipelines and warehouse models: grain, partitioning, idempotent loads, late-arriving data, data quality tests, PII controls, and cost monitoring, before building them. Use when adding or changing a dbt model, warehouse table, scheduled transformation, or ingestion job. Not for transactional schema design (use the database-design skill) or event-sourced stores (use the event-sourcing-architecture skill).
Also in 3 projects that use this
- +1 more from Infopibe
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- sessions/session-m2-03-spaces-and-context/lab/solution/ecommerce-project/.github/copilot-instructions.mdCopilot instructions
- sessions/session-m2-03-spaces-and-context/lab/solution/instructions-lab/.github/copilot-instructions.mdCopilot instructions
- sessions/session-m3-02-cloud-agent/lab/starter/copilot-instructions.mdCopilot instructions
- sessions/session-m5-03-hve-core-challenge/lab/solution/decision-api/.github/copilot-instructions.mdCopilot instructions
- baoyu-infographicSkill
- diagram-creatorSkill
- docxSkill
- excalidraw-diagramSkill
- humanize-contentSkill
- impeccableSkill
- pdfSkill
- pptxSkill
- rvap-brandSkill
- skill-creatorSkill
- xlsxSkill
- impeccableSkill
- session-format-validatorSkill
- deploymentSkill
- grillingSkill
- grill-meSkill
- deploymentSkill
- replace-with-directory-nameSkill
- decision-interviewSkill
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.