El-DT-Lightweight-Army / rules
Cursor rule4 starsChanged 19 days agoMITView on GitHub
OBLIGATORIO al consultar Google Drive vía MCP — solo carpetas registradas, solo lectura, consulta dirigida
In this repository163 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/00-orquestador-core.mdcCursor rule
- .cursor/rules/01-protocolos-dt.mdcCursor rule
- .cursor/rules/02-documentacion.mdcCursor rule
- .cursor/rules/03-catalogo-subagentes.mdcCursor rule
- .cursor/rules/05-multi-project-git.mdcCursor rule
- .cursor/rules/06-dt-colaboracion.mdcCursor rule
- .cursor/rules/07-orden-continuo.mdcCursor rule
- .cursor/rules/08-stack-web-default.mdcCursor rule
- .cursor/rules/10-arquitectura-backend.mdcCursor rule
- .cursor/rules/15-engineering-reuse.mdcCursor rule
- .cursor/rules/16-numeric-grounding.mdcCursor rule
- .cursor/rules/17-canvas-first.mdcCursor rule
- .cursor/rules/19-gmail-contexto.mdcCursor rule
- .cursor/rules/20-frontend-ui.mdcCursor rule
- .cursor/rules/21-calendar-contexto.mdcCursor rule
- .cursor/rules/30-testing.mdcCursor rule
- .cursor/rules/31-agent-inbox.mdcCursor rule
- .cursor/rules/40-devops.mdcCursor rule
- .cursor/rules/90-seguridad-secrets.mdcCursor rule
- analisis-propuestaSkill
- arquitectoSkill
- atelier-actualizarSkill
- atelierSkill
- auditoria-legalSkill
- bragSkill
- brand-guardianSkill
- content-creatorSkill
- data-auditorSkill
- deploySkill
- development-plannerSkill
- devopsSkill
- docSkill
- dt-actualizarSkill
- dt-bootstrapSkill
- dt-calendarSkill
- dt-configSkill
- dt-driveSkill
- dt-gmailSkill
- dt-oficialSkill
- dt-ordenarSkill
- dt-sessionSkill
- dt-setupSkill
- dt-skillsSkill
- engineering-reuseSkill
- feedback-synthesizerSkill
- frontendSkill
- git-actualizarSkill
- git-guardarSkill
- github-save-releaseSkill
- growth-hackerSkill
- hack-auditSkill
- marketing-strategistSkill
- operations-maintainerSkill
- pitch-specialistSkill
- prd-creatorSkill
- product-strategistSkill
- qaSkill
- The first 60 shown.
The file
Files
18-drive-contexto.mdc
---
description: OBLIGATORIO al consultar Google Drive vía MCP — solo carpetas registradas, solo lectura, consulta dirigida
globs: "vitals/config/drive-context.yaml, vitals/config/drive-context.yaml.example, vitals/config/google-apps.yaml, vitals/config/google-apps.yaml.example"
alwaysApply: false
---
# Google Drive como contexto del cerebro
Integración **opcional** vía el MCP **oficial del IDE**. Aplica cuando existe `vitals/config/drive-context.yaml` o el usuario invocó `/drive`.
`google-drive-dt` está descontinuado — spec `vitals/specs/google-apps-mcp.md`.
## Cuándo consultar Drive
- El usuario pide contexto que probablemente vive en Drive ("buscá en mis briefs", "qué dice el doc de X").
- Necesitás información de carpetas registradas en `drive-context.yaml`.
- Generar entregables a partir de documentos en Drive **sin** copiarlos al repo (solo lectura).
## Límites obligatorios
1. **Solo carpetas registradas** — con `sync_mode: selective`, consultar únicamente dentro de los `folders[].id` del registro. Con `full_drive`, advertir que la búsqueda es amplia.
2. **Solo lectura** — no crear, editar, mover, borrar ni compartir, aunque el plugin oficial tenga esas tools.
3. **Consulta dirigida** — listar/buscar primero; leer solo archivos relevantes. No volcar carpetas enteras al contexto.
4. **Charter no-secrets** — no persistir en Git tokens, credenciales ni contenido sensible de Drive sin confirmación (`vitals/charter/no-secrets.md`).
5. **Drive ≠ memoria del repo** — destilar a `vitals/` o `docs/` solo si el usuario pide guardar algo en el cerebro compartido.
6. **Embudo** — preguntar si el acceso es solo Drive o también Gmail y Calendar. Instalar el MCP oficial de **ese IDE** (`vitals/specs/google-apps-mcp.md`).
## Resolución de carpeta
Antes de buscar, leer `vitals/config/drive-context.yaml`:
- Matchear la intención del usuario con `purpose` y `keywords` de cada carpeta.
- Si hay ambigüedad, preguntar qué carpeta usar.
- Citar siempre nombre de carpeta + archivo consultado en la respuesta.
## Referencias
- Skill: `.cursor/skills/dt-drive/` · command `/drive` · Gmail `/gmail` · Calendar `/calendar`
- Spec: `vitals/specs/google-apps-mcp.md`
- Guía usuario: `docs/02_guides/drive-cerebro-setup.md` (`DOC-GUIDE-009`)
- Paridad de skills: `/skills` · `vitals/specs/skill-standard.md`
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.