snowflake

Convert static HTML pages into Adobe Edge Delivery Services overlay pages.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/aemcoder/skills --skill snowflake-aemcoder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: snowflake
Source: https://github.com/aemcoder/skills/tree/main/skills/snowflake
Command: npx skills add https://github.com/aemcoder/skills --skill snowflake-aemcoder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, git, curl, jq, npm, playwright-cli, and includes scripts (resource) components.

What problem does it solve?

This skill converts AI-generated static HTML pages into Adobe Edge Delivery Services (EDS) overlay pages where the original DOM is preserved byte-for-byte, while text and images become authorable in Document Authoring.

Core Features & Use Cases

  • Static-to-EDS overlay conversion using an overlay pattern that preserves the original DOM structure and content rendering.
  • 6-phase workflow that captures the source page, analyzes section boundaries and slot opportunities, generates template + fragments + CSS/JS, wires them into the target repo, and verifies via local and production round-trips.
  • DA-ready authoring model that writes a DA-source body fragment with slot rows so authors can edit content without losing design fidelity.

Quick Start

Tell the assistant: Convert https://www.example.com/page to owner/eds-repo using the snowflake skill, ensuring the target repo has the overlay substrate and you have a DA admin token available.

Frequently Asked Questions about snowflake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert static HTML to Adobe Edge Delivery Services overlays for Document Authoring?

Converting static HTML to Adobe Edge Delivery Services overlays preserves the original DOM byte-for-byte while exposing text and images for Document Authoring edits. The process extracts assets, generates templates and fragments, wires slots into the repo, and verifies via local and production round-trips.

Can I import AI-generated HTML from Relume, Lovable, v0, or Figma into EDS without losing the DOM structure?

Yes, AI-generated static HTML from Relume, Lovable, v0, and Figma can be imported into EDS without losing DOM structure. The conversion uses an overlay pattern that preserves the original DOM byte-for-byte while enabling Document Authoring edits.

What is the best way to make static HTML text and images authorable in Document Authoring?

The best way to make static HTML authorable in Document Authoring is generating a DA-source body fragment with slot rows. This exposes text and image content for edits while preserving the original design fidelity through strict template slot wiring semantics.

Do I need playwright-cli and jq to verify EDS overlay conversions?

Yes, playwright-cli and jq are required dependencies for EDS overlay conversions. Playwright-cli enables end-to-end browser verification and visual validation, while jq processes JSON data during the overlay substrate installation and slot wiring phases.

Why does the EDS overlay conversion process require a DA admin token?

The EDS overlay conversion requires a DA admin token to write DA content fragments and wire slot rows into the Document Authoring system. This token authorizes the automated generation of authorable content blocks during the template and fragment generation phase.

When should I use Media Bus absolute URLs for DA images in Edge Delivery Services?

Media Bus absolute URLs for DA images should be used when wiring images into EDS overlay templates. This constraint ensures that Document Authoring can correctly resolve and render images extracted from the static HTML during the authoring and publication process.