mdk-gen
Read-onlyIdempotent
Generates MDK pages, actions, i18n files, and rule examples from prompts or search queries to simplify mobile app development.
Instructions
Generates MDK artifacts including pages, actions, i18n files, and rule references. Returns prompts for LLM processing (pages, actions, i18n) or searches for rule examples.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| folderRootPath | No | The path of the current project root folder (not required for rule artifact type). | |
| artifactType | Yes | The type of artifact to generate: • page: Generate MDK page files (.page) with databinding or layout • action: Generate MDK action files (.action) • i18n: Generate internationalization files (.properties) • rule: Search for and return relevant JavaScript rule examples | |
| pageType | No | The type of page (required when artifactType is 'page'): • databinding: Data-driven pages with controls bound to OData • layout: Structure-focused pages with specific layouts | |
| controlType | No | The control type for databinding pages (required when pageType is 'databinding'). | |
| oDataEntitySets | No | Optional: The OData entity sets to use for page/action generation, separated by commas (required only when artifactType is 'action' or artifactType is 'page' and pageType is 'databinding'). | |
| layoutType | No | The layout type for layout pages (required when pageType is 'layout'). | |
| actionType | No | The type of action (required when artifactType is 'action'). | |
| query | No | Search query for rule reference (required only when artifactType is 'rule'). Examples: 'get app name', 'handle form validation', 'navigate to page', etc. |