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
Validate code changes and write maintainable tests in AEM Edge Delivery Services projects.
aem up (ports in git worktrees, serving ./content/, cleaning up stale ./content/ files that shadow remote .aem.page updates)Exercise the block in a real browser on the test content URL(s): every variant, mobile, tablet and desktop widths (e.g. 375px, 768px, 1200px), and every interaction. Use whatever tooling you have: browser/Playwright MCP tools, a throwaway Playwright script (delete it afterwards), or a manual browser.
Committed tests guard functional behavior so it doesn't silently regress. Write a test only when a wrong answer is plausible and costly to miss. 100% coverage is not the goal, and neither is a test per variant or per branch; a block with static decoration and no behavior may need no tests at all.
Use the project's test tools. Find them in package.json scripts, test config and existing tests, and follow their file locations and naming. Don't add a second framework. aem-boilerplate ships without one; if the project has no test setup, ask the user before adding one.
Browser (E2E) tests assert the block's functional behavior. Rules for E2E specs:
./content/drafts/).decorate() adds, or hardcoded authored copy; when you need a label, read it from the page at runtime. The block root class (.{block}) comes from aem.js and is stable.toHaveCSS, getComputedStyle), geometry (boundingBox), or screenshot comparisons (toHaveScreenshot).If package.json defines test scripts (the boilerplate has none), run them, including any new tests. E2E suites usually need the dev server (aem up) running.
aem up is running and check the port it logged (in a git worktree aem up uses a branch-hashed port, not 3000; see aem-cli)../content/ (e.g. content/drafts/my-block.html served at /drafts/my-block with no --html-folder flag). If testing a remote .aem.page update, make sure a stale file in ./content/ isn't shadowing that path..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