describe-canonical-locations
File locations for laws, style, phases, and docs. Load when locating or creating Ushabti state files.
npx skills add majiayu000/claude-skill-registry --skill describe-canonical-locations --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## Canonical Location 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.
- Canonical Location
What does the describe-canonical-locations skill do?
File locations for laws, style, phases, and docs. Load when locating or creating Ushabti state files.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill describe-canonical-locations --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.