Skills for building AEM Edge Delivery Services sites — block development, content modeling, code review, testing, and page import.
82
76%
Does it follow best practices?
Impact
88%
1.04xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
CSS block scoping and custom properties
Block selector scoping
0%
100%
No unscoped selectors
100%
100%
CSS custom properties for color
100%
100%
CSS custom properties for typography
100%
100%
Mobile-first default styles
100%
100%
Modern media query syntax
0%
100%
Standard breakpoints
100%
100%
No !important usage
100%
100%
Variant CSS pattern
50%
100%
No -wrapper/-container suffix inside block
100%
100%
Gap over margin hacks
100%
100%
No hardcoded font families
100%
100%
JavaScript block decoration patterns
Default export decorate
100%
100%
JSDoc comment on decorate
0%
0%
Scoped DOM queries
100%
100%
No innerHTML for structures
100%
100%
Element reuse not recreation
100%
100%
No orphaned elements
100%
100%
Import .js extensions
100%
100%
Single quotes for strings
100%
100%
camelCase identifiers
100%
100%
No global DOM mutation
100%
100%
variant check via classList
100%
100%
ES6+ syntax
100%
100%
Block file structure and performance patterns
Correct directory path
100%
100%
Correct CSS file path
100%
100%
IntersectionObserver for lazy load
100%
100%
Observer disconnect after trigger
100%
100%
Minimal initial decoration
100%
100%
Dynamic import for heavy module
100%
100%
aem.js imports with .js extension
100%
100%
aem.js not modified
100%
100%
async decorate function
0%
100%
Default export decorate
100%
100%
Error handling on fetch
100%
100%
Bug clearly restated
100%
70%
Root cause analysis
93%
53%
Expected behavior defined
100%
83%
Reproduction criteria
70%
30%
Edge cases identified
66%
66%
Cross-browser scope
100%
100%
No premature solution
80%
40%
Responsive behavior considered
50%
87%
Definition of done is testable
62%
62%
Regression prevention
60%
40%
Variant behavior clearly defined
100%
100%
Video attributes specified
100%
100%
Mobile fallback addressed
100%
100%
Impact on existing variant assessed
100%
80%
Edge cases identified
58%
58%
Responsive behavior specified
70%
100%
Author experience documented
100%
100%
Accessibility considered
100%
0%
Definition of done is testable
100%
87%
Functional requirements listed
100%
100%
Pricing toggle addressed
80%
100%
Edge cases identified
60%
80%
Responsive behavior specified
75%
100%
Author experience documented
66%
100%
No premature implementation details
70%
100%
Definition of done is testable
70%
90%
Ambiguities flagged
0%
50%
Structured format used
87%
100%
Table of Contents