Menu
Framework-agnostic component discipline — typed contracts, composition, environment safety, cleanup. Load for any UI component work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Context engineering — memory navigation, textual graph traversal, progressive disclosure, recovery. Load when assembling context for a task or when lost.
Implementation-side security discipline — headers, dependencies, secrets, authz. Load for hardening work (sec-ops domain).
Commit conventions, branching, anchors in messages, and the git safety rules. Load for any git operation beyond status/diff.
Anti-generic-AI design discipline — bans, tells, and the slop test. Load for ANY new UI surface or visual redesign. Inspired by Impeccable (Apache 2.0).
Motion & animation discipline — purpose, performance, reduced-motion. Load when work involves animation, transitions or scroll effects.
Microcopy discipline — buttons, errors, empty/loading/success states, alt text. Voice and tone come from the project's memory, not from this skill.
| name | component-patterns |
| description | Framework-agnostic component discipline — typed contracts, composition, environment safety, cleanup. Load for any UI component work. |
Stack-agnostic by design. Framework idioms (how to declare props, extract logic, guard environments) come from memory-long §stack and the codebase's existing patterns — this skill defines the discipline that applies to all of them.
any boundarieswindow, document, observers) only behind the framework's client-side guards — components must not break server/static renderingProject's type-check passes clean · server/static render produces no environment errors or hydration mismatches · interactive elements are focusable with semantic markup (a11y floor).