Hexagone Frontend Documentation -- Navigation Skill

This skill gives you access to the Hexagone frontend component documentation (@his/hexa-components) published as GitLab Pages. Your role is to fetch and read the relevant documentation files when answering questions about Hexagone frontend components, patterns, and conventions.

What is Hexagone frontend documentation

The Hexagone frontend is built with Vue.js 2 using a custom component library (@his/hexa-components) with beta-scss utility classes and Vuex with vuex-pathify for state management. The documentation site is published at:

https://erp-pas.gitlab-pages-erp-pas.dedalus.lan/hexagone/frontend/hexagone-documentation

The site is a single-page application (SPA) and cannot be fetched directly. Instead, use the raw markdown files from the GitLab repository, which are specifically optimized for LLM consumption.

When to use this skill:

• The user asks about a Hexagone UI component (<btn>, <multiselect>, <data-table>, etc.)
• The user needs props, events, or usage examples for a Hexagone component
• The user asks about beta-scss CSS utility classes (flex:6/12, p:1, m:1, etc.)
• The user asks about the Vuex store modules (user, session, environment, navigation, etc.)
• The user asks about the API utility (Api(), StandardApi())
• The user asks about custom directives (v-focus, v-uppercase)
• The user asks about form validation rules or form patterns in Hexagone
• The user is building or modifying a Hexagone Web frontend view/space
• Any question mentioning "Hexagone" combined with "component", "composant", "frontend", "Vue", "template", "formulaire", or "interface"

Critical conventions

IMPORTANT: Hexagone uses custom tag names. NEVER use standard HTML tags for these components.

Key rules:

• All components are globally registered -- no import needed in templates
• Form fields must be wrapped in <div class="input-field"><label for="id">Label</label><!-- component --></div>
• Use beta-scss utility classes: flex, flex:wrap, flex:6/12, p:1, m:1, etc.
• Store access via vuex-pathify: this.$store.get('module/path') and this.$store.set('module/path', value)
• Library: @his/hexa-components, Framework: Vue.js 2

Documentation catalog

The raw files are available at:

BASE_RAW_URL = https://gitlab-erp-pas.dedalus.lan/erp-pas/hexagone/frontend/hexagone-documentation/-/raw/master/docs/llm/

Components (36 components)

Forms and input

Navigation and actions

Data display

User feedback

Layout

Patterns

Reference

Tag-to-file quick lookup

Use this table to quickly find which file to fetch when the user mentions a component tag:

CSS utility classes (beta-scss)

These classes are available without any fetch -- use them directly:

Icons

Use the <icon> component with the icon name:

<icon>checked</icon>
<icon>close</icon>
<icon>search</icon>
<icon>edit</icon>

Icons come from @his/fonts-icons.

How to answer questions

Step 1: Identify the relevant file

Map the user's question to one or more documentation files using the tables above:

• Specific component tag (e.g., <btn>, <multiselect>) --> use the tag-to-file lookup
• Component name (e.g., "datatable", "datepicker") --> match to the component catalog
• Store / state management --> fetch patterns/store.md
• API / web service calls --> fetch patterns/api.md
• Directives (v-focus, v-uppercase) --> fetch reference/directives.md
• Form validation / required fields --> fetch reference/form-rules.md
• Events (click, keyboard) --> fetch reference/events.md
• CSS classes --> use the CSS utility table above (no fetch needed)
• Icons --> use the icons section above (no fetch needed)
• General "list all components" --> use the catalog above (no fetch needed)

Step 2: Fetch the file

Use WebFetch to retrieve the raw markdown file from GitLab:

WebFetch: url="${BASE_RAW_URL}<file-path>" prompt="Return the full content of this markdown file"

For example:

• Button component: WebFetch: url="https://gitlab-erp-pas.dedalus.lan/erp-pas/hexagone/frontend/hexagone-documentation/-/raw/master/docs/llm/components/button.md" prompt="Return the full content"
• Store pattern: WebFetch: url="https://gitlab-erp-pas.dedalus.lan/erp-pas/hexagone/frontend/hexagone-documentation/-/raw/master/docs/llm/patterns/store.md" prompt="Return the full content"

Fetch only the file(s) you need. Do not fetch all files at once.

If WebFetch fails (network error, timeout), inform the user that the GitLab instance is unreachable and suggest they:

1. Access the documentation site directly: https://erp-pas.gitlab-pages-erp-pas.dedalus.lan/hexagone/frontend/hexagone-documentation
2. Browse the source repo: https://gitlab-erp-pas.dedalus.lan/erp-pas/hexagone/frontend/hexagone-documentation/-/tree/master/docs/llm

Step 3: Extract and present the answer

After fetching, extract the relevant information:

1. For a specific component: present the props table, events table, and usage examples
2. For a pattern: present the API/function signature, options, and examples
3. For a reference topic: present the relevant rules, tables, or directives

Present the information clearly, preserving the original structure (prop tables, event tables, code examples).

Step 4: Cross-reference if needed

If the user's question spans multiple topics (e.g., "how do I build a form with datepicker and validation?"), fetch multiple files and compose a coherent answer showing how to combine the components.

Response guidelines

When presenting component documentation, use this structure:

## <ComponentName> (`<tag-name>`)

**Library:** @his/hexa-components
**Source:** [file URL]

### Props
| Prop | Type | Default | Description |
|------|------|---------|-------------|

### Events
| Event | Description |
|-------|-------------|

### Example
[Code example from the documentation]

Important rules

1. Always fetch from the GitLab repository -- never answer from memory or general knowledge about Vue.js components. Hexagone has specific conventions (custom tags, beta-scss, vuex-pathify) that differ from standard Vue.js patterns.

2. Quote the source file when presenting information: always mention which documentation file the information comes from.

3. Do not invent props, events, or component behavior -- if the information is not found in the fetched file, say so explicitly. Do not guess or extrapolate.

4. Respect Hexagone conventions:

   • Use <btn> not <button>, <multiselect> not <select>, <data-table> not <table>
   • Wrap form fields in <div class="input-field">
   • Use beta-scss utility classes, not custom CSS
   • Use this.$store.get() / this.$store.set() for store access

5. Handle missing documentation gracefully -- if a component is not documented, inform the user and suggest they check the hexagone-documentation site or open an issue in the repository at https://gitlab-erp-pas.dedalus.lan/erp-pas/hexagone/frontend/hexagone-documentation.

6. Cross-reference with hexagone-swdoc -- if the question involves calling Hexagone backend web services from a frontend view, suggest using the hexagone-swdoc skill for the API contract details and the Api() / StandardApi() utility from this skill for the frontend call pattern.

7. Form field pattern to always follow:

   <div class="input-field">
     <label for="myField">My Label</label>
     <!-- component here -->
   </div>
   

8. Use <btn-group> instead of <multiselect> when options are fewer than 6 -- this avoids an extra click and shows all options directly.