@iress-oss/ids-mcp-server 0.0.1 → 5.14.2

package/build/tools.js

@@ -1,165 +0,0 @@
-/**
- * Tool definitions for the IDS MCP Server
- */
-export const toolDefinitions = [
-    {
-        name: "find_component",
-        description: "Find IDS components by name or functionality. Perfect for discovering which component to use for specific UI needs.",
-        inputSchema: {
-            type: "object",
-            properties: {
-                query: {
-                    type: "string",
-                    description: "Component name (e.g., 'button', 'input') or functionality (e.g., 'form submission', 'navigation')",
-                },
-                category: {
-                    type: "string",
-                    description: "Optional: filter by category (components, foundations, resources)",
-                    enum: ["components", "foundations", "resources"],
-                },
-            },
-            required: ["query"],
-        },
-    },
-    {
-        name: "get_component_props",
-        description: "Get detailed prop information and usage examples for IDS components. Essential for implementing components correctly.",
-        inputSchema: {
-            type: "object",
-            properties: {
-                component: {
-                    type: "string",
-                    description: "Component name (e.g., 'button', 'input', 'table')",
-                },
-            },
-            required: ["component"],
-        },
-    },
-    {
-        name: "get_usage_examples",
-        description: "Get code examples and implementation patterns for IDS components. Shows real-world usage in React applications.",
-        inputSchema: {
-            type: "object",
-            properties: {
-                component: {
-                    type: "string",
-                    description: "Component name to get examples for",
-                },
-                pattern: {
-                    type: "string",
-                    description: "Optional: specific usage pattern (e.g., 'form', 'modal', 'table')",
-                },
-            },
-            required: ["component"],
-        },
-    },
-    {
-        name: "search_ids_docs",
-        description: "Search across all IDS documentation for specific terms, patterns, or implementation details.",
-        inputSchema: {
-            type: "object",
-            properties: {
-                query: {
-                    type: "string",
-                    description: "Search term (component names, props, CSS classes, implementation patterns)",
-                },
-                case_sensitive: {
-                    type: "boolean",
-                    description: "Whether to perform case-sensitive search",
-                    default: false,
-                },
-            },
-            required: ["query"],
-        },
-    },
-    {
-        name: "list_components",
-        description: "List all available IDS components, organized by category. Great for component discovery.",
-        inputSchema: {
-            type: "object",
-            properties: {
-                category: {
-                    type: "string",
-                    description: "Filter by category: components, foundations, or resources",
-                    enum: ["components", "foundations", "resources", "all"],
-                    default: "all",
-                },
-            },
-        },
-    },
-    {
-        name: "get_design_tokens",
-        description: "Get information about IDS design tokens (colors, spacing, typography) for consistent UI implementation.",
-        inputSchema: {
-            type: "object",
-            properties: {
-                type: {
-                    type: "string",
-                    description: "Type of design token to search for",
-                    enum: ["colors", "spacing", "typography", "breakpoints", "all"],
-                    default: "all",
-                },
-            },
-        },
-    },
-    {
-        name: "get_iress_component_info",
-        description: "Get comprehensive information about Iress components mentioned by their full name (e.g., IressButton, IressInput, IressTable). Perfect for when components are mentioned with the Iress prefix.",
-        inputSchema: {
-            type: "object",
-            properties: {
-                component_name: {
-                    type: "string",
-                    description: "Full Iress component name (e.g., 'IressButton', 'IressInput', 'IressTable')",
-                },
-                include_examples: {
-                    type: "boolean",
-                    description: "Whether to include usage examples in the response",
-                    default: true,
-                },
-                include_props: {
-                    type: "boolean",
-                    description: "Whether to include prop information in the response",
-                    default: true,
-                },
-            },
-            required: ["component_name"],
-        },
-    },
-    {
-        name: "analyze_component_mentions",
-        description: "Analyze text to find all Iress component mentions (e.g., IressButton, IressInput) and provide information about each one.",
-        inputSchema: {
-            type: "object",
-            properties: {
-                text: {
-                    type: "string",
-                    description: "Text content to analyze for Iress component mentions",
-                },
-                detailed: {
-                    type: "boolean",
-                    description: "Whether to provide detailed information for each component found",
-                    default: false,
-                },
-            },
-            required: ["text"],
-        },
-    },
-    {
-        name: "get_design_guidelines",
-        description: "Get IDS design guidelines covering core principles, visual standards, accessibility requirements, and best practices for consistent design implementation.",
-        inputSchema: {
-            type: "object",
-            properties: {
-                section: {
-                    type: "string",
-                    description: "Optional: specific guideline section (e.g., 'principles', 'typography', 'accessibility', 'layout', 'colors')",
-                },
-                query: {
-                    type: "string",
-                    description: "Optional: search for specific guidelines or best practices",
-                },
-            },
-        },
-    },
-];

package/docs/guidelines.md

