skills.rest
wagnerra23
wagnerra23COMMUNITY
Explore all skills by this author →
GitHub

personas-resolve

Resolve UX personas for UI edits via charter, module mapping, and clarification.

Updated May 14, 2024
Search Tags:#ADR compliance#persona resolution#UI coding guardrails#design contextualization#charter workflow#React TSX pages#multi-tenant client context
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill personas-resolve
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: personas-resolve
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/personas-resolve
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill personas-resolve

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about personas-resolve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce persona context before writing React TSX pages?▼

To enforce persona context for React TSX pages, the system applies a three-level resolution fallback: reading the tela charter, checking module persona mappings, and finally asking for interactive clarification to ensure persona-aware UI coding.

Why does UI coding fail when no real-client persona is resolved?▼

UI coding fails because ADR 0105 compliance enforces a Tier A blocking rule that halts progression when a target persona cannot be tied to a real client, preventing mismatched UX and inconsistent design decisions.

What is the fallback sequence for persona resolution in UI workflows?▼

The persona resolution fallback sequence first reads tela charter persona targets, then falls back to module mapping in personas-por-modulo.yml, and finally prompts interactive clarification with charter persistence if the persona is still missing.

How do I load persona JTBD and friction data into my coding context?▼

You load persona JTBD and friction data by resolving the target UX persona, which automatically emits full persona YAMLs, JTBD, frictions, and 15D weighted dimensions from memory/clientes into the runtime coding context.

Can I use hypothetical personas for multi-tenant client UI design?▼

No, you cannot use hypothetical personas for multi-tenant client UI design. The safety rule against hypothetical personas blocks progression unless the persona is tied to a real client, reinforcing contextual design per ADR UI-0016.

Where should persona YAML files be stored for module screen generation?▼

Persona YAML files must be stored in the memory/clientes/<cliente>/personas/<slug>.yml directory structure to be successfully loaded and applied during module screen generation and visual refactoring workflows.

Related Skills

Explore More Software Engineering Skills→
wagnerra23wagnerra23

feedback-capture

Capture customer feedback into structured 7-field friction records with persona and charter links.

Community
Advanced
wagnerra23wagnerra23

design-deep-analysis

Analyze Inertia screens with persona-weighted scoring across 15 dimensions.

Community
Advanced
wagnerra23wagnerra23

memory-schema-preflight

Validate canonical YAML frontmatter and required Markdown sections in memory artifacts before CI.

Community
Intermediate
TrevorEdrisTrevorEdris
2

switch-persona

Switch AI personas by updating persona.yaml in .claude or .cursor folders.

Community
Basic