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

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

@@ -0,0 +1,4 @@
+## Occurence
+
+| Composent | Product | Page |
+| Profil Cards | Freelance | Search Results |

package/dist/doc/zeroheight/guidelines/2447204/figma-cover.md

@@ -0,0 +1,3 @@
+## Freelancer Tribe
+
+## Client Tribe

package/dist/doc/zeroheight/guidelines/2447204/figma-page-structure.md

@@ -0,0 +1,3 @@
+## Page structure
+
+![image](/uploads/L3ut-MWVKvaO0urIzG2_Fw.png)

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

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Start a new project",
+  "slug": "start-a-new-project",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 2447204,
+  "pageUid": "2447204",
+  "fetchedAt": "2026-07-15T08:24:45.894Z",
+  "tabs": [
+    "Template",
+    "Figma Page Structure",
+    "Figma Cover"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/start-a-new-project/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/2447204/template.md

@@ -0,0 +1,42 @@
+## 1- Open Starter File
+
+### Step 1 : Duplicate It
+
+![image](/uploads/_X_VmP1njl1-7OINsVeniA.png)
+
+### Step 2 : Move it into the right team
+
+![image](/uploads/xPRwsuJBh6nG9if4Wrdk-w.png)
+
+## 2- Open your new template
+
+### Step 1 : Change Name file
+
+Following the current status option, update the template file name with your name project
+
+#### Figma Name Status
+
+**🚧 : Design in Progress**
+
+✅ : **Ready To Dev**
+
+📦 : **Done**
+
+🔍 : **Exploration**
+
+### Step 2: Update cover
+
+The cover allows to quickly differentiate the projects within the Figma teams
+
+Update it with the following information :
+
+- Name tribe
+- Designer name
+- Project name
+- Short resumer
+- Starting Date
+- Project Status
+
+![image](/uploads/56RP4pAZzJqHTpQ1DG5G6w.gif)
+
+## 3- Enjoy

package/dist/doc/zeroheight/guidelines/2465594/change-log.md

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

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1 @@
+A dedicated, compact display used to present a user's key profile information, such as their name, photo, and title, across the product.

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

@@ -0,0 +1,35 @@
+![Profile card portrait example](/uploads/E5ZYKM4ddVMaNGCCfE0HTA.png)
+
+## Anatomy
+
+### Portrait
+
+### Landscape
+
+## Type of user card
+
+| **Variant** | **Purpose** |
+| Portrait | Compact lists (e.g., AI search, Keywork search). |
+| Landscape | Full-width results displays where quick scanning is primary (e.g., **ATS**). |
+## Size
+
+| Format | Type | **Size** | **Height** |
+| Portrait | / | MEDIUM | / |
+| Landscape | 3 Columns Side-by-Side | LARGE | ≥1024px |
+| Landscape | 2 Columns + Bottom Row | MEDIUM | min width - 768max width - 1023 |
+| Landscape | Single Column Stack | SMALL | <768px |
+## Components
+
+### Portrait
+
+### Landscape
+
+### Slots
+
+#### Body
+
+#### Header informations
+
+## Example
+
+## Related

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

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Profile Card",
+  "slug": "profile-card",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 2465594,
+  "pageUid": "2465594",
+  "fetchedAt": "2026-07-15T08:24:45.863Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "🚧 Content",
+    "Change log 🔄"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/profile-card/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1,8 @@
+### **Usage**
+
+The Freelancer Profile Card provides a consistent, high-level summary of a freelancer's professional profile. Its primary function is to allow users to quickly scan and compare key information across various product views before engaging with a full profile.
+
+### Do/don't
+
+- Do: Do use truncation (e.g., an ellipsis ...) for the freelancer's long title or location in the smaller layout.
+- Don't: Don't add complex, secondary data like a detailed project history or full bio directly to the card.

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

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

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

@@ -0,0 +1,5 @@
+## iOS
+
+## Android
+
+## Related

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

@@ -0,0 +1,16 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "App Store Icons",
+  "slug": "app-store-icons",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 2487804,
+  "pageUid": "2487804",
+  "fetchedAt": "2026-07-15T08:24:45.700Z",
+  "tabs": [
+    "Introduction",
+    "Usage"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/app-store-icons/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1,14 @@
+## 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/2732341/components.md

@@ -0,0 +1,24 @@
+## Components
+
+A component is a single, reusable chunk of a user interface.
+
+In Joy :
+
+- Components / View
+- Components / Forms
+
+References :
+
+- [Component Gallery : What is a component ?](https://component.gallery/about/#what-is-a-component)
+
+## Web Components
+
+Web Components are a collection of browser features and JavaScript APIs that allow developers to define custom elements by extending native HTML elements. Web Components aren't just another framework, they're a standardised way to build components that work across browsers and devices, without the need to load a large JavaScript library.
+
+In Joy :
+
+- Check the technical documentation : [https://doc.malt.tech/joy-storybook/](https://doc.malt.tech/joy-storybook/?path=/story/versions-core-2-6-0--page)
+
+References :
+
+- [https://www.webcomponents.org/introduction](https://www.webcomponents.org/introduction)

package/dist/doc/zeroheight/guidelines/2732341/core-design.md

@@ -0,0 +1,15 @@
+## Core design
+
+What we define as **CORE DESIGN** is the MALT's **own UI identity **built with our [design tokens](https://joy.malt.com/6bf479565/p/571cec-glossary/t/482ccb).
+
+It defines all the rules and the visual design that we want to display in the MALT ecosystem (web, app, mail...).
+
+#### Examples :
+
+In this example, our dialog respects the CORE design. The content inside is free and not design system related but the global UI respect and use all the components and rules based on JOY.
+
+- Do: Good use of our design tokens
+- Don't: - Wrong Colors
+- Wrong typographies
+- Wrong shaping (Radius)
+- Wrong buttons alignements

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

@@ -0,0 +1 @@
+Welcome to our technical glossary, you will find definitions of regularly used terms in Joy

package/dist/doc/zeroheight/guidelines/2732341/design-tokens.md

@@ -0,0 +1,34 @@
+## Design Tokens
+
+A design token is like a building block for making things look good on a website or app. Just like how you use Legos to build a toy house, designers use design tokens to build the look and feel of a digital product.
+
+Design tokens are the specific values for colors, font sizes, spacings, and other design elements that are used consistently throughout a product to maintain its visual coherence.
+
+Think of it like a recipe for making a yummy cake. A design token is like the list of ingredients you need, and the instructions you follow to make the cake look and taste just right.
+
+By using design tokens, designers can make sure that the website or app they are building looks great and works well, no matter what device someone is using to view it.
+
+We use design tokens to define and build our [CORE DESIGN](https://joy.malt.com/6bf479565/p/571cec-glossary/t/666ffd) patterns.
+
+Our design tokens in Joy are :
+
+- [Colors](https://zeroheight.com/6bf479565/p/027b08)
+- [Elevation](https://zeroheight.com/6bf479565/p/8989ce)
+- [Spacings](https://zeroheight.com/6bf479565/p/175ef4)
+- [Typography ](https://zeroheight.com/6bf479565/p/549b42)
+- [Transition](https://zeroheight.com/6bf479565/p/86c854)
+- [Shape](https://zeroheight.com/6bf479565/p/43c94f)
+- [Spacings](https://zeroheight.com/6bf479565/p/175ef4)
+
+#### **Examples :**
+
+![image](/uploads/wy8nKZdaYr-h_nMGRVtOzw.svg)
+
+![image](/uploads/zawgtXxLOj8Wfm-Y3RSGgw.svg)
+
+References :
+
+- [Design Tokens for dummies](https://uxdesign.cc/design-tokens-for-dummies-8acebf010d71)
+- [Brad Frost : Design tokens](https://bradfrost.com/blog/tag/design-tokens/)
+- [Design Tokens : What they are and how to use them](https://www.invisionapp.com/inside-design/design-tokens/)
+-

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

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "📓 Glossary",
+  "slug": "glossary",
+  "category": "guidelines",
+  "component": null,
+  "pageId": 2732341,
+  "pageUid": "2732341",
+  "fetchedAt": "2026-07-15T08:24:45.689Z",
+  "tabs": [
+    "Core Design",
+    "Design Tokens",
+    "Components",
+    "Theme"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/glossary/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/guidelines/2732341/theme.md

@@ -0,0 +1,20 @@
+## Theme
+
+The theme define how our brand will apply on our UI
+
+Theming affects our entire UI, including individual components, like a button.
+
+In Joy :
+
+- [Colors](https://zeroheight.com/6bf479565/p/027b08)
+- [Brand](https://zeroheight.com/6bf479565/n/68f93a)
+
+#### **Examples :**
+
+In this example by changing the [design tokens](https://joy.malt.com/6bf479565/p/571cec-glossary/t/482ccb) we can apply différents theme to our [Core design ](https://joy.malt.com/6bf479565/p/571cec-glossary/t/666ffd)
+
+![Default vs Dark Theme vs Blue Theme](/uploads/8_rMkkTqoAeEHrdUXLAQsg.svg)
+
+References :
+
+- [Material Theming](https://material.io/design/material-theming/overview.html#using-material-theming)

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

@@ -0,0 +1 @@
+A **pattern** is a collection of components, or "molecules," arranged in a specific configuration to solve a common user problem (e.g., a login form or a navigation bar). Following the Atomic Design principle, patterns act as "organisms" that provide a repeatable and consistent solution for a recurring design challenge, ensuring a cohesive user experience across all products.

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1,13 @@
+{
+  "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

@@ -0,0 +1 @@
+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

@@ -0,0 +1,16 @@
+{
+  "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

@@ -0,0 +1,9 @@
+![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

@@ -0,0 +1,36 @@
+## 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

@@ -0,0 +1,27 @@
+## 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

@@ -0,0 +1 @@
+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

@@ -0,0 +1,17 @@
+{
+  "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

@@ -0,0 +1,46 @@
+![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

@@ -0,0 +1,18 @@
+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

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

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

@@ -0,0 +1 @@
+

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

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

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

@@ -0,0 +1,47 @@
+## 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

@@ -0,0 +1,18 @@
+{
+  "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

@@ -0,0 +1,11 @@
+## 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

@@ -0,0 +1,36 @@
+![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