@iress-oss/ids-mcp-server 0.0.1-dev.3 → 0.0.1

package/generated/docs/foundations-user-experience-docs.md

@@ -1,63 +0,0 @@
-[](#user-experience)User experience
-===================================
-
-We use heuristic guidelines to assess the usability and user-centred design quality of all Iress products.
-
-[](#system-feedback)System Feedback
------------------------------------
-
-*   Always show users where they are, what just happened, and what’s possible next.
-*   Provide immediate visual and textual feedback for all actions and states.
-*   Ensure feedback is clear, contextual, and proportionate to the importance of the action.
-
-[](#language-and-mental-models)Language and Mental Models
----------------------------------------------------------
-
-*   Use user-centred language and avoid technical jargon.
-*   Follow cultural and industry conventions for colour, iconography, terminology, and layout.
-*   Align interaction patterns with real-world analogues wherever feasible.
-
-[](#control-and-forgiveness)Control and Forgiveness
----------------------------------------------------
-
-*   Make actions reversible and provide undo where errors may occur.
-*   Let users easily backtrack, edit inputs, or abandon flows.
-*   Provide escape hatches from any process without penalty.
-
-[](#standards-and-consistency)Standards and Consistency
--------------------------------------------------------
-
-*   Use consistent layout, labelling, iconography, and grammar.
-*   Reinforce expectations by placing similar elements in predictable positions.
-*   Apply colour, spacing, and visual patterns consistently across all screens.
-
-[](#error-prevention-and-recovery)Error Prevention and Recovery
----------------------------------------------------------------
-
-*   Prevent errors by anticipating misuse and validating early.
-*   Phrase error messages with clarity, empathy, and constructive suggestions.
-*   Where errors occur, explain why and how they can be resolved.
-
-[](#recognition-over-recall)Recognition Over Recall
----------------------------------------------------
-
-*   Display necessary information at the point of decision.
-*   Use visual grouping, spacing, and affordance to reveal hierarchy.
-*   Prioritise visual clarity over novelty.
-
-[](#simplicity-and-minimalism)Simplicity and Minimalism
--------------------------------------------------------
-
-*   Remove unnecessary detail—every word, element, or feature should earn its place.
-*   Design for clarity of purpose with visually distinct, semantically meaningful UI components.
-*   Use whitespace, clean alignment, and simplified flows to reduce cognitive load.
-
-On this page
-
-*   [System Feedback](#system-feedback)
-*   [Language and Mental Models](#language-and-mental-models)
-*   [Control and Forgiveness](#control-and-forgiveness)
-*   [Standards and Consistency](#standards-and-consistency)
-*   [Error Prevention and Recovery](#error-prevention-and-recovery)
-*   [Recognition Over Recall](#recognition-over-recall)
-*   [Simplicity and Minimalism](#simplicity-and-minimalism)

package/generated/docs/foundations-visual-design-docs.md

@@ -1,46 +0,0 @@
-[](#visual-design-standards)Visual Design Standards
-===================================================
-
-[](#typography)Typography
--------------------------
-
-*   Use systematic font sizing with heading scales (H1-H6)
-*   Implement consistent line heights and font weights
-*   Provide text colour hierarchies (primary, muted, success, warning, danger)
-*   Support responsive typography scaling
-
-[](#colour-system)Colour System
--------------------------------
-
-*   Maintain semantic colour meanings:
-    *   **Primary**: Main call-to-action colour with high contrast
-    *   **Success**: Positive outcomes and confirmations
-    *   **Warning**: Caution and important notices
-    *   **Danger**: Errors and destructive actions
-    *   **Info**: Neutral information and guidance
-    *   **Positive/Negative**: Financial context (buy/sell actions)
-*   Ensure all colour combinations meet accessibility contrast requirements
-*   Provide consistent hover and active state colours
-
-[](#spacing-and-layout)Spacing and Layout
------------------------------------------
-
-*   Use systematic spacing scale (xs, sm, md, lg, xl)
-*   Apply consistent gutter systems for layout components
-*   Implement responsive breakpoints for adaptive layouts
-*   Maintain proper margin and padding relationships
-
-[](#interactive-states)Interactive States
------------------------------------------
-
-*   Provide clear hover, focus, active, and disabled states
-*   Use consistent transition timing and easing
-*   Implement proper focus indicators for keyboard navigation
-*   Show loading states for asynchronous operations
-
-On this page
-
-*   [Typography](#typography)
-*   [Colour System](#colour-system)
-*   [Spacing and Layout](#spacing-and-layout)
-*   [Interactive States](#interactive-states)