UI UX Pro Max

Quick Summary

Goal: Provide searchable UI/UX design intelligence -- 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks.

Workflow:

1. Analyze — Extract product type, style keywords, industry, and stack from user request
2. Search — Query search.py across domains: product, style, typography, color, landing, chart, UX
3. Stack Guidelines — Get stack-specific best practices (default: html-tailwind)
4. Implement — Synthesize search results into cohesive design and code

Key Rules:

• No emojis as UI icons (use SVG: Heroicons, Lucide, Simple Icons)
• All clickable elements need cursor-pointer and hover feedback
• Light mode text must have 4.5:1 minimum contrast ratio
• Every async surface MUST handle all its states — show a loading indicator while in-flight, a user-visible error (with retry) on failure, and a meaningful empty state when there's no data. Never a frozen blank, a silent failure, or a blank list.
• Responsive by default — layouts MUST stay usable on small devices. Preferred: reflow (rows flex-wrap or row → column, grids collapse to one column). Acceptable fallback when a layout genuinely can't reflow (tables, canvases, wide grids): fixed min-width/min-height + overflow: auto scroll — scrolling is OK. Hard minimum: nothing broken — no clipped, cut-off, or unreachable content. If small-screen support needs a refactor too big for the task, confirm scope with the user first.
• Test both light/dark modes, all UI states (loading/error/empty), and responsive breakpoints (320/768/1024/1440) before delivery

Pre-read (project design system): When the project has a design system, load designSystem.canonicalDoc + tokenFiles from docs/project-config.json and prefer project tokens/components over the generic style intelligence database.

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

UI/UX Pro Max - Design Intelligence

Searchable database of UI styles, color palettes, font pairings, chart types, product recommendations, UX guidelines, and stack-specific best practices.

Prerequisites

Check if Python is installed:

python3 --version || python --version

If Python is not installed, install it based on user's OS:

macOS:

brew install python3

Ubuntu/Debian:

sudo apt update && sudo apt install python3

Windows:

winget install Python.Python.3.12

How to Use This Skill

When user requests UI/UX work (design, build, create, implement, review, fix, improve), follow this workflow:

Step 1: Analyze User Requirements

Extract key information from user request:

• Product type: SaaS, e-commerce, portfolio, dashboard, landing page, etc.
• Style keywords: minimal, playful, professional, elegant, dark mode, etc.
• Industry: healthcare, fintech, gaming, education, etc.
• Stack: React, Vue, Next.js, or default to html-tailwind

Step 2: Search Relevant Domains

Use search.py multiple times to gather comprehensive information. Search until you have enough context.

python .claude/skills/ui-ux-pro-max/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]

Recommended search order:

1. Product - Get style recommendations for product type
2. Style - Get detailed style guide (colors, effects, frameworks)
3. Typography - Get font pairings with Google Fonts imports
4. Color - Get color palette (Primary, Secondary, CTA, Background, Text, Border)
5. Landing - Get page structure (if landing page)
6. Chart - Get chart recommendations (if dashboard/analytics)
7. UX - Get best practices and anti-patterns
8. Stack - Get stack-specific guidelines (default: html-tailwind)

Step 3: Stack Guidelines (Default: html-tailwind)

If user doesn't specify a stack, default to html-tailwind.

python .claude/skills/ui-ux-pro-max/scripts/search.py "<keyword>" --stack html-tailwind

Available stacks: html-tailwind, react, nextjs, vue, svelte, swiftui, react-native, flutter

Search Reference

Available Domains

Available Stacks

Example Workflow

User request: "Làm landing page cho dịch vụ chăm sóc da chuyên nghiệp"

AI should:

# 1. Search product type
python .claude/skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --domain product

# 2. Search style (based on industry: beauty, elegant)
python .claude/skills/ui-ux-pro-max/scripts/search.py "elegant minimal soft" --domain style

# 3. Search typography
python .claude/skills/ui-ux-pro-max/scripts/search.py "elegant luxury" --domain typography

# 4. Search color palette
python .claude/skills/ui-ux-pro-max/scripts/search.py "beauty spa wellness" --domain color

# 5. Search landing page structure
python .claude/skills/ui-ux-pro-max/scripts/search.py "hero-centric social-proof" --domain landing

