@maltjoy/mcp-server 0.5.0-beta.0 → 0.6.0-beta.0

package/dist/doc/zeroheight/guidelines/3060512/meta.json

@@ -1,13 +0,0 @@
-{
-  "source": "https://zeroheight.com/6bf479565/",
-  "title": "🔁 PATTERNS",
-  "slug": "patterns",
-  "category": "guidelines",
-  "component": null,
-  "pageId": 3060512,
-  "pageUid": "3060512",
-  "fetchedAt": "2026-07-15T08:24:45.690Z",
-  "tabs": [],
-  "imagesPath": "packages/core-vue/static/zeroheight/patterns/",
-  "extraction": "zeroheight-api"
-}

package/dist/doc/zeroheight/guidelines/3060514/description.md

@@ -1 +0,0 @@
-A **form pattern** is a pre-defined arrangement of components, such as input fields, labels, and buttons, that guides users through a process of submitting information.

package/dist/doc/zeroheight/guidelines/3060514/meta.json

@@ -1,16 +0,0 @@
-{
-  "source": "https://zeroheight.com/6bf479565/",
-  "title": "Forms pattern",
-  "slug": "forms-pattern",
-  "category": "guidelines",
-  "component": null,
-  "pageId": 3060514,
-  "pageUid": "3060514",
-  "fetchedAt": "2026-07-15T08:24:45.761Z",
-  "tabs": [
-    "Overview",
-    "Usage"
-  ],
-  "imagesPath": "packages/core-vue/static/zeroheight/forms-pattern/",
-  "extraction": "zeroheight-api"
-}

package/dist/doc/zeroheight/guidelines/3060514/overview.md

@@ -1,9 +0,0 @@
-![Form pattern example](/uploads/AQD8Qt-9ZDwnfWtbP-IcMQ.png)
-
-## Specifications
-
-### Stacking
-
-> Stacking is a form of spacing that creates equal distance between components or a group of items.
-
-#### Example

package/dist/doc/zeroheight/guidelines/3060514/usage.md

