Skills for building AEM Edge Delivery Services sites — site creation, block development, content modeling, code review, testing, and page import.
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
EDS rules for block and site code that differ from general front-end practice. Follow the project's existing blocks, AGENTS.md and lint config for everything else. For a new block, a reference implementation from Block Collection (see block-collection-and-party) is a good start.
decorate(block))decorate(); load them when the block comes into view (IntersectionObserver) or on interaction, and reserve their space (e.g. aspect-ratio) so late content doesn't shift the layout.main > .section > div. Don't override them on the block. For outer layout such as a full-bleed background, style .{block-name}-container (the section) or .{block-name}-wrapper (the block's parent), not 100vw or calc(50% - 50vw). Don't reuse those class names inside the block.:root in styles/styles.css. Sites embedded with aem-embed load styles into a shadow root, so declare them on :root, :host there.loadDelayed() in scripts.js. Analytics and martech go in consented.js, which consent-check.js loads only after consent. Older projects may have delayed.js instead; follow what the project has.When the code works, test it with testing-blocks.
.tessl-plugin
skills
aem-block-library
aem-cli
aem-layout-view
block-collection-and-party
brand-setup
references
building-blocks
code-review
content-driven-development
references
content-modeling
create-site
da-auth
figma-to-content
find-test-content
generate-import-html
identify-page-structure
migrate-header
page-decomposition
page-import
preview-import
scrape-webpage
slicc-handoff
snowflake
assets
substrate
substrate-milo
examples
knowledge
scripts
testing-blocks
ue-component-model