AdobeDocs
Official@adobedocs
Adobe Open Source Documentation
Agent Skills by AdobeDocs
Showing 7 vetted skills indexed across 4 GitHub repositories.
AdobeDocsuse-case-pattern-page-builder
Generate templated Markdown pages for use-case patterns and update TOC.md and overview.md.
AdobeDocsarchitecture-diagram-page-builder
Create architecture diagram pages with templates and TOC integration for Adobe Experience Platform Blueprint.
AdobeDocsremove-preview-highlighting
Remove preview-only markup and wrappers from Workfront Markdown documents.
AdobeDocsindustry-use-case-builder
Automate Adobe Experience Platform Blueprints use-case creation across industries.
AdobeDocsuse-case-pattern-builder
Automates creation of use-case pattern Markdown files and updates cross-links in Adobe Blueprints repositories.
AdobeDocsuse-case-icon-generator
Generate icon specifications and image-generation prompts for industry use cases.
AdobeDocsblueprint-document-reference
Standardize blueprint reference documents with explicit frontmatter and structured sections.
Frequently Asked Questions About AdobeDocs
FAQPage SchemaWhat specific documentation tasks does AdobeDocs enable?▼
AdobeDocs enables the systematic generation of architecture diagram pages, standardized blueprint references, and industry-specific use-case patterns. It facilitates the maintenance of technical documentation by updating tables of contents, cross-linking related files, and ensuring consistent frontmatter across large-scale enterprise repositories.
Which technical personas benefit from these documentation utilities?▼
Technical writers, enterprise architects, and documentation engineers working within the Adobe Experience Platform ecosystem are the primary users. These utilities assist those responsible for maintaining complex technical specifications, architecture diagrams, and industry-aligned use-case documentation at scale.
What are the prerequisites for implementing these documentation builders?▼
Implementation requires a repository environment structured for Adobe Experience Platform blueprints. Users must ensure their source files utilize standard Markdown formatting and adhere to the expected frontmatter schemas required by the blueprint-document-reference and page-builder utilities to ensure successful TOC integration and cross-link updates.