Skip to content
cccskills
FreePublished on GitHub

canonical-catalog-expansion

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

canonical-catalog-expansion

Grow the canonical data catalog without degrading schema quality.

Procedure

  1. 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.
  2. Use claw collections list, claw collections <collection> schema, and claw db <collection> list|query when available.
  3. Decide whether the entity is built-in canonical or belongs in a custom database.
  4. 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.
  5. Add purpose, evidence tags, sparse optional fields, semantic relation fields, aliases, and migration/debt notes.
  6. Keep user-facing structured records in the main database unless a sidecar reason is technical and explicit.
  7. Update docs, tests, generated catalog coverage, and CLI/schema discovery together.

Constraints

  • 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Govern Clawix accessibility changes across screen reader behavior, keyboard navigation, focus order, contrast, reduced motion, text scaling, timed interactions, and agent-generated UI.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Review or update stable, canonical, any-human, PMF, and adoption claims using adoption/canonicity governance packets.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Turn a new or changed ADR into implemented behavior, routing docs, tests, and guardrails rather than leaving it as standalone prose.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Repair confirmed architecture drift in small batches while preserving public canon and avoiding broad opportunistic refactors.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Given an existing Style, generate a human-readable brand guidelines document covering colors, typography, voice, do/don't, imagery rules, and usage examples. Use when the user asks for a brand book, brand guide, or design system document.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Apply the 90/10 visual-to-text rule when composing a piece on a canvas (poster, card, social post). Use when the deliverable lives on a single fixed surface where each element competes for attention.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

See all skills by clawic

Report a problem with this skill