backend-architecture
Skill0 starsChanged 22 days agoMITView on GitHub
Backend architecture decisions mid-project: how should we architect, ERP/OMS sync, order sync, webhook reliability, idempotency, data model, ADR, scale this. Smallest design first. NOT new-project setup (dev-kickoff), NOT code patterns (dev-patterns), NOT UI/React (frontend-system-design).
12 other projects use a version of this.
Adopted by
Most recently taken up by
- adymire/CraftLayertheir own version, first seen Nov 15, 2026
- veegres/ivorytheir own version, first seen Nov 9, 2026
- polyant-ai/polyanttheir own version, first seen Nov 3, 2026
- mahik504/orchestra-workflowtheir own version, first seen Nov 1, 2026
- overmind-core/overmindtheir own version, first seen Oct 13, 2026
- LuisaGroup/LuisaComputetheir own version, first seen Oct 8, 2026
Used with
Projects with it also use frontend-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.
MicrosoftSkillfrontend-architecture
Internal frontend architecture, design, implementation, verification, and audit rules loaded only when an explicitly invoked repository SDD prompt directs the agent to this skill.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- LuisaGroup/LuisaCompute★ 1.1ksame name
- overmind-core/overmind★ 759same name
- veegres/ivory★ 282same name
- GoldenWing-360/claude-security-skills★ 16same name
- polyant-ai/polyant★ 10same name
- alyanhaider/system-architecture★ 2same name
- jerry-20160416/skills★ 2same name
- we-are-singular/skills★ 2same name
- bedomax/webdesigner-agent★ 1same name
- mahik504/orchestra-workflow★ 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 repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/setup-project-context/templates/CLAUDE.mdCLAUDE.md
- build-review-loopSkill
- capability-intakeSkill
- competitor-market-analysisSkill
- context-auditSkill
- data-analysis-insightsSkill
- data-privacy-securitySkill
- dev-agentsSkill
- dev-patternsSkill
- frontend-system-designSkill
- idea-validatorSkill
- intellectual-property-licensingSkill
- international-legal-researchSkill
- legal-document-drafterSkill
- llm-councilSkill
- make-slidesSkill
- password-authentication-securitySkill
- privacy-data-protection-lawSkill
- project-estimation-planningSkill
- project-startSkill
- rea-researchSkill
- requirements-business-analystSkill
- secrets-credential-managerSkill
- seo-tech-stackSkill
- setup-project-contextSkill
- shopify-ui-auditSkill
- site-incidentSkill
- sop-process-builderSkill
- task-dispatchSkill
- technical-feasibilitySkill
- tech-research-intelligenceSkill
- update-mdSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
No invented numbers. Never present RPS, latency, cost, uptime or a provider API limit as fact.
- Distinctive: line 34
No app code written, nothing installed, nothing deployed, no destructive DB action.
- Very specific: line 41
Is review even needed?: If a single straightforward write covers it, say so and hand to dev-patterns.
“Common” is measured: kept by at least 6 in 10 of the 10 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-architecture
Decision: $ARGUMENTS
A reference and structured decision checklist for ONE hard backend call mid-project: which design, the trade-offs, an ADR, failure modes, and the idempotency / consistency / reconciliation decisions. Reference only. Writes no app code, installs nothing, deploys nothing.
The gap this fills (do not duplicate these)
dev-kickoffowns new-project intake, stack choice, scaffold and the first architecture docs. This skill is NOT project intake.dev-patternsowns the exact code shape for auth, payments, webhooks, jobs, DB, API. This skill decides WHICH design;dev-patternsbuilds it.frontend-system-designowns React/UI state and rendering. This skill is backend only.technical-feasibilityanswers "can it be built". Run it first if that is still open.build-review-loopowns coding + review.task-dispatchowns capability choice and the 80+ gate.
When it fires (selective, no slash needed)
Fire only for a substantive backend design or review: Shopify/app to ERP or OMS order sync, payment/order lifecycle, multi-tenant data boundaries, a WordPress/Woo integration with jobs and retries, or a scale decision backed by real numbers.
Stay INACTIVE for: Shopify Liquid/theme edits, trivial CRUD, one-line API fixes, WordPress styling, UI work. If data-integrity or scale risk is not material, say so and hand back.
Hard rules
- Smallest viable architecture. Default is one service + one database + the managed platform's own features (cron, platform queue, managed Postgres). Never recommend microservices, a message broker, Redis, Kubernetes or a second datastore without measured evidence that requires it.
- No invented numbers. Never present RPS, latency, cost, uptime or a provider API limit as fact. Mark every scale/limit/cost claim
(verify)and check the provider's current official docs (Context7 or the provider's own page) before relying on it. - Evidence first. Read real constraints (users/traffic, data sensitivity, deploy + maintenance budget, integration contracts, failure tolerances). State what evidence is missing instead of assuming scale.
- Server is the source of truth: amount, price, role, status, ownership. A client or an inbound payload is a request, never a fact.
- Exactly-once BUSINESS EFFECT via idempotency; never promise exactly-once message delivery.
- No app code written, nothing installed, nothing deployed, no destructive DB action. Approval gate before any implementation or production change.
- Client-owned accounts and emails; no
org/the-orgin client code or identifiers; project docs stay local; secrets are env-var NAMES only. Verify the outcome, not a proxy (verify-the-outcome-not-a-proxy). - Original checklists only. Do not vendor or paraphrase copyrighted system-design material; develop from first principles.
Lean process
- Constraints + evidence. Restate the decision. List known numbers and failure tolerances; mark unknowns
(verify). Read the projectCLAUDE.md+ Docs map (stack, host, ORM, auth) and grep for an existing implementation to extend. - Is review even needed? If a single straightforward write covers it, say so and hand to
dev-patterns. Otherwise continue. - Describe the system. Primary workflows, actors, trust boundaries, API/events, persistence, data ownership, and the failure points.
- At most TWO viable alternatives. Trade-offs across complexity, cost, ops burden, consistency, latency and reversibility. Lead with the smaller one.
- Material cross-cutting concerns only. Pull the reference(s) below for auth, tenant isolation, webhook signatures, idempotency, rate limits, retries, queues, transaction/consistency, migrations/backups, monitoring, recovery. Skip what does not apply.
- Output an ADR (Context -> Decision -> Consequences), a mermaid flow when it clarifies, a failure-mode table, and testable acceptance checks. Label every item
plannedorimplemented. - Approval + hand off. Get explicit approval before building. Then: project docs ->
dev-kickoff/setup-project-context; exact code ->dev-patterns; build + review ->build-review-loop; release ->deploy-runbook.
Reference index (load one on demand, never all)
| Need | Load |
| Inbound webhooks, ack + persist, dedupe, replays, idempotency, queue vs cron, scheduled jobs | references/distributed-jobs.md |
| Schema, indexes, transaction boundaries, consistency, tenant isolation, migrations, backup/restore | references/data-architecture.md |
| Payment/order state machine, reconciliation, duplicate events, refunds, auditability | references/payments-and-integrity.md |
| Provider quotas, backoff, 429/Retry-After, circuit breakers, pagination windows, timeouts | references/api-and-rate-limits.md |
Output templates
ADR-NN: <decision>
Context: <constraints + evidence; (verify) items>
Decision: <chosen design, smallest that meets the need>
Alternatives: <A vs B, one trade-off line each>
Consequences: <cost, ops, reversibility; what we accept>
Status: proposed | accepted · Approval: <who, pending/given>| Failure mode | Likelihood | Blast radius | Detection | Mitigation | planned/implemented |
Acceptance checks: name the observable end state and assert it on the real path. e.g. "webhook delivered 3x -> 1 order, 1 email"; "revoked user gets 401 on /orders"; "tenant A query never returns tenant B rows"; "refund marked done only after the gateway confirms settled".
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.

