html-spec-review

Validates consistency between HTML bundle prototypes and markdown planning documents, then applies safe patches.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dadafinger/dadafinger-skills --skill html-spec-review-dadafinger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: html-spec-review
Source: https://github.com/dadafinger/dadafinger-skills/tree/main/proprium/cursor/skills/html-spec-review
Command: npx skills add https://github.com/dadafinger/dadafinger-skills --skill html-spec-review-dadafinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? HTML prototype bundles and their markdown planning documents often drift out of sync, making it unclear which version is the source of truth. This Skill decodes the bundle, compares it 1:1 against the markdown spec, and safely patches only the confirmed differences. ## Core Features & Use Cases - Read-only triage: Decodes the gzip+base64 babel JSX bundle from the manifest, cross-checks every markdown claim against the actual build, and reports a match table plus mismatch count. - Fork and stale-version detection: Flags footguns such as forked copies or outdated builds before any change is made. - Surgical patching: After the user decides which side is correct, it backs up the live HTML, re-encodes only the changed assets, verifies with a babel round-trip, and syncs the markdown. - Use Case: A planner asks whether the prototype matches the spec document; the Skill produces a discrepancy report, then patches the live HTML once the user confirms the correct version. ## Quick Start Ask the assistant to check whether the HTML bundle matches the markdown planning document and fix any confirmed differences.

Frequently Asked Questions about html-spec-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if an HTML prototype matches its planning document?▼

Run the review to decode the bundle's gzip+base64 babel JSX from the manifest and compare every markdown claim against the actual build. It returns a match table with a count of discrepancies for your decision.

How to safely patch a live HTML bundle without breaking it?▼

The Skill backs up the live HTML first, re-encodes only the changed assets, and verifies integrity with a babel round-trip check. Only differences you explicitly confirm as correct are patched.

Does this review modify files during the initial check?▼

No, the first phase is strictly read-only triage. It decodes the bundle, builds the comparison report, and asks you to decide which side is correct before any patching occurs.

What is the difference between html-spec-review and figma-spec-review?▼

html-spec-review checks consistency between HTML bundles and markdown planning documents, while figma-spec-review validates Figma node specifications. Use the one matching your artifact type.

Why does the review warn about forks or outdated versions?▼

Forked copies or stale builds are common footguns that make comparisons meaningless. The triage phase detects these conditions so you do not patch against the wrong baseline.