@siemens/ix-mcp-angular 3.2.0-v.1.7.7 → 3.2.0-v.1.7.9

package/AGENTS.md

@@ -0,0 +1,86 @@
+# iX Development Guidelines
+
+## Project Overview
+
+This document provides guidelines for developing applications using the Siemens iX design system
+packages. The libraries are available as `@siemens/ix-angular` and related packages including
+`@siemens/ix-aggrid`, `@siemens/ix-echarts`, and `@siemens/ix-icons`.
+
+The iX design system is built on Angular and includes comprehensive theming capabilities for
+consistent styling across industrial and enterprise applications.
+
+## Development Approach
+
+Always search iX documentation first before implementing any UI components or patterns. This
+includes looking up component APIs, design patterns, accessibility guidelines, and theming options
+from the official documentation.
+
+Use modern Angular syntax with standalone components, Angular Signals for state management, and
+separate template/style files. Avoid inline templates or styles unless they are very short. Import
+components individually and use arrow functions with const declarations.
+
+Prefer using existing iX components and patterns over implementing custom solutions. Follow the
+established design principles of atomic design, composition over inheritance, and
+accessibility-first development. Use the iX theme system with CSS custom properties rather than
+hardcoded styles.
+
+## Code Quality
+
+Write minimal comments only where necessary, focusing on why rather than what. Avoid meta-comments
+about changes or obvious explanations. Don't add unnecessary error handling for well-established iX
+component APIs and assume components work as documented.
+
+Use iX design tokens and CSS custom properties from the theme system when available instead of
+writing custom CSS. Don't override iX component internals - use documented APIs, props, and CSS
+custom properties for customization. Leverage the established color tokens, spacing system, and
+layout patterns.
+
+Use modern HTML5 and JavaScript features and avoid deprecated syntax. Maintain type safety with iX
+component interfaces and event types.
+
+## Package Management and Testing
+
+Install iX packages using the appropriate package manager and follow the integration guides for each
+framework. Fix import paths when packages exist but imports fail - check for correct package names
+and component exports.
+
+Run available lint, format, and test commands from package.json scripts.
+
+## Implementation Strategy
+
+When building applications, research iX layout patterns and navigation components first. Plan
+component structure using iX building blocks like cards, buttons, modals, and navigation elements.
+Create appropriate mock data that reflects real industrial/enterprise use cases.
+
+Apply iX themes consistently throughout the application. Use the documented layout patterns and
+component compositions. Verify accessibility compliance using iX's built-in accessibility features
+and test with screen readers and keyboard navigation.
+
+Follow the established iX component lifecycle patterns for events, state management, and data
+binding. Use documented event handlers and avoid direct DOM manipulation of iX components.
+
+## Theming and Customization
+
+Use the iX theme system with CSS custom properties for customization. Available themes include
+classic-light, classic-dark, and brand-specific variants not available to non-Siemens projects.
+Apply themes at the application level and use theme-aware CSS custom properties for consistent
+styling.
+
+Don't override iX component styles directly. Instead, use the documented CSS custom properties,
+theme tokens, and layout utilities. Create custom themes following the established token structure
+when brand customization is required.
+
+## Testing and Quality Assurance
+
+Test iX component integration using the established testing patterns. Refrain from testing iX
+component internals. Use ARIA properties in case you need access to shadow DOM elements, instead of
+custom selectors. Verify functionality across different browsers and devices using iX's browser
+support matrix.
+
+Ensure accessibility compliance by testing with screen readers, keyboard navigation, and following
+WCAG 2.1 AA guidelines that iX components are designed to meet. Use iX's built-in accessibility
+features rather than implementing custom solutions.
+
+This approach ensures high-quality development within the iX ecosystem while maintaining modern
+framework practices and leveraging the full design system capabilities for industrial and enterprise
+applications.

package/config.json

@@ -27,7 +27,7 @@
     "DOC_SUCCESS_HEADER": "# iX Documentation Results\n\nFound **{count}** relevant documentation section(s) for \"{query}\":\n\n",
     "DOC_RESULT_NOTE": "> Note: If documentation mentions missing API docs or examples, those features may not be available in the current version. The search results show the most relevant available documentation based on semantic similarity.\n\n> Need more specific results? Try refining your search with more specific terms or component names.\n\n> Not all information provided here is relevant to your query or task, make sure to only use what is relevant for the user request.",
     "ICON_SEARCH_INSTRUCTION": "Please check the icon search tool before using or recommending any icons from @siemens/ix-icons. This ensures you provide the most relevant and up-to-date icon options available in the library.",
-    "ICON_SEARCH_TOOL_DESCRIPTION": "Semantic search tool for Siemens iX Design System and Angular component library. This tool provides intelligent search across comprehensive documentation for:\n\nSupported Libraries:\n• @siemens/ix-angular - All angular ui components (e.g. ix-button, ix-application-header)\n• @siemens/ix - Contains styling, theming and utility functionality\n\nUse Cases:\n• Find component APIs and properties\n• Discover usage examples and code snippets\n• Learn about component styling and theming\n• Understand integration patterns\n• Explore design system guidelines\n\nSearch Tips:\n• Use component names: \"button\", \"chart\", \"map\"\n• Describe functionality: \"data visualization\", \"user input\"\n• Ask about APIs: \"input\", \"output\", \"attributes\", \"methods\", \"type\"\n\nThe search returns relevant documentation chunks with similarity scores and contextual headers to help you find exactly what you need.",
+    "ICON_SEARCH_TOOL_DESCRIPTION": "Semantic search tool for Siemens iX Icons (including their metadata like tags)",
     "ICON_SEARCH_QUERY_DESCRIPTION": "Search query for icons (name, term, or category)",
     "ICON_NO_RESULTS": "No icons found for query: \"{query}\"\n\nThis could mean:\n• The icon does not exist in the current version of @siemens/ix-icons\n• The icon was renamed or removed\n• The search terms don't match available icons\n\nSuggestions:\n• Check spelling or try broader terms (e.g., \"settings\" instead of \"gear\")\n\nAvailable Libraries:\n@siemens/ix-icons",
     "ICON_SUCCESS_HEADER": "# iX Icon Search Results\n\nFound **{count}** relevant icon(s) for \"{query}\":\n\n",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@siemens/ix-mcp-angular",
-  "version": "3.2.0-v.1.7.7",
+  "version": "3.2.0-v.1.7.9",
   "description": "iX MCP server for Angular",
   "license": "MIT",
   "main": "dist/src/index.js",
@@ -24,7 +24,8 @@
   "files": [
     "dist",
     "database",
-    "config.json"
+    "config.json",
+    "AGENTS.md"
   ],
   "repository": {
     "type": "git",