eds-skills

Manual asset processing skill for Figma layers. Accepts layer URLs and writes deterministic files to drafts/media using curl+sips, with optional get_screenshot fallback.

Phase 3 of athenai-implement pipeline — execute tasks from plan.md and produce working block code. Includes lint-aware CSS generation and mandatory design compliance check when design.md exists.

Phase 0 of athenai-implement pipeline — conditionally produce design.md from Figma. Includes decision logic, extraction-only rules, manual asset handoff, and Phase 1 context pre-loading optimization.

End-to-end implementation pipeline — design, plan, tasks, implement, test cases, test content. Demo mode: skips unit tests and research deep-dives. Records phase wall times via `.specify/scripts/phase-timer.py` (per-phase start/end, subagent logs + merge when parallel). Explicit invocation only — never load from context or topic. Optional flags: --no-parallel (run all phases sequentially in main agent, no subagents), --no-test-cases (skip Phase 4 test case generation).

Phase 1-2 of athenai-implement pipeline — produce plan.md with authored HTML structure, parsing logic, and tasks section. Includes draft test content generation with mandatory edge case coverage.

Phase 4 of athenai-implement pipeline — generate testcases.csv from spec.md. Includes guard for --no-test-cases flag and coverage requirements for user journeys, acceptance criteria, and edge cases.

Phase 5 of athenai-implement pipeline — verify local draft HTML exists, validate .plain.html structure, and print pipeline summary with execution time report.

Guide for creating new AEM Edge Delivery blocks or modifying existing blocks. Use this skill whenever you are creating a new block from scratch or making significant changes to existing blocks that involve JavaScript decoration, CSS styling, or content model changes.

Apply a Content Driven Development process to AEM Edge Delivery Services development. Use for all development tasks, including building new blocks, modifying existing blocks, making changes to core decoration functionality, etc.

Scaffold a new AEM component folder structure with all required XML, HTL, and clientlib files. Use when asked to create a new component, scaffold a component, or generate component boilerplate.

EDS analytics data layer integration. Trigger when implementing analytics events, Google Analytics/Adobe Data Layer tracking, or creating analytics for AEM Edge Delivery blocks.

EDS block documentation authoring. Trigger when creating or updating block README files, authoring guides, or technical docs for AEM Edge Delivery blocks.

EDS label naming conventions and design compliance testing. Trigger when naming label/ARIA identifiers in HTML/JS, creating design-expectations.json, or running assert-design-compliance.js CSS checks.

EDS block CSS styling. Trigger when writing CSS for AEM Edge Delivery blocks, using shared tokens (--dxn-* or project vars), or applying block-scoped (BEM-like) class naming.

WCAG 2.2 AA accessibility for AEM Edge Delivery blocks. Trigger when implementing ARIA attributes, keyboard navigation, focus management, live regions, or accessibility features in HTML/JS/CSS.

Fetches a Figma node screenshot via MCP and saves it to disk. Use when the user asks to save a Figma design reference, capture a design for specs, or store a screenshot for verification.

Strict pull request code review for aem-code (and related AEM repos). Trigger when reviewing a PR from GitHub workflows, when the user asks for a PR review, or when performing regression-safe code review.

Enforces server-side rendering over JavaScript DOM manipulation for AEM components. Use when generating HTL templates, component JavaScript, or SCSS for any component where content is available from the Sling Model at page load.

Analyze cross-artifact consistency across spec.md, plan.md, and tasks.md. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit-analyze".

Generate requirements quality checklists for a speckit feature. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit-checklist".

Clarify ambiguous requirements in a speckit feature spec. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit-clarify".

Upload a speckit block's draft HTML to the DA Library and register it in blocks.json. Atomic skill — invoke manually after speckit-fast (or any pipeline that produced a local draft HTML file). Reads drafts/{blockname}.plain.html, wraps it, uploads to DA, and updates blocks.json. Explicit invocation only.

Generate design-expectations.json from design.md and run assert-design-compliance CSS checks. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit design-compliance".

Generate or update the component authoring guide after implementation. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit-document".

Extract visual design context from Figma and save it as design.md. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit figma-specify".

Execute the implementation plan for a speckit feature. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit-implement".

Generate an implementation plan for a speckit feature. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit-plan".

Create a new feature specification from a natural language description. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit-specify".

Generate a tasks.md for a speckit feature. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit-tasks".

Generate a testcases.csv from a speckit feature spec. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit-testcases".

Upload block test content to the DA Library via MCP. Uses speckit draft or user-specified HTML.

Validate implementation by running CDD Phase 3 (validate portion): test with real content, comprehensive testing, and PR preparation. Explicit invocation only — never load from context or topic. Use only when the user types the exact command "speckit-validate".

Guide for testing code changes in AEM Edge Delivery projects including blocks, scripts, and styles. Use this skill after making code changes and before opening a pull request to validate functionality. Covers unit testing for utilities and logic, browser testing with Playwright/Puppeteer, linting, performance validation, and guidance on which tests to maintain vs use as throwaway validation.