design-docs-agent

Automating design token extraction from article HTML involves orchestrating parallel waves for CSS tokens, page structure, charts, and icons. The process merges these outputs into a single machine-readable config with strict frontmatter metadata and type-safety validation.

Generating TypeScript constants from raw HTML requires ingesting the article content, extracting structural and styling data in parallel waves, and validating the merged output for type-safety. This ensures brand-wide consistency across generated production-ready code artifacts.

Validating frontmatter metadata for machine-readable design docs requires strict type-safety checks during the ingestion pipeline. The system enforces frontmatter-driven metadata rules while merging parallel extraction outputs into a unified ARTICLES config entry.

Yes, you can orchestrate parallel extraction waves for charts and icons by providing an optional local HTML path alongside the article URL. The pipeline coordinates extraction, merges results, and triggers generation and verification steps automatically.

The design docs pipeline supports pre-flight audits and delta reporting for brand syncs directly within its orchestration workflow. It ensures brand-wide consistency across 15 tabs by validating type-safety and wiring brand pages during the generation phase.

HTML to TypeScript design doc pipelines fail type-safety validation when frontmatter metadata is missing or inconsistent. The orchestration process enforces strict frontmatter-driven metadata rules and validates generated TypeScript constants before merging them into the final config.