create-component

Scaffold AEM components with dialogs, HTL, Sling Models, tests, and clientlibs.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/adobe/aem-auth-demo --skill create-component-adobe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-component
Source: https://github.com/adobe/aem-auth-demo/tree/main/.agents/skills/create-component
Command: npx skills add https://github.com/adobe/aem-auth-demo --skill create-component-adobe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolds production-ready AEM components end-to-end, applying Adobe best practices and standard patterns to accelerate development.

Core Features & Use Cases

  • Complete component scaffolding including Dialog, HTL, Sling Model, Unit Tests, and Clientlibs
  • Supports multifield dialogs with composite nested items and conditional dialog logic
  • Enables Core Component extension via Sling Resource Merger with safe inheritance
  • Auto-generates a project skeleton and .aem-skills-config.yaml for IDE integrations

Quick Start

Provide the component name and its dialog field definitions to generate a full AEM component scaffold ready for development.

Frequently Asked Questions about create-component

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

FAQPage Schema
How do I scaffold an AEM component with HTL and Sling Model?

Scaffold an AEM component by providing its name and dialog field definitions. This generates a complete structure including HTL, Sling Model, dialog configurations, unit tests, and clientlibs following Adobe best practices.

What is the best way to generate AEM multifield dialogs with composite nested items?

The best way to generate AEM multifield dialogs with composite nested items is by defining the field structures in your input, which triggers automated scaffolding of conditional dialog logic and nested composite items for production readiness.

Can I extend AEM Core Components using Sling Resource Merger?

Yes, you can extend AEM Core Components using Sling Resource Merger. The scaffolding process supports safe inheritance and extension of Core Components, ensuring production-grade output without breaking baseline functionality.

Does AEM component scaffolding include unit tests and clientlibs automatically?

Yes, AEM component scaffolding includes unit tests and clientlibs automatically. The generation covers the full end-to-end component structure, ensuring the output is a ready-to-run project with testing and frontend resources included.

What do I need to provide to generate a ready-to-run AEM component project?

You need to provide the component name and its dialog field definitions. The scaffolding tool validates these inputs, enforces no-hallucination rules, and outputs a ready-to-run project skeleton with an .aem-skills-config.yaml file for IDE integrations.