CtrlK
BlogDocsLog inGet started
Tessl Logo

po-ux

Product Owner + UX/UI Designer fusión v4 (post pm-redesign 2026-05 Punto 4). Toma 1 UI standard story (CRUD/list/detail/form/dashboard) state=refining → produce 01-spec.md UNIFICADO con Gherkin AI-resistant + wireframes inline (ASCII / HTML mockup / Figma link) + estados visuales + microcopy Spanish neutro + Playwright graders → transition state=refining→refined al ratificar. NO se usa para agentic-stories (use /ux-agentico) ni service-stories (use /po). Loop iterativo Chris hasta ratificación. Activa cuando user dice: '/po-ux', 'definamos esta historia UI', 'spec + diseño', 'pantalla CRUD', 'dashboard', 'form nuevo', 'list view', 'detail page', 'wireframe', 'mockup'.

69

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An action-oriented, well-sequenced skill body with strong executable examples and a hard validation gate plus feedback loops. Its main weaknesses are version-stamp/changelog noise that hurts conciseness and an inlined spec-template scaffold that would score higher on progressive disclosure if lifted into a separate reference file.

Suggestions

Consolidate the repeated "★ v4.1" / R26 / 2026-05 date stamps into a single changelog note and stop restating the sub-categoría list in Step 3, Step 5, and Anti-patterns — reference one canonical table instead.

Extract the full 01-spec.md section scaffold (§ Context through § Brand voice) into a separate template reference file and have the body point to it, leaving the SKILL.md as a tighter overview.

Remove decorative emphasis ("HARD GATE", "★ HARD", repeated ❌ duplication of the same rules) where the checklist already enforces the gate.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence (no explanations of Gherkin, Shadcn, or Tailwind), but it is padded with repeated version stamps ("★ v4.1 cement 2026-05-19", "R26 2026-05-05", "post reorg 2026-05-15") and restates the sub-categoría list across Step 3, Step 5, and Anti-patterns. Not a 4 because the redundant emphasis and changelog noise are clearly trimmable; not a 2 because the core guidance is tight and not concept-level padding.

3 / 5

Actionability

Fully executable guidance: concrete bash ("WS=$(git rev-parse --show-toplevel)", "python3 -m http.server 8888"), copy-paste YAML frontmatter, grader YAML snippets, ASCII wireframe templates, and filled microcopy/component tables. Specific examples cover the common CRUD/list/detail/form/dashboard cases.

5 / 5

Workflow Clarity

Clear Step 1→5 sequence with an explicit validation gate (Step 5 checkbox checklist, "Si gate FAIL → STOP, NO transition refining→refined") and feedback loops ("Iterá con Chris hasta cobertura completa", "Loop hasta ratified_by_chris: true", "Anti-pattern: rendirte tras 1 iter"). Checkpoints and error recovery are explicit throughout.

5 / 5

Progressive Disclosure

A "Referencias" section lists one-level-deep external files with clear paths, but the body is far over 50 lines and inlines a large spec-template scaffold (Context/Gherkin/Wireframes/Estados/Componentes/Data flow/Microcopy/Responsive/a11y sections) that arguably belongs in a separate template reference rather than the SKILL.md overview. Not a 4 because content that should be split out is inline; not a 2 because navigation and sections are reasonably organized.

3 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, highly specific description with explicit trigger terms, clear what/when answers, and crisp boundaries against sibling skills. The only blemish is the version-metadata preamble ("fusión v4 (post pm-redesign 2026-05 Punto 4)") which adds noise without capability information.

Suggestions

Drop the changelog preamble "fusión v4 (post pm-redesign 2026-05 Punto 4)" from the description — version history belongs in the body, not the frontmatter description.

Trim "Loop iterativo Chris hasta ratificación" redundancy since the ratification trigger is already implied by "transition state=refining→refined al ratificar".

DimensionReasoningScore

Specificity

Lists several specific concrete actions ("produce 01-spec.md UNIFICADO con Gherkin AI-resistant + wireframes inline + estados visuales + microcopy Spanish neutro + Playwright graders → transition state=refining→refined"), with only minor gaps; the leading "fusión v4 (post pm-redesign 2026-05 Punto 4)" version metadata is mild noise rather than a capability. Not a 5 because the version/changelog preamble dilutes the otherwise comprehensive action list.

4 / 5

Completeness

Clearly and explicitly answers both what ("Toma 1 UI standard story ... → produce 01-spec.md UNIFICADO con Gherkin AI-resistant + wireframes ... + Playwright graders → transition state=refining→refined") and when ("Activa cuando user dice: ..."), plus explicit negative scope ("NO se usa para agentic-stories ... ni service-stories").

5 / 5

Trigger Term Quality

Comprehensive coverage of natural trigger terms via "Activa cuando user dice: '/po-ux', 'definamos esta historia UI', 'spec + diseño', 'pantalla CRUD', 'dashboard', 'form nuevo', 'list view', 'detail page', 'wireframe', 'mockup'" — these are exactly the phrases a user would say, including the slash invocation and synonyms.

5 / 5

Distinctiveness Conflict Risk

Clear niche (UI standard CRUD/list/detail/form/dashboard stories) with distinct slash-trigger /po-ux and explicit routing away from sibling skills ("use /ux-agentico", "use /po"), giving minimal conflict risk. Voice is third person ("Toma", "Activa"), incurring no penalty.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
alpacapurpura/luana-method
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.