use-case-pattern-page-builder

Generate templated Markdown pages for use-case patterns and update TOC.md and overview.md.

Updated Jul 13, 2022
One-click install
npx skills add https://github.com/AdobeDocs/blueprints-learn.zh-Hans --skill use-case-pattern-page-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-case-pattern-page-builder
Source: https://github.com/AdobeDocs/blueprints-learn.zh-Hans/tree/main/.claude/skills/use-case-pattern-page-builder
Command: npx skills add https://github.com/AdobeDocs/blueprints-learn.zh-Hans --skill use-case-pattern-page-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a guided workflow to create new use-case pattern content for the Adobe Experience Platform Blueprint repository. It streamlines collecting required pattern details, generating Markdown content with the correct templates, and updating cross-reference pages like TOC.md and overview.md.

Core Features & Use Cases

  • Template-driven generation: Collects pattern information and produces Markdown pages that conform to the standard use-case pattern template.
  • Cross-link updates: Automatically updates TOC.md and overview.md to reflect new patterns and ensure discoverability.
  • Reference-driven design: Reads reference templates and checklists to enforce consistent structure and fields.

Quick Start

Prompt the user for all required pattern details and execute the content generation pipeline to create the new Markdown page and update related references.

Frequently Asked Questions about use-case-pattern-page-builder

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

FAQPage Schema
How do I automate use-case pattern documentation creation for Markdown pages?

To automate use-case pattern content creation, this skill collects required pattern details and generates Markdown pages using reference templates. It enforces frontmatter integrity, applies standard template structures, and automatically updates cross-references in TOC.md and overview.md.

What is the best way to keep TOC.md and overview.md in sync when adding new documentation patterns?

Keeping TOC.md and overview.md in sync requires automated cross-linking updates during the build process. When a new pattern page is generated, the system automatically updates these cross-reference files to ensure the new documentation remains discoverable and structurally consistent.

How do I enforce frontmatter integrity and template structure in generated Markdown documentation?

Enforcing frontmatter integrity in Markdown documentation relies on a reference-driven design that reads template checklists during generation. This ensures every new use-case pattern page conforms to the required metadata fields and standard structural layout before it is committed.

What information do I need to provide to generate a new use-case pattern page?

Generating a use-case pattern page requires providing specific pattern details through a guided workflow prompt. The system collects the necessary metadata inputs, validates them against reference checklists, and then executes the content generation pipeline to produce the final Markdown file.

Does this documentation automation work for repositories outside of Adobe Experience Platform Blueprints?

This automation is designed for documentation workflows that add patterns and keep TOC.md and overview.md in sync. While built for Adobe Experience Platform Blueprint repositories, the template-driven Markdown generation and cross-linking logic can apply to any similar pattern documentation structure.