naming-surface-audit

Audit and improve stable names, aliases, vocabulary, field casing, routes, ports, packages, and agent-search discoverability.

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 naming-surface-audit

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.

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

name	naming-surface-audit
description	Audit and improve stable names, aliases, vocabulary, field casing, routes, ports, packages, and agent-search discoverability.
keywords	["naming","aliases","vocabulary","casing","routes","packages","search"]

Improve naming quality across public and stable surfaces.

Read the naming guide, naming ADR, and decision-map rows for the affected surface.
Inventory names across code, docs, tests, CLI help, schemas, events, tables, package manifests, ports, env vars, and generated registries.
Check casing rules: JSON/API/YAML/framework fields use camelCase; CLI flags use kebab-case; SQL/collections use snake_case; events use domain.action.
Identify stale synonyms, ambiguous abbreviations, legacy names, or names that agents cannot search naturally.
Prefer explicit aliases and migration notes over silent renames when the surface is public.
Add or update guards when a naming rule should stay frozen.

Do not rename a public surface without a migration or explicit pre-public removal decision.
Do not introduce project-private brands, bundle ids, local paths, or maintainer names.
Names must be human-meaningful and agent-discoverable.