detect-personas

Identify user personas by analyzing frontend UI routes, layouts, roles, tiers, and feature flags to generate a matrix for Breeze graph tools.

2|2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/accionlabs/breezeai-claude-plugin --skill detect-personas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-personas
Source: https://github.com/accionlabs/breezeai-claude-plugin/tree/main/skills/detect-personas
Command: npx skills add https://github.com/accionlabs/breezeai-claude-plugin --skill detect-personas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detecting personas from a frontend UI repository is error-prone and time-consuming; this skill automates persona discovery by analyzing routes, layouts, subscription tiers, roles, and access controls to produce a Breeze-ready matrix.

Core Features & Use Cases

  • Route & Layout Analysis: Identifies product variants through route definitions and layout components across regions and platforms.
  • Role & Permission Mapping: Detects role definitions and checks to reveal who can access and perform actions in features.
  • Tier & Feature Flag Correlation: Links subscription tiers and feature flags to determine different user experiences.
  • Persona Matrix Output: Generates a structured set of personas suitable for ingestion by Breeze graph tools.

Quick Start

Run the persona detector in your frontend repo to generate a Breeze-ready persona matrix from your codebase.

Frequently Asked Questions about detect-personas

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

FAQPage Schema
How do I detect user personas from frontend routes and layout components?

Detect user personas by scanning a frontend UI repository to map route definitions, layout components, role checks, and feature flags into a structured persona matrix ready for graph integration.

What is persona discovery from UI code and when do I need it?

Persona discovery from UI code automates identifying user types by correlating subscription tiers, roles, and access controls. Use it when manual analysis of frontend permissions and route variants becomes error-prone and time-consuming.

Can I generate a persona matrix from feature flags and subscription tier configurations?

Yes, you can generate a persona matrix by correlating subscription tiers and feature flags with role definitions and access controls, linking them to determine distinct user experiences across regions and plans.

Does persona detection work with frontend repositories that use region and plan-based access controls?

Yes, persona detection works with frontend repositories containing route definitions, layout components, role checks, and feature flags across regions and plans, validating frontend markers to map dimensional signals.

What's the best way to map role permissions and access controls to distinct user personas?

The best way to map role permissions to personas is automating detection of role definitions and checks in frontend code, correlating them with routes, tiers, and feature flags to reveal who can access and perform actions.

Why does persona detection require specific frontend markers like route definitions and layout components?

Persona detection requires frontend markers like route definitions and layout components because it validates these markers, parses configuration, and correlates dimensional signals to generate distinct, actionable personas.