Menú
Documentation workflow for design specs and progress tracking in the migrate project. Use when planning, implementing milestones, or recording project status updates.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Version synchronization policy for MigLib and mig CLI packages. Use when bumping versions, releasing, or modifying features in either package to keep both versions identical.
F# style rules for the migrate project. Use when editing or reviewing `.fs`/`.fsi` files to enforce single-argument call syntax, module-per-file declarations, and Fantomas formatting requirements.
Use when writing or refactoring F# functions whose body mixes abstraction levels, construction details, or implicit invariants that should be isolated behind named steps.
Use when an F# source file or module mixes stacked responsibility layers whose dependency direction should be made explicit through files, modules, and a stable facade.
Build, test, and install workflow for the migrate project. Use when validating changes, building release artifacts, or installing the `mig` tool so commands follow the canonical `build.fsx` flow.
Code generation conventions for `mig codegen` project files. Use when generating or reviewing `.fsproj` output and package references to ensure Central Package Management (CPM) compatibility.
| name | migrate-docs-workflow |
| description | Documentation workflow for design specs and progress tracking in the migrate project. Use when planning, implementing milestones, or recording project status updates. |
specs/.PROGRESS.md.PROGRESS.md when finishing major milestones.PROGRESS.md during active development when plan status changes.