-
Notifications
You must be signed in to change notification settings - Fork 784
Add Maia Agent Skills documentation #11203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: development
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,33 +10,57 @@ description_list: true | |
| ## Introduction | ||
|
|
||
| {{% alert color="info" %}} | ||
| Maia Make capabilities are grouped into a conversational interface, which is available in Studio Pro 11.8 and above. | ||
| Maia Make capabilities are available in Studio Pro 11.8 and above. | ||
|
|
||
| To use this interface and Maia Make capabilities, an internet connection and signing in to Studio Pro are required. | ||
| To use Maia Make capabilities, an internet connection and signing in to Studio Pro are required. | ||
| {{% /alert %}} | ||
|
|
||
| Maia Make is a set of AI-assisted development capabilities in Studio Pro that are available through a unified conversational interface. Describe your requirements in natural language, and Maia generates development artifacts such as data structures, pages, and microflows. | ||
|
|
||
| You can also ask Maia to provide explanations of your existing documents, such as microflows, workflows, and pages. Moreover, this interface allows you to integrate with external tools, such as Playwright and Figma, via MCP Servers, and it supports story-based development by generating app artifacts based on existing user stories. | ||
|
|
||
| The key Maia Make capabilities are as follows: | ||
| ## Maia Capabilities Overview | ||
|
|
||
| * Conversational assistance for general Mendix development queries | ||
| * Explanations of documents to clarify existing implementation details | ||
| * Generation of documents from natural language descriptions, such as domain model, pages, and microflows | ||
| * Integration with external tools, such as Playwright and Figma, via compatible MCP Servers | ||
| * Story-based development to help realize existing user stories | ||
| * Support for PDF and image inputs to help Maia better understand your requirements | ||
| * Adding relevant documents, such as microflows and pages, to the interface to give Maia a more desired context | ||
| * Editing existing documents, including renaming elements inside of documents such as entities, attributes, and microflow parameters | ||
| * Removing elements from documents, enabling more advanced refactoring (in Studio Pro 11.9 and above) | ||
| * Undoing changes generated on a per-document basis (in Studio Pro 11.9 and above) | ||
| The following table lists the major Maia Make capabilities, their descriptions, and the Studio Pro versions in which they were introduced as part of Maia Make: | ||
|
|
||
| {{% alert color="info" %}} | ||
| Support for workflows, view entities, enumerations, constants, modules, Java actions, and JavaScript actions was introduced in Studio Pro 11.9. In this version, Java actions are read-only; they can be used in microflows and explained. JavaScript actions can only be explained. | ||
| | Capability | Description | Available in Maia Make from | | ||
| | --- | --- | --- | | ||
| | [Maia Chat](/refguide/maia-chat/) | Answers questions about all aspects of Mendix development. | Studio Pro 11.8 | | ||
| | [Maia Explain](/refguide/maia-explain/) | Explains the purpose and logic of existing documents such as microflows and pages. | Studio Pro 11.8 | | ||
| | [Maia for Domain Model](/refguide/maia-for-domain-model/) | Generates and explains domain models. | Studio Pro 11.8 | | ||
| | [Maia for Pages](/refguide/maia-for-pages/) | Generates pages and widgets from text or image input. | Studio Pro 11.8 | | ||
| | [Maia for Microflows](/refguide/maia-for-microflows/) | Generates microflow logic from natural language descriptions. | Studio Pro 11.8 | | ||
| | [Maia for Workflows](/refguide/maia-for-workflows/) | Generates workflows from natural language or image input. | Studio Pro 11.9 | | ||
| | [Maia for OQL](/refguide/maia-for-oql/) | Generates and manages OQL queries. | Studio Pro 11.9 | | ||
| | [Maia MCP Client](/refguide/maia-mcp/) | Connects Maia to external MCP servers, giving it access to third-party tools during chat. | Studio Pro 11.8 | | ||
| | [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/) | Exposes Studio Pro as an MCP server for use by external AI tools. | Studio Pro 11.10 | | ||
| | [Maia Web Fetch](/refguide/maia-web-fetch/) | Fetches and reads content from public websites and APIs during chat. | Studio Pro 11.10 | | ||
| | [Maia Agent Skills](/refguide/maia-agent-skills/) | Extends Maia with reusable, domain-specific knowledge that applies automatically when relevant. | Studio Pro 11.11 | | ||
|
|
||
| In addition to the core capabilities listed above, Maia Make includes the following features: | ||
|
|
||
| | Capability | Description | Available in Maia Make from | | ||
| | --- | --- | --- | | ||
| | Story-based development | Generates app artifacts based on existing user stories to support story-driven development workflows. | Studio Pro 11.8 | | ||
| | PDF/image support | Allows you to provide PDFs and images as input to help Maia better understand your requirements. | Studio Pro 11.8 | | ||
| | Adding documents as context | Lets you add relevant documents, such as microflows and pages, to provide Maia with additional context during chat. | Studio Pro 11.8 | | ||
| | Editing existing documents | Enables Maia to modify existing documents, including renaming elements such as entities, attributes, and microflow parameters. | Studio Pro 11.8 | | ||
| | Removing elements | Allows Maia to remove elements from documents to support more advanced refactoring tasks. | Studio Pro 11.9 | | ||
| | Undo support | Allows you to undo Maia-generated changes on a per-document basis. | Studio Pro 11.9 | | ||
|
|
||
| ### Other Supported Document Types | ||
|
|
||
| In Studio Pro 11.9, support for enumerations, constants, modules, Java actions, and JavaScript actions was added. In this version, Java actions are read-only; they can be used in microflows and explained. JavaScript actions can only be explained. | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Suggestion: Should we extend one of the existing tables or add a new table instead of having this very long sentence? I think it will be easier for us to maintain if we use a table. One thing we could do is separate document types from features and group them together that way. Currently you have a capability table on line 26, which includes both document types as well as general Maia features. And then again the same on line 42, which mostly contains features. What do you think? Could we perhaps restructure this?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I like this idea. The only thing is that if we group the capabilities conceptually, as you suggested, the order will no longer match the navigation menu under Maia Make Capabilities. That’s only a minor drawback, though. In the long run, grouping them conceptually could indeed make future updates easier. |
||
|
|
||
| Starting with Studio Pro 11.10, Maia can generate JavaScript actions, add parameters to existing ones, and create or update the JavaScript file associated with a JavaScript action. | ||
| {{% /alert %}} | ||
|
|
||
| ### Support for Folder Structure | ||
|
|
||
| In Studio Pro 11.10 and above, Maia understands and leverages the existing folder structure within your Mendix applications for all documents except for pages. This enables Maia to: | ||
|
KONRADS098 marked this conversation as resolved.
|
||
|
|
||
| * Organize documents into folders: When creating new documents, Maia can place them directly into relevant folders, respecting your project's organization. | ||
| * Follow existing folder structures: Maia works within your established folder hierarchy, making it easier to maintain consistency. | ||
| * Adhere to Mendix best practices: Maia can help organize documents according to the standard Mendix best practices for folder structure. For detailed guidance on optimal organization of folders, refer to the [Folder Structure](/refguide/naming-convention-best-practices/#folder-structure) section in *Naming Convention Best Practices*. | ||
|
|
||
| ## Using Maia Make Capabilities | ||
|
|
||
|
|
@@ -67,29 +91,6 @@ The conversational interface includes the following options: | |
| * **{{% icon name="paperclip" %}} Add** (Image, Story, PDF) - With this option, you can attach images, PDFs, or user stories to help Maia understand your requirements better. | ||
| * **Add file to Maia Chat** (@ icon) - It allows you to add certain logic or pages to Maia as context. You can also access this option by right-clicking the documents (microflows or pages) in the **App Explorer** and it appears in the context menu. | ||
|
|
||
| #### Support for Folder Structure | ||
|
|
||
| In Studio Pro 11.10 and above, Maia understands and leverages the existing folder structure within your Mendix applications for all documents except for pages. This enables Maia to: | ||
|
|
||
| * Organize documents into folders: When creating new documents, Maia can place them directly into relevant folders, respecting your project's organization. | ||
| * Follow existing folder structures: Maia works within your established folder hierarchy, making it easier to maintain consistency. | ||
| * Adhere to Mendix best practices: Maia can help organize documents according to the standard Mendix best practices for folder structure. For detailed guidance on optimal organization of folders, refer to the [Folder Structure](/refguide/naming-convention-best-practices/#folder-structure) section in *Naming Convention Best Practices*. | ||
|
|
||
| For more information on how each Maia Make capability work, refer to the following documents: | ||
|
|
||
| * [Maia Chat](/refguide/maia-chat/) | ||
| * [Maia Explain](/refguide/maia-explain/) | ||
| * [Maia for Domain Model](/refguide/maia-for-domain-model/) | ||
| * [Maia for Pages](/refguide/maia-for-pages/) | ||
| * [Maia for Microflows](/refguide/maia-for-microflows/) | ||
| * [Maia for Workflows](/refguide/maia-for-workflows/) (in Studio Pro 11.9 and above) | ||
| * [Maia for OQL](/refguide/maia-for-oql/) (in Studio Pro 11.9 and above) | ||
| * [Maia MCP Client](/refguide/maia-mcp/) | ||
| * [Studio Pro MCP Server](/refguide/studio-pro-mcp-server/) | ||
| * [Maia Web Fetch](/refguide/maia-web-fetch/) | ||
|
|
||
| In Studio Pro 11.8 and above, most of the features described in the documents above are available only through the chat interface. There are no separate entry points to these features in their respective editors. [Maia Explain](/refguide/maia-explain/) is an exception. You can still access this feature by right-clicking the documents (for example, microflows or pages) in the **App Explorer** and the **Maia Explain** option is in the context menu. | ||
|
|
||
| ## Read More | ||
|
|
||
| * [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/) | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,101 @@ | ||
| --- | ||
| title: "Maia Agent Skills" | ||
| linktitle: "Agent Skills" | ||
| url: /refguide/maia-agent-skills/ | ||
| weight: 95 | ||
| description: "Describes how to create and manage agent skills that equip Maia with domain-specific knowledge, applied automatically whenever relevant." | ||
| #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details. | ||
| --- | ||
|
|
||
| ## Introduction | ||
|
|
||
| {{% alert color="info" %}} | ||
| This feature was released as part of [Maia Make](/refguide/maia-make/) capabilities in Studio Pro 11.11. | ||
|
|
||
| To use Maia Agent Skills, an internet connection and signing in to Studio Pro are required. | ||
| {{% /alert %}} | ||
|
Yiyun333 marked this conversation as resolved.
|
||
|
|
||
| Maia Agent Skills are modular, reusable instructions that extend Maia's capabilities with domain-specific knowledge, giving it the context, workflows, and guidance it needs to work the way your team works. | ||
|
|
||
| Instead of typing the same context into every chat, you define agent skills once, and Maia applies them automatically whenever relevant. This eliminates the need to repeat the same guidance across conversations. | ||
|
|
||
| Use agent skills to equip Maia with the domain knowledge and conventions it needs, whether those are company-wide standards or team-specific workflows. For example, a skill capturing your company's Mendix naming conventions means Maia applies them consistently whenever it generates entities, attributes, or microflows without you having to mention them each time. | ||
|
|
||
| For guidance on writing effective skills, see [Best Practices for Skill Creators](https://agentskills.io/skill-creation/best-practices) and [Optimizing Skill Descriptions](https://agentskills.io/skill-creation/optimizing-descriptions) in the [Agent Skills documentation](https://agentskills.io/). | ||
|
|
||
| ## Creating an Agent Skill {#creating-a-skill} | ||
|
|
||
| To create a new agent skill in Studio Pro, follow these steps: | ||
|
|
||
| 1. In the **App Explorer**, expand **Maia** > **skills**. | ||
| 2. Right-click **skills** and click **Add** > **Skill**. | ||
| 3. Enter a name for the skill. | ||
|
|
||
| Studio Pro creates the `SKILL.md` file. You can continue adding the skill content. | ||
|
|
||
| ### SKILL.md Format {#skill-md-format} | ||
|
|
||
| Each `SKILL.md` file must include YAML frontmatter at the top, followed by the skill content in Markdown: | ||
|
|
||
| ```yaml | ||
| --- | ||
| name: your-skill | ||
| description: Applies company-wide naming conventions for entities, attributes, and microflows. | ||
| --- | ||
|
|
||
| Write your skill instructions here in plain Markdown. Use the `references/` subdirectory | ||
| to add supplementary content and refer to it from here as needed. | ||
|
|
||
| See [my-reference](references/my-reference.md) for details. | ||
| ``` | ||
|
|
||
| | Field | Required | Description | | ||
| | --- | --- | --- | | ||
| | `name` | Yes | Must match the skill's parent directory name exactly. For full naming rules, see [Agent Skills Specification](https://agentskills.io/specification#name-field). | | ||
| | `description` | Yes | See [Agent Skills Specification](https://agentskills.io/specification#description-field). | | ||
|
|
||
| The `name` field must match the skill's parent directory name exactly. A mismatch prevents the skill from loading. For example, if the skill directory is `skillssource/your-skill/`, the `name` field must be `your-skill`. | ||
|
|
||
| ### Directory Structure {#directory-structure} | ||
|
|
||
| Skills are stored in the `skillssource/` directory at the root of your application directory. You can also manage skills directly in the file system, for example, to copy in skills from another project. After making changes in the file system, go to **App** > **Synchronize App Directory** (keyboard shortcut: <kbd>F4</kbd>) to make the changes visible in Studio Pro. | ||
|
|
||
| ``` | ||
| skillssource/ | ||
| your-skill/ | ||
| SKILL.md | ||
| references/ | ||
| GLOSSARY.md | ||
| NOTES.md | ||
| ``` | ||
|
|
||
| ## Adding Reference Files {#reference-files} | ||
|
|
||
| Reference files let you keep your skill focused by moving supplementary content into separate documents, such as a glossary of domain terms, a data dictionary, or detailed architecture notes. Maia accesses reference file content on demand, only when relevant to your request. | ||
|
|
||
| To add a reference file to a skill, follow these steps: | ||
|
|
||
| 1. In the **App Explorer**, under **Maia** > **skills**, right-click the skill you want to add a reference to. | ||
| 2. Click **Add** > **Reference**. | ||
| 3. Enter a name for the reference file. | ||
|
|
||
| For more information on how skills and reference files load, and when they apply, see [Agent Skills Specification](https://agentskills.io/specification#progressive-disclosure). | ||
|
|
||
| ## How Agent Skills Work | ||
|
|
||
| At the start of each chat session, Maia becomes aware of all agent skills in your project. As you work, Maia picks up the relevant skill content automatically. You do not need to reference or invoke skills explicitly. | ||
|
|
||
| If you add or edit a skill while a session is active, those changes take effect the next time you start a chat. | ||
|
|
||
| ## Limitations {#limitations} | ||
|
|
||
| * Only Markdown files are supported as reference files. Files in other formats are ignored. | ||
| * Changes you make to skills take effect the next time you start a chat. | ||
|
|
||
| ## Read More | ||
|
|
||
| * [Maia Make Capabilities](/refguide/maia-make/) | ||
| * [Mendix AI Assistance (Maia)](/refguide/mendix-ai-assistance/) | ||
| * [Maia Chat](/refguide/maia-chat/) | ||
| * [Best Practices for Skill Creators](https://agentskills.io/skill-creation/best-practices) – guidance on writing effective skill content | ||
| * [Agent Skills Specification](https://agentskills.io/specification) – the full specification for the agent skills format | ||
Uh oh!
There was an error while loading. Please reload this page.