eto-apere

Installation
SKILL.md

Ètò Àpẹrẹ

Own the implementation contract between confirmed visual decisions and reusable tokens/component specifications:

confirmed raw values → semantic purpose aliases → component properties/states

Do not seed a project with default colors, fonts, spacing, radii, shadows, component variants, dimensions, state treatments, animation timings, or framework mappings.

Workflow

  1. Read token architecture, then inspect the project's existing tokens, theme files, component conventions, selected UI library, and confirmed brand / amoye-ui-ux direction. Existing project values and approved brand roles are inputs; do not replace them with starter defaults.
  2. Define only required primitives for confirmed raw values. Map them to semantic roles such as background, foreground, primary, muted, destructive, focus, and product-specific roles.
  3. Add component tokens/specifications only when a component property, variant, or state needs a stable reusable contract beyond the semantic layer. Read component contract when that detail is material. Do not invent component anatomy, variants, states, sizes, timings, or accessibility behavior that the product/library has not established.
  4. Preserve aliases rather than flattening semantic/component references to primitive values. Theme switching should normally remap semantic aliases rather than rewrite components.
  5. Validate all token references, cycles, and CSS-name collisions before installing generated output. Prefer a current project-native token compiler when one already owns the representation; otherwise use the bundled narrow compiler.
  6. Install generated artifacts through the project's normal mutation/proof path. Framework integration belongs to the active project/version and its current documentation; Ètò Àpẹrẹ supplies the token/component contract, not a cached Tailwind/shadcn/framework recipe.
  7. Review changed consumers for inappropriate hardcoded values, missing required states, contrast, and broken aliases through project-native lint/typecheck/build/render proof. A raw literal is evidence to inspect, not automatically a violation.
Installs
20
First Seen
Aug 15, 2026
eto-apere — quantipixels/skills