enonic-content-type-generator

Included with Lifetime

$97 forever

Generates Enonic XP content type XML schema definitions from natural-language descriptions. Covers structured content modeling including input types, form layout, option sets, item sets, mixins, x-data, and content-type inheritance. Use when creating, scaffolding, or generating Enonic XP content type definitions, adding fields or sets to existing content types, or querying Enonic XP input types and super-types. Do not use for non-Enonic content modeling, GraphQL queries, JavaScript/TypeScript controllers, or generic XML editing unrelated to Enonic schemas.

Backend & APIsscriptsassets

What this skill does


# Enonic XP Content Type Generator

## Procedures

**Step 1: Detect Enonic XP Project**
1. Execute `node scripts/find-enonic-targets.mjs [workspaceRoot]` to locate Enonic XP project roots.
2. If the script returns an empty array, warn that no Enonic XP project markers were found and ask for the target directory.
3. Store the detected project root for use in subsequent steps.

**Step 2: Gather Requirements**
1. Identify the content type name from the request. The name must be lowercase-hyphenated (e.g., `blog-post`).
2. Identify the display name — a human-readable label (e.g., `Blog Post`).
3. Determine the super-type. Default to `base:structured` unless the request specifies a folder (`base:folder`) or another built-in type.
4. List all requested fields with their input types. Read `references/content-type-reference.md` to map natural-language field descriptions to the correct Enonic XP input type and configuration.
5. Identify any item sets (repeatable grouped fields), option sets (single-select or multi-select choices), or mixin references.
6. If the request mentions a mixin, determine whether to generate the mixin file or reference an existing one.
7. If the request mentions x-data, determine whether to generate the x-data file or reference an existing one.

**Step 3: Generate the Content Type XML**
1. Read `assets/content-type.template.xml` to obtain the starter template.
2. Replace `DISPLAY_NAME` with the display name from Step 2.
3. Replace `DESCRIPTION` with a short description or remove the element if none was provided.
4. Set the `<super-type>` element to the value determined in Step 2.
5. Populate the `<form>` element with the identified inputs, item sets, option sets, field sets, and mixin references.
6. For each input:
   - Set the `name` attribute using camelCase.
   - Set the `type` attribute to the exact Enonic XP input type name (case-sensitive).
   - Add `<label>`, `<occurrences>`, `<help-text>`, `<default>`, and `<config>` as required.
7. For ComboBox and RadioButton inputs, include all options inside `<config>`.
8. For ContentSelector, ImageSelector, and MediaSelector inputs, include `<config>` with `allowContentType`, `allowPath`, `treeMode`, and `hideToggleIcon` as specified.
9. For TextLine and TextArea, add `<config>` with `max-length`, `show-counter`, or `regexp` if validation constraints are requested.
10. For Long and Double, add `<config>` with `min` and `max` if range constraints are requested.
11. For DateTime, add `<config>` with `<timezone>true</timezone>` if timezone-aware storage is requested.
12. If examples are needed for reference, read `references/examples.md`.

**Step 4: Write the File**
1. Construct the target path: `[projectRoot]/src/main/resources/site/content-types/[name]/[name].xml`
2. Create the directory if it does not exist.
3. Write the generated XML to the file.
4. If a mixin was generated, write it to: `[projectRoot]/src/main/resources/site/mixins/[name]/[name].xml`
5. If x-data was generated, write it to: `[projectRoot]/src/main/resources/site/x-data/[name]/[name].xml`
6. If x-data references are needed in `site.xml`, add `<x-data>` entries with `allowContentTypes` and `optional` attributes as specified.

**Step 5: Validate Output**
1. Verify the generated XML is well-formed.
2. Confirm every `<input>` has a valid `type` attribute by cross-referencing `references/content-type-reference.md`.
3. Confirm all `name` attributes are unique within their nesting level.
4. Confirm `<occurrences>` values are logically consistent (minimum <= maximum, or maximum = 0 for unlimited).
5. If the request asks about super-types, input types, or schema structure without requesting file generation, answer the question using `references/content-type-reference.md` without creating files.

## Error Handling

* If `scripts/find-enonic-targets.mjs` exits with a non-zero code, report the stderr message and ask for the project root path manually.
* If the requested input type does not match any known Enonic XP input type, read `references/content-type-reference.md` and suggest the closest match. Do not invent input type names.
* If XML validation fails, read `references/troubleshooting.md` to diagnose and correct the error, then regenerate the file.
* If a mixin reference cannot be resolved, confirm the mixin file path exists before writing the content type.

Files: 6

Size: 42.0 KB

Complexity: 80/100

Category: Backend & APIs

Source: https://github.com/webmaxru/enonic-agent-skills/tree/main/skills/enonic-content-type-generator

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts