personas-resolve

What problem does it solve?

This skill prevents visual edits and new screens from being implemented without the correct customer persona context, avoiding mismatched UX, wrong frictions, and inconsistent design decisions.

Core Features & Use Cases

• Tier A blocker for visual work in Pages: automatically resolves persona targets before any Edit/Write/MultiEdit in resources/js/Pages/**/*.tsx or when creating a new screen file.
• 3-level persona resolution with guardrails: (1) reads <Tela>.charter.md persona targets, (2) falls back to module mapping in memory/requisitos/_DesignSystem/personas-por-modulo.yml, and (3) if still missing, asks Wagner interactively and then saves the resolved persona back into the charter.
• Safety rule against hypothetical personas: enforces ADR 0105 by blocking progression when persona cannot be tied to a real client, and reinforces contextual design per ADR UI-0016.
• Operational output for coding decisions: ensures the runtime context includes full persona YAMLs, JTBD, frictions, and weighted dimensions (15D) to guide implementation choices.

Quick Start

Activate personas-resolve by asking the AI to create or edit a screen file under resources/js/Pages/ so it will load the correct persona from the charter or mapping and confirm before coding proceeds.