Name: design md evidence extractor
Availability: InStock
Author: Agensi

See it in action

You say

Extract an evidence-backed DESIGN.md from https://example.com using the homepage, pricing page, and one product page. Do not copy text or images. Save the result under ./output and tell me whether coverage is READY or PARTIAL.

Your agent does

Creates ./output/DESIGN.md, design-tokens.json, extraction-evidence.json, coverage-report.md, and rebuild-brief.md. The coverage report states READY, PARTIAL, or BLOCKED with a score, missing groups, conflicts, warnings, and the next safe capture action. Every proposed token keeps page-level provenance in extraction-evidence.json.

About this skill

Design.md Evidence Extractor is built for frontend developers, agencies, design-system teams, and AI coding workflows that need more than a guessed palette. Its Evidence-Lock Extraction Pipeline captures rendered computed styles from representative pages, preserves page-level provenance, detects conflicting variables and component variants, scores coverage, and compiles a five-file design intelligence pack. The output includes DESIGN.md, normalized design tokens, an evidence ledger, a coverage report, and a rebuild brief. Thin pages, blocked stylesheets, bot challenges, missing states, and inconsistent themes are not hidden: the skill returns READY, PARTIAL, or BLOCKED with a specific recovery path. It intentionally excludes page copy, cookies, form values, images, logos, proprietary scripts, and other source assets. Use it to document a legacy UI, create an authorized migration baseline, prepare agent-ready visual context, compare page families, or reduce unsupported design guesses before implementation.