content-driven-development
Audited by Runlayer on Feb 25, 2026
Malicious tool definition detected
Tool: SKILL.md [1/3] Description: --- name: content-driven-development description: Apply a Content Driven Development process to AEM Edge Delivery Services development. Use for ALL code changes - new blocks, block modifications, CSS styling, bug fixes, core functionality (scripts.js, styles, etc.), or any JavaScript/CSS work that needs validation.
Tool: SKILL.md [2/3] Description: -w "%{http_code}" http://localhost:3000/path` 3.
Tool: SKILL.md [3/3]
Malicious tool definition detected
Tool: resources/cdd-philosophy.md Description: # Why Content-First Matters Content Driven Development isn't just a process—it's a philosophy that prioritizes author needs and content reality over developer convenience.
Malicious tool definition detected
Tool: resources/html-structure.md [1/2] Description: # HTML File Structure for Test Content When creating local `.plain.html` files for testing blocks in the `drafts/` folder, follow this structure to match how AEM Edge Delivery Services processes authored content.
Tool: resources/html-structure.md [2/2] Description: provide WebP format with fallbacks - Use `media` attributes for responsive breakpoints (typically `(min-width: 600px)` for desktop) - Include width query parameters (`?width=750` for mobile, `?width=2000` for desktop) - Add `format` and `optimize=medium` parameters for image optimization - The final `<img>` element is the fallback - Always include `alt` attribute for accessibility - Use `loading="lazy"` for images below the fold, `loading="eag