Menú
File locations for laws, style, phases, and docs. Load when locating or creating Ushabti state files.
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
| name | describe-canonical-locations |
| description | File locations for laws, style, phases, and docs. Load when locating or creating Ushabti state files. |
| user-invocable | false |
All Ushabti state lives under .ushabti/. This is the single source of truth.
.ushabti/
├── laws.md # Project invariants (absolute constraints)
├── style.md # Conventions (how we build)
└── docs/ # Docs directory
│ └── *.md # Documentation on project systems
│ └── index.md # Index of all project documentation
└── phases/ # Phase directories
└── NNNN-slug/ # Zero-padded sequential
No mirrors. No duplicates. No top-level copies.
Bootstrap phase context for Builder. Provides current phase, next step, and full phase file contents.
Bootstrap phase context for Overseer. Provides phase under review with full file contents and card metadata.
Approve a phase — sets status to complete, marks all steps reviewed, updates linked card. Use when declaring a phase green.
Create a phase directory with all required files in one call. Use instead of separate mkdir + Write calls when creating a new phase.
Kick a phase back to building — sets status and adds new step entries to progress.yaml. Use when requesting fixes from Builder.
Mark a step as implemented in progress.yaml with notes and touched files. Use after completing each step instead of manual Edit calls.