skills/latex-version-control/SKILL.md
Add and maintain version control tables in LaTeX corporate documents. Trigger: When creating new LaTeX documents, updating document versions, or reviewing document history.
npx skillsauth add 333-333-333/agents latex-version-controlInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill works alongside:
| Skill | Purpose |
|-------|---------|
| latex-corporate-docs | Corporate template and document structure |
Every LaTeX document MUST include a version control table immediately after \maketitle and \thispagestyle{fancy} (if present), BEFORE any content (confidentiality notices, resumen ejecutivo, etc.).
The \versiontable command is defined in the document preamble. It uses the corporate color palette for consistent styling.
Source:
assets/version_macros.tex
Place the macro definition in the preamble (after custom macros section), then call it right after \maketitle:
Example:
assets/version_usage.tex
Before adding or updating a version entry, the agent MUST ask the user who made the changes. Never assume "Equipo Bastet" or any generic author. The version table tracks individual accountability, so the author field must reflect the real person.
Example prompt:
"¿Quién es el autor de estos cambios para la tabla de versiones?"
| Rule | Detail |
|------|--------|
| Placement | Immediately after \maketitle (and \thispagestyle{fancy} if present), before any other content |
| Ordering | Newest version LAST (chronological, top-to-bottom) |
| Version format | MAJOR.MINOR — increment MAJOR for structural changes, MINOR for content updates |
| Date format | Mes Año (e.g., Enero 2026) — matches \date{} convention |
| Author | The specific person who made the changes — ALWAYS ask the user, never assume |
| Changes | Brief description of what changed (1 sentence) |
| Initial version | Always 1.0 with description Versión inicial del documento |
| Change Type | Version Bump | Example | |-------------|-------------|---------| | New document | 1.0 | Initial creation | | Content updates, corrections | +0.1 | Fix typos, update figures | | New sections added | +0.1 | Add appendix, new analysis | | Major restructuring | +1.0 | Rewrite, change scope | | Data refresh (economics) | +0.1 | Update CLP values, exchange rates |
\versiontable and \versionrow macros defined in preamble\maketitletesting
Review Flutter components and screens for UX/UI compliance. Trigger: When user invokes /ux-review command or requests UX audit.
development
TypeScript strict patterns and best practices. Trigger: When implementing or refactoring TypeScript in .ts/.tsx (types, interfaces, generics, const maps, type guards, removing any, tightening unknown).
testing
Testing philosophy and strategy for every feature: test pyramid, mandatory levels per change type, completion checklist, and skill delegation. Trigger: When planning tests for a feature, reviewing test coverage, defining acceptance criteria, or asking what tests a change needs.
development
Terraform security practices: sensitive variables, secret management, state protection, .gitignore patterns, and CI/CD credential handling. Trigger: When handling secrets in Terraform, configuring state backends, reviewing .gitignore for Terraform, or setting up CI/CD pipelines for infrastructure.