メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | create-component |
| description | 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. |
| argument-hint | <component-name> [--title "Title"] [--description "Desc"] [--group "Group"] [--super-type "path"] [--is-container] [--version v1] [--with-js] [--dry-run] |
| allowed-tools | Bash, Read, Write, Glob |
Scaffolds a complete AEM component with the correct folder hierarchy, XML namespaces, and naming conventions.
Parse the user's arguments. The component name (kebab-case, without dxn- prefix) is required. Optional flags:
--title "Component Title" — sets jcr:title (defaults to title-cased name)--description "Description" — sets jcr:description--group "Group Name" — sets componentGroup (default: DigitalXn General)--super-type "path" — sets sling:resourceSuperType (default: core/wcm/components/component/v1/component)--is-container — sets cq:isContainer to true--version v1 — version folder (default: v1)--with-js — include JS bundle file and js.txt in clientlibs--dry-run — preview file tree without creating filesRun the scaffolding script:
python3 scripts/create_component.py <component-name> [flags]
Report what was created to the user, listing all generated files.
Remind the user of recommended next steps:
_cq_dialog/.content.xml to add component-specific dialog fieldsdxn-{name}.htmlREFERENCE.md in this skill folder for XML template examplesFor detailed XML templates and naming conventions, see REFERENCE.md in this directory.
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.