# 6. Search UX guidelines
python .claude/skills/ui-ux-pro-max/scripts/search.py "animation" --domain ux
python .claude/skills/ui-ux-pro-max/scripts/search.py "accessibility" --domain ux

# 7. Search stack guidelines (default: html-tailwind)
python .claude/skills/ui-ux-pro-max/scripts/search.py "layout responsive" --stack html-tailwind

Then: Synthesize all search results and implement the design.

Tips for Better Results

1. Be specific with keywords - "healthcare SaaS dashboard" > "app"
2. Search multiple times - Different keywords reveal different insights
3. Combine domains - Style + Typography + Color = Complete design system
4. Always check UX - Search "animation", "z-index", "accessibility" for common issues
5. Use stack flag - Get implementation-specific best practices
6. Iterate - If first search doesn't match, try different keywords

Curation Constraints (UI/UX Design Principles)

The databases RECOMMEND; the 40 UI/UX Design Principles (UI-1.1–UI-9.4, the SYNC:ui-ux-design-principles block below) CONSTRAIN what you may recommend. A search hit is a CANDIDATE, not a verdict — verify it against the clauses before handing it to the user or to design. Project design-system docs outrank both the clauses and these databases; a genuine conflict goes to the user, NEVER resolved silently.

When a curated recommendation cannot satisfy a clause, say so explicitly with the clause ID and offer the compliant alternative — a beautiful palette that fails UI-3.1 is a FINDING, not a deliverable.

Common Rules for Professional UI

These are frequently overlooked issues that make UI look unprofessional:

Icons & Visual Elements

Interaction & Cursor

Light/Dark Mode Contrast

Layout & Spacing

Async UI States & Feedback (the most-missed fundamentals)

Every screen or component that fetches, submits, or mutates data MUST render all of its states — not just the happy path. A UI that looks perfect when populated but shows a frozen blank while loading, fails silently on error, or shows nothing when empty is broken UX. Canonical state vocabulary (shared with design-spec): Default / Loading / Disabled / Error / Empty / Success.

Responsive & Multi-Device (usable on small screens)

Pre-Delivery Checklist

Before delivering UI code, verify these items:

Visual Quality

• No emojis used as icons (use SVG instead)
• All icons from consistent icon set (Heroicons/Lucide)
• Brand logos are correct (verified from Simple Icons)
• Hover states don't cause layout shift

Interaction

• All clickable elements have cursor-pointer
• Hover states provide clear visual feedback
• Transitions are smooth (150-300ms)
• Focus states visible for keyboard navigation

States & Feedback (async surfaces — verify every one)

• Loading — every data fetch / submit / mutation shows a spinner or skeleton while in-flight (never a frozen blank screen)
• Error — every operation that can fail shows a human-readable error with a retry / recovery path (no silent failure, no raw stack trace)
• Empty — every list / table / collection view has a meaningful empty state (message + optional CTA), not a blank area
• In-flight disable — submit/action buttons are disabled or busy while their request runs (no double-submit)
• Success — completed mutations give confirmation feedback (toast / inline / updated data)

Light/Dark Mode

• Light mode text has sufficient contrast (4.5:1 minimum)
• Glass/transparent elements visible in light mode
• Borders visible in both modes
• Test both modes before delivery

Layout & Responsiveness

• Floating elements have proper spacing from edges
• No content hidden behind fixed navbars
• Responsive at 320px, 768px, 1024px, 1440px
• Rows flex-wrap or switch row → column on small screens; multi-column grids collapse to one column
• Usable down to 320px — nothing broken (no clipped, cut-off, or unreachable content); where a layout genuinely can't reflow, a min-width/min-height + overflow: auto scroll is acceptable
• Any small-screen fix that needs a large layout refactor was flagged and confirmed with the user (not silently rewritten)

Accessibility

• All images have alt text
• Form inputs have labels
• Color is not the only indicator
• prefers-reduced-motion respected

Related

• design --lane=marketing — Marketing/creative UI (landing pages, campaigns)
• design --lane=product — Product UIs (dashboards, admin panels, SaaS apps)
• shadcn-tailwind
• design-spec

