content-driven-development

Coordinate content-first development workflows for AEM Edge Delivery Services tasks.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/mhaack/sewjaland --skill content-driven-development-mhaack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-driven-development
Source: https://github.com/mhaack/sewjaland/tree/main/.claude/skills/content-driven-development
Command: npx skills add https://github.com/mhaack/sewjaland --skill content-driven-development-mhaack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Content-driven development ensures code changes are tested against real content and realistic authoring patterns, preventing developer-only solutions that break in production.

Core Features & Use Cases

  • Orchestrates a content-first workflow across planning, modeling, content creation, and validation.
  • Guides end-to-end tasks from test content discovery to final acceptance before shipping.
  • Supports documentation and PR readiness through defined steps and artifacts.

Quick Start

Begin by identifying or creating representative test content and follow Steps 0 through 8 to validate, lint, test, and ship changes.

Frequently Asked Questions about content-driven-development

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

FAQPage Schema
What is content-driven development for AEM Edge Delivery Services?

It is a workflow that validates code changes against real content and realistic authoring patterns. This ensures AEM Edge Delivery Services modifications are tested with actual content structures, preventing solutions that break in production.

How do I validate AEM blocks using a content-first workflow?

Orchestrate a content-first workflow from test content discovery through modeling, test content creation, linting, testing, and final validation. This ensures code changes are validated against realistic authoring patterns before shipping.

How do I prepare a pull request for AEM Edge Delivery Services CSS and JS changes?

Follow defined content-first workflow steps from content discovery to final acceptance. This process generates documented artifacts and ensures CSS and JS changes are validated against real content before PR readiness.

Does content-driven development work for AEM core decoration and bug fixes?

Content-driven development applies to AEM core decoration, bug fixes, and CSS or JS work requiring content-driven validation. It enforces steps from content discovery and modeling to test content creation, linting, and testing.

What's the best way to test AEM Edge Delivery Services code against real content?

Use a content-first development workflow that discovers representative test content, models it, creates test content, and runs linting and testing before final validation and shipping.