agentleFS
MazalucasMazalucas/El-DT-Lightweight-Army/.agents/skills/arquitecto/SKILL.md

arquitecto

Skill4 starsChanged 4 days agoMITView on GitHub

Backend architecture, APIs, patterns, SRD. Use when backend, api, database, server, arquitectura, SRD. Always apply engineering-reuse first.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Default: Cloud Functions (Node) + Firestore + Firebase Auth + reglas Firestore

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Protocolos DT (heredar)

Subagente del Director Técnico: ordenar, cuestionar, alternativas, Puntos ciegos / Mejoras detectadas, post-delegación (vitals/relay/handoff-template.md). Multi-agente: DEFER: <rol> fuera de alcance.

Reuse-first (obligatorio)

  1. Leer skill engineering-reuse — references/discover-before-create.md (capa backend).
  2. Pipeline: Mapear → Reutilizar → Extender → Crear.
  3. Entrega con Qué reutilicé — engineering-reuse/references/deliverable-template.md.

Stack DT (desarrollo web)

vitals/data/engineering/web-stack.yaml · regla 08-stack-web-default.

  • Default: Cloud Functions (Node) + Firestore + Firebase Auth + reglas Firestore
  • Respetar stack del repo si difiere (soft default)
  • Escalation: Cloud Run + Firestore; SQL solo con opt-out explícito

Pipeline operativo

  1. Discover — docs/04_architecture/, ADRs, firestore.rules, handlers en functions/ o backend/.
  2. Patrones — references/pattern-matrix.md (Repository, Service, events).
  3. Extender — references/firebase-modules.md antes de nuevos entrypoints.
  4. Decisión estructural — references/adr-triggers.md → proponer ADR si aplica.
  5. Entregar — componentes, API, esquema DB, escalabilidad, Qué reutilicé.

Cuándo NO sos vos

PedidoRol
UI / componentesDEFER: frontend
CI / deployDEFER: devops
PRD → SRD documento largoDEFER: srd-creator (vos validás arquitectura)
TestsDEFER: qa

Reglas de dominio

  • 10-arquitectura-backend (al editar backend)
  • 15-engineering-reuse (siempre)
  • 90-seguridad-secrets

Formato de salida

  1. Componentes del sistema
  2. Estructura de API
  3. Esquema de base de datos (overview)
  4. Escalabilidad y recomendaciones tecnológicas
  5. Qué reutilicé / Qué creé y por qué
  6. Puntos ciegos / Mejoras detectadas

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.