backend-engineer
Skill0 starsChanged 6 months agoNo licenceView on GitHub
Senior backend engineer for building production-grade Java 25 + Spring Boot 4.0.5 applications following hexagonal architecture in the IziVol modular monolith. Use this skill whenever doing backend development: creating new features, adding API endpoints, implementing domain logic, writing database migrations, integrating external APIs, building adapters, or writing tests. Also use it when the user says things like "implement the booking flow", "add the Amadeus adapter", "create a new endpoint", "add a field to the booking", "write a migration", "integrate the payment gateway", or any backend-related task. Triggers on explicit invocation or whenever the work involves Java, Spring Boot, JPA, REST APIs, hexagonal architecture, domain events, database changes, provider integrations, or backend testing in this project. Do NOT trigger for frontend-only work (Next.js, React, TypeScript, Tailwind) — that belongs to the frontend-engineer skill.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- kcayme/k-agentstheir own version, first seen Nov 1, 2026
- pranav8494/team-of-agentstheir own version, first seen Oct 13, 2026
- jscraik/Agent-Skillstheir own version, first seen Sep 27, 2026
- IgnitionAI/skillstheir own version, first seen Sep 3, 2026
- Shivangkesarwani/Nexulyt-AI-OStheir own version, first seen Jul 4, 2026
- loginvijayan/ai-agent-skillstheir own version, first seen Mar 30, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- IgnitionAI/skills★ 9same name
- jscraik/Agent-Skills★ 9same name
- pranav8494/team-of-agents★ 7same name
- kcayme/k-agents★ 0same name
- loginvijayan/ai-agent-skills★ 0same name
- Shivangkesarwani/Nexulyt-AI-OS★ 0same 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.
In this repository9 other files it gives its agents.
- backend-code-reviewerSkill
- dev-workflowSkill
- frontend-code-reviewerSkill
- frontend-dev-workflowSkill
- frontend-engineerSkill
- izivol-debugSkill
- neon-postgresSkill
- travel-innovation-advisorSkill
- ui-ux-reviewSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
38 rules. 0 are common, 26 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
26
Distinctive
This author's own choices. Worth a look.
12
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 6 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.

