page-decomposition

Identify content sequences and breaking points within page sections.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/paul-hosking-cdw-com/da-with-ue-demo --skill page-decomposition-paul-hosking-cdw-com
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: page-decomposition
Source: https://github.com/paul-hosking-cdw-com/da-with-ue-demo/tree/main/.claude/skills/page-decomposition
Command: npx skills add https://github.com/paul-hosking-cdw-com/da-with-ue-demo --skill page-decomposition-paul-hosking-cdw-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a single page section to identify content sequences and breaking points, producing neutral descriptions that avoid assigning specific block names for AEM Edge Delivery Services.

Core Features & Use Cases

  • Identifies content sequences within a section from top to bottom and marks where the pattern changes.
  • Produces neutral, non-naming descriptions to inform authoring decisions and downstream tooling (block inventory, content modeling).
  • Designed to be invoked per section during page import to support incremental page assembly and debugging.

Quick Start

Supply the target section's screenshot and cleaned HTML for analysis.

Frequently Asked Questions about page-decomposition

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

FAQPage Schema
How do I break down AEM page sections into neutral content sequences?

To break down AEM page sections, you analyze each section's visuals and clean HTML to identify content sequences from top to bottom, outputting neutral descriptions that avoid assigning specific block names.

What inputs do I need to analyze content structure for AEM Edge Delivery page imports?

Analyzing content structure for AEM Edge Delivery page imports requires section screenshots to establish boundaries and cleaned HTML input to accurately identify sequences and breaking points for neutral descriptions.

Why use neutral descriptions instead of block names when analyzing AEM page sections?

Neutral descriptions avoid premature block naming during page import, enabling better authoring decisions and supporting downstream tooling like block inventory and content modeling for AEM Edge Delivery Services.

Can I use section decomposition for incremental page assembly and debugging in AEM?

Yes, section decomposition is designed to be invoked per section during page import, supporting incremental page assembly and debugging by identifying content sequences and breaking points within individual sections.

Does section analysis work with specific block identification for AEM Edge Delivery Services?

Section analysis produces neutral descriptions that inform later block identification, allowing downstream tooling and block inventory processes to assign specific block names based on the identified content sequences and breaking points.