القائمة
EDS block documentation authoring. Trigger when creating or updating block README files, authoring guides, or technical docs for AEM Edge Delivery blocks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | eds-documentation |
| description | EDS block documentation authoring. Trigger when creating or updating block README files, authoring guides, or technical docs for AEM Edge Delivery blocks. |
Apply when creating or updating documentation for EDS blocks. Skip for temporary files or personal notes.
# [Block Name] Block
## Overview
Brief description of the block's purpose and functionality.
## Block Details
- **Block Name**: `[block-name]`
- **Files**: `blocks/[block-name]/[block-name].js`, `blocks/[block-name]/[block-name].css`
- **Content Model**: [Describe the block table structure authors use]
## Content Model
| Column | Content | Required |
|--------|---------|----------|
| [column-name] | [description] | yes/no |
## Authoring
[How authors add and configure the block in the CMS]
## Variants
[Document any variant classes and their effects]
## Accessibility
[Document accessibility features and WCAG compliance]
## Testing
[Document testing requirements and test content paths]
<br/>, <b>, <i>, etc.)Author-facing documentation helps content authors understand how to use the block. Different projects use different approaches:
Sidekick Library (Google Drive/SharePoint authoring):
/tools/sidekick/library.html in the codebaseDocument Authoring (DA) Library:
Universal Editor (UE) projects:
Simple documentation pages:
/drafts or /docsblocks/{block-name}/README.md when block is complex.specify/memory/components/authoring-guides/)