CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

91%

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

85%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 exceptionally actionable, well-sequenced multi-phase workflow with explicit gates and real on-demand reference files. The main weakness is redundancy — session-folder rules, mode-scoping notes, and legacy/current path mappings are each repeated across sections.

Suggestions

State the session-folder path rule once (in the 'Session Folder' section) and have later phases reference it instead of repeating 'never write to /tmp, docs/flow-specs/, docs/ui-specs/' in Phase 5 and Phase 6.

Remove the mode-scoping rows from the Edge Cases table that duplicate the Phase 5 Step 3 scope-control table (e.g., studio-scoped filtering).

Consolidate the PM-handoff legacy path references (docs/pm-nico/pis/... vs docs/product/stories/...) into the deprecation banner at the top so the workflow section carries only the current path.

DimensionReasoningScore

Conciseness

Largely tight and table-driven, but the session-folder rule ('never write to /tmp, docs/flow-specs/, docs/ui-specs/') is stated three times, mode-scoping appears in both the Edge Cases table and Phase 5 Step 3, and the PM-handoff section carries dual legacy/current path references that could be consolidated.

3 / 5

Actionability

Fully executable guidance throughout: exact Glob/Grep patterns with real file paths ('frontend/src/components/shared/layout/app-sidebar.tsx'), runnable bash (mkdir, python3 -m http.server 8888 -d ...), and concrete per-phase output formats and tables.

5 / 5

Workflow Clarity

Six phases are explicitly sequenced with a mode-detection table mapping user signals to phases, and every phase ends in an explicit 'Gate' user-confirmation checkpoint with iteration loops in Phases 4–5 — clear validation and feedback structure.

5 / 5

Progressive Disclosure

SKILL.md is the orchestrating overview; the four templates (flow-spec, html-prototype-system, journey, navigation-patterns) all exist in ./references/ and are loaded on demand with clearly signaled 'Load X with Read' instructions, one level deep.

5 / 5

Total

18

/

20

Passed

Description

96%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 description: third-person voice, concrete end-to-end capability list, explicit use-when guidance, and bilingual natural-language triggers. Only minor overlap risk from a handful of generic trigger terms shared with closely related UX skills.

DimensionReasoningScore

Specificity

Lists six concrete capabilities — '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', 'outputs FLOW-SPEC.md plus per-screen UI-SPEC updates' — with comprehensive coverage and no generic filler.

5 / 5

Completeness

Explicitly answers both 'what' (full audit→journey mapping→gap detection→proposals→prototypes→spec outputs pipeline) and 'when' via a dedicated 'Use when the user asks about...' clause plus a trigger list with concrete phrases.

5 / 5

Trigger Term Quality

The 'Triggers:' list spans natural user phrasings in both Spanish ('no encuentro', 'dónde está', 'rutas huérfanas', 'cómo llega el usuario') and English ('flow audit', 'dead end', 'orphaned routes', 'user flow'), covering synonyms and colloquial variants a real user would say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Nicolify cross-feature navigation architecture with FLOW-SPEC/UI-SPEC outputs) and mostly distinct triggers, but a few generic terms ('sidebar', 'navegación', 'discoverability') overlap with the sibling UX-design skills (ux-disruptivo, nicolify-ux-designer) that this skill's own body references.

4 / 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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

Revision

caa08df

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill