deploy
Skill4 starsChanged 2 days agoMITView on GitHub
[Trabajo] Desplegar la app del proyecto — primera ejecución autocompleta la config desde el repo; luego sigue vitals/config/deploy.yaml. Use when the user invokes /deploy or wants to publish to production/staging.
159 other projects use a version of this.
Adopted by
Most recently taken up by
- maxwell2732/claudecode-research-harness-workflowtheir own version, first seen Nov 15, 2026
- patrickjaja/claude-desktop-extratheir own version, first seen Nov 15, 2026
- nazmirket/skillstheir own version, first seen Nov 15, 2026
- np25071984/kepttheir own version, first seen Nov 15, 2026
- davision0102/fabriktheir own version, first seen Nov 15, 2026
- onblueroses/stratatheir own version, first seen Nov 12, 2026
Used with
Projects with it also use pm-discovery, qa-phase and 10 more.
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.
ww-w-aiSkillpm-discovery
PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.
Also in 3 projects that use this
ww-w-aiSkillqa-phase
Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.
Also in 3 projects that use this
- +10 more from ww-w-ai
Other versions159 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 159
- ok-oldking/ok-wuthering-waves★ 8.6ksame name
- memovai/mimiclaw★ 5.8ksame name
- KingKongRobotics/jumper★ 3.1ksame name
- jhd3197/ServerKit★ 1.8ksame name
- pedrohcgs/claude-code-my-workflow★ 1.7ksame name
- mattmireles/gemma-tuner-multimodal★ 1.5ksame name
- microsoft/power-platform-skills★ 1.2ksame name
- jazzyalex/agent-sessions★ 948same name
- awslabs/agent-plugins★ 943same name
- patrickjaja/claude-desktop-extra★ 761same name
149 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 repository169 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/18-drive-contexto.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
- development-plannerSkill
- devopsSkill
- docSkill
- dt-actualizarSkill
- dt-ayudaSkill
- dt-bootstrapSkill
- dt-calendarSkill
- dt-configSkill
- dt-driveSkill
- dt-gmailSkill
- dt-oficialSkill
- dt-ordenarSkill
- dt-revisar-instalacionSkill
- 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
- The first 60 shown.
The file
Files
deploy
Skill genérico: la primera vez descubre cómo se despliega este proyecto y materializa la config; las siguientes ejecuciones la siguen.
No confundir con: subagente devops (diseño de pipelines) · /github-save-small (release del template DT).
Pre-requisitos
- Sesión válida —
vitals/ops/session.yamlconoperator.id; si falta →/yo. - Working tree razonablemente limpio en paths de deploy (build artifacts no commiteados).
- Secretos nunca en el repo — Firebase Secrets, Cloud Run env, etc. (regla
90-seguridad-secrets).
Modo de operación
Leer vitals/config/deploy.yaml (plantilla: vitals/config/deploy.yaml.example).
| Estado | Acción |
Archivo ausente o initialized: false | Bootstrap (sección abajo) — no ejecutar deploy real hasta confirmación |
initialized: true | Ejecutar según deploy.yaml + references/project-deploy.md si existe |
Bootstrap — primera ejecución de /deploy
Objetivo: que la IA complete la skill con lo que este repo ya tiene (o debería tener).
- Discover (solo lectura):
- Docs:
docs/DEPLOY.md,docs/**/deploy*.md, README sección deploy - Infra:
firebase.json,.firebaserc,Dockerfile,cloudbuild.yaml,.github/workflows/*deploy* - Scripts:
package.json(scripts.deploy*,scripts.build), monorepo enapps/*,frontend/,backend/ - Stack default DT:
vitals/data/engineering/web-stack.yaml· regla08-stack-web-default - Referencia Firebase: skill
devops→devops/references/firebase-deploy.md
- Docs:
- Inferir plataforma principal (
firebase|cloud-run|vercel|docker|custom) y entornos (production,staging, …). - Generar (pedir confirmación antes de escribir):
vitals/config/deploy.yaml— desde example,initialized: truetras OK del operador.cursor/skills/deploy/references/project-deploy.md— usar plantillareferences/project-deploy.template.md
- Contenido mínimo de
project-deploy.md: prerequisitos CLI, orden de comandos,--only/ targets, secrets, rollback en una línea, checklist post-deploy. - Buenas prácticas (incluir en el doc generado):
- Build local o CI antes de deploy; no
--forceen prod sin acuerdo - Predeploy hooks en
firebase.jsonreutilizados, no scripts duplicados - Un workflow CI por entorno si ya existe — extender, no clonar
- Verificar health/smoke tras deploy (URL, función ping, etc.)
- Rollback: tag/commit anterior + redeploy (ver
devops/references/rollback-runbook.md)
- Build local o CI antes de deploy; no
- Tras confirmación del operador → escribir archivos → incluir en el próximo commit (
/guardar)vitals/config/deploy.yamlyreferences/project-deploy.mdantes de deploy a producción → ofrecer ejecutar deploy del entorno indicado.
Regla: deploy reproducible = config versionada en Git; no desplegar a prod con bootstrap solo local.
Gate duro: cambios en remotes, borrado de recursos, firebase deploy a prod sin confirmación explícita.
Ejecutar deploy (config inicializada)
- Releer
vitals/config/deploy.yamlyreferences/project-deploy.md. - Confirmar entorno (
productionpor defecto; preguntar si hay varios). - Ejecutar en orden:
pre_deploy(lint, test, build)- comando(s) del entorno
post_deploy(smoke, invalidación CDN, etc.)
- Capturar salida; si falla → no declarar éxito; sugerir rollback según runbook.
- Versión: si el deploy incluye bump de versión de app, coordinar con
/guardar(versión del proyecto, no del DT).
Entrega
- Entorno desplegado + comando(s) ejecutados
- URL o recurso resultante
- Si fue bootstrap: paths escritos y qué falta (secrets, CI, DNS)
- Puntos ciegos: drift entre doc y scripts, secrets faltantes, deploy manual no reproducible
Referencias
- Checklist bootstrap:
references/bootstrap-checklist.md - Plantilla doc proyecto:
references/project-deploy.template.md - Example config:
vitals/config/deploy.yaml.example
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.

