frontend-harness-slides

Frontend Harness Slides

Build HTML slides that survive iteration. This skill does not provide a starter project or require React, Vite, Tailwind, Playwright, or any other stack. Its unit is the harness contract: stable frame address, registry, fixed stage, frozen mode, audit surface, visual checks, and verified handoff.

PRE-BUILD ALIGNMENT HARD GATE

Before creating or modifying any HTML slide artifact, this is a hard gate. DO NOT create files, scaffold a project, write code, start a dev server, or begin implementation until the user has explicitly confirmed the Pre-Build Alignment in plain text.

Demand alignment is the first deliverable. Understand what the user is trying to accomplish, who will consume the deck, what the deck should include or exclude, and what outcome the presentation should drive. Walk the decision tree one branch at a time: purpose and audience, content boundary and story, presentation format and density, style and motion, then deck root, build, testing, and delivery. For each unresolved branch, ask a plain-text question with a recommended answer and rationale. If the answer can be found by reading source material, an existing deck, a repository, a deployed URL, or project files, inspect that source first and present the inference instead of asking a generic question. Keep each round focused on the next highest-impact decision; group low-risk execution confirmations only when that reduces back-and-forth without hiding uncertainty. Implementation begins only after the user confirms the final shared understanding.

Treat Pre-Build Alignment as focused, lightweight grilling-style alignment: explore discoverable facts first, challenge a vague brief when assumptions are unclear, expose the highest-impact tradeoffs, and keep moving toward a shared understanding the user can confirm. Do not turn the intake into a checklist dump or a form. Related low-risk confirmations can be grouped, but each key question still needs a recommended answer, rationale, and impact.