canonical-catalog-expansion

Add or improve canonical data catalog collections, fields, aliases, relations, evidence tags, docs, and tests.

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

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.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/clawic/Clawix --skill canonical-catalog-expansion

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Run or change the macOS UX trace harness for action-to-visual-completion latency, scroll stability, fixture pressure, and baseline evidence.

Capture and compare Clawix UI performance budgets for critical flows before optimizing visible or runtime UI behavior.

Work from a registered surface or transverse route by inspecting nodes, neighbors, edges, contracts, owners, tests, and gaps before editing.

name	canonical-catalog-expansion
description	Add or improve canonical data catalog collections, fields, aliases, relations, evidence tags, docs, and tests.
keywords	["catalog","database","collections","schemas","fields","relations"]

Grow the canonical data catalog without degrading schema quality.

Treat ClawJS as canonical for catalog/RFC work. Read sibling ClawJS docs/canonical-data-catalog.md, docs/adr/0005-canonical-data-catalog.md, docs/governance/rfc-process.md, data-storage boundary, and naming guide. In Clawix, read only the local mirror/routing docs named by docs/decision-map.md; do not invent a parallel catalog.
Use claw collections list, claw collections <collection> schema, and claw db <collection> list|query when available.
Decide whether the entity is built-in canonical or belongs in a custom database.
For promotion to canonical type or canonical user-profile attribute, require the RFC process record, public review link, and maintainer sign-off before treating the shape as accepted canon.
Add purpose, evidence tags, sparse optional fields, semantic relation fields, aliases, and migration/debt notes.
Keep user-facing structured records in the main database unless a sidecar reason is technical and explicit.
Update docs, tests, generated catalog coverage, and CLI/schema discovery together.

A business category alone is not a reason for a separate database.
Separate sidecars for volume, churn, blobs, sync complexity, logs, caches, encrypted vaults, or reconstructable indexes.
Do not let Clawix define a parallel canonical schema.