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
Read a Figma frame, assemble a page from EDS blocks and default content, and publish it to Document Authoring. Runs with a Figma MCP (to read the design) and a DA IMS token (to write content) — no proprietary tooling required.
This skill orchestrates existing skills; it does not reimplement DA rules, block knowledge, or block-building. Invoke those skills — do not inline them. The condensed rules quoted in this file are pointers to jog the right skill, never a substitute for loading it: when a phase names a skill, invoke it and work from its actual guidance. Running this file as a self-contained procedure — hand-writing blocks, authoring DA HTML from memory, skipping the browser/visual check — is the single most common way a run goes wrong. Phase 2.3 turns the confirmed plan into an explicit manifest of the sub-skills you must invoke.
Classify each section of the design, then follow the matching path:
A single design usually mixes all three (known blocks + default content + one or two new blocks).
| For | Use skill |
|---|---|
DA IMS token (DA_TOKEN) | da-auth |
| DA body-fragment HTML rules, Source API, preview/publish, media | da-content |
| Whether a block exists + its authoring model & examples | block-collection-and-party |
| Surveying the whole available block palette | identify-page-structure (Step 2.5) |
| Designing a content model for a new block | content-modeling |
| Building a new block (full dev workflow) | content-driven-development (invokes building-blocks, testing-blocks) |
| Rendering a block + visual comparison to the design (the reuse gate) | testing-blocks (browser/Playwright screenshot + "compare implementation to design") |
The DA-write contract in Phase 5 is the same one da-content documents
(see its SKILL.md).
blocks/, and required for the content+code path to
add block code). Its GitHub {owner}/{repo} and the deploy {branch}.daOrg, daRepo (the DA namespace), page PATH (no
extension, lowercase/dash only). In the
standard EDS+DA setup daOrg/daRepo equal the GitHub {owner}/{repo};
confirm, because Phase 5 writes to daOrg/daRepo but previews/renders on
the GitHub {owner}/{repo}/{branch}.DA_TOKEN — via da-auth, whose helper caches it at
~/.aem/da-token.json (expires_at in epoch ms; lifetime varies). Prefer a
$DA_TOKEN already set in this session; read the cache file only if that's
unset. Two distinct failures: a 401 means the token is missing, invalid or
expired → re-auth (da-auth); a
cache file that can't be read because the execution sandbox has no $HOME
access means the token is unreachable, not expired (see Phase 0 step 3) —
don't conflate them.From here to Phase 5 this file is the outline. The text of each phase is in references/, in the file the phase names. Read that file in full when you reach the phase; never work from a heading alone. The Guardrails at the end apply in every phase.
Read references/phase-0-preflight.md in full before you act on this section.
Read references/phase-1-read-figma.md in full before you act on this section.
Read references/phase-2-resolve.md in full before you act on this section. It covers: 2.0 — Know the project's block palette; 2.1 — Resolve each section; 2.2 — Confirm the plan before deploying; 2.3 — Lock the orchestration manifest.
Read references/phase-3-blocks.md in full before you act on this section.
Read references/phase-3-blocks.md in full before you act on this section.
Read references/phase-3-blocks.md in full before you act on this section.
Read references/phase-4-da-html.md in full before you act on this section.
Read references/phase-5-deploy.md in full before you act on this section. It covers: Pre-publish gate — the page is not "done" until every box is checked; Publish to the live host — the FINAL step, gated on the checklist.
https://da.live/edit#/$DA_ORG/$DA_REPO/$Phttps://$BRANCH_HOST--$GH_REPO--$GH_OWNER.aem.page/$Phttps://$BRANCH_HOST--$GH_REPO--$GH_OWNER.aem.live/$Pblocks/<existing>/*), scripts.js, or
head.html to make it match a design, and never add per-section or
block-specific rules to global CSS — build a new isolated block instead.
Allowed, and expected once per project: retargeting the global design
tokens — the :root custom properties and base typography/button styling
in styles/styles.css — to the design system. That token retheme is how a
reused block picks up the design's palette/type; restyling a specific
existing block is not (→ new block).content.da.live) is the
working default (it internalizes to the media bus at preview and supports
cross-page reuse); external sideloaded URLs remain supported. Confirm the
default for v1.0.0.Optional enhancement (not required for v1.0.0):
.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