ux-flow-architect

Interactive cross-feature navigation architect for Nicolify. Audits all routes and sidebar entries, maps user journeys across studios, detects orphaned features and dead-end flows, proposes navigation improvements with ASCII diagrams, generates clickable multi-page HTML prototypes on localhost:8888, and outputs FLOW-SPEC.md plus per-screen UI-SPEC updates for implementation agents. Use when the user asks about navigation coherence, user flows, journey mapping, orphaned features, dead-end screens, sidebar reorganization, cross-studio navigation, or feature discoverability. Triggers: 'flujo de usuario', 'navegación', 'journey', 'user flow', 'sidebar', 'rutas huérfanas', 'orphaned routes', 'dead end', 'flow audit', 'navigation audit', 'ux-flow', 'flow architect', 'cómo llega el usuario', 'discoverability', 'no encuentro', 'dónde está', 'reorganizar navegación', 'cross-feature flow', 'audita la navegación', 'mapa de rutas', 'flujos de la app'.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

73%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.

The body is a well-sequenced, highly actionable multi-phase workflow with strong validation gates and sensible progressive disclosure to bundled reference files. Its main weakness is conciseness: dated deprecation/paradigm commentary and overall length add tokens that do not aid execution.

Suggestions

Consolidate the deprecation banner and scattered dated paradigm notes ('2026-05-06', 'post 2026-05 redesign') into a single clearly marked 'Deprecated / Legacy' section so time-sensitive context stops cluttering the live workflow.

Verify or remove cross-skill reference paths (ux-disruptivo/references/ascii-mockup-guide.md, ui-spec-template.md, frontend-expert references) since they are absent from this skill's bundle and may resolve to missing files.

Tighten the Edge Cases and Common Mistakes tables into a single condensed table to reduce length without losing the operational warnings.

Dimension	Reasoning	Score
Conciseness	Mostly operational and avoids explaining concepts Claude already knows, but it is long (530+ lines) and carries time-sensitive dated debris — a deprecation banner plus inline paradigm notes ('post 2026-05 redesign', 'paradigm migrated 2026-05-06') — that adds noise without earning its tokens.	3 / 5
Actionability	Provides concrete, mostly executable guidance — exact Glob/Grep patterns, specific Read targets, copy-paste bash (mkdir, pkill, python3 http.server) and defined output schemas — with only minor gaps where exact content is deferred to reference templates.	4 / 5
Workflow Clarity	A clearly sequenced 6-phase process with an explicit 'Gate:' user-confirmation checkpoint after every phase, mode detection up front, and feedback loops for prototype iteration and route verification (reinforced by the Common Mistakes table).	5 / 5
Progressive Disclosure	Good one-level-deep structure: the body points to four real reference files (flow-spec-template, html-prototype-system, navigation-patterns, journey-template) via clear 'Load ... with Read' signals, but it also references two files from other skills (ascii-mockup-guide.md, ui-spec-template.md from ux-disruptivo) that are not in this skill's bundle, leaving minor broken-reference risk.	4 / 5
	Total	16 / 20 Passed

Description

100%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.

The description is exemplary: third-person voice, specific capabilities, an explicit 'Use when' clause, and a rich bilingual trigger list. It comprehensively answers what the skill does and when to invoke it with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Audits all routes and sidebar entries, maps user journeys across studios, detects orphaned features and dead-end flows, proposes navigation improvements with ASCII diagrams, generates clickable multi-page HTML prototypes on localhost:8888, and outputs FLOW-SPEC.md plus per-screen UI-SPEC updates' — with comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (the audit/mapping/prototyping/spec-output actions) and 'when' via a clear 'Use when...' clause plus a concrete 'Triggers:' list of phrases.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural terms across both English and Spanish, including synonyms and colloquial user phrases ('no encuentro', 'dónde está', 'cómo llega el usuario', 'journey', 'user flow', 'sidebar').	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — cross-feature navigation architecture for Nicolify with distinct outputs (FLOW-SPEC.md, HTML prototypes on localhost:8888) — and its triggers are specific enough to avoid firing for screen-design skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (533 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: alpacapurpura/luana-method
Path: claude/skills/ux-flow-architect/SKILL.md
Commit: caa08df

Reviewed: ~22 hours ago

Table of Contents

Discovery Implementation Validation

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.