backend-engineering
Skill48 starsChanged 6 months agoApache-2.0View on GitHub
Always-on backend engineering quality kernel for Rust/Axum harness work. Use when changing or reviewing backend services, servers, workers, contracts, repo-tools, platform-facing backend metadata, or backend documentation. Guides invariant-first design, boundary discipline, evidence language, and template-quality code judgment without overriding ownership skills.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- hamzzaqureshi/gravidextheir own version, first seen Nov 8, 2026
- AntonioMellies/claude-code-skillstheir own version, first seen Nov 1, 2026
- rogue-dev-studio/ai-agents-roguetheir own version, first seen Nov 1, 2026
- alfonsusenrico/pakemtheir own version, first seen Oct 25, 2026
- PhoenixNest/AGENT-GLOBAL-BASEtheir own version, first seen Oct 20, 2026
- foreturn/product-studiotheir own version, first seen Oct 14, 2026
Used with
Projects with it also use software-architecture.
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.
nek1987Skillsoftware-architecture
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- magnus919/agent-skills★ 177same name
- foreturn/product-studio★ 3same name
- JimmyVGDY/codex-long-term-assistant-skills★ 3same name
- adtn0810/truestack★ 2same name
- AntonioMellies/claude-code-skills★ 2same name
- PhoenixNest/AGENT-GLOBAL-BASE★ 2same name
- rogue-dev-studio/ai-agents-rogue★ 2same name
- yuexueyu/anna-agent-skills★ 2same name
- hamzzaqureshi/gravidex★ 1same name
- alfonsusenrico/pakem★ 0same name
1 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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- contract-agentSkill
- harness-architecture-reviewSkill
- harness-diagnoseSkill
- harness-grillSkill
- harness-tddSkill
- harness-zoom-outSkill
- plannerSkill
- platform-ops-agentSkill
- server-agentSkill
- service-agentSkill
- skill-authoringSkill
- worker-agentSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
9
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 13
Use this skill as the default quality lens for backend harness work.
- Distinctive: line 19
Keep the template small, explicit, typed, testable, and production-minded without pretending it is production-proven.
- Distinctive: line 21
Prefer the smallest design that preserves:
- Distinctive: line 32
Before changing backend behavior, answer:
- Distinctive: line 53
Keep expected failures typed and matchable.
- Distinctive: line 57
Do not add traits, managers, adapters, compatibility layers, or generic repositories unless they protect a real boundary or remove proven …
- Distinctive: line 58
Prefer reference-module reuse over new structure, but do not copy business semantics blindly.
- Distinctive: line 63
Use evidence terms precisely:
- Very specific: line 70
Never upgrade a claim from declared to checked, tested, or proven without executable evidence.
- Distinctive: line 74
Use focused workflow skills only when risk justifies deeper analysis:
“Common” is measured: kept by at least 6 in 10 of the 5 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 Engineering
Use this skill as the default quality lens for backend harness work.
Workflow skills guide judgment. Ownership skills still decide writable boundaries.
Objective
Keep the template small, explicit, typed, testable, and production-minded without pretending it is production-proven.
Prefer the smallest design that preserves:
- backend correctness
- hard service, protocol, server, worker, and platform boundaries
- topology-late growth
- executable evidence
- template-user simplicity
- agent resistance to drift
Decision Kernel
Before changing backend behavior, answer:
- What invariant must not be violated?
- Which boundary owns the violated or changed behavior?
- What is synchronous, asynchronous, durable, idempotent, replayable, or eventually consistent?
- What is the cheapest correct design that restores the invariant?
- What evidence can honestly be claimed after this change?
Boundary Rules
services/**are business capability libraries by default, not service processes.servers/**adapt protocols and compose services; handlers do not own domain logic.workers/**advance async state and must make retry, idempotency, checkpoint/replay, dedupe, and recovery explicit when touched.packages/contracts/**owns shared protocol shapes before external API or event changes land elsewhere.platform/model/**describes platform-level metadata and global defaults; service-local semantics stay inservices/<name>/model.yaml.- Generated artifacts are read-only; change sources and regenerate.
- Optional app shells and UI packages must not become backend-core prerequisites.
Quality Rules
- Represent important invariants in types, constructors, constraints, or final transaction boundaries.
- Keep expected failures typed and matchable; do not leak internal dependency details to clients.
- Retries for side-effecting work require durable idempotency or an explicit reason they are safe.
- Cross-boundary events require a clear atomic state mutation and publication story, usually outbox-driven.
- Async work must have bounded concurrency, cancellation/shutdown behavior, timeout or backpressure expectations, and observable failure paths when relevant.
- Do not add traits, managers, adapters, compatibility layers, or generic repositories unless they protect a real boundary or remove proven duplication.
- Prefer reference-module reuse over new structure, but do not copy business semantics blindly.
- Fix the smallest causal closed loop; avoid broad rewrites without an invariant-driven reason.
Evidence Rules
Use evidence terms precisely:
declared: docs, metadata, manifests, or model files state intent.checked: schema, static validation, typecheck, drift check, or boundary check inspected structure.tested: automated tests exercised behavior.proven: a relevant executed gate or runtime/operational evidence supports the claimed invariant.
Never upgrade a claim from declared to checked, tested, or proven without executable evidence.
When To Deepen Review
Use focused workflow skills only when risk justifies deeper analysis:
- architecture review, release readiness, or template admission work
- distributed semantics, replay, idempotency, outbox, or worker recovery changes
- security, secrets, authorization, or tenant boundary changes
- broad backend refactors or cross-boundary protocol changes
- user explicitly asks for top-level backend review or code-quality audit
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.