[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ATTENTION ask user whether to skip.

UI/UX Design Principles (Rev 1.0 — 40 clauses, web + mobile) — the working rule set for ANY task that designs, plans, implements, or reviews a user interface. Applies to BOTH platforms unless a clause names one (§8 is mobile/touch). Cite clauses by ID: UI-3.1, UI-8.2.

Precedence: project design-system / SCSS / frontend-pattern docs OUTRANK these clauses; these clauses outrank generic taste. A genuine conflict is SURFACED to the user with both sides — NEVER resolved silently. — why: the project's own recorded decision is the authority; these clauses are the default when it is silent.

1.0 Visual Hierarchy & Layout

• UI-1.1 One focal point per screen. Two elements competing for first read → demote one.
• UI-1.2 Signal order: size → weight → colour → position. Use the cheapest signal that works before adding another.
• UI-1.3 Group by proximity, NEVER by border. Whitespace separates cleanly; boxes inside boxes do not.
• UI-1.4 Align to a shared edge. Every unexplained indent reads as an accident.
• UI-1.5 Design the empty, loading and error state FIRST. The full state is the easy one.

2.0 Typography

• UI-2.1 Max 2 families, 3 weights each. More variety reads as inconsistency, not range.
• UI-2.2 Body text 16px web, 17px mobile. NEVER below 14px for anything a user must read.
• UI-2.3 Line length 45–75 characters. Constrain the measure, not the container.
• UI-2.4 Leading scales inversely with size: 1.5 body, 1.1–1.2 display.
• UI-2.5 Fixed type scale — 6 named steps shared with engineering. NEVER one-off sizes.

3.0 Colour & Contrast

• UI-3.1 Contrast 4.5:1 text, 3:1 UI edges. Measure it — NEVER judge by eye on a bright screen.
• UI-3.2 One accent, one job. An accent that is everywhere points at nothing.
• UI-3.3 Colour NEVER carries meaning alone — pair it with an icon, label or position.
• UI-3.4 Dark mode is NOT inverted light mode. Lift surfaces to signal elevation; soften pure-white text.

4.0 Spacing & Grid

• UI-4.1 One spacing unit, multiplied — 4px or 8px base; every gap a multiple of it.
• UI-4.2 Space belongs to the container, not the child. Use gap; reserve margins for exceptions.
• UI-4.3 Tighter inside, looser between — inner padding always smaller than the gap to the next group.
• UI-4.4 Breakpoints follow content, not devices. Break where the layout stops working.

5.0 Interaction & Feedback

• UI-5.1 Every action gets a response under 100ms, even when the result takes longer.
• UI-5.2 Specify all 5 states — default, hover, focus, active, disabled — plus loading where it applies.
• UI-5.3 Prefer undo over confirmation. Confirm ONLY what cannot be reversed.
• UI-5.4 Motion clarifies cause and effect: 150–250ms, ease-out, honours reduced-motion.
• UI-5.5 Keep the visible focus ring. Restyle it if it clashes; NEVER remove it.

6.0 Navigation & IA

• UI-6.1 Every screen answers: where am I, what's here, where next.
• UI-6.2 Max 5 top-level destinations. Depth beats a crowded first level.
• UI-6.3 Label by the user's word, not the internal one. Team vocabulary is not a taxonomy.
• UI-6.4 Every state deserves a URL or a back path. Deep links and hardware back must land somewhere sensible.

7.0 Forms & Input

• UI-7.1 Ask for less. Every field needs a reason it exists today.
• UI-7.2 Labels stay visible. Placeholders are hints, NEVER labels.
• UI-7.3 Validate on blur, not on keystroke. Errors sit next to the field and say how to fix it.
• UI-7.4 Match keyboard to data type — correct input type, autocomplete and autocapitalise on every field.
• UI-7.5 NEVER lose entered data. Preserve input across errors, navigation and refresh.

8.0 Mobile & Touch (mobile/touch surfaces)

• UI-8.1 Hit target ≥44×44pt, 8px apart. The target may exceed the visible icon.
• UI-8.2 Primary actions in the bottom third — that is where the thumb lives.
• UI-8.3 Gestures are shortcuts, NEVER the only route. Anything swipeable is also tappable.
• UI-8.4 Respect safe areas and the keyboard. Notch, home indicator and on-screen keyboard all steal space.

9.0 Speed & Perceived Speed

• UI-9.1 Show structure before data — skeletons for known layouts, spinners only for unknown waits.
• UI-9.2 Assume success optimistically. Update UI first, reconcile after, roll back visibly on failure.
• UI-9.3 Reserve space for anything that loads. Images, ads and fonts must NEVER shift the layout.
• UI-9.4 Design for the slow connection. Offline, timeout and retry are states, NOT edge cases.

Apply by role — the clauses are one set; what you DO with them depends on the task:

Role	Obligation
DESIGN / PLAN a surface	Clauses shape the artifact: empty/loading/error specified first (UI-1.5), all 5 states enumerated (UI-5.2), type scale + spacing unit declared (UI-2.5, UI-4.1)
IMPLEMENT a component	Pre-completion gate: states · tokens · contrast · focus ring · touch target · reserved space (UI-5.2, UI-2.5/UI-4.1, UI-3.1, UI-5.5, UI-8.1, UI-9.3)
REVIEW UI code or a design artifact	Each clause is a fail-condition; every finding cites UI-<clause> + file:line + severity. NEVER a tick-box sweep — one focused pass per section
SCAN / document a UI system	Record where the PROJECT deliberately deviates, so the overriding doc becomes the recorded authority

Skip ONLY when the change has no user-facing surface (backend-only, tooling, docs) — state that explicitly so the skip is auditable, not an omission.

AI Mistake Prevention — Failure modes to avoid on every task:

Re-read files after context changes. Context compaction, resume, or long-running work can make memory stale; verify current files before acting. Verify generated content against source evidence. AI hallucinates APIs, names, claims, and document facts. Check the relevant source before documenting or referencing. Check downstream references before deleting or renaming. Removing an artifact can stale docs, generated mirrors, configs, and callers; map references first. Trace the full impact chain after edits. Changing a definition can miss derived outputs and consumers. Follow the affected chain before declaring done. Verify ALL affected outputs, not just the first. One green check is not all green checks; validate every output surface the change can affect. Assume existing values are intentional — ask WHY before changing OR flagging one as a defect. Before changing or reporting a constant, limit, flag, cutoff, wording, or pattern, read nearby context and history, the CALLER's ordering, and 2+ sibling call sites of the same convention. A doc stating WHAT without WHY is missing rationale, not proof of a missing guard. Surface ambiguity before acting — don't pick silently. Multiple valid interpretations require an explicit question or stated assumption with risk. Assert the outcome your system owns, not the intermediate state your infrastructure owns. When verifying async work, assert the final business state — never the delivery/retry bookkeeping held in shared infrastructure that any co-running process can write. Such a check passes when run alone and flakes the moment anything else shares that infrastructure. Keep shared guidance role-relevant. Universal guidance must help every receiving skill or agent; code-specific obligations belong only in code-specific protocols.

Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.

[BLOCKING] Design distinctiveness gate (DD-1–DD-8) — binds on ANY task that designs, plans, mocks up, implements, or reviews a user-facing visual surface. Deep catalog: .claude/docs/design-knowledge.md. Cite findings as DD-<clause> + file:line.

Precedence (resolve in this order, never silently): the brief's own stated visual direction WINS outright — including when it asks for one of the DD-4 tells. Then the project's design-system / SCSS / frontend-pattern docs and accepted ADRs — a house style IS an intentional identity, and re-deciding it per feature is the incoherence this gate prevents. Then these clauses. A genuine conflict is SURFACED to the user with both sides, NEVER resolved silently.

Relationship to UI-1.1–UI-9.4: a different question, no overlap — the 40 clauses ask "is this usable, accessible, consistent?" (a measurable floor); this gate asks "is this THIS product's interface, or the one any generator would emit for any brief?". A surface can pass all 40 clauses and still be a template. BOTH bind; where they touch (type scale, colour, motion timing) the clause sets the floor and this gate picks the value.

• DD-1 Ground it in the subject matter. Before designing, name the concrete subject, the audience, and the design's primary job — and CONFIRM with the user when the brief is silent. Distinctive choices come FROM the subject's industry, materials and vernacular; they are never taste applied on top. Test: if the palette, type and layout would fit a different product unchanged, there is no identity yet.
• DD-2 Every choice carries a WHY. "It's common", "it's clean", "users expect it" are not reasons. A decision with no articulable reason is a default that arrived unnoticed. Defaults hide in what feels like infrastructure — typography, navigation, data display, and TOKEN NAMES. Token-name test: someone reading only your CSS variables should be able to guess what product this is (--ink/--parchment evoke a world; --gray-700/--surface-2 evoke a template).
• DD-3 Two passes, and the review pass is mandatory. (1a) Write a compact design plan — Colour (4–6 named hex values) · Type (families + roles + scale) · Layout (one-sentence prose + ASCII wireframes to compare alternatives, including alignment: left/centre/justified) · Principles (what makes THIS page unique). (1b) BLOCKING generic test — before any code: work through a similar prompt and see whether you arrive somewhere similar; any part that reads like the generic default for any comparable page rather than a choice for THIS brief gets REVISED, and you state what you changed and why. Then (2a) build the REVISED plan, (2b) critique. — why: writing a plan and going straight to code reproduces the default, because the plan came from the same patterns the code will.
• DD-4 Audit every FREE axis against the generated-design tell catalog ([model-knowledge], calibration not prohibition — each trait is legitimate for SOME brief): T1 cream #F4F1EA + high-contrast serif + terracotta near #D97757 (Anthropic's own interaction accent — on a user's brief it reads specifically as a tell) · T2 near-black + one acid-green/vermilion accent · T3 broadsheet hairline-rule pastiche, zero radius, dense columns · T4 the SaaS-card kit: identical rounded cards, ONE radius regardless of hierarchy, the same rgba(0,0,0,.1) shadow under each, gradient washes as decoration · T5 template chrome whatever the subject: tracked-out ALL-CAPS eyebrow above every heading, meta strings joined with middle dots (A · B · C), WORD — fragment labels with a spaced em dash, tinted near-black (#0B0B0B/#111) standing in for black, monospace for small data labels, → appended to link/button text. A match is a HYPOTHESIS about a missed decision, never a defect — promote it only by naming the axis, that the brief left it free, and what the subject suggested instead.
• DD-5 Typography carries the personality. One family, or two CLEARLY distinct ones — you do NOT need separate display and body faces. Choose deliberately, not the default you would reach for on any project. Set a real scale with intentional weights, widths and spacing. When type is a headline it is an ACTIVE part of the design, not a neutral delivery vehicle. Measure under ~80 characters; serifs tolerate slightly longer lines and want slightly more line-height than sans at the same size. Hierarchy needs weight/tracking/opacity, not size alone. Avoid the three commonest tells: accenting a single word in a headline (italic/bold/colour) · ALL CAPS labels · an eyebrow label that names the section the heading already names.
• DD-6 Structure is information, not decoration. Outlines, borders, numbering, eyebrows, dividers and labels must encode something about the content. Before adding numbered markers (01 / 02 / 03), check the content really IS a sequence — a stepped process, timeline or ranking. For every device ask: what does this tell the reader that whitespace would not? Nothing → cut it. Hero: open with the most characteristic thing in the subject's world, in whatever form fits (headline, image, animation, live demo, interactive moment) — big-number-plus-small-label-plus-gradient is the DEFAULT treatment, so use it only when it is genuinely best here. Composition: rhythm over monotone (same card size, same gap, same density everywhere is the sound of no one deciding); proportions must say something you can articulate; one dominant focal point.
• DD-7 Motion sparingly and deliberately. Non-user-triggered motion draws attention ONLY. One orchestrated moment — a single page-load sequence or one reveal — lands better than scattered effects; fade-and-slide-up entrances on each section and hover transitions on every card are the generic default and read as generated. Motion that ANSWERS a person's action (opening, expanding, confirming) is welcome when it shows what changed. Honour prefers-reduced-motion.
• DD-8 Spend boldness once, then remove one accessory. Let ONE element be the memorable thing and keep everything around it quiet and disciplined; cut any decoration that does not serve the brief. Critique the BUILT page, not just the plan — composition, craft (density is a decision, not a constant), content coherence, and CSS honesty (negative margins undoing a parent's padding, calc() values that exist only as workarounds, absolute positioning to escape layout flow are lies; the correct answer is always simpler than the hack). Take screenshots to review where the environment supports it — a picture is worth 1000 tokens. Then ask "if they said this lacks craft, what would they point to?" and fix that. Build the quality floor in silently — responsive, visible keyboard focus, reduced-motion respected, measured contrast, tokens never raw hex or magic numbers — and watch CSS selector specificity, where a type-based selector (.section) and an element-based one (.cta) most often cancel each other's padding/margin.

Memory: vary between briefs — light and dark, families, direction. NEVER converge on the same choice across generations (Space Grotesk, for example). Where the project already has a design system, tokens, or an interface-system.md, ADOPT and record it rather than re-deciding; write back any pattern used 2+ times with measurements worth remembering.

Skip ONLY when the change has NO user-facing visual surface (backend-only, tooling, docs) — state that reason explicitly so the skip is auditable, not an omission.

Words are design content, not decoration — binds whenever a task authors, changes, or reviews user-visible strings (labels, CTAs, headings, empty/error/loading text, toasts, placeholder content). Deep detail: .claude/docs/design-knowledge.md §8. Copy makes a design feel as templated as the visuals do.

Before writing anything, ask what the design needs to SAY and how it can best be said to help the person navigate the experience. Then:

1. Write from the end user's perspective. Name things by what users will understand in simple language, not by how the system is built — a user manages notifications, not webhook config. Describe what something is or does in plain terms rather than selling it. Being specific and legible to a new user ALWAYS beats being clever.
2. Active voice by default. A CTA says exactly what happens when it is used: "Save changes", NEVER "Submit".
3. One name per action, across the whole flow. The button that says Publish produces a toast that says Published. The vocabulary of an interface is the signposting for someone navigating the product — cohesion and consistency are how people learn their way around.
4. Failure and emptiness give DIRECTION, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors do NOT apologize, and are NEVER vague about what happened. An empty screen is an invitation to act.
5. Conversational tone, one job per element. Plain verbs, sentence case, no filler, tone matched to the brand and the audience; let each written element do exactly one job.
6. Real content, never lorem. When the brief supplies no copy, write plausible strings for the ACTUAL subject. Coherence check — read every visible string as a user would, checking for truth, not typos: could a real person at a real company be looking at exactly this data right now, or does the page title belong to one product, the body to another, and the sidebar metrics to a third? A beautifully designed interface with nonsensical content is a movie set with no script.

Skip ONLY when the change surfaces no user-visible text — state that explicitly.

Front-End Design Review Checklist — the EXECUTABLE review protocol for any artifact carrying a user-facing front-end surface. Full catalog (A1…Q, ~130 checks with failure signals and default severities): .claude/docs/design-review-checklist.md. This gate carries the protocol and the triage pass; the file carries the checks.

Applies when — and ONLY when — the change, plan, or artifact carries a user-facing front-end surface. A back-end-only diff, a doc edit, or a config change is N/A: state that once and move on. NEVER run a UI review on a non-UI change to manufacture coverage. When it DOES apply, MUST ATTENTION READ .claude/docs/design-review-checklist.md and work its sections — a review that cites a check ID without opening the catalog is asserting, not checking.

CL-1 Context before checks (§0.1). Establish platform · primary user & expertise · primary task · success metric · constraints · review scope · available artifacts. Fewer than four known → state the gap at the top of the report and mark affected findings low confidence — why: a check judged against an unknown task is a guess wearing an ID.

CL-2 Evidence or nothing (§0.2). Every finding cites a specific location (screen · element · file:line). NEVER invent a measurement — contrast, tap-target size, and load time that cannot be measured from the given artifact are NOT VERIFIABLE, never a guessed number. Tag every finding MEASURED · OBSERVED · HEURISTIC. Status values: PASS · FAIL · PARTIAL · N/A · NOT VERIFIABLE.

CL-3 Severity, then a cap (§0.3). P0 blocks task completion / loses data / excludes a protected group (ship blocker) · P1 significant friction or a legal accessibility floor (fix before release) · P2 measurable inefficiency (next iteration) · P3 polish (backlog) · P4 note. Cap the report at the top 10 by severity unless a full audit was requested. A clean section reports "no issues found" — NEVER pad. Every P0/P1 carries a concrete fix.

CL-4 Section sweep, in order.

…(truncated)