1---
2name: pbi-mockup
3description: '[Project Management] Use when you need to generate an HTML mockup report from PBI and story artifacts.'
4metadata:
5 source: https://skillmd.com/skills/duc01226/pbi-mockup
6---
7
8> Codex compatibility note:
9>
10> - Invoke repository skills with `$skill-name` in Codex; this mirrored copy rewrites legacy Claude `/skill-name` references.
11> - Task tracker mandate: BEFORE executing any workflow or skill step, create/update task tracking for all steps and keep it synchronized as progress changes.
12> - User-question prompts mean to ask the user directly in Codex.
13> - Ignore Claude-specific mode-switch instructions when they appear.
14> - Strict execution contract: when a user explicitly invokes a skill, execute that skill protocol as written.
15> - 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.
16> - Do not skip, reorder, or merge protocol steps unless the user explicitly approves the deviation first.
17> - For workflow skills, execute each listed child-skill step explicitly and report step-by-step evidence.
18> - If a required step/tool cannot run in this environment, stop and ask the user before adapting.
19
20<!-- CODEX:PROJECT-REFERENCE-LOADING:START -->
21
22## Codex Project-Reference Loading (No Hooks)
23
24Codex uses static project-reference loading instead of runtime-injected project docs.
25When coding, planning, debugging, testing, or reviewing, open project docs explicitly using this routing.
26
27**Always read:**
28
29- `docs/project-config.json` (project-specific paths, commands, modules, and workflow/test settings)
30- `docs/project-reference/docs-index-reference.md` (routes to the full `docs/project-reference/*` catalog)
31- `docs/project-reference/lessons.md` (always-on guardrails and anti-patterns)
32
33**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.
34
35**Situation-based docs:**
36
37- Project structure/architecture/tech-stack/deployment/setup (any layer — backend, frontend, or infra): `project-structure-reference.md`
38- Backend/CQRS/API/domain/entity changes: `backend-patterns-reference.md`, `domain-entities-reference.md`
39- Frontend/UI/styling/design-system: `frontend-patterns-reference.md`, `scss-styling-guide.md`, `design-system/README.md`
40- Spec authoring, `docs/specs/` pathing, or TC format: `feature-spec-reference.md`, `spec-system-reference.md`, `spec-principles.md`
41- Behavior/public-contract changes or spec-test-code sync: `workflow-spec-test-code-cycle-reference.md` plus the spec docs above
42- Derived spec indexes/ERDs/reimplementation guides: `spec-system-reference.md` and source Feature Specs under `docs/specs/`
43- Integration test implementation/review: `integration-test-reference.md`
44- E2E test implementation/review: `e2e-test-reference.md`
45- Code review/audit work: `code-review-rules.md` plus domain docs above based on changed files
46
47Do not read all docs blindly. Start from `docs-index-reference.md`, then open only relevant files for the task.
48
49<!-- CODEX:PROJECT-REFERENCE-LOADING:END -->
50
51<!-- PROMPT-ENHANCE:STEP-TASK-ANCHOR:START -->
52
53> **[BLOCKING]** Execute skill steps in declared order. NEVER skip, reorder, or merge steps without explicit user approval.
54> **[BLOCKING]** Before each step or sub-skill call, update task tracking: set `in_progress` when step starts, set `completed` when step ends.
55> **[BLOCKING]** Every completed/skipped step MUST include brief evidence or explicit skip reason.
56> **[BLOCKING]** If Task tools are unavailable, create and maintain an equivalent step-by-step plan tracker with the same status transitions.
57
58<!-- PROMPT-ENHANCE:STEP-TASK-ANCHOR:END -->
59
60## Quick Summary
61
62**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.
63
64**Summary:**
65
66- 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.
67- **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.
68- 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.
69- 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`.
70- 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.
71- 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.
72- 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.
73
74**Workflow:**
75
761. **Locate PBI Artifact** — find PBI + story files in `team-artifacts/pbis/`; read fully
772. **Extract UI Specs** — parse UI Layout/Wireframe, Components, States, Interaction Flow, Acceptance Criteria + priority/rank
78 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
793. **Load Design System** — baseline + matched per-app design tokens, colors, typography (NEW→canonical, REFACTOR→per-app)
80 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
81 3c. **Load Domain Entities** — entity fields, relationships, enums for realistic sample data
824. **Generate HTML** — one self-contained scripted clickable prototype + guided walkthrough matching the app's look and feel
835. **Save** — write `{pbi-filename}-mockup.html` beside the PBI artifact
846. **Report** — path, priority, stories, demo flows, components, states, fidelity + demo-quality verdicts
857. **[BLOCKING] Fidelity Validation** — mock-up matches inventoried UI (tokens/components/layout/connected flows); record PASS/FAIL
868. **[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
87
88**Key Rules:**
89
90- 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.
91- One HTML file per PBI (all stories shown as sections/tabs)
92- Plan the demo flows (Step 2b) BEFORE generating; sign off with the Demo-Quality gate (Step 8) AFTER
93- 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>`
94- Self-contained: inline CSS/JS, no external dependencies except Google Fonts
95- **Must resemble the project's current UI** — read existing component templates and page layouts
96- 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`
97- Match project design system: colors, typography, spacing, BEM naming
98- Use **real domain entity fields and realistic sample data** — not Lorem ipsum
99- Include component states (default, loading, empty, error)
100- Responsive layout with mobile/desktop preview
101- Save in same directory as the PBI artifact
102- **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.
103
104**Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).**
105
106# PBI HTML Mockup Generator
107
108Generate visual HTML mockup reports from PBI and user story artifacts.
109
110---
111
112## When to Use
113
114- After PBI and stories are finalized (reviewed, challenged, gated)
115- Before moving to implementation planning or design spec
116- When stakeholders need a visual preview of the feature
117- As the final step in `workflow-idea-to-pbi` and similar workflows
118
119**NOT for**: Implementing production UI (use `$feature-implement`), creating design specs (use `$design-spec`), or wireframing from scratch (use `$design-spec --mode=wireframe`).
120
121---
122
123## Quick Reference
124
125### Input
126
127| Source | Path |
128| --------------- | ------------------------------------------------------- |
129| PBI artifact | `team-artifacts/pbis/{YYMMDD}-pbi-{slug}.md` |
130| Story artifacts | `team-artifacts/pbis/stories/{YYMMDD}-us-{pbi-slug}.md` |
131| Explicit path | User provides path as argument |
132
133### Output
134
135| Type | Path |
136| ----------- | ---------------------------------------------- |
137| HTML mockup | `{same-dir-as-pbi}/{pbi-filename}-mockup.html` |
138
139### Related
140
141- **Input from:** `$refine`, `$story`
142- **Command:** `$pbi-mockup`
143- **Next Step:** `$prioritize`, `$design-spec`, `$plan`
144
145---
146
147## Detailed Workflow
148
149### Step 1: Locate PBI Artifact
150
1511. If argument provided, use it as path
1522. Otherwise, find most recent PBI: `Glob("team-artifacts/pbis/*-pbi-*.md")` sorted by modification time
1533. Read the PBI artifact fully
1544. Check for associated stories: `Glob("team-artifacts/pbis/stories/*-us-{pbi-slug}*.md")`
1555. Read all story artifacts if found
156
157### Step 2: Extract UI Specifications
158
159From the PBI and story artifacts, extract:
160
161| Section | What to Extract |
162| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
163| `## UI Layout` / `## UI Wireframe` | ASCII wireframe, layout description |
164| `### Components` | Component names, behaviors, tiers |
165| `### States` | Default, Loading, Empty, Error states |
166| `### Interaction Flow` | User actions and system responses |
167| `## Acceptance Criteria` | GIVEN/WHEN/THEN scenarios for context |
168| `## Description` | User role, capability, business value |
169| frontmatter `priority` / `rank` | PBI priority label + numeric rank — render in the header (Step 4). MANDATORY when present; the mockup MUST carry the same priority info as the backlog. |
170
171If no UI sections exist (backend-only PBI), inform user and skip mockup generation:
172
173> "This PBI has no UI sections (marked as backend-only). No mockup generated."
174
175### Step 2b: [BLOCKING] Plan the Demo Flows (think → plan → many todos BEFORE generating)
176
177> **[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.
178
1791. **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.
1802. **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.
1813. **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.
182
183> See `references/interactive-demo.md` §1 for the flow-spec schema + a worked example.
184
185### Step 3: Load Design System Context
186
1871. Read PBI `module` field from frontmatter
1882. Load design system docs dynamically (project-config.json + glob fallback). The HTML mock-up design must be based on these project reference design docs:
189 - **Mandatory baseline:** Read `docs/project-reference/design-system/README.md` and `docs/project-reference/design-system/design-system-canonical.md`
190 - **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.
191 - **Fallback:** `Glob("docs/project-reference/design-system/*.md")` → match module name against discovered file names (case-insensitive substring match)
192 - **Default:** If no match found, use `docs/project-reference/design-system/README.md`
193 - **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).
194
1953. Extract from design system docs (read enough of the canonical and matched per-app docs to apply the rules):
196 - **Colors:** Primary, secondary, accent, background, text colors
197 - **Typography:** Font families, sizes, weights
198 - **Spacing:** Margin/padding scale
199 - **Border radius:** Component roundness
200 - **Shadows:** Elevation levels
201
2024. Optionally read `docs/project-reference/scss-styling-guide.md` (first 100 lines) for BEM patterns
203
204### Step 3b: [BLOCKING] Inventory Existing UI + Map Connected Flows (match current system UI)
205
206> **[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.
207
208The mockup should resemble the project's actual UI, not generic HTML. Discover existing components AND map the flows that connect to this screen:
209
2101. 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
2112. Glob the project's shared component library (if exists):
212 - `Glob("**/libs/*common*/**/*.component.ts")` or `Glob("**/shared/**/*.component.ts")` — discover reusable components (buttons, tables, forms, dialogs, filters, status badges)
213 - Read 2-3 key component files to understand their HTML template structure and CSS class naming
2143. Glob the module's own components (if PBI module detected):
215 - Search for existing page components in the module to understand the current UI layout patterns
216 - Read 1-2 existing page templates to capture the actual look and feel (sidebar layout, toolbar patterns, card grids, etc.)
2174. Extract from discovered components:
218 - **Layout patterns:** Sidebar + content, full-width, split-panel, tabbed
219 - **Common components:** Table with pagination, filter bar, action buttons, status chips, breadcrumbs
220 - **Form patterns:** Form groups, validation display, multi-step forms
221 - **Navigation:** Tab bars, breadcrumbs, sidebar menus
2225. **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.
223
224> **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.
225
226### Step 3c: Load Domain Entity Context
227
228Use real domain entities and relationships for realistic mockup data:
229
2301. Read `docs/project-reference/domain-entities-reference.md` (if exists) — extract entities, fields, relationships for the PBI's module
2312. From the PBI artifact, extract referenced entities from `## Domain Context` section
2323. Use entity field names and types to generate **realistic sample data** in the mockup:
233 - Entity names → table column headers, form field labels
234 - Entity relationships → navigation links, dropdowns, nested displays
235 - Entity statuses/enums → status badges, filter options
236 - Date fields → realistic date values
237 - String fields → domain-appropriate sample text (customer names, invoice titles, etc.)
238
239> **Key principle:** Sample data should use actual entity field names and realistic domain values — not "Lorem ipsum" or "Item 1, Item 2".
240
241### Step 4: Generate HTML Mockup
242
243Generate a **single self-contained HTML file** with the following structure:
244
245```html
246<!DOCTYPE html>
247<html lang="en">
248 <head>
249 <meta charset="UTF-8" />
250 <meta name="viewport" content="width=device-width, initial-scale=1.0" />
251 <title>Mockup: {PBI Title}</title>
252 <link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet" />
253 <style>
254 /* Design system tokens as CSS variables */
255 /* Component styles matching project BEM conventions */
256 /* Responsive breakpoints */
257 /* Dark/light theme support */
258 </style>
259 </head>
260 <body>
261 <!-- PBI Header: title, description, metadata -->
262 <!-- Navigation tabs (one per story) -->
263 <!-- Story sections with mockup UI -->
264 <!-- Component state toggles (default/loading/empty/error) -->
265 <!-- Interactive prototype: screens/states + hotspots + demo control bar + explanation panel + "⚠ Simulated" banner -->
266 <script>
267 /* Tab navigation */
268 /* State toggles */
269 /* Theme toggle */
270 /* Responsive preview toggle */
271 /* Prototype engine: goTo(stateId) router + hotspots + simulated submit — see references/interactive-demo.md §2 */
272 /* Guided walkthrough: ▶ Play ⏭ Next ⏮ Prev ↺ Reset ⏏ Exit — see references/interactive-demo.md §3 */
273 </script>
274 </body>
275</html>
276```
277
278#### Interactive Prototype + Guided Walkthrough
279
280The 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:
281
2821. **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.
2832. **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`).
2843. **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`).
2854. **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`).
286
287> **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`).
288
289#### Design-Principles Build Constraints (real markup, not advice)
290
291The 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.
292
2931. **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.
2942. **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.
2953. **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.
2964. **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.
2975. **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.
2986. **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.
2997. **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.
3008. **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.
3019. **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).
30210. **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.
303
304#### HTML Structure Requirements
305
3061. **Header Section:**
307 - PBI ID and title
308 - Module badge
309 - **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.
310 - Story count summary
311 - Generation date
312
3132. **Navigation:**
314 - Tab bar with one tab per story (or section per PBI acceptance criteria)
315 - Active tab highlight using design system primary color
316
3173. **Story Panels:**
318 - Story title and description ("As a... I want... So that...")
319 - Visual mockup of the UI described in wireframe/layout sections
320 - Component placeholders with realistic sample data
321 - State toggle buttons (Default | Loading | Empty | Error)
322
3234. **Footer:**
324 - "Generated from PBI {ID}" attribution
325 - Link back to artifact path
326 - Generation timestamp
327
328#### Styling Rules
329
330- Base every visual decision on the loaded project reference design docs; cite the docs used in the generation notes when reporting the mock-up.
331- Use CSS custom properties (variables) from design system tokens
332- Follow BEM naming: `mockup__header`, `mockup__nav`, `mockup__panel`
333- Match the project's color palette, typography, and spacing
334- Include both light and dark theme (toggle button in header)
335- 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
336- Use realistic placeholder data (names, dates, numbers) — not "Lorem ipsum"
337
338#### Component Rendering
339
340Map wireframe components to HTML elements AND to their scripted demo interaction (the hotspot/transition that advances the flow — `references/interactive-demo.md §2`):
341
342| Wireframe Component | HTML Rendering | Demo Interaction (scripted/simulated) |
343| ------------------- | ------------------------------------------ | --------------------------------------------------------- |
344| Table/Grid | `<table>` with design system styles | Row click → `goTo` detail screen/state |
345| Form | `<form>` with labeled inputs | Submit → simulated success toast + in-memory row insert |
346| Button | `<button>` with primary/secondary variants | Hotspot → advances the demo to the next screen/state |
347| Card | `<div class="card">` with shadow | Card click → `goTo` the card's detail screen/state |
348| List | `<ul>` or data list | Item click → `goTo` selected-item screen/state |
349| Modal/Dialog | Overlay `<div>` (toggleable) | Trigger → open dialog state; confirm/cancel → `goTo` next |
350| Tab panel | Tab navigation with content panels | Tab → switch panel (no nav away) |
351| Search/Filter | Input with icon | Apply → simulated filtered result state |
352| Status badge | `<span>` with color coding | Non-interactive (illustrative state indicator) |
353| Empty state | Centered message with icon | Primary CTA → `goTo` the create/first-action screen/state |
354| Loading state | Skeleton placeholder or spinner | Transient → auto-advances to the loaded screen/state |
355| Error state | Error banner with message | Retry → `goTo` back to the prior screen/state |
356
357### Step 5: Save HTML File
358
359- **Path:** Same directory as the PBI artifact
360- **Name:** `{pbi-filename-without-ext}-mockup.html`
361- Example: `team-artifacts/pbis/260324-pbi-goal-tracking-mockup.html`
362
363### Step 6: Report to User
364
365After generation, output:
366
367```
368Mockup generated: {path}
369- PBI priority: {priority label} · Rank #{rank} (or "not yet prioritized")
370- Stories covered: {count}
371- Demo flows: {count} ({flow titles})
372- Components rendered: {list}
373- States included: {default, loading, empty, error}
374- Fidelity vs existing UI: PASS | FAIL
375- Demo quality: PASS | FAIL
376
377Open in browser to preview. Click highlighted hotspots or press ▶ Play to walk a flow. Use theme toggle for dark/light mode.
378```
379
380---
381
382### Step 7: [BLOCKING] Fidelity Validation — Mockup Matches Existing UI
383
384> **[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.
385
386Validate the produced mockup against the inventoried existing UI and record an explicit pass/fail:
387
3881. **Design tokens** — colors, typography, spacing match the project design system (Step 3).
3892. **Component patterns** — tables, forms, dialogs, status chips, and navigation reuse the existing component patterns (Step 3b), not generic HTML.
3903. **Layout/structure** — the screen layout matches the existing pages of the related feature (sidebar / toolbar / card-grid conventions).
3914. **Connected flows** — entry/exit navigation matches the connected feature flows mapped in Step 3b.
392
393Record the outcome in the Step 6 report:
394
395```
396Fidelity vs existing UI: PASS | FAIL — tokens / components / layout / flows matched? If FAIL: what diverged + the fix.
397```
398
399If **FAIL**, revise the mockup to match the existing UI and re-validate before handoff.
400
401---
402
403### Step 8: [BLOCKING] Demo-Quality Review Gate
404
405> **[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`.
406
407**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:
408
4090. **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.
4101. **Every main-story flow clicks end-to-end** — each flow's `steps[]` reach its `endState` via real hotspots; no path dead-ends.
4112. **No dead controls** — every button/hotspot advances the demo or is visibly disabled-with-tooltip.
4123. **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.
4134. **Opens offline standalone** — no external `<script src>`; Google Fonts CSS only; no JS console errors.
4145. **Real domain data** — screens/rows use real entity field names + realistic values, never Lorem ipsum.
4156. **iframe-safe** — works self-contained inside an `<iframe srcdoc>` sandbox (no parent-document or network dependency) so the deck can embed it.
416
417Record the outcome in the Step 6 report:
418
419```
420Demo 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.
421```
422
423If **FAIL**, fix the prototype (re-author from the flow-spec — cheap) and re-audit before handoff.
424
425---
426
427## Mockup Quality Checklist
428
429Before completing:
430
431- [ ] HTML file is self-contained (opens correctly without a server)
432- [ ] All stories from PBI are represented as sections/tabs
433- [ ] Every main-story flow (Step 2b) is rendered as a scripted clickable prototype with guided narration
434- [ ] Design is based on `design-system-canonical.md` plus the matched per-app design-system doc when available
435- [ ] Design system colors and typography match the project
436- [ ] Component states are toggleable (where defined in artifact)
437- [ ] 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)
438- [ ] Realistic placeholder data used (not Lorem ipsum)
439- [ ] PBI metadata shown in header (ID, title, module, date)
440- [ ] 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
441- [ ] File saved alongside the PBI artifact
442- [ ] Fidelity validation (Step 7) recorded PASS — mockup matches existing UI tokens, components, layout, and connected flows
443- [ ] Demo-Quality gate (Step 8) recorded PASS — every flow clicks end-to-end, no dead controls, narration + "⚠ Simulated" banner present, offline, iframe-safe
444- [ ] 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
445
446---
447
448## Edge Cases
449
450| Scenario | Handling |
451| --------------------------------- | ------------------------------------------------------- |
452| Backend-only PBI (no UI sections) | Skip mockup, inform user |
453| No stories yet (PBI only) | Generate HTML mock-up from PBI's UI Layout section only |
454| Multiple modules | Load primary module's design system |
455| No design system docs | Use sensible defaults (Inter font, neutral palette) |
456| Very large PBI (10+ stories) | Group stories into categories, use collapsible sections |
457
458---
459
460## Anti-Patterns
461
462| Anti-Pattern | Correct Approach |
463| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
464| Production-quality CSS framework | Simple inline CSS matching design tokens |
465| External dependencies (CDN libs) | Self-contained except Google Fonts |
466| Pixel-perfect implementation | Approximate visual representation |
467| Real backend/business logic (auth, live API, persistence) | Scripted/simulated prototype interactivity only — clickable nav, simulated transitions, guided demo; NO real business logic or data writes |
468| Dead / non-wired buttons | Every control either advances the demo or is visibly disabled-with-tooltip |
469| Lorem ipsum placeholder text | Realistic domain-specific sample data |
470
471---
472
473## Workflow Recommendation
474
475> **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:
476>
477> 1. **Activate `workflow-idea-to-pbi` workflow** (Recommended) — includes mockup as final step
478> 2. **Execute `$pbi-mockup` directly** — run this skill standalone on an existing PBI
479
480---
481
482## Next Steps
483
484**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:
485
486- **"$prioritize (Recommended)"** — Prioritize the PBI in the backlog
487- **"$design-spec"** — Create detailed design specification from mockup
488- **"$plan"** — Start implementation planning
489- **"Skip, continue manually"** — user decides
490
491> **[IMPORTANT]** Use task tracking to break ALL work into small tasks BEFORE starting.
492
493> **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).
494
495<!-- SYNC:existing-ui-research -->
496
497> **[BLOCKING] Understand the existing UI before you design or spec a new/updated screen.** Before producing any wireframe, mockup, screen design, or UI spec:
498>
499> 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).
500> 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.
501> 3. **Reuse before invent** — prefer existing components, patterns, and layout conventions; justify any new component against what already exists.
502> 4. **Record findings** — note the matched existing screens/components + connected flows in the artifact so downstream design faithfully matches the current UI system.
503>
504> **Skip ONLY** when the feature is backend-only (no UI) — state that explicitly.
505
506<!-- /SYNC:existing-ui-research -->
507
508<!-- SYNC:ui-ux-design-principles -->
509
510> **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`.
511>
512> **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.
513>
514> **1.0 Visual Hierarchy & Layout**
515>
516> - `UI-1.1` One focal point per screen. Two elements competing for first read → demote one.
517> - `UI-1.2` Signal order: size → weight → colour → position. Use the cheapest signal that works before adding another.
518> - `UI-1.3` Group by proximity, NEVER by border. Whitespace separates cleanly; boxes inside boxes do not.
519> - `UI-1.4` Align to a shared edge. Every unexplained indent reads as an accident.
520> - `UI-1.5` Design the empty, loading and error state FIRST. The full state is the easy one.
521>
522> **2.0 Typography**
523>
524> - `UI-2.1` Max 2 families, 3 weights each. More variety reads as inconsistency, not range.
525> - `UI-2.2` Body text 16px web, 17px mobile. NEVER below 14px for anything a user must read.
526> - `UI-2.3` Line length 45–75 characters. Constrain the measure, not the container.
527> - `UI-2.4` Leading scales inversely with size: 1.5 body, 1.1–1.2 display.
528> - `UI-2.5` Fixed type scale — 6 named steps shared with engineering. NEVER one-off sizes.
529>
530> **3.0 Colour & Contrast**
531>
532> - `UI-3.1` Contrast 4.5:1 text, 3:1 UI edges. Measure it — NEVER judge by eye on a bright screen.
533> - `UI-3.2` One accent, one job. An accent that is everywhere points at nothing.
534> - `UI-3.3` Colour NEVER carries meaning alone — pair it with an icon, label or position.
535> - `UI-3.4` Dark mode is NOT inverted light mode. Lift surfaces to signal elevation; soften pure-white text.
536>
537> **4.0 Spacing & Grid**
538>
539> - `UI-4.1` One spacing unit, multiplied — 4px or 8px base; every gap a multiple of it.
540> - `UI-4.2` Space belongs to the container, not the child. Use `gap`; reserve margins for exceptions.
541> - `UI-4.3` Tighter inside, looser between — inner padding always smaller than the gap to the next group.
542> - `UI-4.4` Breakpoints follow content, not devices. Break where the layout stops working.
543>
544> **5.0 Interaction & Feedback**
545>
546> - `UI-5.1` Every action gets a response under 100ms, even when the result takes longer.
547> - `UI-5.2` Specify all 5 states — default, hover, focus, active, disabled — plus loading where it applies.
548> - `UI-5.3` Prefer undo over confirmation. Confirm ONLY what cannot be reversed.
549> - `UI-5.4` Motion clarifies cause and effect: 150–250ms, ease-out, honours reduced-motion.
550> - `UI-5.5` Keep the visible focus ring. Restyle it if it clashes; NEVER remove it.
551>
552> **6.0 Navigation & IA**
553>
554> - `UI-6.1` Every screen answers: where am I, what's here, where next.
555> - `UI-6.2` Max 5 top-level destinations. Depth beats a crowded first level.
556> - `UI-6.3` Label by the user's word, not the internal one. Team vocabulary is not a taxonomy.
557> - `UI-6.4` Every state deserves a URL or a back path. Deep links and hardware back must land somewhere sensible.
558>
559> **7.0 Forms & Input**
560>
561> - `UI-7.1` Ask for less. Every field needs a reason it exists today.
562> - `UI-7.2` Labels stay visible. Placeholders are hints, NEVER labels.
563> - `UI-7.3` Validate on blur, not on keystroke. Errors sit next to the field and say how to fix it.
564> - `UI-7.4` Match keyboard to data type — correct input type, autocomplete and autocapitalise on every field.
565> - `UI-7.5` NEVER lose entered data. Preserve input across errors, navigation and refresh.
566>
567> **8.0 Mobile & Touch** _(mobile/touch surfaces)_
568>
569> - `UI-8.1` Hit target ≥44×44pt, 8px apart. The target may exceed the visible icon.
570> - `UI-8.2` Primary actions in the bottom third — that is where the thumb lives.
571> - `UI-8.3` Gestures are shortcuts, NEVER the only route. Anything swipeable is also tappable.
572> - `UI-8.4` Respect safe areas and the keyboard. Notch, home indicator and on-screen keyboard all steal space.
573>
574> **9.0 Speed & Perceived Speed**
575>
576> - `UI-9.1` Show structure before data — skeletons for known layouts, spinners only for unknown waits.
577> - `UI-9.2` Assume success optimistically. Update UI first, reconcile after, roll back visibly on failure.
578> - `UI-9.3` Reserve space for anything that loads. Images, ads and fonts must NEVER shift the layout.
579> - `UI-9.4` Design for the slow connection. Offline, timeout and retry are states, NOT edge cases.
580>
581> **Apply by role** — the clauses are one set; what you DO with them depends on the task:
582>
583> | Role | Obligation |
584> | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
585> | 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`) |
586> | 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`) |
587> | 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 |
588> | SCAN / document a UI system | Record where the PROJECT deliberately deviates, so the overriding doc becomes the recorded authority |
589>
590> **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.
591
592<!-- /SYNC:ui-ux-design-principles -->
593
594<!-- SYNC:ai-mistake-prevention -->
595
596> **AI Mistake Prevention** — Failure modes to avoid on every task:
597>
598> **Re-read files after context changes.** Context compaction, resume, or long-running work can make memory stale; verify current files before acting.
599> **Verify generated content against source evidence.** AI hallucinates APIs, names, claims, and document facts. Check the relevant source before documenting or referencing.
600> **Check downstream references before deleting or renaming.** Removing an artifact can stale docs, generated mirrors, configs, and callers; map references first.
601> **Trace the full impact chain after edits.** Changing a definition can miss derived outputs and consumers. Follow the affected chain before declaring done.
602> **Verify ALL affected outputs, not just the first.** One green check is not all green checks; validate every output surface the change can affect.
603> **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.
604> **Surface ambiguity before acting — don't pick silently.** Multiple valid interpretations require an explicit question or stated assumption with risk.
605> **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.
606> **Keep shared guidance role-relevant.** Universal guidance must help every receiving skill or agent; code-specific obligations belong only in code-specific protocols.
607
608<!-- /SYNC:ai-mistake-prevention -->
609
610<!-- SYNC:critical-thinking-mindset -->
611
612> **Critical Thinking Mindset** — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act.
613> **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.
614
615<!-- /SYNC:critical-thinking-mindset -->
616
617<!-- SYNC:critical-thinking-mindset:reminder -->
618
619**MUST ATTENTION** apply critical + sequential thinking — every claim needs appropriate traced evidence (`file:line` for repo/code claims; source URL or artifact section for research, product, content, and docs claims); confidence >80% to act, <60% DO NOT recommend. Anti-hallucination: never present guess as fact, admit uncertainty freely, cross-reference independently, stay skeptical of own confidence.
620
621<!-- /SYNC:critical-thinking-mindset:reminder -->
622
623<!-- SYNC:ai-mistake-prevention:reminder -->
624
625**MUST ATTENTION** apply AI mistake prevention — verify generated content against evidence, trace downstream references before deleting or renaming, verify all affected outputs, re-read files after context loss, and surface ambiguity before acting.
626
627<!-- /SYNC:ai-mistake-prevention:reminder -->
628
629<!-- SYNC:ui-ux-design-principles:reminder -->
630
631- **MUST ATTENTION** apply the 40 UI/UX Design Principles (`UI-1.1`–`UI-9.4`) to any user-facing surface: one focal point, proximity grouping, empty/loading/error designed FIRST (§1) · ≤2 families, 16px web / 17px mobile body, never <14px, 45–75ch, fixed 6-step scale (§2) · 4.5:1 text / 3:1 edges measured, one accent, colour never alone, dark mode ≠ inversion (§3) · one 4/8px unit, `gap` over margins, tighter-inside-looser-between, content-driven breakpoints (§4) · <100ms response, all 5 states, undo over confirm, 150–250ms ease-out honouring reduced-motion, visible focus ring (§5) · where-am-I/what's-here/where-next, ≤5 top-level destinations, user's words, URL or back path (§6) · fewer fields, visible labels, validate on blur, matched keyboard, NEVER lose input (§7) · ≥44×44pt targets 8px apart, bottom-third primaries, gestures never the only route, safe areas (§8) · structure before data, optimistic update with visible rollback, reserved space, slow-connection states (§9). Project design-system docs OUTRANK these clauses — a genuine conflict goes to the user, NEVER resolved silently. Cite every finding as `UI-<clause>` + `file:line`. Skip ONLY for changes with no user-facing surface, stated explicitly.
632
633<!-- /SYNC:ui-ux-design-principles:reminder -->
634
635<!-- PROMPT-ENHANCE:STEP-TASK-CLOSING:START -->
636
637## Prompt-Enhance Closing Anchors
638
639**IMPORTANT MUST ATTENTION** follow declared step order for this skill; NEVER skip, reorder, or merge steps without explicit user approval
640**IMPORTANT MUST ATTENTION** for every step/sub-skill call: set `in_progress` before execution, set `completed` after execution
641**IMPORTANT MUST ATTENTION** every skipped step MUST include explicit reason; every completed step MUST include concise evidence
642**IMPORTANT MUST ATTENTION** if Task tools unavailable, maintain an equivalent step-by-step plan tracker with synchronized statuses
643
644<!-- PROMPT-ENHANCE:STEP-TASK-CLOSING:END -->
645
646<!-- SYNC:project-protocol-overlay -->
647
648> **Project Protocol Overlay** — Before executing this skill, resolve any PROJECT overlay rules layered onto it: match this skill's name against the `Target` column of the project's skill-protocol index (`docs/project-reference/skill-protocols-reference.md` by default; a `referenceDocs` entry in `docs/project-config.json` overrides the path), taking the most specific matching tier ONLY — exact name > glob > `*`. **That precedence orders overlays against EACH OTHER, never against this skill.** Read ONLY the matched bodies, resolved as `<protocols-dir>/<Name>.md`; a row's Body link is display text, never a read path. A matched body that is missing or malformed is REPORTED and skipped — never reconstructed from the index Description. No index, or no match -> proceed with no overlay, silently. Full contract: `.claude/skills/project-skill-protocol/references/registry.md`.
649>
650> Overlays are **ADDITIVE ONLY**: they ADD rules on top of this skill's own protocol and NEVER replace, override, disable, or reinterpret a rule it already states — removing every overlay must return this skill to exactly its documented behavior. An overlay is a BRIEF, not an authority escalation: it can NEVER waive a workflow gate, git discipline, a review gate, or a user-confirmation gate. A genuine overlay-vs-skill conflict, or two equally-specific overlays that directly contradict -> surface both to the user; NEVER resolve silently.
651
652<!-- /SYNC:project-protocol-overlay -->
653
654<!-- SYNC:project-protocol-overlay:reminder -->
655
656**MUST ATTENTION** resolve project protocol overlays for this skill BEFORE executing — most specific matching tier only (exact > glob > `*`, which ranks overlays against each other, NEVER against this skill), read only matched bodies at `<protocols-dir>/<Name>.md`; a missing or malformed body is reported, never reconstructed. Overlays are ADDITIVE ONLY (they never replace this skill's own rules) and are a brief, NEVER an authority escalation; an equal-specificity contradiction goes to the user.
657
658<!-- /SYNC:project-protocol-overlay:reminder -->
659
660## Closing Reminders
661
662**IMPORTANT MUST ATTENTION Goal:** Give stakeholders a clickable, self-narrating MVP prototype of every story's main-flow UI — built from real domain data and the project's actual design system — before implementation begins, so layout/UX/flow/state gaps surface while changes are still cheap.
663
664**Protocols in force (concise digest of the SYNC/shared blocks this skill carries):**
665
666- **AI Mistake Prevention:** verify generated content against evidence, trace downstream references, verify all affected outputs, re-read after context loss, surface ambiguity.
667- **Critical Thinking:** MUST ATTENTION traced proof per claim, confidence >80% to act, NEVER guess.
668
669**IMPORTANT MUST ATTENTION** run ONLY on finalized PBIs/stories (reviewed, challenged, gated); for a backend-only PBI with no UI sections, SKIP generation and tell the user — never fabricate UI — why: a mock-up of an unfinished or UI-less PBI previews the wrong thing.
670**IMPORTANT MUST ATTENTION** run the FULL step pipeline in order — locate (1) → extract UI (2) → plan flows [BLOCKING] (2b) → load design system (3) → inventory existing UI [BLOCKING] (3b) → load domain entities (3c) → generate HTML (4) → save (5) → report (6) → fidelity validation [BLOCKING] (7) → demo-quality gate [BLOCKING] (8); NEVER skip the three BLOCKING gates (2b plan · 3b inventory + 7 fidelity · 8 demo-quality) — why: each guards a distinct failure (no plan → incomplete demo; no inventory/fidelity → generic-HTML mismatch; no demo-quality audit → dead controls ship).
671**IMPORTANT MUST ATTENTION** PLAN the demo flows BEFORE generating — Step 2b enumerates the PBI's main-story/MVP flows into flow-specs and task trackings one todo per flow; Step 8 [BLOCKING] Demo-Quality gate signs off AFTER — why: think → plan → many todos → generate → final review is the discipline that makes the prototype complete and click-through-verified.
672**IMPORTANT MUST ATTENTION** render each main-story flow as a **scripted clickable prototype** with guided narration (▶ Play · ⏭ Next · ⏮ Prev · ↺ Reset · ⏏ Exit), an explanation panel, and a visible "⚠ Simulated — illustrative data, no real actions are performed" banner; interactivity is **scripted/simulated only** (canned transitions) — NEVER real `fetch`/auth/persistence/backend; self-contained so it runs inside the deck's `<iframe srcdoc>` (mechanics: `references/interactive-demo.md §2–§4`) — why: a clickable prototype conveys behavior at the lowest cost, but a real backend breaks the offline preview-before-code purpose.
673**IMPORTANT MUST ATTENTION** emit exactly ONE self-contained HTML file per PBI (all stories as tabs/sections), inline CSS/JS, no external deps except Google Fonts, saved as `{pbi-filename}-mockup.html` beside the PBI artifact — why: stakeholders open one file with no server, no build step.
674
675**IMPORTANT MUST ATTENTION** the 40 UI/UX Design Principles (`UI-1.1`–`UI-9.4`) are BUILD CONSTRAINTS on the emitted HTML/CSS, not prose advice — build the empty/loading/error panels FIRST and make them toggleable (`UI-1.5`), emit all 5 interaction states as real CSS with a VISIBLE focus ring (`UI-5.2`, `UI-5.5`), real ≥44×44px touch targets 8px apart with bottom-third primaries in the mobile preview (`UI-8.1`, `UI-8.2`), reserved space so a state switch never shifts layout (`UI-9.3`), the 6-step type scale (`UI-2.5`) and ONE 4/8px spacing unit (`UI-4.1`) emitted as CSS variables with no one-off px values, and contrast MEASURED 4.5:1 text / 3:1 edges in both themes with colour never carrying meaning alone (`UI-3.1`, `UI-3.3`) — why: a mock-up that only describes these previews a quality the built UI will not have.
676
677**IMPORTANT MUST ATTENTION** render the PBI's priority in the header (priority label + numeric rank from frontmatter) whenever the PBI is prioritized — why: the mockup is a stakeholder-facing prototype and MUST carry the same priority info as the backlog, not just the title; downstream `feature-presentation` reuses it.
678
679**MANDATORY IMPORTANT MUST ATTENTION** break work into small todo tasks using task tracking BEFORE starting; add a final review todo to verify quality.
680**MANDATORY IMPORTANT MUST ATTENTION** validate route/next-step decisions with the user by asking the user directly — never auto-decide complexity for the user.
681
682**Domain rules this skill must not skip:**
683
684**IMPORTANT MUST ATTENTION** fidelity is the whole point — the mock-up must LOOK like the existing app: load the mandatory baseline + matched per-app design-system docs (NEW→`designSystem.canonicalDoc`, REFACTOR→matched `designSystem.appMappings` per-app doc), read real shared/module components for layout patterns — why: a generic-HTML mock-up previews a system that does not exist.
685**IMPORTANT MUST ATTENTION** populate with real domain entity field names and realistic sample data — NEVER Lorem ipsum or "Item 1, Item 2" — why: fake data hides the real layout/overflow/state gaps the preview exists to surface.
686**IMPORTANT MUST ATTENTION** render every defined component state (default/loading/empty/error) as a toggleable view — why: stakeholders must see how the UI degrades, not only the happy path.
687**IMPORTANT MUST ATTENTION** keep all accompanying prose/captions/notes tech-agnostic (business/observable terms, NOT framework or CSS class names) per the M1/M2 mandates in `.claude/skills/shared/sdd-artifact-contract.md`; the rendered HTML MAY use real class names internally (implementation, not prose) — why: tech-coupled descriptions break the spec-principles §3 contract while the rendered markup stays free to be concrete.
688**IMPORTANT MUST ATTENTION** read design-system docs, existing components, and domain-entities reference (`docs/project-reference/*`) BEFORE generating — grep/read 2-3 real components first — why: skipping the read produces a mock-up that looks nothing like the app.
689
690**IMPORTANT MUST ATTENTION** cite `file:line` evidence for every claim/finding (confidence >80% to act, <80% verify first) — NEVER speculate about entity fields, design tokens, or component patterns without reading the source — why: hallucinated fields and class names produce a misleading preview.
691
692**Anti-Rationalization:**
693
694| Evasion | Rebuttal |
695| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
696| "PBI looks ready, skip the gated/finalized check" | Run only on reviewed-and-gated PBIs. An unfinished PBI previews the wrong thing. |
697| "A static mockup is faster than a clickable one" | Static conveys layout only, not behavior — the user asked for an MVP demo. Render each flow as a scripted clickable prototype (regenerated from the §1 flow-spec — cheap). |
698| "Skip the flow planning, just generate" | Step 2b (flow-specs + one todo per flow) is BLOCKING; planning the journeys first is what makes the prototype complete and click-through-verifiable. |
699| "Wire it to a real endpoint so it feels real" | Interactivity is scripted/simulated only — canned transitions, illustrative data, "⚠ Simulated" banner. NO real `fetch`/auth/persistence/backend. |
700| "Lorem ipsum is faster" | Fake data hides real overflow/state gaps. Use real entity field names + realistic values. |
701| "Generic clean HTML is good enough" | Fidelity is the point — read design-system docs + 2-3 real components, mimic the actual UI. |
702| "Class names in the notes are fine" | Prose stays tech-agnostic (M1/M2). Real class names live in the rendered HTML, not captions. |
703| "Only need the default state" | Render every defined state (default/loading/empty/error) as toggleable. |
704| "Already know the entity fields" | Show `file:line` from the domain-entities reference. No proof = no read. |
705
706**[TASK-PLANNING]** Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using task tracking.
707
708**IMPORTANT MUST ATTENTION Goal:** clickable, self-narrating MVP prototype of every story's main-flow UI from real domain data + the actual design system, BEFORE implementation — so flow/UX/state gaps surface while cheap.
709**IMPORTANT MUST ATTENTION** PLAN flows first (Step 2b flow-specs + one todo per flow), then the Demo-Quality gate signs off (Step 8); each flow is a scripted clickable prototype with guided narration + "⚠ Simulated" banner — interactivity scripted/simulated only, NEVER real backend.
710**IMPORTANT MUST ATTENTION** ONE self-contained HTML per PBI (Google Fonts only), real domain data not Lorem ipsum, every component state toggleable, prose tech-agnostic (M1/M2).
711**IMPORTANT MUST ATTENTION** read design-system docs + real components + domain-entities reference first; cite `file:line` (>80% confidence) — NEVER guess fields or tokens.
712
713<!-- CODEX:SYNC-PROMPT-PROTOCOLS:START -->
714
715## Hookless Prompt Protocol Mirror (Auto-Synced)
716
717Source: `.claude/.ck.json` + `.claude/skills/shared/sync-inline-versions.md` (`:full` blocks) + `.claude/scripts/lib/hookless-prompt-protocol.cjs`
718
719## [WORKFLOW-EXECUTION-PROTOCOL] [BLOCKING] Workflow Execution Protocol — MANDATORY IMPORTANT MUST CRITICAL. Do not skip for any reason.
720
721**Generic portability boundary:** Reusable skills and protocol text stay project-neutral; project-specific conventions are discovered from docs/project-config.json and docs/project-reference/. Apply shared AI-SDD from `shared/sdd-artifact-contract.md`. Read `docs/project-config.json` and `docs/project-reference/docs-index-reference.md`, then open the project reference docs named there. For spec, test-case, behavior-change, public-contract, or `docs/specs/` work, route through the local spec docs named by the docs index: `feature-spec-reference.md`, `spec-system-reference.md`, `spec-principles.md`, and `workflow-spec-test-code-cycle-reference.md` when specs/tests/code must stay synchronized. If either file or a required reference doc is missing or stale, auto-run `$project-init` (or the narrow lower-level route such as `$project-config`, `$docs-init`, `$scan-all`, or `$scan --target=<key>`) before ordinary project-specific work. Any supported AI tool may execute when this shared context and local docs are available.
722
7231. **DETECT:** If the prompt starts with an explicit slash skill/workflow command, execute it directly. Otherwise match the prompt against the workflow catalog and skill list.
7242. **ANALYZE:** Choose the best option: execute directly, invoke a skill, activate a standard workflow, or compose a custom step combination.
7253. **AUTO-SELECT:** Pick the best option yourself. Do not ask the user to choose between direct execution, skill, standard workflow, or custom workflow.
7264. **ACTIVATE:** For a selected workflow, call `$start-workflow <workflowId>`; for a selected skill, invoke that skill; for a custom workflow, sequence custom steps directly; for direct execution, proceed with the task.
7275. **CREATE TASKS:** task tracking for ALL workflow/skill/custom steps before execution when the selected path has multiple steps.
7286. **PARALLELIZE:** Before executing the task list, tag each task `PAR` (independent inputs + write set disjoint from every other `PAR` task) or `SEQ` (name the blocking dependency), group `PAR` tasks into waves, declare the wave plan, and spawn each wave's sub-agents in ONE message — all-return barrier per wave, fan-out one level deep unless a sub-agent's own definition authorizes further fan-out. Sequential-by-default is a defect when tasks are independent; do not parallelize shared write targets, output-consuming tasks, trivial single-file work, ordering a skill or workflow explicitly fixes, or user-approval gates.
7297. **EXECUTE:** Advance per the **Workflow Step Advancement & Parallel Phases** rule in your context instructions — model-driven; a sub-agent completion advances a step identically to an inline call; a parallel-phase group is an all-return barrier (advance only after ALL members return, never serialize it)
730
731## Shared AI-SDD Protocol Markers
732
733Source: `.claude/skills/shared/sync-inline-versions.md`
734
735## SYNC:ai-sdd-artifact-contract
736
737> **AI-SDD Artifact Contract** — Shared spec-driven development rules stay portable and source-owned.
738>
739> 1. Keep reusable AI-SDD principles in `.claude`; put repository-specific paths, commands, owners, products, and formats in project config/reference docs.
740> 2. Preserve cycle: `spec -> plan -> tasks -> implement -> verify -> update spec/docs`.
741> 3. Trace every requirement or invariant through decision, task, TC/test, source evidence, and docs/spec update.
742> 4. Treat code-to-spec extraction as reference-only until accepted by the canonical spec owner.
743> 5. Any supported AI tool may plan, implement, review, or verify with synced context; using multiple tools is optional.
744> 6. Update `.claude` source first, then sync generated mirrors; do not manually edit `.agents`, `.codex`, or `AGENTS.md`. — why: mirrors are generated artifacts; hand-edits are overwritten on the next sync
745> 7. If `docs/project-config.json`, root instruction files, or a required project-reference doc is missing or stale, auto-run `$project-init` or the narrow lower-level route before ordinary project-specific work.
746>
747> **Active reference:** `shared/sdd-artifact-contract.md` in the active skills root.
748
749---
750
751## SYNC:ai-sdd-artifact-contract:reminder
752
753- **MANDATORY** Apply `shared/sdd-artifact-contract.md`; keep reusable AI-SDD in `.claude` and local rules in project docs.
754- **MANDATORY** Code-to-spec extraction is reference-only until canonical acceptance; any supported AI tool may execute with synced context.
755- **MANDATORY** Update `.claude` source before syncing generated mirrors; do not manually edit `.agents`, `.codex`, or `AGENTS.md`.
756- **MANDATORY** Missing or stale project config, root instruction files, or required reference docs route project-specific work through `$project-init` or the narrow setup route automatically.
757 **[TASK-PLANNING] [MANDATORY]** BEFORE executing any workflow or skill step, create/update task tracking for all planned steps, then keep it synchronized as each step starts/completes.
758
759## [LESSON-LEARNED-REMINDER] [BLOCKING] Task Planning & Continuous Improvement — MANDATORY. Do not skip.
760
761Break work into small tasks (task tracking) before starting. Add final task: "Analyze AI mistakes & lessons learned".
762
763**Extract lessons — ROOT CAUSE ONLY, not symptom fixes:**
764
7651. Name the FAILURE MODE (reasoning/assumption failure), not symptom — "assumed API existed without reading source" not "used wrong enum value".
7662. Generality test: does this failure mode apply to ≥3 contexts/codebases? If not, abstract one level up.
7673. Write as a universal rule — strip project-specific names/paths/classes. Useful on any codebase.
7684. Consolidate: multiple mistakes sharing one failure mode → ONE lesson.
7695. **Recurrence gate:** "Would this recur in future session WITHOUT this reminder?" — No → skip `$learn`.
7706. **Auto-fix gate:** "Could `$code-review`/`$code-simplifier`/`$security-review`/`$lint` catch this?" — Yes → improve review skill instead.
7717. BOTH gates pass → ask user to run `$learn`.
772 **[CRITICAL-THINKING-MINDSET]** Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act.
773 **Anti-hallucination principle:** 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.
774 **AI Attention principle (Primacy-Recency):** Put the 3 most critical rules at both top and bottom of long prompts/protocols so instruction adherence survives long context windows.
775 **Goal-driven execution:** Define success criteria first, loop until verified, and stop only when observable checks pass.
776 **Tests verify intent:** Tests must protect business rules/invariants and fail when the protected intent breaks, not only mirror current behavior.
777
778## Common AI Mistake Prevention (System Lessons)
779
780- **Re-read files after context compaction.** Edit requires prior Read in same context; compaction wipes read state. Re-read before editing.
781- **Grep for old terms after bulk replacements.** AI over-trusts find/replace completeness. Grep full repo after bulk edits for missed refs in docs/configs/catalogs.
782- **Check downstream references before deleting.** Deletions cascade doc/code staleness. Map referencing files before removal.
783- **After memory loss, check existing state before creating new.** Compaction wipes prior-work memory. Query current state to resume — never blindly duplicate.
784- **Verify AI-generated content against actual code.** AI hallucinates APIs, class names, method signatures. Grep to confirm existence before documenting/referencing.
785- **Trace full dependency chain after edits.** Changing a definition misses downstream consumers. Trace the full chain.
786- **When renaming, grep ALL consumer file types.** Some file types silently ignore missing refs (no compile error). Search code, templates, configs, generated files.
787- **Trace ALL code paths when verifying correctness.** Code existing ≠ code executing. Trace early exits, error branches, conditional skips — not just happy path.
788- **Update docs that embed canonical data when source changes.** Docs inlining derived data (workflows, schemas, configs) go stale silently. Update all embedding docs alongside source.
789- **Verify sub-agent results after context recovery.** Background agents may finish while parent compacted — grep-verify output, don't trust assumed completion.
790- **Cross-check full target list against sub-agent assignments.** Parallel sub-agents by category miss boundary items. Reconcile union of assignments against target list before proceeding.
791- **Sub-agents inherit knowledge only from their agent .md definition — use custom agent types, not built-in Explore.** Tool adoption = permission + knowledge + enforcement (numbered workflow step).
792- **Persist sub-agent findings incrementally, not as a final batch.** Long sub-agents hit cutoffs before final write — findings lost. Instruct append-per-section to report file.
793- **When debugging, ask "whose responsibility?" before fixing.** Trace caller (wrong data) vs callee (wrong handling). Fix at responsible layer — never patch symptom site.
794- **Test failure → record a provisional verdict before trace/edit, then investigate.** Use the full five-way taxonomy: SOURCE-WRONG (production violates intent), TEST-WRONG (assertion/setup is stale), TEST-NOT-OPTIMAL (valid but fragile or low-signal test), ENVIRONMENT-BLOCKED (external state prevents a verdict), or AMBIGUOUS (intent/evidence cannot choose safely). Then trace root cause and triangulate against the governing spec (`docs/specs/**` if one exists) AND source. NEVER weaken an assertion, add a skip, relax a timeout, or change source merely to force green.
795- **Grep ALL removed names after extraction/refactoring.** Primary file "done" ≠ secondary files clean. Grep entire scope for every removed symbol before declaring complete.
796- **Assume existing values are intentional — ask WHY before changing OR flagging one as a defect.** Pattern-matching as "wrong" skips context. Before changing or reporting any constant/limit/flag/cutoff: read comments, git blame, the CALLER's ordering (the guarantee that makes the value correct usually lives in code running immediately BEFORE the cited line), and 2+ sibling call sites of the same convention. A doc stating WHAT without WHY is missing rationale, not proof of a missing guard — and in a validation pass, an accurate `file:line` citation proves the transcription, never the defect.
797- **Verify ALL affected outputs, not just the first.** One build green ≠ all green. Multi-stack changes (backend/frontend/tests/docs) require verifying EVERY output.
798- **Evaluate fit before copying a nearby pattern.** Closest example ≠ matching preconditions — verify the new context shares the same constraints, base classes, scope, lifetime.
799- **Holistic-first debugging — resist nearest-attention trap.** Don't dive into first plausible cause. List EVERY precondition (config, env vars, paths, DB, endpoints, creds, versions, DI, data). Verify each against evidence (grep/query — not reasoning). Ask "what would falsify this?" — if nothing, it's not a hypothesis. Most expensive failure: going deeper in "obvious" layer while bug sits in layer never questioned.
800- **Surgical changes — apply the diff test (context-aware).** Two modes: (1) Bug fix → every line traces to the bug; no restyling; orphan cleanup only for imports YOUR changes made unused. (2) Review/enhancement → implement improvements AND announce as "Enhancement beyond main request: [what]". Never silently scope-creep. Diff test: "Would this line exist if I wasn't asked to do X?" — if no, delete or announce.
801- **Surface ambiguity before coding — don't pick silently.** Multiple valid interpretations → present each with effort: "[Request] could mean (1) [N h], (2) [N h]. Which matters?" List scope/format/volume/constraints assumptions first. If simpler path exists, say so. Never silently pick.
802- **[MANDATORY FIRST ACTION] ALWAYS activate a suitable skill or workflow BEFORE responding.** Match task against workflow catalog + skill list; invoke via skill invocation or `$start-workflow <workflowId>`. NEVER answer or write code before checking. Skip = protocol violation.
803- **Why-Review adversarial mindset — apply when reviewing any plan, decision, or design.** Default SKEPTIC not VALIDATOR: steel-man a rejected alternative, invert each stated reason ("what does it sacrifice?"), stress-test top 2-3 assumptions, run pre-mortem ("ships, fails in 3 months — what breaks?"), surface 1-2 alternatives author missed. Section presence ≠ quality; quality = causal reasoning + concrete mitigations + evidence, not "it's better" or "monitor closely".
804- **Front-load report-write in sub-agent prompts for large reviews.** Many-file sub-agents hit budget before final write — findings lost. Design prompts so: (1) report-write is first explicit deliverable, (2) append per-file/section (not batched), (3) scope bounded so reads don't exhaust budget. Truncated mid-sentence with no report file → spawn narrower scope, don't retry same prompt.
805- **After context compaction, re-verify all prior phase outcomes before continuing.** Summaries describe intent, not environment state (git index, filesystem, processes). On resume, FIRST audit: git status, re-read modified files, verify filesystem. Every "completed" claim is an untested hypothesis until evidence confirms.
806- **OOM/memory: check row count before row size.** Triage: (1) Unbounded query — no DB filter for trigger? Push filter to DB; eliminates OOM. (2) Large rows? Projection reduces proportionally. Row reduction > projection in ROI.
807- **Assert the outcome your system OWNS, never the intermediate state your INFRASTRUCTURE owns.** When testing anything asynchronous (queue/broker delivery, retries, background jobs, caches, replication), assert the final business/entity state. NEVER assert the delivery bookkeeping — consume/send status, attempt counts, last-error, row existence or counts in a broker, scheduler, or outbox/inbox table. That bookkeeping lives in shared infrastructure that ANY co-running process (a peer worker, a second replica, a leftover local container) can write, usually under a deterministic shared key, so the assertion silently tests the developer's environment instead of the system: green when run alone, flaky the instant anything else shares that broker + database. Gate question for every assertion: "would this hold no matter WHICH process did the work?" — if no, assert the converged data state instead. Corollary: process-local fault injection and in-process telemetry cannot gate work any process may perform — use them as stress amplifiers (arm → bounded window → disarm → assert convergence), never as preconditions.
808- **Keep domain concepts out of generic/shared/infrastructure layers.** Reusable layer (shared library, framework, infra module) must reference NO consumer-specific domain concept — tenant/customer/product IDs, business entities, feature rules. Leak compiles + runs → passes review silently while coupling the "reusable" layer to one consumer. Keep shared type domain-free; push domain fields/logic down into the consumer via subclass/composition. — why: a layer coupled to one consumer's domain is no longer reusable.
809
810<!-- CODEX:SYNC-PROMPT-PROTOCOLS:END -->