agentleFS
MazalucasMazalucas/El-DT-Lightweight-Army/AGENTS.md

El-DT-Lightweight-Army

AGENTS.md4 starsChanged 19 days agoMITView on GitHub

Cerebro compartido de El DT. Reglas operativas: .cursor/rules/ (Cursor) · espejos en .claude/rules/, .agents/rules/ (Antigravity). Leé vitals/specs/agent-inbox.md y usá ./scripts/dt-agent.sh (login, inbox, sync). Publicá el inbox con sync, no con /guardar. Los subagentes de un chat no se dan de alta en el roster: vitals/relay/handoff-template.md. Primera vez: /bienvenida → /yo → trabajar → /guardar Jornada: /actualizar → /yo → trabajar → /guardar (/actualizar no crea sesión) Si no existe vitals/ops/session.yaml (o falta operator.id) y el operador acaba de clonar o…

The file

We split this AGENTS.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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
  1. Very specific:

    No editar reglas/skills generados a mano en .claude/, .agents/ (espejos) — fuentes en vitals/specs/rule-bodies/ y .cursor/skills/.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

AGENTS.md — puerta de entrada para la IA

Cerebro compartido de El DT. Reglas operativas: .cursor/rules/ (Cursor) · espejos en .claude/rules/, .agents/rules/ (Antigravity).

Índice rápido

PreguntaDónde
Ritual Git / equipodocs/00_overview/cerebro-equipo-mecanismos-dt.md (DOC-OV-004)
Sesión localvitals/ops/session.yaml — sin operator.id → /yo
Cuánto contexto/dt-config — perfil local, no va a Git
Commandsvitals/config/commands-meta.yaml
Reglas y subagentes.cursor/rules/ · README — 24 especialistas
Stack webdocs/03_reference/web-stack-default.md · regla 08-stack-web-default
Reuse / númerosreglas 15-engineering-reuse, 16-numeric-grounding
Docs IAdocs/99_meta/protocolo-documentacion-ia.md · regla 02-documentacion
Pulso / specs DTvitals/INDEX.md
Cumplimiento legal de una app/auditoria-legal · docs/03_reference/auditoria-legal.md (DOC-REF-012)
Captura de conocimiento/ordenar · docs/02_guides/ordenar-captura-conocimiento.md (DOC-GUIDE-016)
Google Drive / Gmail / Calendar (opcional)docs/02_guides/drive-cerebro-setup.md · /drive /gmail /calendar
Skills en todos los IDE/skills · vitals/specs/skill-standard.md · canon .cursor/skills/
Atelier / marketing táctico.cursor/skills/atelier/ · guías design/*/GUIDE.md, marketing/*/GUIDE.md
Paridad multi-IDEvitals/config/ide-targets.yaml · ./scripts/sync-ide.sh
Agentes miembro e inbox entre agentesvitals/specs/agent-inbox.md · plantilla vitals/relay/inbox-message-template.md

Si sos un agente autónomo

Leé vitals/specs/agent-inbox.md y usá ./scripts/dt-agent.sh (login, inbox, sync). Publicá el inbox con sync, no con /guardar. Los subagentes de un chat no se dan de alta en el roster: vitals/relay/handoff-template.md.

Ritual

Primera vez: /bienvenida → /yo → trabajar → /guardar
Jornada: /actualizar → /yo → trabajar → /guardar (/actualizar no crea sesión)

Post-clone — primera conversación (IA)

Si no existe vitals/ops/session.yaml (o falta operator.id) y el operador acaba de clonar o abre el repo por primera vez:

  1. Mostrar el mensaje de bienvenida canónico — skill dt-setup → .cursor/skills/dt-setup/references/welcome-message.md (equivalente a invocar /bienvenida).
  2. Ejecutar el checklist read-only del skill; si falta estructura → incluir /setup como paso explícito en el mensaje.
  3. No escribir en el repo ni proponer commit hasta /yo.

Si el operador escribe /bienvenida, seguir el mismo flujo (modo first-run de dt-setup).

Mantenimiento del framework

/setup (repair drift) · /actualizar-dt (upstream) · verificación: ./scripts/dt-doctor.sh

No editar reglas/skills generados a mano en .claude/, .agents/ (espejos) — fuentes en vitals/specs/rule-bodies/ y .cursor/skills/.

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.