content-driven-development

Guide AEM Edge Delivery Services development through an 8-step content-first workflow.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/Permit-Junction/permitjunction-website --skill content-driven-development-permit-junction
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: content-driven-development
Source: https://github.com/Permit-Junction/permitjunction-website/tree/main/.claude/skills/content-driven-development
Command: npx skills add https://github.com/Permit-Junction/permitjunction-website --skill content-driven-development-permit-junction

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all AEM Edge Delivery Services development is built against real content, leading to more author-friendly content models and robust, validated code.

Core Features & Use Cases

  • Content-First Workflow: Prioritizes identifying or creating test content before writing any code.
  • Structured Development Process: Guides developers through a step-by-step process including analysis, content modeling, implementation, and validation.
  • Use Case: When developing a new AEM block, this Skill ensures you first define or find the content that block will display, preventing rework and ensuring author usability.

Quick Start

Use the content-driven-development skill to start a new AEM block development task.

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?▼

Content-driven development for AEM Edge Delivery Services is a workflow mandating content identification or creation before code implementation, ensuring author-friendly content models and validated code.

How do I build a new AEM block using a content-first workflow?▼

To build a new AEM block, define or create the test content the block will display first, then implement CSS and JavaScript through an 8-step structured development process.

Why should I define AEM content models before writing code?▼

Defining AEM content models before writing code prevents development rework by ensuring the final implementation is built against real content and remains author-friendly.

Does this content-driven development workflow support bug fixes and CSS modifications?▼

Yes, this content-driven development workflow supports new blocks, modifications, bug fixes, and CSS/JavaScript work by validating all code changes against real content.

Can I use this structured development process for AEM blocks without test content?▼

No, you must identify or create test content prior to implementation, as the workflow mandates content creation first to validate author-friendly AEM content models.