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
This file describes how the skill plugs into specific host environments. It is not loaded by the agent at invocation time — it's a reference for whoever installs/maintains the skill on a given host.
The skill body (SKILL.md + phases/*.md) is deliberately host-agnostic.
It uses bash, node (≥22), git, gh (GitHub CLI), curl, jq,
npm/npx, and POSIX sed/grep/awk. Browser interactions are
expressed as intent-level instructions ("open this URL in a browser",
"evaluate this JavaScript", "take a screenshot") — the skill never calls
a specific browser tool directly. The notes below describe how each host
fulfils those intents.
Install:
upskill aemcoder/skills --path skills/snowflakeThis drops the skill into /workspace/skills/snowflake/ inside the
Slicc cone container. SKILL.md's <SKILL_DIR> references resolve to
that path.
Invocation:
description activate
the cone. The cone reads SKILL.md, then walks the phases.sprinkle, skill snowflake. The cone handles the lick directly
(does not delegate to a scoop) and walks the phases.Parallel block generation: In block-level conversion, Phase 3 (B.5) says blocks can be generated in parallel. In Slicc, the cone should orchestrate this by dispatching one scoop per block (scoops cannot create scoops — the cone must be the dispatcher). Each scoop writes one block's JS + CSS; the cone collects results and proceeds to B.6. Sequential fallback is fine if scoop dispatch is unavailable.
Browser: Use playwright-cli (pre-installed in Slicc cones) to
fulfil browser intents — open URLs, evaluate JS, take screenshots.
Use --tab <id> per the Slicc stateless-tab convention.
Progress reporting (optional): if the host wants live UI
updates, a wrapper script can read the project's state.json
between phases and emit sprinkle send snowflake '<json>' events.
The skill body itself does NOT emit sprinkle events — it only writes
state.json.
Worktree config (optional): the skill writes to the target EDS
repo (not the skills repo). The cone's working directory must be the
target repo when phases run. Slicc's typical pattern (cd into
/shared/<target-repo>) works fine.
Install (project-level, recommended):
.claude/skills/snowflake/
in the target EDS repo.<SKILL_DIR> is ${CLAUDE_SKILL_DIR} at runtime.Install (global, alternative):
~/.claude/skills/snowflake/.Invocation:
/snowflake in the chat.Parallel block generation: In block-level conversion, Phase 3
(B.5) says blocks can be generated in parallel. In Claude Code, use
the Agent tool to dispatch one subagent per block — each writes its
block's JS + CSS independently. Worktree isolation (isolation: "worktree") is not needed since blocks write to separate file paths
with no overlap. The main agent collects results and proceeds to B.6.
Browser: Use whatever browser tool is available in the environment. Good options, in preference order:
cmux-browser skill — if running inside a cmux terminal, use its
embedded browser (non-intrusive, no external window).playwright-cli — if available on the bash PATH.Do not use mcp__playwright__* tools — those are Claude-Code-only
and break host portability.
Auto-memory: the skill notes in phases/6-reflect.md step 6.5
that hosts with persistent memory should record user-feedback rules.
Claude Code's auto-memory at
~/.claude/projects/<project>/memory/MEMORY.md is the canonical
location.
Permission prompts: the user will see permission prompts for
git push, curl ... admin.da.live, and similar mutating
operations. The skill's idempotency (state.json) means a denied
prompt can be retried after the user adjusts permissions.
The skill body is bash-and-node only. Any host that gives the agent a bash shell can run it:
node (≥22), git, gh (GitHub CLI),
curl, jq, npm. A browser tool (playwright-cli or equivalent)
must be available for Phase 5 browser intents.<SKILL_DIR> references resolve).phases/<N>-*.md and executing the bash blocks within.There's no progress-reporting primitive in generic shell — the agent's text output IS the progress.
A target EDS repo can be a vanilla adobe/aem-boilerplate clone OR
a repo already partially modified by an earlier overlay attempt. The
skill ships an idempotent installer that brings either to the
expected overlay-substrate state:
node <SKILL_DIR>/scripts/install-substrate.mjs [--dry-run] [--force]The installer is pure Node (built-ins only) and uses
import.meta.url to self-locate the bundled assets/substrate/ directory
— it works regardless of where the skill is mounted on a given host.
It is driven by <SKILL_DIR>/assets/substrate/MANIFEST.json (declarative)
and stamps .snowflake/config.json with the installed version on
success. Files it overwrites are backed up to
.snowflake/.backup/<timestamp>/.
Phase 0 of the skill (see phases/0-prereq.md) drives this
installer. Subsequent invocations see the matching version in
.snowflake/config.json and skip Phase 0 silently.
The installer performs three kinds of change driven by MANIFEST.json:
replace (wholesale file copy, with backup), ignorePatches/gitignore
(idempotent line merges), and inject (anchored, idempotent code insertion).
scripts.js is the sole inject target — the overlay engine lives in the
wholesale-replaced scripts/overlay-engine.js, and scripts.js receives only
a small import + loadEager guard so upstream boilerplate evolution is kept.
.snowflake/ directory (all hosts)All per-repo state, project artifacts, and project-specific
knowledge live under .snowflake/ at the target repo's root:
.snowflake/
├── config.json ← substrate version + repo defaults
├── knowledge/ ← OPTIONAL project-specific overrides
├── projects/<NNN>-<slug>/ ← per-run state, notes, learnings,
│ input/output/diff artifacts
└── .backup/<timestamp>/ ← substrate-install rollbackPhase prompts resolve knowledge with
.snowflake/knowledge/<file>.md first, then bundled
<SKILL_DIR>/knowledge/<file>.md. Project-specific overrides win.
Defaults live in the defaults block of
<SKILL_DIR>/assets/substrate/MANIFEST.json:
"defaults": {
"projectsDir": ".snowflake/projects",
"branchPrefix": "snowflake-",
"trunkBranch": "main",
"tagPrefix": "snowflake-"
}The installer (scripts/install-substrate.mjs) stamps these into
.snowflake/config.json on every install or upgrade. User-edited values
in an existing config are preserved — the merge order is:
manifest.defaults → existing config → substrateVersion/installedAt.
To override a default for a specific repo, edit .snowflake/config.json
directly — the installer will never clobber keys you've already set.
A maintainer extending the skill should treat .snowflake/ as the
single source of truth for any per-repo state, NEVER write to the
skill bundle, NEVER write to /workspace.
The skill expects:
A DA admin token from one of (in order):
$DA_TOKEN environment variable.~/.aem/da-token.json (the cache the da-auth skill writes).{ "access_token": "<jwt>", "expires_at": <epoch_ms>, ... }.GitHub auth via gh CLI (gh auth status should be green for
the target repo's owner). Used for the git push in Phase 5 and
for repo-identity lookups.
These are user prerequisites, not things the skill provisions.
<SKILL_DIR> pathsPhase prompts reference files like <SKILL_DIR>/knowledge/methodology.md
or invoke node <SKILL_DIR>/scripts/install-substrate.mjs. The assistant
resolves <SKILL_DIR> to the absolute path of the directory containing
SKILL.md, then substitutes that absolute path into the bash invocation.
Per host:
SKILL.md from the plugin
cache (e.g. ~/.claude/plugins/cache/.../skills/snowflake/) and
substitutes that path. Bash CWD is the target EDS repo, not the
skill directory — never use bare ./scripts/foo.mjs.gh upskill / npx skills: skills are installed to
.claude/skills/snowflake/ at the target repo root; <SKILL_DIR>
resolves there.<SKILL_DIR> = /workspace/skills/snowflake/.SKILL.md and
uses that absolute path.Node scripts inside scripts/ self-locate via import.meta.url and
work regardless of CWD once invoked with the correct absolute path.
When extending the skill, do NOT use:
sprinkle send, upskill, workspace_* helpers,
scoop dispatch.mcp__* tool calls, WebFetch, WebSearch,
named Agent subagent types, ${CLAUDE_SKILL_DIR} in skill body
prompts (it's fine in HOST-NOTES.md and in scripts that auto-locate).playwright-cli tab-new,
playwright-cli evaluate, etc.) in the skill body — use intent-level
prose instead ("open URL in a browser", "evaluate this JS", "take a
screenshot"). The host adapter (this file) maps intents to tools.gh (GitHub CLI) IS allowed — it is a standard allowed primitive.
Ensure gh auth status is green for the target repo's owner before
Phase 5 (it is required for git push and repo-identity lookups).
If a host has an obvious richer primitive (live status updates, GUI
preview, etc.), wire it up at the host's outer layer — by reading the
skill's state.json and emitting host-specific events — not by
editing the skill body.
.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