aem-skill-content-driven-development

Orchestrates content-first development workflows for AEM Edge Delivery Services blocks.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill aem-skill-content-driven-development-capella-hotel-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aem-skill-content-driven-development
Source: https://github.com/capella-hotel-group/capella-hotel-group-poc/tree/main/.github/skills/aem-skill-content-driven-development
Command: npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill aem-skill-content-driven-development-capella-hotel-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers often write AEM block code based on assumptions about content structure, leading to author-hostile content models, rework, and bugs discovered late. This Skill enforces a Content Driven Development workflow where test content and content models are established before any TypeScript or CSS code is written. ## Core Features & Use Cases - Eight-step orchestrated workflow: Starts the dev server with npm run start, analyzes requirements, designs content models, creates test content, implements, lints, validates, and ships with Conventional Commits. - Sub-skill coordination: Invokes aem-skill-content-modeling for table structure design, aem-skill-building-blocks for TypeScript/CSS implementation, and aem-skill-testing-blocks for browser validation. - Test content management: Supports CMS-hosted content or local .plain.html files in drafts/ for rapid iteration, with URL validation via curl. - Use Case: When asked to build a new hero block, the Skill first ensures a content model and accessible test URL exist, then guides implementation, linting, viewport validation, and PR creation with a preview link. ## Quick Start Ask the assistant to build or modify an AEM block using the content driven development workflow, starting with identifying test content before writing any code.

Frequently Asked Questions about aem-skill-content-driven-development

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

FAQPage Schema
How do I develop a new AEM Edge Delivery Services block?▼

Follow the Content Driven Development workflow: start the dev server with npm run start, design a content model, create or identify test content, then implement the block in src/blocks with TypeScript and CSS. Finish with lint checks, viewport validation, and a Conventional Commit on a feature branch.

What is Content Driven Development in AEM projects?▼

Content Driven Development is a workflow that requires identifying or creating real test content before writing any block code. It ensures content models are author-friendly and code is validated against actual content throughout development rather than after.

Can I test AEM blocks locally without CMS content?▼

Yes, create .plain.html files in the drafts/ folder following the section and block div structure, then preview them at localhost:3000/drafts/your-file. However, CMS content is required before creating a PR because preview links need real hosted content for PSI checks.

Why should I use npm run start instead of aem up?▼

npm run start wraps TypeScript watch compilation, Vite watch mode, and aem up in a single command. Running aem up alone skips TypeScript compilation, so changes in src/blocks would not be built into the served output.

When should I not use the Content Driven Development workflow?▼

Skip this workflow for documentation-only changes, configuration changes that do not affect authoring, and research tasks that involve no code modifications. It is designed specifically for code changes that need content validation.