constituicao-ui-aware

What problem does it solve?

This Skill prevents UI code from drifting away from the project’s canonical design framework by forcing developers to re-check the correct UI hierarchy, the applicable screen pattern, and the pre-merge anti-pattern rules before editing or writing UI files.

Core Features & Use Cases

• Always-on UI guardrails: Activates when editing or creating Inertia Pages, shared TSX components, or cockpit/inertia CSS to reduce accidental divergence from the design system.
• Constitution UI v2 4-layer hierarchy enforcement: Reminds the agent to follow Fundações→Shell→PT→Módulo and resolves conflicts by stating that lower layers win.
• Pattern selection by file intent: Guides correct usage of PT-01 for Index pages and the drawer 760 approach for cadastral Edit/Create screens when PT-02..PT-05 are not yet documented.
• Anti-padrões PRE-MERGE-UI checklist: Highlights key violations like hardcoded colors, reinvented components, missing multi-tenant storage prefix, wrong icon set, and copy language issues.

Quick Start

Use the skill when you are about to edit a file like resources/js/Pages/<Modulo>/Index.tsx or resources/js/Components/shared/**/*.tsx and you need to align the change with the Constitution UI v2, the correct PT template, and the PRE-MERGE-UI anti-pattern rules.