backend
Skill0 starsChanged 2 months agoMITView on GitHub
Optional skill for API or server-side work that is not covered by the Supabase skill. Use only when the product outcome explicitly needs a backend beyond frontend mocks or Supabase.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- gabros20/backend-skilltheir own version, first seen Nov 1, 2026
- hushh-labs/hushh-researchtheir own version, first seen Nov 1, 2026
- darknecrocities/SkillBuildertheir own version, first seen Nov 1, 2026
- marcusbelz/di2-starter-kittheir own version, first seen Oct 31, 2026
- hilmifawwazsaad/NextJS-js-Boilerplatetheir own version, first seen Oct 20, 2026
- langwatch/langwatchtheir own version, first seen Oct 17, 2026
Used with
Projects with it also use security, help and 2 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.
0xSeroSkillsecurity
Also in 5 projects that use this
MicrosoftSkillhelp
Entry point for the MedImageInsight plugin, covering the getting-started walkthrough, how the skills work, what MI2 is, and troubleshooting.
Also in 3 projects that use this
VercelSkilldeploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
Also in 3 projects that use this
- MicrosoftSkill
api-design
Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- langwatch/langwatch★ 5ksame name
- AlexPEClub/ai-coding-starter-kit★ 382same name
- hushh-labs/hushh-research★ 40same name
- ElmatadorZ/skynetclaw★ 16same name
- DojoCodingLabs/code-sensei★ 14same name
- darknecrocities/SkillBuilder★ 13same name
- udaysharmadev/Skills★ 12same name
- mnzralee/claude-multi-agent-architecture★ 8same name
- darker2016/WorkbuddySkillGroups4DSH★ 6same name
- MarvelCollin/agent-skills★ 5same name
9 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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-decisionSkill
- developer-handoffSkill
- react-fsd-pocSkill
- component-designSkill
- databaseSkill
- devopsSkill
- prototypeSkill
- supabaseSkill
- testingSkill
- acceptance-criteriaSkill
- product-definitionSkill
- product-discoverySkill
- project-analysisSkill
- user-storySkill
- ux-flowSkill
- validationSkill
- security-reviewSkill
- verificationSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Keep product UI free of provider leakage.
- Distinctive: line 25
Leave reproducible contracts, types, and setup notes in the repository.
- Distinctive: line 26
Verify the primary backend-dependent journey before delivery.
- Distinctive: line 27
Do not expand into a general DevOps or platform redesign unless asked.
- Distinctive: line 31
Use templates, references, and evaluations for scope and exit evidence.
“Common” is measured: kept by at least 6 in 10 of the 16 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
Backend (optional)
This skill is optional. Most Product-Skills work stays frontend-oriented. Load this skill only when the task needs a non-Supabase API, service, or server boundary.
When to use
- an existing backend must be integrated;
- the team chose a backend other than Supabase;
- contracts, auth, or server behavior are in scope for the current outcome.
When not to use
- UI-only or mock-data work;
- Supabase already covers the need — prefer
supabase; - the request is really architecture ownership for Solution Architects — surface that instead of inventing a platform.
Expectations
- Keep product UI free of provider leakage.
- Leave reproducible contracts, types, and setup notes in the repository.
- Verify the primary backend-dependent journey before delivery.
- Do not expand into a general DevOps or platform redesign unless asked.
Standard resources
Use templates, references, and evaluations for scope and exit evidence.
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.