@@ -1,269 +0,0 @@
-# Iress Design System Guidelines
-
-## Overview
-
-The Iress Design System (IDS) serves as a shared visual language, working code, design tools and resources, human interface guidelines, and a community of contributors. It supports designers and developers building digital products for both B2B (Financial Advisors, Paraplanners) and B2B2C (client customers) segments.
-
----
-
-## Core Design Principles
-
-### Consistency
-
-- Maintain brand consistency across all applications and experiences
-- Use standardised component naming conventions (all components start with `Iress` prefix)
-- Leverage shared design tokens for spacing, colours, typography, and interactive states
-- Ensure consistent behaviour patterns across similar components
-
-### Accessibility First
-
-- Meet or exceed WCAG 2.1 Level AA Accessibility Guidelines
-- Provide proper colour contrast ratios (minimum 4.5:1 for AA, 7:1 for AAA)
-- Implement comprehensive keyboard navigation support
-- Include screen reader compatibility with appropriate ARIA attributes
-- Support focus management and skip navigation patterns
-
-### Clarity and Usability
-
-- Prioritise clear visual hierarchy through typography scales and spacing systems
-- Use progressive disclosure to manage complexity
-- Provide immediate feedback for user actions (loading states, validation, etc.)
-- Design for touch-friendly interfaces with adequate target sizes
-
-### Developer Experience
-
-- Maintain clean component APIs with predictable prop patterns
-- Provide comprehensive documentation with usage examples
-- Support both controlled and uncontrolled component patterns
-- Enable efficient testing strategies with semantic roles and accessible queries
-
----
-
-## Visual Design Standards
-
-### 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
-
-- 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
-
-- 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
-
-- 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
-
----
-
-## Component Guidelines
-
-### Buttons
-
-- **Primary**: Limit to one per view for main call-to-action
-- **Secondary**: Use for secondary actions
-- **Tertiary**: Extra affordance between secondary actions
-- **Link**: Button styled as link (avoid with icon-only content)
-- **Danger**: Destructive actions requiring extra confirmation
-- **Positive/Negative**: Financial transactions (buy/sell)
-
-### Forms
-
-- Always use `IressField` wrapper for proper label, hint, and error placement
-- Provide clear validation feedback with appropriate error messages
-- Use consistent input sizing based on expected content length
-- Implement proper form state management and accessibility
-
-### Navigation
-
-- Use semantic HTML5 navigation elements
-- Provide skip links for keyboard users
-- Implement proper ARIA labelling for navigation sections
-- Ensure consistent navigation patterns across applications
-
-### Data Display
-
-- Use semantic table structures with proper headers
-- Provide clear visual hierarchy in data presentations
-- Implement consistent sorting and filtering patterns
-- Use appropriate loading states for data-heavy components
-
-### Modals and Overlays
-
-- Reserve modals for critical tasks requiring full attention
-- Provide multiple dismissal methods (backdrop, escape key, close button)
-- Implement proper focus management and restoration
-- Use slideouts for supplementary tasks where underlying content needs visibility
-
----
-
-## Interaction Patterns
-
-### Keyboard Navigation
-
-- Support standard keyboard shortcuts (Tab, Arrow keys, Enter, Space, Escape)
-- Implement proper focus order and visual focus indicators
-- Provide keyboard alternatives for mouse-only interactions
-- Follow established ARIA patterns for complex widgets
-
-### Touch Interactions
-
-- Provide adequate touch target sizes (minimum 44px)
-- Implement touch-friendly spacing between interactive elements
-- Support gesture-based interactions where appropriate
-- Ensure consistent behaviour across device types
-
-### Loading and Feedback
-
-- Use appropriate loading patterns based on context:
-  - **Page**: Full page loading states
-  - **Component**: Local loading within sections
-  - **Button**: Inline loading for form submissions
-  - **Validate**: Server-side validation feedback
-- Provide clear success and error feedback
-- Use progressive enhancement for better perceived performance
-
----
-
-## Responsive Design
-
-### Breakpoint Strategy
-
-- Implement mobile-first responsive design
-- Use consistent breakpoint values across all components
-- Provide appropriate component variants for different screen sizes
-- Consider content priority and progressive disclosure on smaller screens
-
-### Adaptive Behaviour
-
-- Reduce option counts on mobile devices where appropriate
-- Implement responsive navigation patterns
-- Adjust spacing and sizing for different contexts
-- Maintain usability across all supported devices
-
----
-
-## Content Strategy
-
-### Microcopy Guidelines
-
-- Use clear, concise language that matches user mental models
-- Provide helpful error messages with actionable guidance
-- Implement consistent tone of voice across all interface text
-- Use progressive disclosure for complex information
-
-### Iconography
-
-- Use icons consistently with established meanings
-- Provide screen reader text for meaningful icons
-- Avoid using icons as the sole means of communication
-- Maintain consistent icon sizing and alignment
-
----
-
-## Quality Assurance
-
-### Testing Standards
-
-- Test components across supported browsers and devices
-- Validate accessibility compliance with automated and manual testing
-- Ensure proper keyboard navigation functionality
-- Test with assistive technologies (screen readers, voice control)
-
-### Documentation Requirements
-
-- Provide clear usage examples for all components
-- Document accessibility considerations and requirements
-- Include common patterns and anti-patterns
-- Maintain up-to-date prop documentation and type definitions
-
----
-
-## Implementation Guidelines
-
-### Code Standards
-
-- Follow consistent naming conventions for CSS classes and component props
-- Use semantic HTML elements where appropriate
-- Implement proper TypeScript typing for better developer experience
-- Maintain clean separation between presentation and logic
-
-### Performance Considerations
-
-- Optimise component rendering and re-rendering
-- Implement appropriate code splitting strategies
-- Use efficient animation and transition patterns
-- Consider bundle size impact of component dependencies
-
----
-
-# UX Heuristic Foundations
-
-These principles serve as a lens to assess the usability and user-centred design quality of all Iress products.
-
-## 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
-
-- 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
-
-- 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
-
-- 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
-
-- 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
-
-- 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
-
-- 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.
-
----
-
-_This document is a living standard. Revisit and revise regularly to reflect evolving needs, technologies, and user expectations._
-

package/docs/ids/components-popover-docs.md

@@ -1,4 +0,0 @@
-<!-- Error extracting markdown: page.goto: Timeout 30000ms exceeded.
-Call log:
-  - navigating to "http://localhost:6006/iframe.html?viewMode=docs&id=components-popover--docs", waiting until "networkidle"
- -->