Pbi Mockup

Codex compatibility note:

• Invoke repository skills with $skill-name in Codex; this mirrored copy rewrites legacy Claude /skill-name references.
• Task tracker mandate: BEFORE executing any workflow or skill step, create/update task tracking for all steps and keep it synchronized as progress changes.
• User-question prompts mean to ask the user directly in Codex.
• Ignore Claude-specific mode-switch instructions when they appear.
• Strict execution contract: when a user explicitly invokes a skill, execute that skill protocol as written.
• Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
• Do not skip, reorder, or merge protocol steps unless the user explicitly approves the deviation first.
• For workflow skills, execute each listed child-skill step explicitly and report step-by-step evidence.
• If a required step/tool cannot run in this environment, stop and ask the user before adapting.

Codex Project-Reference Loading (No Hooks)

Codex uses static project-reference loading instead of runtime-injected project docs. When coding, planning, debugging, testing, or reviewing, open project docs explicitly using this routing.

Always read:

• docs/project-config.json (project-specific paths, commands, modules, and workflow/test settings)
• docs/project-reference/docs-index-reference.md (routes to the full docs/project-reference/* catalog)
• docs/project-reference/lessons.md (always-on guardrails and anti-patterns)

Missing/stale context route: If docs/project-config.json, the docs index, lessons.md, CLAUDE.md, AGENTS.md, or any task-required reference doc is missing or stale, auto-run $project-init or the narrow setup route ($project-config, $docs-init, $scan-all, $scan --target=<key>, $claude-md-init) before ordinary project-specific work. If Codex mirrors or AGENTS.md are missing/stale, ask the user to run $sync-codex; do not auto-run it.

Situation-based docs:

• Project structure/architecture/tech-stack/deployment/setup (any layer — backend, frontend, or infra): project-structure-reference.md
• Backend/CQRS/API/domain/entity changes: backend-patterns-reference.md, domain-entities-reference.md
• Frontend/UI/styling/design-system: frontend-patterns-reference.md, scss-styling-guide.md, design-system/README.md
• Spec authoring, docs/specs/ pathing, or TC format: feature-spec-reference.md, spec-system-reference.md, spec-principles.md
• Behavior/public-contract changes or spec-test-code sync: workflow-spec-test-code-cycle-reference.md plus the spec docs above
• Derived spec indexes/ERDs/reimplementation guides: spec-system-reference.md and source Feature Specs under docs/specs/
• Integration test implementation/review: integration-test-reference.md
• E2E test implementation/review: e2e-test-reference.md
• Code review/audit work: code-review-rules.md plus domain docs above based on changed files

Do not read all docs blindly. Start from docs-index-reference.md, then open only relevant files for the task.

[BLOCKING] Execute skill steps in declared order. NEVER skip, reorder, or merge steps without explicit user approval. [BLOCKING] Before each step or sub-skill call, update task tracking: set in_progress when step starts, set completed when step ends. [BLOCKING] Every completed/skipped step MUST include brief evidence or explicit skip reason. [BLOCKING] If Task tools are unavailable, create and maintain an equivalent step-by-step plan tracker with the same status transitions.

Quick Summary

Goal: Give stakeholders a clickable, self-narrating MVP prototype of every story's main-flow UI — by generating a self-contained interactive HTML mock-up file (one per PBI covering all stories) from finalized PBI/story artifacts, styled from the project's reference design docs, existing UI, components, and real domain entity data — before implementation begins, so layout/UX/flow/state gaps surface while changes are still cheap.

Summary:

• PRE-implementation preview tool, not a UI builder: run ONLY on finalized PBIs/stories (reviewed, gated); backend-only PBI with no UI sections → skip generation and tell the user; NEVER use for production UI, design specs, or scratch wireframes — why: it previews the wrong thing otherwise.
• Main pipeline (run in order): locate PBI/stories (1) → extract UI specs (2) → [BLOCKING] plan demo flows into flow-specs + one todo each (2b) → load design system (3) → [BLOCKING] inventory existing UI + map connected flows (3b) → load domain entities (3c) → generate the self-contained HTML prototype (4) → save beside the PBI (5) → report (6) → [BLOCKING] fidelity validation (7) → [BLOCKING] demo-quality gate (8). The three BLOCKING gates (2b · 3b+7 · 8) must NEVER be skipped.
• Plan first, generate second: enumerate the PBI's main-story/MVP flows into flow-specs and create one todo per flow (Step 2b) BEFORE generating; sign off with a final Demo-Quality review gate (Step 8) auditing the generated prototype.
• Output is exactly ONE self-contained HTML file per PBI (all stories as tabs/sections), inline CSS/JS, no external deps except Google Fonts, saved alongside the PBI artifact as {pbi-filename}-mockup.html.
• The mock-up is a scripted clickable prototype — each main-story flow clicks through end-to-end ("click X → see Y → move to Z") with guided narration (▶ Play / ⏭ Next / ⏮ Prev / ↺ Reset / ⏏ Exit), an explanation panel, and a visible "⚠ Simulated" banner; interactivity is scripted/simulated only (canned transitions, illustrative data) — NEVER real auth, persistence, or backend.
• Fidelity is the whole point — the mock-up must LOOK like the existing app: load the canonical + matched per-app design-system docs (NEW→canonical, REFACTOR→per-app), read real shared/module components for layout patterns, and populate with real domain entity fields and realistic sample data, never Lorem ipsum.
• Render every defined component state (default/loading/empty/error) as toggleable, keep any accompanying prose/captions tech-agnostic (business terms, not framework/CSS class names) per the M1/M2 mandates, even though the rendered HTML may use real class names internally.

Workflow:

1. Locate PBI Artifact — find PBI + story files in team-artifacts/pbis/; read fully
2. Extract UI Specs — parse UI Layout/Wireframe, Components, States, Interaction Flow, Acceptance Criteria + priority/rank 2b. [BLOCKING] Plan the Demo Flows — enumerate main-story/MVP flows, author one flow-spec per flow, task tracking one todo per flow BEFORE generating
3. Load Design System — baseline + matched per-app design tokens, colors, typography (NEW→canonical, REFACTOR→per-app) 3b. [BLOCKING] Inventory Existing UI + Map Connected Flows — read real shared/module components + map entry/exit flows so the mock-up matches the current system 3c. Load Domain Entities — entity fields, relationships, enums for realistic sample data
4. Generate HTML — one self-contained scripted clickable prototype + guided walkthrough matching the app's look and feel
5. Save — write {pbi-filename}-mockup.html beside the PBI artifact
6. Report — path, priority, stories, demo flows, components, states, fidelity + demo-quality verdicts
7. [BLOCKING] Fidelity Validation — mock-up matches inventoried UI (tokens/components/layout/connected flows); record PASS/FAIL
8. [BLOCKING] Demo-Quality Review Gate — every flow clicks end-to-end, no dead controls, narration + "⚠ Simulated" banner, offline, real data, iframe-safe; record PASS/FAIL

Key Rules:

• Ask AI to generate an interactive HTML mock-up for UI PBIs; do not stop at an ASCII-only or static mockup — every main-story flow is a scripted clickable prototype with guided narration.
• One HTML file per PBI (all stories shown as sections/tabs)
• Plan the demo flows (Step 2b) BEFORE generating; sign off with the Demo-Quality gate (Step 8) AFTER
• Interactivity is scripted/simulated only (canned transitions, illustrative data, "⚠ Simulated" banner) — NEVER real fetch/auth/persistence/backend; self-contained so it runs inside the deck's <iframe srcdoc>
• Self-contained: inline CSS/JS, no external dependencies except Google Fonts
• Must resemble the project's current UI — read existing component templates and page layouts
• Design must be based on project reference design docs: docs/project-reference/design-system/README.md, docs/project-reference/design-system/design-system-canonical.md, and the matched per-app design-system doc from docs/project-config.json
• Match project design system: colors, typography, spacing, BEM naming
• Use real domain entity fields and realistic sample data — not Lorem ipsum
• Include component states (default, loading, empty, error)
• Responsive layout with mobile/desktop preview
• Save in same directory as the PBI artifact
• Tech-agnostic descriptive prose (M1/M2): See .claude/skills/shared/sdd-artifact-contract.md → "AI-SDD Mandates (M1-M7)" for BLOCKING criteria. Any narrative, captions, annotations, generation notes, or component/state descriptions accompanying the mock-up describe components and states by business/observable terms (e.g., "status indicator", "record list", "loading placeholder"), NOT by framework component names or CSS class names. The rendered HTML itself may use real class names internally (that is implementation, not prose), but the human-readable descriptions stay tech-agnostic per docs/project-reference/spec-principles.md §3.

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

PBI HTML Mockup Generator

Generate visual HTML mockup reports from PBI and user story artifacts.

When to Use

• After PBI and stories are finalized (reviewed, challenged, gated)
• Before moving to implementation planning or design spec
• When stakeholders need a visual preview of the feature
• As the final step in workflow-idea-to-pbi and similar workflows

NOT for: Implementing production UI (use $feature-implement), creating design specs (use $design-spec), or wireframing from scratch (use $design-spec --mode=wireframe).

Quick Reference

Input

Output

Related

• Input from: $refine, $story
• Command: $pbi-mockup
• Next Step: $prioritize, $design-spec, $plan

Detailed Workflow

Step 1: Locate PBI Artifact

1. If argument provided, use it as path
2. Otherwise, find most recent PBI: Glob("team-artifacts/pbis/*-pbi-*.md") sorted by modification time
3. Read the PBI artifact fully
4. Check for associated stories: Glob("team-artifacts/pbis/stories/*-us-{pbi-slug}*.md")
5. Read all story artifacts if found

Step 2: Extract UI Specifications

From the PBI and story artifacts, extract:

If no UI sections exist (backend-only PBI), inform user and skip mockup generation:

"This PBI has no UI sections (marked as backend-only). No mockup generated."

Step 2b: [BLOCKING] Plan the Demo Flows (think → plan → many todos BEFORE generating)

[BLOCKING] Do NOT generate the mock-up until every main-story flow is planned as a flow-spec and a todo exists per flow. The mock-up is a clickable, self-narrating prototype of the PBI's main user-story happy paths — plan the journeys first, generate second.

1. Enumerate the main-story / MVP flows — from ### Interaction Flow, the ## Acceptance Criteria GIVEN/WHEN/THEN scenarios, and each story's "As a / I want / So that". One flow per main user story (MVP happy path) — not every edge case.
2. Author one flow-spec per flow — fill the references/interactive-demo.md §1 schema: id, business-language title, persona, trigger, ordered steps[] where each step = { action: "user clicks/selects/types X", result: "screen/state Y appears", explain: "plain-language why" }, and endState. The explain/title prose stays tech-agnostic (business terms, not class names) per M1/M2.
3. task tracking one todo per flow — so each journey is generated and later verified (Step 8) individually; add the Step 8 Demo-Quality review as the final todo.

See references/interactive-demo.md §1 for the flow-spec schema + a worked example.

Step 3: Load Design System Context

1. Read PBI module field from frontmatter

2. Load design system docs dynamically (project-config.json + glob fallback). The HTML mock-up design must be based on these project reference design docs:

   • Mandatory baseline: Read docs/project-reference/design-system/README.md and docs/project-reference/design-system/design-system-canonical.md
   • Primary: Read top-level designSystem in docs/project-config.json: use designSystem.docsPath + designSystem.canonicalDoc, then match the PBI/app context against designSystem.appMappings[] to select the per-app doc. Do NOT look for designSystem on module entries.
   • Fallback: Glob("docs/project-reference/design-system/*.md") → match module name against discovered file names (case-insensitive substring match)
   • Default: If no match found, use docs/project-reference/design-system/README.md
   • Triage rule (NEW vs REFACTOR): For NEW pages/components → load designSystem.canonicalDoc from top-level project-config.json (single source of truth for new code). For REFACTOR of existing screens → load the matched per-app doc via top-level designSystem.appMappings (current-state inventory).

3. Extract from design system docs (read enough of the canonical and matched per-app docs to apply the rules):

   • Colors: Primary, secondary, accent, background, text colors
   • Typography: Font families, sizes, weights
   • Spacing: Margin/padding scale
   • Border radius: Component roundness
   • Shadows: Elevation levels

4. Optionally read docs/project-reference/scss-styling-guide.md (first 100 lines) for BEM patterns

Step 3b: [BLOCKING] Inventory Existing UI + Map Connected Flows (match current system UI)

[BLOCKING] Do NOT generate the mockup until this inventory + connected-flow map is done (canonical: SYNC:existing-ui-research). The mockup must faithfully match the current UI system, not generic HTML.

The mockup should resemble the project's actual UI, not generic HTML. Discover existing components AND map the flows that connect to this screen:

1. Read docs/project-reference/frontend-patterns-reference.md (first 200 lines) — extract base component classes, common UI patterns, form patterns, table/grid patterns, dialog/modal patterns
2. Glob the project's shared component library (if exists):
   • Glob("**/libs/*common*/**/*.component.ts") or Glob("**/shared/**/*.component.ts") — discover reusable components (buttons, tables, forms, dialogs, filters, status badges)
   • Read 2-3 key component files to understand their HTML template structure and CSS class naming
3. Glob the module's own components (if PBI module detected):
   • Search for existing page components in the module to understand the current UI layout patterns
   • Read 1-2 existing page templates to capture the actual look and feel (sidebar layout, toolbar patterns, card grids, etc.)
4. Extract from discovered components:
   • Layout patterns: Sidebar + content, full-width, split-panel, tabbed
   • Common components: Table with pagination, filter bar, action buttons, status chips, breadcrumbs
   • Form patterns: Form groups, validation display, multi-step forms
   • Navigation: Tab bars, breadcrumbs, sidebar menus
5. Map connected feature flows — identify every existing feature/screen that links to, embeds, includes, or navigates to/from this new screen; note the entry/exit flows so the mockup fits the surrounding navigation, not just a standalone page.

Key principle: Mimic existing system UI. If the project has a table with specific column patterns, use that pattern. If it has card-based layouts, use cards. The mockup should feel like it belongs in the existing application.

Step 3c: Load Domain Entity Context

Use real domain entities and relationships for realistic mockup data:

1. Read docs/project-reference/domain-entities-reference.md (if exists) — extract entities, fields, relationships for the PBI's module
2. From the PBI artifact, extract referenced entities from ## Domain Context section
3. Use entity field names and types to generate realistic sample data in the mockup:
   • Entity names → table column headers, form field labels
   • Entity relationships → navigation links, dropdowns, nested displays
   • Entity statuses/enums → status badges, filter options
   • Date fields → realistic date values
   • String fields → domain-appropriate sample text (customer names, invoice titles, etc.)

Key principle: Sample data should use actual entity field names and realistic domain values — not "Lorem ipsum" or "Item 1, Item 2".

Step 4: Generate HTML Mockup

Generate a single self-contained HTML file with the following structure:

<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="UTF-8" />
        <meta name="viewport" content="width=device-width, initial-scale=1.0" />
        <title>Mockup: {PBI Title}</title>
        <link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet" />
        <style>
            /* Design system tokens as CSS variables */
            /* Component styles matching project BEM conventions */
            /* Responsive breakpoints */
            /* Dark/light theme support */
        </style>
    </head>
    <body>
        <!-- PBI Header: title, description, metadata -->
        <!-- Navigation tabs (one per story) -->
        <!-- Story sections with mockup UI -->
        <!-- Component state toggles (default/loading/empty/error) -->
        <!-- Interactive prototype: screens/states + hotspots + demo control bar + explanation panel + "⚠ Simulated" banner -->
        <script>
            /* Tab navigation */
            /* State toggles */
            /* Theme toggle */
            /* Responsive preview toggle */
            /* Prototype engine: goTo(stateId) router + hotspots + simulated submit — see references/interactive-demo.md §2 */
            /* Guided walkthrough: ▶ Play ⏭ Next ⏮ Prev ↺ Reset ⏏ Exit — see references/interactive-demo.md §3 */
        </script>
    </body>
</html>

Interactive Prototype + Guided Walkthrough

The mock-up is a scripted clickable prototype of each planned flow (Step 2b), not a still image. For EVERY flow-spec, render the journey so a stakeholder can click through it and watch it narrate. Mechanics are delegated — do NOT inline the engine here:

1. Screen/state router + hotspots — render each flow's screens/states as DOM sections and wire clickable hotspots that goTo the next state (references/interactive-demo.md §2). Simulated submit → success toast → in-memory row insert; NO real fetch/persistence/backend.
2. Demo controls + guided walkthrough — a control bar (▶ Play · ⏭ Next · ⏮ Prev · ↺ Reset · ⏏ Exit) auto-/step-walks the flow, spotlighting the active hotspot (references/interactive-demo.md §3).
3. Explanation panel + "⚠ Simulated" banner — a persistent panel names the current flow + step (n / total) + the step's plain-language explain; a visible "⚠ Simulated — illustrative data, no real actions are performed" banner is the scope guard (references/interactive-demo.md §4).
4. Affordances + a11y — hotspots visibly highlighted (pulse/outline), disabled controls show a tooltip, demo never traps the user, prefers-reduced-motion respected (references/interactive-demo.md §5).

Scope guard: interactivity is scripted/simulated only (canned transitions, illustrative data) — never real auth, persistence, or backend calls; self-contained so it runs inside the deck's <iframe srcdoc> sandbox (references/interactive-demo.md §6).

Design-Principles Build Constraints (real markup, not advice)

The 40 UI/UX Design Principles (UI-1.1–UI-9.4, the SYNC:ui-ux-design-principles block below) are BUILD CONSTRAINTS on the emitted HTML/CSS — the mock-up must actually DO these, not merely describe them. Project design-system tokens outrank the clause defaults; a genuine conflict goes to the user, NEVER resolved silently.

1. Build the empty, loading and error views FIRST (UI-1.5) — author those three state panels BEFORE the populated one and wire each into the state toggle (Default | Loading | Empty | Error) so a stakeholder can click into them. A story panel rendering only the populated view is incomplete.
2. Real focus rings (UI-5.5) — every focusable control keeps a VISIBLE :focus-visible outline in the emitted CSS. outline: none with no replacement ring is a build defect; tab through each flow before the Step 8 gate.
3. All 5 interaction states as real CSS (UI-5.2) — :hover, :focus-visible, :active, [disabled] and the default rule exist for every button, link, input, tab and hotspot; disabled controls are visibly muted AND non-interactive, not merely unbound.
4. Real 44×44pt touch targets (UI-8.1, UI-8.2) — every tappable element carries a min-width/min-height of at least 44px (the hit area may exceed the visible icon) with ≥8px separation, in the responsive/mobile preview as well as desktop; primary actions sit in the bottom third of the mobile viewport.
5. Reserved space for anything that loads (UI-9.3, UI-9.1) — images, avatars, charts and skeletons carry explicit width/height or aspect-ratio so switching Default ↔ Loading NEVER shifts the layout; skeletons for known layouts, spinners only for unknown waits.
6. Declared scales emitted as CSS variables (UI-2.5, UI-4.1) — the type scale as 6 named custom properties and the spacing scale from ONE 4px or 8px base; every font-size, padding, margin and gap references a variable. Hard-coded one-off px values are a build defect.
7. Measured contrast (UI-3.1, UI-3.2, UI-3.3) — text ≥4.5:1 and UI edges/borders ≥3:1 against their ACTUAL backgrounds in BOTH themes, one accent with one job, and status chips / validation states pair colour with an icon or text label so colour never carries the meaning alone.
8. Body type and measure (UI-2.2, UI-2.3) — body text 16px (17px in the mobile preview) and never below 14px for readable content; prose columns constrained to a 45–75 character measure.
9. Motion budget (UI-5.4) — transitions 150–250ms ease-out, and the guided walkthrough honours prefers-reduced-motion (already required by the prototype a11y rule above).
10. Forms (UI-7.2, UI-7.3, UI-7.5) — visible labels on every input (placeholders are hints, NEVER labels); the error state shows the message beside its field with a fix instruction; simulated navigation between demo steps preserves entered values.

HTML Structure Requirements

1. Header Section:

   • PBI ID and title
   • Module badge
   • Priority badge — the PBI's priority label + numeric rank from frontmatter (e.g. "Priority: Must Have · Rank #2"). MANDATORY when the PBI carries priority/rank; the mockup MUST surface the same priority info as the backlog so stakeholders see it on the prototype itself. Omit only when the PBI genuinely has no priority assigned yet.
   • Story count summary
   • Generation date

2. Navigation:

   • Tab bar with one tab per story (or section per PBI acceptance criteria)
   • Active tab highlight using design system primary color

3. Story Panels:

   • Story title and description ("As a... I want... So that...")
   • Visual mockup of the UI described in wireframe/layout sections
   • Component placeholders with realistic sample data
   • State toggle buttons (Default | Loading | Empty | Error)

4. Footer:

   • "Generated from PBI {ID}" attribution
   • Link back to artifact path
   • Generation timestamp

Styling Rules

• Base every visual decision on the loaded project reference design docs; cite the docs used in the generation notes when reporting the mock-up.
• Use CSS custom properties (variables) from design system tokens
• Follow BEM naming: mockup__header, mockup__nav, mockup__panel
• Match the project's color palette, typography, and spacing
• Include both light and dark theme (toggle button in header)
• Responsive: mobile (< 768px) and desktop layout — mobile must stay usable: reflow where possible (stack rows, collapse grids to one column); where a block genuinely can't reflow (tables, wide grids) give it overflow: auto scroll rather than letting it clip; nothing broken or cut off
• Use realistic placeholder data (names, dates, numbers) — not "Lorem ipsum"

Component Rendering

Map wireframe components to HTML elements AND to their scripted demo interaction (the hotspot/transition that advances the flow — references/interactive-demo.md §2):

Step 5: Save HTML File

• Path: Same directory as the PBI artifact
• Name: {pbi-filename-without-ext}-mockup.html
• Example: team-artifacts/pbis/260324-pbi-goal-tracking-mockup.html

Step 6: Report to User

After generation, output:

Mockup generated: {path}
- PBI priority: {priority label} · Rank #{rank}  (or "not yet prioritized")
- Stories covered: {count}
- Demo flows: {count} ({flow titles})
- Components rendered: {list}
- States included: {default, loading, empty, error}
- Fidelity vs existing UI: PASS | FAIL
- Demo quality: PASS | FAIL

Open in browser to preview. Click highlighted hotspots or press ▶ Play to walk a flow. Use theme toggle for dark/light mode.

Step 7: [BLOCKING] Fidelity Validation — Mockup Matches Existing UI

[BLOCKING] After the HTML is generated, validate it faithfully matches the existing UI inventoried in Step 3b before handing off. Do NOT report the mockup as done until this validation records a result — a mockup that does not match the current system is not done.

Validate the produced mockup against the inventoried existing UI and record an explicit pass/fail:

1. Design tokens — colors, typography, spacing match the project design system (Step 3).
2. Component patterns — tables, forms, dialogs, status chips, and navigation reuse the existing component patterns (Step 3b), not generic HTML.
3. Layout/structure — the screen layout matches the existing pages of the related feature (sidebar / toolbar / card-grid conventions).
4. Connected flows — entry/exit navigation matches the connected feature flows mapped in Step 3b.

Record the outcome in the Step 6 report:

Fidelity vs existing UI: PASS | FAIL — tokens / components / layout / flows matched? If FAIL: what diverged + the fix.

If FAIL, revise the mockup to match the existing UI and re-validate before handoff.

Step 8: [BLOCKING] Demo-Quality Review Gate

[BLOCKING] This is the final review todo (Step 2b created it). After fidelity passes, audit the GENERATED interactive prototype's demo quality before handoff. Do NOT report the mock-up as done until this records a result — a prototype with a dead control or a flow that does not click through is not done. Full checklist: references/interactive-demo.md §7.

First, confirm the result SATISFIES the PBI's intent (not merely that it renders): every main user story in the PBI's ## Acceptance Criteria / ### Interaction Flow is represented by a flow-spec demo (coverage — no main story missing), AND each prototype faithfully demonstrates that story's intended behavior end-to-end. Then audit the produced prototype against every planned flow-spec and record an explicit pass/fail:

0. Satisfies the PBI intent — every main-story/MVP flow from the acceptance criteria is present and its demo conveys the intended behavior; if a story has no demo or the demo misrepresents it, this gate FAILS regardless of the items below.
1. Every main-story flow clicks end-to-end — each flow's steps[] reach its endState via real hotspots; no path dead-ends.
2. No dead controls — every button/hotspot advances the demo or is visibly disabled-with-tooltip.
3. Narration present + tech-agnostic — every step shows its plain-language explain; copy is business-language (M1/M2), not class names; the "⚠ Simulated — illustrative data, no real actions are performed" banner is visible on every flow.
4. Opens offline standalone — no external <script src>; Google Fonts CSS only; no JS console errors.
5. Real domain data — screens/rows use real entity field names + realistic values, never Lorem ipsum.
6. iframe-safe — works self-contained inside an <iframe srcdoc> sandbox (no parent-document or network dependency) so the deck can embed it.

Record the outcome in the Step 6 report:

Demo quality: PASS | FAIL — satisfies PBI intent (every main story demoed + faithful) / flows click end-to-end / no dead controls / narration tech-agnostic + banner / offline / real data / iframe-safe? If FAIL: what broke + the fix.

If FAIL, fix the prototype (re-author from the flow-spec — cheap) and re-audit before handoff.

Mockup Quality Checklist

Before completing:

• HTML file is self-contained (opens correctly without a server)
• All stories from PBI are represented as sections/tabs
• Every main-story flow (Step 2b) is rendered as a scripted clickable prototype with guided narration
• Design is based on design-system-canonical.md plus the matched per-app design-system doc when available
• Design system colors and typography match the project
• Component states are toggleable (where defined in artifact)
• Responsive layout works for mobile and desktop — usable on small screens with nothing clipped/cut-off/unreachable (reflow preferred; overflow: auto scroll acceptable where a block can't reflow)
• Realistic placeholder data used (not Lorem ipsum)
• PBI metadata shown in header (ID, title, module, date)
• PBI priority shown in header (priority label + numeric rank from frontmatter) when the PBI is prioritized — the mockup carries the same priority info as the backlog
• File saved alongside the PBI artifact
• Fidelity validation (Step 7) recorded PASS — mockup matches existing UI tokens, components, layout, and connected flows
• Demo-Quality gate (Step 8) recorded PASS — every flow clicks end-to-end, no dead controls, narration + "⚠ Simulated" banner present, offline, iframe-safe
• Design-Principles build constraints hold — UI-1.5 empty/loading/error panels BUILT and toggleable, UI-5.5 visible focus ring on every focusable control, UI-5.2 all 5 interaction states in real CSS, UI-8.1/UI-8.2 real ≥44×44px touch targets 8px apart with bottom-third primaries in the mobile preview, UI-9.3 reserved space so state switches never shift layout, UI-2.5/UI-4.1 6-step type scale + ONE 4/8px spacing unit emitted as CSS variables, UI-3.1/UI-3.3 contrast measured 4.5:1 text / 3:1 edges in both themes and colour never the sole carrier of meaning

Edge Cases

Anti-Patterns

Workflow Recommendation

MANDATORY IMPORTANT MUST ATTENTION — NO EXCEPTIONS: If you are NOT already in a workflow, you MUST ATTENTION use ask the user directly to ask the user. Do NOT judge task complexity or decide this is "simple enough to skip" — the user decides whether to use a workflow, not you:

1. Activate workflow-idea-to-pbi workflow (Recommended) — includes mockup as final step
2. Execute $pbi-mockup directly — run this skill standalone on an existing PBI

Next Steps

MANDATORY IMPORTANT MUST ATTENTION — NO EXCEPTIONS after completing this skill, you MUST ATTENTION use ask the user directly to present these options. Do NOT skip because the task seems "simple" or "obvious" — the user decides:

• "$prioritize (Recommended)" — Prioritize the PBI in the backlog
• "$design-spec" — Create detailed design specification from mockup
• "$plan" — Start implementation planning
• "Skip, continue manually" — user decides

[IMPORTANT] Use task tracking to break ALL work into small tasks BEFORE starting.

Evidence Gate: MANDATORY IMPORTANT MUST ATTENTION — every claim, finding, and recommendation requires file:line proof or traced evidence with confidence percentage (>80% to act, <80% must verify first).

[BLOCKING] Understand the existing UI before you design or spec a new/updated screen. Before producing any wireframe, mockup, screen design, or UI spec:

1. Inventory existing related UI — search the project for screens, pages, and components already serving this feature or its domain (consult design-system docs + the real component inventory).
2. Map connected flows — identify every feature that links to, embeds, includes, or navigates to/from the new screen; trace its entry and exit flows so the new screen fits them.
3. **Reuse before invent

…(truncated)