[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736FXNWAMW1BYF13PVYMPCB":3,"skill-same:01M736FXNWAMW1BYF13PVYMPCB":124},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M736FXNWAMW1BYF13PVYMPCB","create-component",null,"Creates complete AEM components with dialog, HTL template, Sling Model, unit tests, and clientlibs.\nSupports extending Core Components and project components. When a Figma design URL is provided,\nfetches the design via Figma MCP (get_design_context) and translates it into pixel-perfect HTL, CSS,\nand JS. Follows Adobe Experience League best practices for AEM Cloud Service and 6.5.\nUse this skill whenever the user mentions creating, building, generating, or scaffolding an AEM\ncomponent, or mentions component types like teaser, card, hero, banner, accordion, tabs, carousel,\nlist, navigation, breadcrumb, or any custom AEM component. Also trigger when the user wants to\nextend a Core Component, create a component dialog, add a Sling Model, or convert a Figma design\ninto an AEM component.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: create-component\ndescription: |\n  Creates complete AEM components with dialog, HTL template, Sling Model, unit tests, and clientlibs.\n  Supports extending Core Components and project components. When a Figma design URL is provided,\n  fetches the design via Figma MCP (get_design_context) and translates it into pixel-perfect HTL, CSS,\n  and JS. Follows Adobe Experience League best practices for AEM Cloud Service and 6.5.\n  Use this skill whenever the user mentions creating, building, generating, or scaffolding an AEM\n  component, or mentions component types like teaser, card, hero, banner, accordion, tabs, carousel,\n  list, navigation, breadcrumb, or any custom AEM component. Also trigger when the user wants to\n  extend a Core Component, create a component dialog, add a Sling Model, or convert a Figma design\n  into an AEM component.\ncompatibility: Requires AEM as a Cloud Service or AEM 6.5. Maven project structure with core, ui.apps modules. Figma design integration requires the `plugin-figma-figma` MCP server to be enabled in the IDE.\nlicense: Apache-2.0\nmetadata:\n  author: AEM Dev Agent\n  version: \"1.0\"\n  aem_version: \"6.5\u002FCloud Service\"\n---\n# AEM Component Creation Skill\n\nCreates complete AEM components following Adobe best practices.\n\n## Configuration Gate Check — Do This First\n\n> This configuration check needs to happen first because without it, the skill will use incorrect project paths and package names, causing every generated file to be wrong.\n\n**First tool call**: Read `.aem-skills-config.yaml` in the **project root** (same level as `pom.xml`).\n\n**Check**: Does the file exist and does it have `configured: true`?\n\n| Status | Action |\n| --- | --- |\n| File missing or configured: false | Stop and display the error message below. Do not explore the codebase or proceed — the config values are needed for correct file paths and naming. Wait for the user to configure. |\n| configured: true | Read project, package, and group values from the YAML file. Proceed with component creation. |\n\n### If NOT configured, Display This Message and Stop:\n\n```\nProject configuration required!\n\nBefore creating components, configure your project settings in:\n`.aem-skills-config.yaml` (in your project root, same level as pom.xml)\n\nOpen the file and update:\n- project: Your AEM project name (e.g., 'mysite', 'wknd')\n- package: Your Java package (e.g., 'com.mysite.core')\n- group: Your component group (e.g., 'MySite Components')\n- configured: true\n\nAfter updating, ask me to create the component again.\n```\n\n### Why you should not explore the codebase when unconfigured:\n\nDoing any of the following before configuration is set will lead to incorrect assumptions and wasted effort:\n\n- Reading any other repository files\n- Listing directories to \"understand the project\"\n- Checking existing components for patterns\n- Looking at pom.xml, Java files, or folder structures\n- Inferring values from any source\n\nThe config file is the single source of truth for project values — skipping it leads to wrong paths and package names in every generated file.\n\n## No Hallucination Rule\n\nOnly create the exact fields the user specified — adding extra fields creates authoring confusion and maintenance burden, and renaming fields breaks content contracts.\n\n**Load reference for full rules:** `references\u002Fno-hallucination-rules.md`\n\n## Workflow Overview\n\n| Step | Action |\n| --- | --- |\n| 0 | Configuration validation (do this first — see above) |\n| 1 | Extract & validate component name |\n| 1.5 | Component extension decision (if extending) |\n| 2 | Gather requirements & confirm dialog specification |\n| 2.3 | Figma design fetch (if Figma URL provided) |\n| 3 | Create all component files |\n| 3.11 | Dependency verification (required for servlets) |\n| 4 | Completion summary |\n\n## Step 0: Configuration Validation\n\n### 0.1 Read Configuration\n\n1. Read `.aem-skills-config.yaml` from the project root\n2. Check that `configured: true`\n3. Read `project`, `package`, and `group` values\n\n### 0.2 Validate — Use Only the Config File\n\nDo not infer project values from the file system, existing components, Java files, pom.xml, or prior knowledge. These sources may be outdated or inconsistent — `.aem-skills-config.yaml` is the single source of truth because the user explicitly sets it.\n\n### 0.3 Load Conventions\n\n1. Read `references\u002Faem-conventions.md` for file structure templates, naming conventions, and patterns\n\n### 0.4 Project State Analysis (after configuration validated)\n\n1. **Check Component Name Uniqueness** - Look in `\u002Fapps\u002F[project]\u002Fcomponents\u002F`\n2. **Check Model Class Conflicts** - Look in `core\u002Fsrc\u002Fmain\u002Fjava\u002F[package-path]\u002Fmodels\u002F`\n3. **Analyze Existing Patterns** - Review 1-2 recent components for style reference\n\n## Step 1: Extract & Validate Component Name\n\n- Parse component name from user's message (ask if not provided)\n- Normalize to lowercase kebab-case (e.g., `My Component` -> `my-component`)\n- Validate: starts with letter, only letters\u002Fnumbers\u002Fhyphens, no consecutive hyphens\n\n## Step 1.5: Component Extension Decision\n\n### When user says \"extend {component}\":\n\n**Tier 1: Check Project Components First**\n\n- Search `\u002Fapps\u002F{project}\u002Fcomponents\u002F{component}`\n- If found -> Use as `sling:resourceSuperType`\n\n**Tier 2: Check Core Components**\n\n| User Says | Maps To |\n| --- | --- |\n| image | core\u002Fwcm\u002Fcomponents\u002Fimage\u002Fv3\u002Fimage |\n| teaser, card | core\u002Fwcm\u002Fcomponents\u002Fteaser\u002Fv2\u002Fteaser |\n| text, richtext | core\u002Fwcm\u002Fcomponents\u002Ftext\u002Fv2\u002Ftext |\n| title, heading | core\u002Fwcm\u002Fcomponents\u002Ftitle\u002Fv3\u002Ftitle |\n| list | core\u002Fwcm\u002Fcomponents\u002Flist\u002Fv4\u002Flist |\n| button, cta | core\u002Fwcm\u002Fcomponents\u002Fbutton\u002Fv2\u002Fbutton |\n| navigation, nav | core\u002Fwcm\u002Fcomponents\u002Fnavigation\u002Fv2\u002Fnavigation |\n| container, section | core\u002Fwcm\u002Fcomponents\u002Fcontainer\u002Fv1\u002Fcontainer |\n| accordion | core\u002Fwcm\u002Fcomponents\u002Faccordion\u002Fv1\u002Faccordion |\n| tabs | core\u002Fwcm\u002Fcomponents\u002Ftabs\u002Fv1\u002Ftabs |\n| carousel | core\u002Fwcm\u002Fcomponents\u002Fcarousel\u002Fv1\u002Fcarousel |\n| embed, video | core\u002Fwcm\u002Fcomponents\u002Fembed\u002Fv2\u002Fembed |\n\n**Tier 3: Not Found** - Ask user for clarification.\n\n**For extension patterns, load:** `references\u002Fextending-core-components.md`\n\n## Step 1.6: Core Component Extension Requirements\n\n**Required when extending with \"hide\", \"remove\", \"add custom field\", or \"override\"** (these operations need Sling Resource Merger patterns to work correctly):\n\n**Load reference:** `references\u002Fextending-core-components.md`\n\n| User Request | Action |\n| --- | --- |\n| \"Add custom fields\" | Create new tab OR add to existing |\n| \"Hide {tab}\" | Use sling:hideResource=\"{Boolean}true\" |\n| \"Hide {field}\" | Use sling:hideResource=\"{Boolean}true\" |\n| \"Override {field}\" | Use sling:hideProperties + new values |\n\n**When extending Core Components:**\n\n- Use `@Self @Via(type = ResourceSuperType.class)` for model delegation\n- Implement `ComponentExporter` interface\n- Add `resourceType` to `@Model` annotation\n- Use `sling:hideResource` in dialog for inherited tabs\u002Ffields\n\n> **Note:** If the parent component is a project component (not a Core Component), use direct Java class extension (`extends ParentModel`) instead of the delegation pattern. The `@Self @Via(type = ResourceSuperType.class)` pattern is only for Core Components. Load `references\u002Fextending-core-components.md` for the decision table.\n\n## Step 2: Gather Requirements\n\n### 2.1 Parse Dialog Specification\n\nEcho back EXACTLY what you understood before creating:\n\n```\nDialog Specification Confirmed:\nI will create exactly {N} fields:\n| # | Field Label | Field Type | Property Name |\n|---|-------------|------------|---------------|\n| 1 | {label1}    | {type1}    | {name1}       |\nNo additional fields will be added.\nIs this correct?\n```\n\n### 2.2 Mockup Image Handling\n\n- **Both mockup AND spec provided:** Dialog spec takes precedence. Mockup for HTML\u002FCSS only.\n- **Only mockup provided:** Propose fields and ASK for confirmation.\n\n### 2.3 Figma Design Input\n\n**Load:** `references\u002Ffigma-design-rules.md`\n\nWhen user provides a Figma URL (`figma.com\u002Fdesign\u002F...`, `figma.com\u002Fmake\u002F...`, or `figma.com\u002Fboard\u002F...`):\n\n1. **Parse the URL** to extract `fileKey` and `nodeId` (see references\u002Ffigma-design-rules.md Rule 1)\n\n- Convert `-` to `:` in the `node-id` query parameter\n- Use `branchKey` as `fileKey` for branch URLs\n\n1. **Call **`get_design_context` via the `plugin-figma-figma` MCP server (see Rule 2):`{ \"server\": \"plugin-figma-figma\", \"toolName\": \"get_design_context\", \"arguments\": { \"nodeId\": \"\u003Cextracted-node-id>\", \"fileKey\": \"\u003Cextracted-file-key>\", \"clientLanguages\": \"html,css,javascript\", \"clientFrameworks\": \"htl\" } }`\n2. **Extract design tokens** from the response — colors, fonts, sizes, spacing, layout (see Rules 3-4)\n3. **Use the Figma output** for HTL structure, CSS styling, and JS behavior — **NOT** for dialog fields\n\n**Precedence when BOTH dialog spec AND Figma URL are provided:**\n\n- **Dialog specification** → determines dialog fields (absolute precedence, no hallucination)\n- **Figma design** → determines HTML structure, CSS styling, JS behavior only\n\n**When ONLY Figma URL is provided (no dialog spec):**\n\n- Analyze the design and **PROPOSE** dialog fields to the user\n- **ASK for confirmation** before proceeding\n\n**Figma response handling:**\n\n- The response is React+Tailwind — treat as a REFERENCE, not production code\n- Convert JSX to semantic HTL with BEM classes (see Rule 5)\n- Extract all CSS values to the component clientlib (see Rule 6)\n- Create JS only if interactivity is implied (see Rule 7)\n- Do not hardcode Figma temporary image URLs — they expire and will break in production (see Rule 8)\n\n### 2.4 Dynamic Content Requirements\n\n| User Indicates | Servlet Required? |\n| --- | --- |\n| External API integration | Yes (GET) |\n| Dynamic data loading | Yes (GET) |\n| Form submission | Yes (POST) |\n| Search\u002Ffilter | Yes (GET) |\n| Static dialog content | No |\n\n## Step 3: Create Component Files\n\nCreate ALL files in this order:\n\n### 3.1 Component Definition\n\n**Path:** `ui.apps\u002Fsrc\u002Fmain\u002Fcontent\u002Fjcr_root\u002Fapps\u002F[project]\u002Fcomponents\u002F{component-name}\u002F.content.xml`\n\nLoad: `references\u002Faem-conventions.md`\n\n### 3.2 Component Dialog\n\n**Path:** `ui.apps\u002F...\u002Fcomponents\u002F{component-name}\u002F_cq_dialog\u002F.content.xml`\n\n**Load:** `references\u002Fdialog-patterns.md`\n\n**For extended components:** Load `references\u002Fextending-core-components.md` — Sling Resource Merger is required here because dialog inheritance only works through the merger; without it, parent dialog nodes won't be resolved.\n\n### 3.2.1 Image Field Handling\n\nWhen a user specifies an image or photo field:\n\n- **Default approach:** Embed the Core Image component via `data-sly-resource` — do NOT create a fileupload dialog field with manual `\u003Cimg>` rendering.\n- **Fileupload is only for non-image files** (PDFs, documents, etc.). Only use `cq\u002Fgui\u002Fcomponents\u002Fauthoring\u002Fdialog\u002Ffileupload` when the user explicitly asks for a non-image file upload.\n- **Load** `references\u002Fhtl-patterns.md` (Image Handling section) for the correct embedding pattern.\n\n### 3.3 HTL Template\n\n**Path:** `ui.apps\u002F...\u002Fcomponents\u002F{component-name}\u002F{component-name}.html`\n\n**Load:** `references\u002Fhtl-patterns.md`**If Figma URL provided, ALSO load:** `references\u002Ffigma-design-rules.md` (Rules 5, 8) — Convert JSX structure to semantic HTL with BEM classes. Replace static text with Sling Model expressions. Use the Figma screenshot as visual truth for element hierarchy.\n\n**i18n check:** If the component has static display text (labels, button text, placeholder strings), use HTL i18n expressions: `${'Label Text' @ i18n}`. Do not handle static text translation in the Sling Model — keep it in HTL where translation is automatic.\n\n### 3.4 Sling Model\n\n**Path:** `core\u002Fsrc\u002Fmain\u002Fjava\u002F[package-path]\u002Fmodels\u002F{ComponentName}Model.java`\n\n**Load:** `references\u002Fmodel-patterns.md`, `references\u002Fjava-standards.md`\n\n**For extensions:** Load `references\u002Fextending-core-components.md`\n\n**Delegation Pattern (for Core Component extensions):**\n\n```java\n@Model(adaptables = SlingHttpServletRequest.class,\n       adapters = {CustomModel.class, ComponentExporter.class},\n       resourceType = CustomModel.RESOURCE_TYPE)\n@Exporter(name = ExporterConstants.SLING_MODEL_EXPORTER_NAME,\n          extensions = ExporterConstants.SLING_MODEL_EXTENSION)\npublic class CustomModel implements ComponentExporter {\n    @Self @Via(type = ResourceSuperType.class)\n    private com.adobe.cq.wcm.core.components.models.List coreList;\n    \u002F\u002F Use FQN for core interfaces to avoid import collision\n}\n```\n\n### 3.5 Child Item Model - If Multifield\n\n**Path:** `core\u002Fsrc\u002Fmain\u002Fjava\u002F[package-path]\u002Fmodels\u002F{ItemName}.java`\n\n### 3.6 Unit Test\n\n**Path:** `core\u002Fsrc\u002Ftest\u002Fjava\u002F[package-path]\u002Fmodels\u002F{ComponentName}ModelTest.java`\n\n**Load:** `references\u002Ftest-patterns.md`\n\n### 3.7 Component Clientlib — Create for Every Component\n\n**Path:** `ui.apps\u002F...\u002Fclientlibs\u002Fclientlib-{component-name}\u002F`\n\n**Load:** `references\u002Fclientlib-patterns.md`**If Figma URL provided, ALSO load:** `references\u002Ffigma-design-rules.md` (Rules 6, 7) — Extract exact colors, fonts, sizes, spacing, border-radius from the Figma response. Place all CSS into `css\u002F{component-name}.css` using BEM naming. Create JS in `js\u002F{component-name}.js` only if the design implies interactivity. Verify pixel-perfect fidelity against the Figma screenshot.\n\n### 3.8 Dialog Clientlib - If Conditional Logic\n\n**Path:** `ui.apps\u002F...\u002Fclientlibs\u002Fclientlib-{component-name}-dialog\u002F`\n\n**Load:** `references\u002Fclientlib-patterns.md` (Dialog JavaScript Pattern section)\n\n### 3.9 Sling Servlet - If Dynamic Content\n\n**Path:** `core\u002Fsrc\u002Fmain\u002Fjava\u002F[package-path]\u002Fservlets\u002F{ComponentName}Servlet.java`\n\n**Load:** `references\u002Fsling-servlet-standards.md`\n\n### 3.10 Servlet Unit Test\n\n**Path:** `core\u002Fsrc\u002Ftest\u002Fjava\u002F[package-path]\u002Fservlets\u002F{ComponentName}ServletTest.java`\n\n### 3.11 Dependency Verification — Required for Servlets\n\n**Before completing, verify dependencies in **`core\u002Fpom.xml`**:**\n\n- Do not hardcode versions — check parent pom.xml for version properties instead, since hardcoded versions drift out of sync and cause build conflicts\n- Most common APIs included in `aem-sdk-api` (GSON, Jackson, Commons)\n- Use `provided` scope for AEM runtime libraries\n\n## Step 4: Completion Summary\n\n```\nComponent '{component-name}' created successfully!\n\n## Files Created\n- ui.apps\u002F...\u002Fcomponents\u002F{component-name}\u002F.content.xml\n- ui.apps\u002F...\u002Fcomponents\u002F{component-name}\u002F_cq_dialog\u002F.content.xml\n- ui.apps\u002F...\u002Fcomponents\u002F{component-name}\u002F{component-name}.html\n- core\u002F...\u002Fmodels\u002F{ComponentName}Model.java\n- core\u002F...\u002Fmodels\u002F{ComponentName}ModelTest.java\n- ui.apps\u002F...\u002Fclientlibs\u002Fclientlib-{component-name}\u002F\n[+ servlet files if applicable]\n\n## Dialog Fields (Exact Match)\n{table matching specification}\n\nWould you like me to add any additional fields or build the project?\n```\n\n## Quick Reference: Field Type Mapping\n\n| User Says | Granite Resource Type |\n| --- | --- |\n| Textfield | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Ftextfield |\n| Textarea | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Ftextarea |\n| Richtext, RTE | cq\u002Fgui\u002Fcomponents\u002Fauthoring\u002Fdialog\u002Frichtext |\n| Pathfield, Path | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fpathfield |\n| Image, Photo | Embed Core Image component (see references\u002Fhtl-patterns.md Image Handling section). Do not use fileupload for image rendering. |\n| Fileupload, File Upload | cq\u002Fgui\u002Fcomponents\u002Fauthoring\u002Fdialog\u002Ffileupload (for non-image files: PDFs, documents) |\n| Multifield | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fmultifield |\n| Checkbox | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fcheckbox |\n| Select, Dropdown | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fselect |\n| Numberfield | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fnumberfield |\n| Datepicker | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fdatepicker |\n\nFor complete mappings: `assets\u002Ffield-type-mappings.md`\n\n## Reference Files\n\nLoad on-demand based on what you're creating:\n\n| Creating | Load Reference |\n| --- | --- |\n| Any component | .aem-skills-config.yaml (project root, load first — see Configuration Gate Check), then references\u002Faem-conventions.md |\n| Dialog XML | references\u002Fdialog-patterns.md |\n| HTL Template | references\u002Fhtl-patterns.md |\n| Sling Model | references\u002Fmodel-patterns.md, references\u002Fjava-standards.md |\n| Unit Tests | references\u002Ftest-patterns.md |\n| Clientlibs | references\u002Fclientlib-patterns.md |\n| Extending Core Component | references\u002Fextending-core-components.md |\n| Extending Core Component — worked example & checklists | references\u002Fextending-core-components-example.md (load when you need a complete worked example of extending a Core Component, unit testing patterns, or the implementation checklist) |\n| Sling Servlet | references\u002Fsling-servlet-standards.md |\n| Core Component patterns | references\u002Fcore-components.md |\n| No Hallucination rules | references\u002Fno-hallucination-rules.md |\n| Figma design integration | references\u002Ffigma-design-rules.md |\n| Troubleshooting | references\u002Ftroubleshooting.md |\n| Examples | references\u002Fexamples.md |\n\nIf encountering issues during or after component creation, consult `references\u002Ftroubleshooting.md` for common problems and solutions.","# AEM Component Creation Skill\n\nCreates complete AEM components following Adobe best practices.\n\n## Configuration Gate Check — Do This First\n\n> This configuration check needs to happen first because without it, the skill will use incorrect project paths and package names, causing every generated file to be wrong.\n\n**First tool call**: Read `.aem-skills-config.yaml` in the **project root** (same level as `pom.xml`).\n\n**Check**: Does the file exist and does it have `configured: true`?\n\n| Status | Action |\n| --- | --- |\n| File missing or configured: false | Stop and display the error message below. Do not explore the codebase or proceed — the config values are needed for correct file paths and naming. Wait for the user to configure. |\n| configured: true | Read project, package, and group values from the YAML file. Proceed with component creation. |\n\n### If NOT configured, Display This Message and Stop:\n\n```\nProject configuration required!\n\nBefore creating components, configure your project settings in:\n`.aem-skills-config.yaml` (in your project root, same level as pom.xml)\n\nOpen the file and update:\n- project: Your AEM project name (e.g., 'mysite', 'wknd')\n- package: Your Java package (e.g., 'com.mysite.core')\n- group: Your component group (e.g., 'MySite Components')\n- configured: true\n\nAfter updating, ask me to create the component again.\n```\n\n### Why you should not explore the codebase when unconfigured:\n\nDoing any of the following before configuration is set will lead to incorrect assumptions and wasted effort:\n\n- Reading any other repository files\n- Listing directories to \"understand the project\"\n- Checking existing components for patterns\n- Looking at pom.xml, Java files, or folder structures\n- Inferring values from any source\n\nThe config file is the single source of truth for project values — skipping it leads to wrong paths and package names in every generated file.\n\n## No Hallucination Rule\n\nOnly create the exact fields the user specified — adding extra fields creates authoring confusion and maintenance burden, and renaming fields breaks content contracts.\n\n**Load reference for full rules:** `references\u002Fno-hallucination-rules.md`\n\n## Workflow Overview\n\n| Step | Action |\n| --- | --- |\n| 0 | Configuration validation (do this first — see above) |\n| 1 | Extract & validate component name |\n| 1.5 | Component extension decision (if extending) |\n| 2 | Gather requirements & confirm dialog specification |\n| 2.3 | Figma design fetch (if Figma URL provided) |\n| 3 | Create all component files |\n| 3.11 | Dependency verification (required for servlets) |\n| 4 | Completion summary |\n\n## Step 0: Configuration Validation\n\n### 0.1 Read Configuration\n\n1. Read `.aem-skills-config.yaml` from the project root\n2. Check that `configured: true`\n3. Read `project`, `package`, and `group` values\n\n### 0.2 Validate — Use Only the Config File\n\nDo not infer project values from the file system, existing components, Java files, pom.xml, or prior knowledge. These sources may be outdated or inconsistent — `.aem-skills-config.yaml` is the single source of truth because the user explicitly sets it.\n\n### 0.3 Load Conventions\n\n1. Read `references\u002Faem-conventions.md` for file structure templates, naming conventions, and patterns\n\n### 0.4 Project State Analysis (after configuration validated)\n\n1. **Check Component Name Uniqueness** - Look in `\u002Fapps\u002F[project]\u002Fcomponents\u002F`\n2. **Check Model Class Conflicts** - Look in `core\u002Fsrc\u002Fmain\u002Fjava\u002F[package-path]\u002Fmodels\u002F`\n3. **Analyze Existing Patterns** - Review 1-2 recent components for style reference\n\n## Step 1: Extract & Validate Component Name\n\n- Parse component name from user's message (ask if not provided)\n- Normalize to lowercase kebab-case (e.g., `My Component` -> `my-component`)\n- Validate: starts with letter, only letters\u002Fnumbers\u002Fhyphens, no consecutive hyphens\n\n## Step 1.5: Component Extension Decision\n\n### When user says \"extend {component}\":\n\n**Tier 1: Check Project Components First**\n\n- Search `\u002Fapps\u002F{project}\u002Fcomponents\u002F{component}`\n- If found -> Use as `sling:resourceSuperType`\n\n**Tier 2: Check Core Components**\n\n| User Says | Maps To |\n| --- | --- |\n| image | core\u002Fwcm\u002Fcomponents\u002Fimage\u002Fv3\u002Fimage |\n| teaser, card | core\u002Fwcm\u002Fcomponents\u002Fteaser\u002Fv2\u002Fteaser |\n| text, richtext | core\u002Fwcm\u002Fcomponents\u002Ftext\u002Fv2\u002Ftext |\n| title, heading | core\u002Fwcm\u002Fcomponents\u002Ftitle\u002Fv3\u002Ftitle |\n| list | core\u002Fwcm\u002Fcomponents\u002Flist\u002Fv4\u002Flist |\n| button, cta | core\u002Fwcm\u002Fcomponents\u002Fbutton\u002Fv2\u002Fbutton |\n| navigation, nav | core\u002Fwcm\u002Fcomponents\u002Fnavigation\u002Fv2\u002Fnavigation |\n| container, section | core\u002Fwcm\u002Fcomponents\u002Fcontainer\u002Fv1\u002Fcontainer |\n| accordion | core\u002Fwcm\u002Fcomponents\u002Faccordion\u002Fv1\u002Faccordion |\n| tabs | core\u002Fwcm\u002Fcomponents\u002Ftabs\u002Fv1\u002Ftabs |\n| carousel | core\u002Fwcm\u002Fcomponents\u002Fcarousel\u002Fv1\u002Fcarousel |\n| embed, video | core\u002Fwcm\u002Fcomponents\u002Fembed\u002Fv2\u002Fembed |\n\n**Tier 3: Not Found** - Ask user for clarification.\n\n**For extension patterns, load:** `references\u002Fextending-core-components.md`\n\n## Step 1.6: Core Component Extension Requirements\n\n**Required when extending with \"hide\", \"remove\", \"add custom field\", or \"override\"** (these operations need Sling Resource Merger patterns to work correctly):\n\n**Load reference:** `references\u002Fextending-core-components.md`\n\n| User Request | Action |\n| --- | --- |\n| \"Add custom fields\" | Create new tab OR add to existing |\n| \"Hide {tab}\" | Use sling:hideResource=\"{Boolean}true\" |\n| \"Hide {field}\" | Use sling:hideResource=\"{Boolean}true\" |\n| \"Override {field}\" | Use sling:hideProperties + new values |\n\n**When extending Core Components:**\n\n- Use `@Self @Via(type = ResourceSuperType.class)` for model delegation\n- Implement `ComponentExporter` interface\n- Add `resourceType` to `@Model` annotation\n- Use `sling:hideResource` in dialog for inherited tabs\u002Ffields\n\n> **Note:** If the parent component is a project component (not a Core Component), use direct Java class extension (`extends ParentModel`) instead of the delegation pattern. The `@Self @Via(type = ResourceSuperType.class)` pattern is only for Core Components. Load `references\u002Fextending-core-components.md` for the decision table.\n\n## Step 2: Gather Requirements\n\n### 2.1 Parse Dialog Specification\n\nEcho back EXACTLY what you understood before creating:\n\n```\nDialog Specification Confirmed:\nI will create exactly {N} fields:\n| # | Field Label | Field Type | Property Name |\n|---|-------------|------------|---------------|\n| 1 | {label1}    | {type1}    | {name1}       |\nNo additional fields will be added.\nIs this correct?\n```\n\n### 2.2 Mockup Image Handling\n\n- **Both mockup AND spec provided:** Dialog spec takes precedence. Mockup for HTML\u002FCSS only.\n- **Only mockup provided:** Propose fields and ASK for confirmation.\n\n### 2.3 Figma Design Input\n\n**Load:** `references\u002Ffigma-design-rules.md`\n\nWhen user provides a Figma URL (`figma.com\u002Fdesign\u002F...`, `figma.com\u002Fmake\u002F...`, or `figma.com\u002Fboard\u002F...`):\n\n1. **Parse the URL** to extract `fileKey` and `nodeId` (see references\u002Ffigma-design-rules.md Rule 1)\n\n- Convert `-` to `:` in the `node-id` query parameter\n- Use `branchKey` as `fileKey` for branch URLs\n\n1. **Call **`get_design_context` via the `plugin-figma-figma` MCP server (see Rule 2):`{ \"server\": \"plugin-figma-figma\", \"toolName\": \"get_design_context\", \"arguments\": { \"nodeId\": \"\u003Cextracted-node-id>\", \"fileKey\": \"\u003Cextracted-file-key>\", \"clientLanguages\": \"html,css,javascript\", \"clientFrameworks\": \"htl\" } }`\n2. **Extract design tokens** from the response — colors, fonts, sizes, spacing, layout (see Rules 3-4)\n3. **Use the Figma output** for HTL structure, CSS styling, and JS behavior — **NOT** for dialog fields\n\n**Precedence when BOTH dialog spec AND Figma URL are provided:**\n\n- **Dialog specification** → determines dialog fields (absolute precedence, no hallucination)\n- **Figma design** → determines HTML structure, CSS styling, JS behavior only\n\n**When ONLY Figma URL is provided (no dialog spec):**\n\n- Analyze the design and **PROPOSE** dialog fields to the user\n- **ASK for confirmation** before proceeding\n\n**Figma response handling:**\n\n- The response is React+Tailwind — treat as a REFERENCE, not production code\n- Convert JSX to semantic HTL with BEM classes (see Rule 5)\n- Extract all CSS values to the component clientlib (see Rule 6)\n- Create JS only if interactivity is implied (see Rule 7)\n- Do not hardcode Figma temporary image URLs — they expire and will break in production (see Rule 8)\n\n### 2.4 Dynamic Content Requirements\n\n| User Indicates | Servlet Required? |\n| --- | --- |\n| External API integration | Yes (GET) |\n| Dynamic data loading | Yes (GET) |\n| Form submission | Yes (POST) |\n| Search\u002Ffilter | Yes (GET) |\n| Static dialog content | No |\n\n## Step 3: Create Component Files\n\nCreate ALL files in this order:\n\n### 3.1 Component Definition\n\n**Path:** `ui.apps\u002Fsrc\u002Fmain\u002Fcontent\u002Fjcr_root\u002Fapps\u002F[project]\u002Fcomponents\u002F{component-name}\u002F.content.xml`\n\nLoad: `references\u002Faem-conventions.md`\n\n### 3.2 Component Dialog\n\n**Path:** `ui.apps\u002F...\u002Fcomponents\u002F{component-name}\u002F_cq_dialog\u002F.content.xml`\n\n**Load:** `references\u002Fdialog-patterns.md`\n\n**For extended components:** Load `references\u002Fextending-core-components.md` — Sling Resource Merger is required here because dialog inheritance only works through the merger; without it, parent dialog nodes won't be resolved.\n\n### 3.2.1 Image Field Handling\n\nWhen a user specifies an image or photo field:\n\n- **Default approach:** Embed the Core Image component via `data-sly-resource` — do NOT create a fileupload dialog field with manual `\u003Cimg>` rendering.\n- **Fileupload is only for non-image files** (PDFs, documents, etc.). Only use `cq\u002Fgui\u002Fcomponents\u002Fauthoring\u002Fdialog\u002Ffileupload` when the user explicitly asks for a non-image file upload.\n- **Load** `references\u002Fhtl-patterns.md` (Image Handling section) for the correct embedding pattern.\n\n### 3.3 HTL Template\n\n**Path:** `ui.apps\u002F...\u002Fcomponents\u002F{component-name}\u002F{component-name}.html`\n\n**Load:** `references\u002Fhtl-patterns.md`**If Figma URL provided, ALSO load:** `references\u002Ffigma-design-rules.md` (Rules 5, 8) — Convert JSX structure to semantic HTL with BEM classes. Replace static text with Sling Model expressions. Use the Figma screenshot as visual truth for element hierarchy.\n\n**i18n check:** If the component has static display text (labels, button text, placeholder strings), use HTL i18n expressions: `${'Label Text' @ i18n}`. Do not handle static text translation in the Sling Model — keep it in HTL where translation is automatic.\n\n### 3.4 Sling Model\n\n**Path:** `core\u002Fsrc\u002Fmain\u002Fjava\u002F[package-path]\u002Fmodels\u002F{ComponentName}Model.java`\n\n**Load:** `references\u002Fmodel-patterns.md`, `references\u002Fjava-standards.md`\n\n**For extensions:** Load `references\u002Fextending-core-components.md`\n\n**Delegation Pattern (for Core Component extensions):**\n\n```java\n@Model(adaptables = SlingHttpServletRequest.class,\n       adapters = {CustomModel.class, ComponentExporter.class},\n       resourceType = CustomModel.RESOURCE_TYPE)\n@Exporter(name = ExporterConstants.SLING_MODEL_EXPORTER_NAME,\n          extensions = ExporterConstants.SLING_MODEL_EXTENSION)\npublic class CustomModel implements ComponentExporter {\n    @Self @Via(type = ResourceSuperType.class)\n    private com.adobe.cq.wcm.core.components.models.List coreList;\n    \u002F\u002F Use FQN for core interfaces to avoid import collision\n}\n```\n\n### 3.5 Child Item Model - If Multifield\n\n**Path:** `core\u002Fsrc\u002Fmain\u002Fjava\u002F[package-path]\u002Fmodels\u002F{ItemName}.java`\n\n### 3.6 Unit Test\n\n**Path:** `core\u002Fsrc\u002Ftest\u002Fjava\u002F[package-path]\u002Fmodels\u002F{ComponentName}ModelTest.java`\n\n**Load:** `references\u002Ftest-patterns.md`\n\n### 3.7 Component Clientlib — Create for Every Component\n\n**Path:** `ui.apps\u002F...\u002Fclientlibs\u002Fclientlib-{component-name}\u002F`\n\n**Load:** `references\u002Fclientlib-patterns.md`**If Figma URL provided, ALSO load:** `references\u002Ffigma-design-rules.md` (Rules 6, 7) — Extract exact colors, fonts, sizes, spacing, border-radius from the Figma response. Place all CSS into `css\u002F{component-name}.css` using BEM naming. Create JS in `js\u002F{component-name}.js` only if the design implies interactivity. Verify pixel-perfect fidelity against the Figma screenshot.\n\n### 3.8 Dialog Clientlib - If Conditional Logic\n\n**Path:** `ui.apps\u002F...\u002Fclientlibs\u002Fclientlib-{component-name}-dialog\u002F`\n\n**Load:** `references\u002Fclientlib-patterns.md` (Dialog JavaScript Pattern section)\n\n### 3.9 Sling Servlet - If Dynamic Content\n\n**Path:** `core\u002Fsrc\u002Fmain\u002Fjava\u002F[package-path]\u002Fservlets\u002F{ComponentName}Servlet.java`\n\n**Load:** `references\u002Fsling-servlet-standards.md`\n\n### 3.10 Servlet Unit Test\n\n**Path:** `core\u002Fsrc\u002Ftest\u002Fjava\u002F[package-path]\u002Fservlets\u002F{ComponentName}ServletTest.java`\n\n### 3.11 Dependency Verification — Required for Servlets\n\n**Before completing, verify dependencies in **`core\u002Fpom.xml`**:**\n\n- Do not hardcode versions — check parent pom.xml for version properties instead, since hardcoded versions drift out of sync and cause build conflicts\n- Most common APIs included in `aem-sdk-api` (GSON, Jackson, Commons)\n- Use `provided` scope for AEM runtime libraries\n\n## Step 4: Completion Summary\n\n```\nComponent '{component-name}' created successfully!\n\n## Files Created\n- ui.apps\u002F...\u002Fcomponents\u002F{component-name}\u002F.content.xml\n- ui.apps\u002F...\u002Fcomponents\u002F{component-name}\u002F_cq_dialog\u002F.content.xml\n- ui.apps\u002F...\u002Fcomponents\u002F{component-name}\u002F{component-name}.html\n- core\u002F...\u002Fmodels\u002F{ComponentName}Model.java\n- core\u002F...\u002Fmodels\u002F{ComponentName}ModelTest.java\n- ui.apps\u002F...\u002Fclientlibs\u002Fclientlib-{component-name}\u002F\n[+ servlet files if applicable]\n\n## Dialog Fields (Exact Match)\n{table matching specification}\n\nWould you like me to add any additional fields or build the project?\n```\n\n## Quick Reference: Field Type Mapping\n\n| User Says | Granite Resource Type |\n| --- | --- |\n| Textfield | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Ftextfield |\n| Textarea | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Ftextarea |\n| Richtext, RTE | cq\u002Fgui\u002Fcomponents\u002Fauthoring\u002Fdialog\u002Frichtext |\n| Pathfield, Path | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fpathfield |\n| Image, Photo | Embed Core Image component (see references\u002Fhtl-patterns.md Image Handling section). Do not use fileupload for image rendering. |\n| Fileupload, File Upload | cq\u002Fgui\u002Fcomponents\u002Fauthoring\u002Fdialog\u002Ffileupload (for non-image files: PDFs, documents) |\n| Multifield | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fmultifield |\n| Checkbox | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fcheckbox |\n| Select, Dropdown | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fselect |\n| Numberfield | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fnumberfield |\n| Datepicker | granite\u002Fui\u002Fcomponents\u002Fcoral\u002Ffoundation\u002Fform\u002Fdatepicker |\n\nFor complete mappings: `assets\u002Ffield-type-mappings.md`\n\n## Reference Files\n\nLoad on-demand based on what you're creating:\n\n| Creating | Load Reference |\n| --- | --- |\n| Any component | .aem-skills-config.yaml (project root, load first — see Configuration Gate Check), then references\u002Faem-conventions.md |\n| Dialog XML | references\u002Fdialog-patterns.md |\n| HTL Template | references\u002Fhtl-patterns.md |\n| Sling Model | references\u002Fmodel-patterns.md, references\u002Fjava-standards.md |\n| Unit Tests | references\u002Ftest-patterns.md |\n| Clientlibs | references\u002Fclientlib-patterns.md |\n| Extending Core Component | references\u002Fextending-core-components.md |\n| Extending Core Component — worked example & checklists | references\u002Fextending-core-components-example.md (load when you need a complete worked example of extending a Core Component, unit testing patterns, or the implementation checklist) |\n| Sling Servlet | references\u002Fsling-servlet-standards.md |\n| Core Component patterns | references\u002Fcore-components.md |\n| No Hallucination rules | references\u002Fno-hallucination-rules.md |\n| Figma design integration | references\u002Ffigma-design-rules.md |\n| Troubleshooting | references\u002Ftroubleshooting.md |\n| Examples | references\u002Fexamples.md |\n\nIf encountering issues during or after component creation, consult `references\u002Ftroubleshooting.md` for common problems and solutions.",{"name":5,"license":15,"metadata":24,"description":28,"compatibility":29},{"author":25,"version":26,"aem_version":27},"AEM Dev Agent","1.0","6.5\u002FCloud Service","Creates complete AEM components with dialog, HTL template, Sling Model, unit tests, and clientlibs.\nSupports extending Core Components and project components. When a Figma design URL is provided,\nfetches the design via Figma MCP (get_design_context) and translates it into pixel-perfect HTL, CSS,\nand JS. Follows Adobe Experience League best practices for AEM Cloud Service and 6.5.\nUse this skill whenever the user mentions creating, building, generating, or scaffolding an AEM\ncomponent, or mentions component types like teaser, card, hero, banner, accordion, tabs, carousel,\nlist, navigation, breadcrumb, or any custom AEM component. Also trigger when the user wants to\nextend a Core Component, create a component dialog, add a Sling Model, or convert a Figma design\ninto an AEM component.\n","Requires AEM as a Cloud Service or AEM 6.5. Maven project structure with core, ui.apps modules. Figma design integration requires the `plugin-figma-figma` MCP server to be enabled in the IDE.","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fadobe-create-component","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add kalash33\u002Fkstack --skill create-component",{"tool":44,"command":45},"bunx","bunx skills add kalash33\u002Fkstack --skill create-component",{"tool":47,"command":48},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill create-component","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002FSKILL.md",true,[52,58,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"assets\u002Ffield-type-mappings.md","ASSET","资产文件",3855,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Fassets\u002Ffield-type-mappings.md",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"README.md","REFERENCE","参考文档",3383,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002FREADME.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Faem-conventions.md",7282,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Faem-conventions.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fclientlib-patterns.md",15084,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Fclientlib-patterns.md",{"path":73,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fcore-components.md",9743,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Fcore-components.md",{"path":77,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fdialog-patterns.md",15673,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Fdialog-patterns.md",{"path":81,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fexamples.md",9858,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Fexamples.md",{"path":85,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fextending-core-components-example.md",17029,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Fextending-core-components-example.md",{"path":89,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fextending-core-components.md",13100,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Fextending-core-components.md",{"path":93,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Ffigma-design-rules.md",22802,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Ffigma-design-rules.md",{"path":97,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fhtl-patterns.md",16854,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Fhtl-patterns.md",{"path":101,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fjava-standards.md",4762,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Fjava-standards.md",{"path":105,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fmodel-patterns.md",9681,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Fmodel-patterns.md",{"path":109,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fno-hallucination-rules.md",1235,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Fno-hallucination-rules.md",{"path":113,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fsling-servlet-standards.md",12639,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Fsling-servlet-standards.md",{"path":117,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Ftest-patterns.md",9283,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Ftest-patterns.md",{"path":121,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":122,"sourceHtmlUrl":123},"references\u002Ftroubleshooting.md",8059,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-create-component\u002Freferences\u002Ftroubleshooting.md",[125,133,140,147,154,161],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":129,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":129,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":129,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":129,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":129,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":129,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]