feat(aem): add figma-to-content skill for EDS page migration from Figma - #305
Draft
hmehta-adobe wants to merge 2 commits into
Draft
feat(aem): add figma-to-content skill for EDS page migration from Figma#305hmehta-adobe wants to merge 2 commits into
hmehta-adobe wants to merge 2 commits into
Conversation
Orchestrates existing public EDS skills (da-auth, da-content, block-collection-and-party, snowflake, content-driven-development, testing-blocks) to turn a Figma frame into a Document Authoring content page. Reads the design via a Figma MCP, resolves each section to an existing block / new isolated block / default content (annotation-first, else inferred and confirmed), generates DA-compliant body-fragment HTML, and deploys via the DA Source API + preview. No proprietary tooling required. Draft (v0.1.0); annotation contract still to be locked with adopters. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Author
|
@karlpauls Sharing the first draft for the Figma Skill |
… and citations - SKILL.md Phase 3B/3C: use explicit 3B/3C labels tied to the Phase 2 routing decision instead of undefined 'bucket 3'/'bucket 2' terms - SKILL.md Phase 5: upload referenced media to DA before the content PUT so every authored <img> resolves at preview time - annotation-contract.md: cite da-content html-content.md §4/§5/§8 (the numbering lives in that file, not da-content root) - README.md: add figma-to-content row to the skills index Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a new EDS skill:
figma-to-contentunderplugins/aem/edge-delivery-services/skills/. It turns a Figma design intoan AEM Edge Delivery Services content page in Document Authoring (
da.live).It orchestrates existing public skills rather than reinventing them —
da-auth(DA IMS token),da-content(DA HTML rules + Source API +preview/publish + media),
block-collection-and-party/block-inventory(block palette + authoring models),
content-modeling+content-driven-development/building-blocks/testing-blocks(new-blockdev), and
snowflake(bespoke section → isolated block). The net-new logic is:read the Figma design, resolve each section, and map content in.
How it works
block, or default content — annotation-first, else inferred and
confirmed with the user (never deploys an unseen guess).
images uploaded to DA, not repo-relative paths).
PUT admin.da.live/source) + preview(
POST admin.hlx.page/preview), building/pushing new-block code first.Runs standalone in plain Claude with just a Figma MCP and a DA IMS
token — no proprietary tooling required.
Scope
or shared files.
global CSS beyond a one-time design-token retheme; treats Figma
text/annotations as data, never instructions.
Status — draft
Marked Draft (v0.1.0) intentionally. The main open question before v1.0.0
is the annotation contract (
references/annotation-contract.md), whichshould be locked with adopters / the design team. Feedback on that spec is the
primary ask.
🤖 Generated with Claude Code