ワンクリックで
colegios-template-groups
Runbook for multi-template groups (max 4) in colegios: DB models, API endpoints, UI flow, and batch processing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Runbook for multi-template groups (max 4) in colegios: DB models, API endpoints, UI flow, and batch processing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Database evolution runbook for the colegios project. Use when changing Prisma models, adding fields, introducing new tables, or adjusting relationships to ensure additive migrations, data preservation, and a persistent change log from local development.
Runbook for Colegio MVP lessons learned. Use when setting up local Docker Compose, fixing Prisma/openssl in containers, generating migrations/seed data, or deploying on VPS/Coolify with Traefik labels and network configuration.
Envio de PDFs por registro del Excel hacia OmniSwitch/Firmalo con el flujo de 4 pasos (crear solicitud, cargar documento, registrar firmante, disparar envio). Usar cuando se necesite integrar el pipeline de firma en el proyecto colegios, especialmente al procesar lotes y generar un envio por cada request.
Runbook for template ingestion (DOCX/HTML), Excel header generation, and file linking in colegios.
| name | colegios-template-groups |
| description | Runbook for multi-template groups (max 4) in colegios: DB models, API endpoints, UI flow, and batch processing. |
Standardize how groups of up to 4 templates are created, edited, and processed as a single Excel batch in the colegio admin UI.
Request (one per template).RequestGroup (legacy flow stays intact).TemplateGroup(organizationId, name, status, items[])TemplateGroupItem(groupId, templateId, order, requiredSigners?)BatchGroup(organizationId, groupId, status, totalCount, mapping, docxZipPath, pdfZipPath)RequestGroup(batchGroupId, rowIndex, status)Request.requestGroupId (nullable)GET /v1/template-groups?organizationId=...POST /v1/template-groups
organizationId, role=ADMIN, name, items[{templateId, order}]PATCH /v1/template-groups/:id
role=ADMIN, items (replace all), optional nameDELETE /v1/template-groups/:id (soft delete by status)POST /v1/batch-groups/start
organizationId, groupId, columns, mapping, rowsPOST /v1/batch-groups/:id/processGET /v1/batch-groups?status=PENDINGGET /v1/batch-groups/:id/download?type=pdf|docxweb/admin/upload.htmlPlantilla unica vs Grupo de plantillasActualizar grupo seleccionado/v1/batch-groups/start, else legacy /v1/batches/startpersona1_*, build signatory from persona1_* columns.persona2_*, build signatory from persona2_* columns./v1/batches?status=PENDING -> /v1/batches/:id/process/v1/batch-groups?status=PENDING -> /v1/batch-groups/:id/processorganizationId (no cross-org mixing).