@@ -1,36 +0,0 @@
-## Required vs Optional
-
-Why use optional fields is always better than required :
-
-- **An asterisk is obvious to you, not to everyone, believe me, there are always some who do not understand**
-- **There are always more fields required than optional**
-- **Less visual noise on your form makes it more readable and therefore faster to complete**
-
-#### Rules
-
-- Do: Add optional only on the required field
-- Don't: Add the * in all the mandatory fields
-
-### Style
-
-|  | Size | Style | Colors |
-| Label | [See documentation](https://joy.malt.com/6bf479565/p/89d9e2-text-input/t/92d67e) | Regular | $-joy-color-neutral-gray-6 |
-| Optional | 14px | Italic | $-joy-color-neutral-gray-4 |
-### Example
-
-![image](/uploads/TGFVsV9NKfgA25ntbZhRLg.png)
-
-## Form validation pattern
-
-### Rule
-
-Keep the button component active but on click navigates the error field
-
-### Do/don't
-
-- Do: On click go on the first error field and then by scrolling go on the next one
-- Don't: Don't go on the second error field
-- Don't: Submit button can only be disabled if a non-validation reason exists (Role, etc.)
-- Do: If it's possible, don't hide the error field content and put it on the first plan 
-- Do: If a Submit button is disabled, it should always have a tooltip explaining the reason.
-- Do: When the user click on the submit button, if the validation is successful, the button should display a loading state and be disabled.

package/dist/doc/zeroheight/guidelines/3279582/content-localization-plugin.md

@@ -1,27 +0,0 @@
-## Content  & localization Plugin
-
-### **Pseudoloc**
-
-**Check if your designs are localization ready**
-
-1. Run the Figma plugin without changing the settings.
-2. Identify the areas where the content breaks the design.
-3. Apply changes and run the plugin one last time to make sure your design is ready.
-
-[Link to the tutorial](https://www.notion.so/maltcommunity/Pseudolocalization-Figma-plugin-5246d951032c4144b04fee7f168be606)
-
-![image](/uploads/FfrHAPMfnrSjHsE4Nadf2A.png)
-
-## Hemingway
-
-**Assess the accessibility**
-
-1. Run the Figma plugin or copy/paste your content in the web app.
-2. Identify the areas of improvement with the color code.
-3. Aim at a “Grade 7” for your readability score.
-
-[Link to the tutorial](https://www.loom.com/share/b2e9ee9fc8044d0ea4a6d6fa9c14c05f)
-
-![image](/uploads/uEVQgF5YhQeuE3jDwgmS8w.png)
-
-## Workflow plugin

package/dist/doc/zeroheight/guidelines/3279582/description.md

@@ -1 +0,0 @@
-Plugin enhance our experience in Figma, they facilitate our life and are real time saver. In order to be Joy compliant we recommend the use of the following plugins.

package/dist/doc/zeroheight/guidelines/3279582/meta.json

@@ -1,17 +0,0 @@
-{
-  "source": "https://zeroheight.com/6bf479565/",
-  "title": "Figma: Plugins & Widgets",
-  "slug": "figma-plugins-widgets",
-  "category": "guidelines",
-  "component": null,
-  "pageId": 3279582,
-  "pageUid": "3279582",
-  "fetchedAt": "2026-07-15T08:24:45.755Z",
-  "tabs": [
-    "Plugins",
-    "Widgets",
-    "Content & Localization plugin"
-  ],
-  "imagesPath": "packages/core-vue/static/zeroheight/figma-plugins-widgets/",
-  "extraction": "zeroheight-api"
-}

package/dist/doc/zeroheight/guidelines/3279582/plugins.md

@@ -1,46 +0,0 @@
-![image](/uploads/WLOubnm6FNlBDw3gK6ejkA.png)
-
-Plugin enhance our experience in FIGMA, they facilitate our life and are real time saver! In order to be Joy compliant we recommend the use of the following plugins.
-
-## Workflow plugin
-
-### Apply Variables
-
-- **Swap styles with variables** of the same name
-- **Apply matching variables (autofix)** to radius or AutoLayout dimension properties
-
-### Style Organizer
-
-Merge and link all color & text styles in the page:
-
-- Overall usage assessment
-
-- Group elements with the same appearance together
-
-- Merge and link to selected style
-
-- Select all elements with the style
-
-- Make all possible fix automatically with a single click
-
-### Deepl translate
-
-Translate texts in Figma width DeepL's engine
-
-1. Install the plugin
-2. use this API key `e3629d90-e443-8ad9-8027-3f7560c7b43a:fx`
-3. Translate
-
-#### How to use
-
-### Rename It
-
-Batch rename selected layer & frame
-
-### Figma Auto-Name
-
-Rename all your layers in one click. Thanks to AI.
-
-#### How to use
-
-![image](/uploads/ENwrPb8IZH7eMAC1AiCYzA.gif)

package/dist/doc/zeroheight/guidelines/3279582/widgets.md

@@ -1,18 +0,0 @@
-Widgets are interactive objects that extend the functionality of design files and FigJam boards. Unlike plugins that run for a specific person, everyone can see and interact with the same widget.
-
-## Jira
-
-Create, link & update your tickets directly from Figma
-
-## Navigate
-
-Use this widget to guide people through your boards with smooth animations.
-
-## Approved
-
-Simply put status on mockups
-
-- Approved
-- Revision
-- Pending
-- Rejected

package/dist/doc/zeroheight/guidelines/3286138/changelog.md

@@ -1 +0,0 @@
-## Change log

package/dist/doc/zeroheight/guidelines/3286138/content.md

@@ -1 +0,0 @@
-

package/dist/doc/zeroheight/guidelines/3286138/description.md

@@ -1 +0,0 @@
-Component description

package/dist/doc/zeroheight/guidelines/3286138/introduction.md

@@ -1,47 +0,0 @@
-## Anatomy
-
-## State
-
-#### Size M
-
-### Subnavigation
-
-#### Main Tab
-
-### Dropdown
-
-### Subtab
-
-### Bottom item
-
-## Animation
-
-#### Transition
-
-| `$transition-duration--Default: 200ms;` |
-## Icons
-
-## Components
-
-### Desktop
-
-### Mobile
-
-## Breakpoint
-
-| **Size of navigation** | **Variables** | **Values** |
-|  | `$bp-screen-tiny_max` | 0 to 359px |
-|  | `$bp-screen-xxs_min` | 360px |
-|  | `$bp-screen-xxs_max` | 479px |
-|  | `$bp-screen-xs_min` | 480px |
-|  | `$bp-screen-xs_max` | 767px |
-| XS (Mobile) | `$bp-screen-sm_min` | 768px |
-|  | `$bp-screen-sm_max` | 991px |
-|  | `$bp-screen-md_min` | 992px |
-| S (Tablet) | `$bp-screen-md_max` | 1199px |
-|  | `$bp-screen-lg_min` | 1200px |
-|  | `$bp-screen-lg_max` | 1599px |
-| **M (Desktop)** | `$bp_screen_xlg_min` | > 1600px |
-## Navigation behavior
-
-## Related

package/dist/doc/zeroheight/guidelines/3286138/meta.json

@@ -1,18 +0,0 @@
-{
-  "source": "https://zeroheight.com/6bf479565/",
-  "title": "Side Navigation",
-  "slug": "side-navigation",
-  "category": "guidelines",
-  "component": null,
-  "pageId": 3286138,
-  "pageUid": "3286138",
-  "fetchedAt": "2026-07-15T08:24:45.883Z",
-  "tabs": [
-    "Introduction",
-    "Usage",
-    "Content",
-    "🔄 Changelog"
-  ],
-  "imagesPath": "packages/core-vue/static/zeroheight/side-navigation/",
-  "extraction": "zeroheight-api"
-}

package/dist/doc/zeroheight/guidelines/3286138/usage.md

@@ -1,11 +0,0 @@
-## Occurrences
-
-| Composent | Size | Product | Page |
-| Header |  | Transversal | Transversal |
-| Profil Cards |  | Freelance | Search |
-## Hovering
-
-1. Wait 0.5 seconds.
-2. If the pointer is still hovering over a navbar item, display its menu within 0.1 seconds.
-3. Keep showing it until the pointer has been outside both the navbar item and the drop-down for 0.5 seconds.
-4. Then, remove it in less than 0.1 seconds.

package/dist/doc/zeroheight/guidelines/3780230/introduction.md

@@ -1,36 +0,0 @@
-![Layout page](/uploads/fHv5GK6grf9c9tYSlbn_bw.png)
-
-## Type of content
-
-| Name of container | Device | Size of container | Margin type |
-| Fixed | Desktop | 1024px | % |
-| Fluid | Desktop | 100% | 32px |
-| Fluid | Tablet | 100% | 24px |
-| Fluid | Mobile | 100% | 16px |
-## Desktop
-
-### Funnel
-
-#### When should I use a funnel layout?
-
-The funnel layout is used when you want to push the user in a step-by-step action.
-
-The main navigation is not displayed and the user cannot leave the page via the header
-
-### Open Navigation - M
-
-### 
-
-### Closed Navigation - S
-
-## Mobile
-
-#### Funnel
-
-### Open Navigation
-
-#### Bottom sheet
-
-## Tablet
-
-## Related

package/dist/doc/zeroheight/guidelines/3780230/meta.json

@@ -1,13 +0,0 @@
-{
-  "source": "https://zeroheight.com/6bf479565/",
-  "title": "Layout type",
-  "slug": "layout-type",
-  "category": "guidelines",
-  "component": null,
-  "pageId": 3780230,
-  "pageUid": "3780230",
-  "fetchedAt": "2026-07-15T08:24:45.820Z",
-  "tabs": [],
-  "imagesPath": "packages/core-vue/static/zeroheight/layout-type/",
-  "extraction": "zeroheight-api"
-}

package/dist/doc/zeroheight/guidelines/3781391/code.md

@@ -1 +0,0 @@
-

package/dist/doc/zeroheight/guidelines/3781391/description.md

@@ -1 +0,0 @@
-The information helper allows you to add additional information or explanation by clicking on an icon.

package/dist/doc/zeroheight/guidelines/3781391/introduction.md

@@ -1,38 +0,0 @@
-![Information helper in a dialog](/uploads/zWBXnhzYr9p95HmjU2zvEA.png)
-
-## Anatomy
-
-## Usage
-
-By clicking on the (?) icon we will display extra information following theses rules :
-
-| Type of component | Size | Action | Content |
-| Tooltips | 16px | While hovering | - Text |
-| Product Tour | 16px | On Click | - Text - Badge |
-| Dialogs | 16px | On Click | - Text - Image - Hight light |
-## Components
-
-### Desktop
-
-### Animation
-
-| **Token** | Components | **Behavior** |
-| `$transition-duration--Default: 200ms;` | Helper | While hovering the (?) |
-| `$transition-duration--Default: 200ms;` | Tooltips | How the tooltip appear |
-| `$transition-duration--Default: 200ms;` | Product Tour | How the product tour appear |
-| `$transition-duration--slow: 400ms;` | Dialogs | How the dialog appear |
-## Example
-
-#### Tooltips
-
-![image](/uploads/cLACTk4r3LdA42vD-PRukg.gif)
-
-#### Dialog
-
-![image](/uploads/oP3vI9eX0K3OSCa2rBgMsg.gif)
-
-#### Product tour
-
-![image](/uploads/Rws1jA_xV-4XWp18GYYaWA.gif)
-
-## Related

package/dist/doc/zeroheight/guidelines/3781391/meta.json

@@ -1,17 +0,0 @@
-{
-  "source": "https://zeroheight.com/6bf479565/",
-  "title": "Information helper",
-  "slug": "information-helper",
-  "category": "guidelines",
-  "component": null,
-  "pageId": 3781391,
-  "pageUid": "3781391",
-  "fetchedAt": "2026-07-15T08:24:45.798Z",
-  "tabs": [
-    "Introduction",
-    "Usage",
-    "Code"
-  ],
-  "imagesPath": "packages/core-vue/static/zeroheight/information-helper/",
-  "extraction": "zeroheight-api"
-}

package/dist/doc/zeroheight/guidelines/3781391/usage.md

@@ -1,14 +0,0 @@
-## Occurrences
-
-| Composent | Size | Product | Page |
-| Header |  | Transversal | Transversal |
-| Profil Cards |  | Freelance | Search |
-## Title
-
-- Do: null
-- Don't: null
-
-## Title
-
-- Do: null
-- Don't: null

package/dist/doc/zeroheight/guidelines/3782376/code.md

@@ -1 +0,0 @@
-

package/dist/doc/zeroheight/guidelines/3782376/description.md

@@ -1 +0,0 @@
-The title page component allows us to standardize the way we use titles within a page

package/dist/doc/zeroheight/guidelines/3782376/introduction.md

@@ -1,11 +0,0 @@
-## Type
-
-### Sidebar
-
-## Demo
-
-#### Example :
-
-![image](/uploads/ANlI0wAA7HYlAcpn-HGJCg.svg)
-
-## Related

package/dist/doc/zeroheight/guidelines/3782376/meta.json

@@ -1,17 +0,0 @@
-{
-  "source": "https://zeroheight.com/6bf479565/",
-  "title": "Title page",
-  "slug": "title-page",
-  "category": "guidelines",
-  "component": null,
-  "pageId": 3782376,
-  "pageUid": "3782376",
-  "fetchedAt": "2026-07-15T08:24:45.905Z",
-  "tabs": [
-    "Introduction",
-    "Usage",
-    "Code"
-  ],
-  "imagesPath": "packages/core-vue/static/zeroheight/title-page/",
-  "extraction": "zeroheight-api"
-}

package/dist/doc/zeroheight/guidelines/3782376/usage.md

@@ -1,11 +0,0 @@
-## Occurrences
-
-| Composent | Size | Product | Page |
-| Header |  | Transversal | Transversal |
-| Profil Cards |  | Freelance | Search |
-## Do/don't
-
-- Do: Use the componant with the good typogrphy (Moderat)
-- Don't: Don't use Agrandir typo for the title
-- Do: Use the good size for subtitle (Primary-400 : 16px)
-- Don't: Don't use other size for subtitle

package/dist/doc/zeroheight/guidelines/3992574/create-a-jira-ticket-for-development.md

@@ -1,47 +0,0 @@
-### When do I need to create a Jira Ticket?
-
-The Jira ticket is created once all the validation steps by the DS manager have been completed and validated.
-
-See the rules -> [How to contribute  | Workflow](https://zeroheight.com/6bf479565/p/595691/b/549c89)
-
-- The components/guidelines are designed in Figma and documented here
-
-- The feasibility has been studied and discussed with the development team concerned
-
-### Step 1 - Go to Jira
-
-#### 🧑🏻‍💻 AS AN ENGINEER
-
-Go to the Front-end Jira board (Ask right to the IT team if needed)
-
--> [https://malt-community.atlassian.net/jira/software/c/projects/FEP/boards/120](https://malt-community.atlassian.net/jira/software/c/projects/FEP/boards/120)
-
-[Check the previous tickets](https://malt-community.atlassian.net/jira/software/c/projects/FEP/boards/120?quickFilter=468)
-
-### Step 2 - Create the ticket
-
-#### 🧑🏻‍💻 AS AN ENGINEER
-
-![image](/uploads/X2RKULhH_qcA6GC5gJTUng.png)
-
-1. Select the type of ticket - **Task, bug...**
-2. Select the State - Selected for development
-3. Select a clear and understandable title  - 	[JOY] New icon pack 1.3
-4. Select the proper component - Design system
-5. Add a proper description
-
-Example of description
-
-- What: Add a new XS button
-- Why: To use on a small table
-- Impact: Need to fit all the different states and typology of buttons
-- Add the link to the documentation with all the specs
-- Add the Figma link
-- Add examples from other design systems if need
-
-![image](/uploads/l0L9znp4XtperdGfiZjauQ.png)
-
-1. Select the Responsable
-2. Create the Ticket
-
-![image](/uploads/bSj7wLtOVCBPYLOqJveX8w.png)

package/dist/doc/zeroheight/guidelines/3992574/create-a-notion-ticket.md

@@ -1,51 +0,0 @@
-### Step 1 : Create
-
-#### 🙅‍♀️ AS A DESIGNER
-
-- Go on the [Design system backlog 2024](https://www.notion.so/maltcommunity/9779b425d491475eb879d04c11a8ccd8?v=b71b30afda074736b6f3d655505e42c0)
-
-- Create a new task on the bottom of the colomn "`🗄️ BACKLOG`"
-
-- Select a clear and understandable title
-
-- ***[NEW] New input tags for Mobile***
-- ***[NEW] New size of button - XL***
-
-![image](/uploads/9QQB2PFGegIaXkdZTG7Oyg.png)
-
-### Step 2 : Select attributes
-
-#### 🙅‍♀️ AS A DESIGNER
-
-- Figma Link
-- Point of contact
-
-![image](/uploads/5EQ997G5w0RwybfScKOmQg.png)
-
-### Step 3 : Content
-
-#### 🙅‍♀️ AS A DESIGNER
-
-I try to explain briefly my need and as much as possible information and context
-
-- Figma file with your proposal
-- Any links or info that you think useful
-- Coded example (if it exists) from
-
-- [https://codepen.io/](https://codepen.io/) (account available in the last pass)
-- [https://material.io/](https://material.io/)
-- ...
-
-Explanation :
-
-- What
-- Why
-- How
-
-![image](/uploads/8uOC5OwjFKgtO--aaZfBLw.png)
-
-### Step 4 : Publish
-
-#### 🙅‍♀️ AS A DESIGNER
-
-- Publish the new task

package/dist/doc/zeroheight/guidelines/3992574/description.md

@@ -1 +0,0 @@
-On this page you will the workflow to properly ask a new components or update a current one with the design system team

package/dist/doc/zeroheight/guidelines/3992574/meta.json

@@ -1,17 +0,0 @@
-{
-  "source": "https://zeroheight.com/6bf479565/",
-  "title": "How to contribute ",
-  "slug": "how-to-contribute",
-  "category": "guidelines",
-  "component": null,
-  "pageId": 3992574,
-  "pageUid": "3992574",
-  "fetchedAt": "2026-07-15T08:24:45.782Z",
-  "tabs": [
-    "Workflow",
-    "Create a Notion Ticket",
-    "Create a Jira ticket for development"
-  ],
-  "imagesPath": "packages/core-vue/static/zeroheight/how-to-contribute/",
-  "extraction": "zeroheight-api"
-}