blueprint-document-reference

Blueprint reference documents require explicit frontmatter fields including title, description, solution, and exl-id to ensure discoverability and alignment with Experience League patterns. These standardized fields maintain consistency across documentation teams.

To structure a blueprint scenario reference, include sections for Applications, Use cases, Prerequisites, Architecture Diagram, Guardrails, and Related documentation. Follow the Reference.md guidance to ensure consistent body content and alignment with Experience League patterns.

The difference between an overview hub and a scenario blueprint lies in their scope. This Skill provides reusable templates and distinct structural guidance for both hub/overview pages and individual scenario blueprint references to ensure proper content discoverability.

Standardize documentation across multiple blueprint pages by enforcing consistent frontmatter fields and structured body sections. Use the SKILL.md as the canonical entry point and apply Reference.md guidance to maintain alignment across teams and Experience League links.

Yes, an exl-id is required. Blueprint reference documents must include explicit frontmatter fields, including the exl-id, to ensure discoverability and proper alignment with Experience League documentation patterns.

A blueprint reference template should include sections for Applications, Use cases, Prerequisites, Architecture Diagram, Guardrails, and Related documentation. This structure ensures comprehensive coverage and consistency for Experience League documentation.