Understanding reports (Spec 4.5)

Buildability score

• 90–100 — Simple, well-defined, ready to build
• 70–89 — Moderate complexity, minor issues
• 50–69 — Significant complexity, needs review
• 0–49 — High risk, major simplification needed

System Adherence (Spec 4.3): 90–100 excellent adherence, 70–89 good, 50–69 moderate violations (needs cleanup), 0–49 poor (major refactoring). Violations list: location (screen, component, layer), type and severity, suggested mapping to primitives, "Refactor to: Card + List + Modal"–style recommendations.

Report output format (Spec 4.2): per-flow Buildability score with explanation, per-screen Complexity score with breakdown, and prioritized issue list with severity ratings.

Rule thresholds (spec 4.2)

Over-complexity flags: flow depth > 7 steps, branching > 4 decision points, modal/overlay stacking > 2 levels, heavy custom animations. Design system checks: off-token colors, typography outside type scale, spacing outside scale, components not mapped to primitives (Button, Input, Modal, etc.). Customize thresholds in Settings.

Design Quality Score

A composite metric (Addendum C) combining flow health (buildability), system adherence, and accessibility. In v3+ it can include responsiveness and security hygiene. Available at project and org levels. Used for governance and CI/CD gating.

Issue types

Blue Painter flags: missing states (loading, error, empty, permission, flow-specific), complexity (depth, branching, component diversity), system alignment (off-token colors, typography/spacing violations, snowflake components, component mapping—with location, suggested mapping to primitives, and "Refactor to: Card + List + Modal"-style recommendations), and interaction realism (platform mismatches, high-effort patterns).

Priority & recommendations

Each issue follows Spec 4.4: Problem summary (description), Impact (derived from priority—blocks development, technical risk, or maintainability), Suggested alternative (recommendation), Patch plan (bullet list a dev or UXer can implement), and Priority rating (must-fix, should-fix, nice-to-have). Recommendations combine narrative explanation (designer-friendly) and technical rationale (dev-friendly).

Persona views

Use the persona switcher in the Issues panel to filter and prioritize issues by role: Designer (design system adherence, UX improvements, simplified alternatives), Developer (implementation complexity, missing states, technical risks), and PM (timeline impact, scope, priority decisions).

Report sections

Navigate with ← → between steps; 1–4 jump to Overview, Design, Flow & issues, Insights. See Keyboard shortcuts.

• Overview — Buildability and System Adherence scores, total issues by severity (critical, high, medium, low), estimated implementation time, and flow complexity summary
• Design — Screen thumbnails with issue overlays (visual reference per screen)
• Flow graph — Visual flow and navigation structure
• Issues — Sortable by severity, priority, type, flow, screen, date, or Resolved (newest); filterable by severity, flow, type (complexity, missing state, system alignment — Spec 4.5), screen, status, and priority. Each issue shows affected screens/flows (Spec 4.5). Sort by Resolved (newest) to see recently fixed issues (Spec 5.7).
• Flow alternatives — Three variants: Minimal (fewest steps, speed), Guided (clarity, low cognitive load), Edge-case safe (all states covered). Each shows buildability score, dev time. Export to Figma creates a new page with wireframe screens, annotations explaining changes, and links back to Blue Painter.
• Blueprint comparison — Compare your flow to battle-tested patterns
• Personalization — Safe-to-personalize vs do-not-personalize guidance based on flow analysis. See Personalization.
• Export — Download as PDF or share link. See Export & sharing for Markdown, Figma comments, and GitHub.