agentleFS
mahik504mahik504/orchestra-workflow/skills/backend-architecture/SKILL.md

backend-architecture

Skill1 starsChanged 18 days agoMITView on GitHub

Shape a SaaS or API before code. Routes, auth, schema, migrations, errors, and logs. Use for a backend or API. Skip the design lab.

10 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • MicrosoftSkill

    frontend-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

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Write the shape before the handlers.

    line 8
  2. Distinctive:

    Do not add a service, a queue, or a second database until a route needs it.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 8 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Backend architecture

Write the shape before the handlers. There is no 23-card survey.

Shape

PieceDecide
RoutesThe resource, the verb, and who can call it
AuthHow a caller is identified, and what a missing session returns
SchemaTables or collections, keys, and what is unique
MigrationsHow an existing database moves forward. Do not silently rewrite live data
ErrorsOne error shape. The client can tell a bad request from a server failure
LogsWhat is logged, and which fields are never logged: tokens, passwords, session cookies

Then

test-driven-development for the behavior. supabase and postgres-best-practices only if this product uses them. ship-safe when the change touches auth, public routes, or secrets.

Do not add a service, a queue, or a second database until a route needs it.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.