Enables AI assistants to generate production-ready Sass color palettes, typography systems, elevations, and complete themes for Ignite UI components.
Also known as IgniteUI/igniteui-theming, igniteui-theming
- Stars
- 44
- Tools
- 15
- Downloads, 30 days
- —
- Latest version
- 30.2.0
- Last commit
- Nov 13, 2026
- License
- MIT
What is Ignite UI Theming MCP?
Ignite UI Theming enables AI assistants to generate production-ready Sass color palettes, typography systems, elevations, and complete themes for Ignite UI components. It exposes 15 tools, such as detect_platform, create_palette, create_custom_palette.
Summary generated from the project's README
About Ignite UI Theming MCP server
Developers building applications with Ignite UI can use this MCP server to automate the creation of production-ready Sass theming code. By connecting to an AI client like Claude Desktop, Cursor, or VS Code, the server acts as a specialized assistant that generates color palettes, typography systems, and elevation shadows. It supports multiple platforms including Angular, React, Web Components, and Blazor.
Users can set up the server locally by pointing their client to the distributed index.js file or by using npx to run the published igniteui-theming package. The server provides specific tools such as create_palette for shade calculations, create_typography for font scales, and create_theme to build comprehensive light or dark mode configurations. It also includes a detect_platform tool to identify the specific Ignite UI framework being used in a project.
What you can do with it
- 1Generate complete application themesAsk your AI assistant to build a full Material Design dark theme based on a specific color scheme.
- 2Create custom color palettesRequest a light theme palette using specific primary and secondary colors.
- 3Configure typography systemsSet up typography using a specific font family and a standard type scale.
- 4Discover component design tokensInquire about the available customizable properties for a specific UI component.
Written from the project's README. Every use case is checked against a quote from it.
How to install Ignite UI Theming MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Ignite UI Theming MCP in Claude Code
$ claude mcp add igniteui-theming -- npx -y igniteui-themingInstall Ignite UI Theming MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"igniteui-theming": {
"command": "npx",
"args": [
"-y",
"igniteui-theming"
]
}
}
}Install Ignite UI Theming MCP in VS Code
.vscode/mcp.json
{
"servers": {
"igniteui-theming": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"igniteui-theming"
]
}
}
}Install Ignite UI Theming MCP in VS Code CLI
$ code --add-mcp '{"name":"igniteui-theming","type":"stdio","command":"npx","args":["-y","igniteui-theming"]}'Install Ignite UI Theming MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"igniteui-theming": {
"command": "npx",
"args": [
"-y",
"igniteui-theming"
]
}
}
}Install Ignite UI Theming MCP in Codex
$ codex mcp add igniteui-theming -- npx -y igniteui-themingInstall Ignite UI Theming MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.igniteui-theming] command = "npx" args = ["-y", "igniteui-theming"]
Install Ignite UI Theming MCP in Gemini CLI
$ gemini mcp add -s user igniteui-theming npx -- -y igniteui-themingInstall Ignite UI Theming MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"igniteui-theming": {
"command": "npx",
"args": [
"-y",
"igniteui-theming"
]
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for igniteui-theming 30.2.0 in an isolated container with no network and no keys. It answered and listed 15 tools.
Ignite UI Theming MCP tools 15
Read from the server with tools/listdetect_platformDetect the target platform by analyzing dependencies and project config files. <use_case> Use this tool FIRST before generating any theme code to ensure platform-optimized output. The detected platform determines the correct Sass module paths and syntax. Output format ("sass" vs "css") is a separate concern — see the output parameter on each generation tool. For non-Angular platforms, prefer "css" unless the project has a confirmed Sass pipeline; use your own file-reading tools or ask the user to confirm before choosing output: "sass". </use_case> <detection_signals> Uses multi-signal detection with confidence scoring: 1. Ignite UI packages (HIGH - 100): igniteui-angular, igniteui-webcomponents, igniteui-react, IgniteUI.Blazor 2. Config files (MEDIUM-HIGH - 80): angular.json, vite.config.*, next.config.*, .csproj 3. Framework packages (LOW - 40): @angular/core, react, lit (fallback only) 4. Generic fallback: When no Ignite UI product is found, returns "generic" for standalone theming </detection_signals> <output> Returns: - platform: "angular" | "webcomponents" | "react" | "blazor" | "generic" | null - confidence: "high" | "medium" | "low" | "none" - ambiguous: true if multiple Ignite UI platforms detected (requires user to specify explicitly) - alternatives: Array of detected platforms when ambiguous - signals: Array of detection signals found - detectedPackage: The primary package that triggered detection - platformInfo: Name, theming module path, and description "generic" means no Ignite UI product framework was found. Most tools work in generic mode (palette, typography, elevations, theme generation, color references, layout tokens with scope). Component-specific tools (create_component_theme, get_component_design_tokens) are NOT available in generic mode. The response includes Sass load path guidance based on detected build tooling. null is reserved for error states (package.json read failure) or ambiguous multi-product detection. </output> <ambiguous_handling> When multiple Ignite UI platforms are detected with significant confidence (≥60), returns: - platform: null - ambiguous: true - alternatives: List of possible platforms with their signals - Action: User must specify platform explicitly in subsequent tool calls </ambiguous_handling> <related_tools> After detection, use the platform value with: - create_palette: Generate color palette - create_theme: Generate complete theme - create_typography: Set up typography - create_elevations: Configure shadows </related_tools> <related_resources> - "theming://guidance/platform-setup": Comprehensive setup guide covering detection workflow, Sass load path configuration, dependency handling, and the recommended theming sequence. Read this for detailed platform-specific setup instructions. </related_resources>
create_paletteGenerate a color palette for Ignite UI themes using the palette() Sass function. <use_case> Use this tool when you have base colors and want to auto-generate a complete palette with all shade variations (50-900, A100-A700). This is the right tool for almost every palette - pass the brand colors and let the generator do the rest. </use_case> <output_formats> - "sass" (default): Generates Sass code using the palette() function. Requires Sass compilation. - "css": Generates CSS custom properties (variables) directly. Ready to use in any CSS file. Use "css" output when: - Working with vanilla CSS projects without Sass - You want immediately usable CSS variables - Using CSS-in-JS or other non-Sass styling approaches </output_formats> <workflow> 1. Validates input colors against the theme variant 2. Generates Sass code OR compiles to CSS based on output parameter 3. Adds warning comments to code if issues detected 4. Returns validation warnings and tips in response </workflow> <important_notes> - Requires primary, secondary, and surface colors (matches Sass palette() API) - Gray, info, success, warn, error are optional (use design system defaults) - Surface color should match variant: light colors for "light", dark for "dark" - Every shade is solved for a contrast target, so a seed supplies HUE and SATURATION, not lightness - a very light or very dark brand color yields the same ramp as a mid-tone one. Pass the brand color as-is. The one caveat: a seed with very little chroma (a tinted gray such #6c757d) keeps that tint rather than being saturated, so it produces a tinted-gray ramp; a seed with no measurable hue produces a pure gray one. SHADE PROGRESSION (important): - Primary, secondary, and all chromatic colors: shades are NEVER inverted. The palette() function always generates 50=lightest to 900=darkest. - Only gray shades behave differently based on variant (for text contrast). - DO NOT manually invert primary/secondary colors for dark themes. SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Generated Sass code with palette() function call, OR - Generated CSS with custom properties (:root { --ig-primary-50: ...; }) - Platform-specific module imports (Sass only) - Validation warnings (if any colors have issues) - Variable name created (e.g., $my-palette) (Sass only) </output> <error_handling> - Invalid color format: Returns error with format examples - Variant mismatch: Warns if surface color doesn't match theme variant </error_handling> <example> Blue brand with orange accent on light theme (Sass output): { "primary": "#1976D2", "secondary": "#FF9800", "surface": "#FAFAFA", "variant": "light" } Same palette as CSS variables: { "primary": "#1976D2", "secondary": "#FF9800", "surface": "#FAFAFA", "variant": "light", "output": "css" } </example> <related_tools> - detect_platform: Run first to get correct platform value - create_custom_palette: Only when exact per-shade values are mandated by a brand spec - create_theme: Use instead if you want palette + typography + elevations together </related_tools> <related_resources> Call read_resource to load reference data: - "theming://presets/palettes" — preset palette colors - "theming://guidance/colors" — color guidance overview - "theming://guidance/colors/rules" — light/dark theme color rules </related_resources>
create_custom_paletteGenerate a custom color palette with fine-grained control over individual shade values. ⚠️ CRITICAL RULES - READ BEFORE GENERATING SHADES: 1. MONOCHROMATIC: Each color (primary, secondary, etc.) must use ONE HUE only. All 14 shades are lighter/darker versions of the SAME color. Example: primary blue → all shades must be blue (#E3F2FD light → #0D47A1 dark). WRONG: mixing blue, green, purple in one color's shades. 2. NEVER INVERT: Chromatic colors always go 50=lightest → 900=darkest. This applies to BOTH light and dark themes. Only gray inverts for dark themes. <use_case> PREFER create_palette. It derives every shade from a seed by solving for a contrast target, so it handles any brand color - light, dark, muted or neon - on its own. Every shade is solved for a contrast target, so a seed supplies HUE and SATURATION, not lightness - a very light or very dark brand color yields the same ramp as a mid-tone one. Pass the brand color as-is. The one caveat: a seed with very little chroma (a tinted gray such #6c757d) keeps that tint rather than being saturated, so it produces a tinted-gray ramp; a seed with no measurable hue produces a pure gray one. Reach for this tool only when: - A brand spec mandates exact values for specific shades, and those values must be reproduced rather than generated - An accessibility audit requires exact contrast color values (rare - the generated adaptive-contrast() is normally what you want) Mixing is supported and is the usual shape: pin the one group the brand specifies and leave every other group in "shades" mode. </use_case> <output_formats> - "sass" (default): Generates Sass code with palette map structure. Requires Sass compilation. - "css": Generates CSS custom properties (variables) directly. Ready to use in any CSS file. Use "css" output when: - Working with vanilla CSS projects without Sass - You want immediately usable CSS variables - Building prototypes or quick demos - Using CSS-in-JS or other non-Sass styling approaches </output_formats> <workflow> 1. For each color group, choose a mode: - mode:"shades" → Auto-generate from baseColor (the default choice) - mode:"explicit" → Reproduce mandated values shade by shade 2. Validates explicit shades for completeness, color format, lightness order and hue consistency 3. Generates Sass code with color() map structure 4. Returns any validation warnings </workflow> <important_notes> CHROMATIC COLORS (primary, secondary, info, success, warn, error): - "shades" mode needs only a baseColor - prefer it - "explicit" mode requires 14 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, A100, A200, A400, A700 - In explicit mode, all shades in a group must be the SAME HUE (±30°) and run 50 lightest to 900 darkest - they are lightness steps of one color, not different colors. Shades mode enforces this for you. - Chromatic shades are NEVER inverted: 50 is lightest and 900 darkest in BOTH light and dark themes GRAY (the only family that inverts): - "explicit" mode requires 10 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900 - LIGHT themes: 50 = lightest, 900 = darkest. DARK themes: inverted - Gray inverts because text and UI elements contrast against the surface SURFACE (not a ramp): - A background plus the layers on it, keyed by 6 layers required: base, sunken, raised, overlay, container, seed - "base" is the page; "sunken"/"raised"/"overlay" step away from it; "container" is a translucent tint; "seed" is the input color - There is no hue ramp to keep monochromatic. Palettes still emit numeric surface shades for compatibility, but they are deprecated: read and override the roles CONTRAST COLORS - OMIT contrastOverrides entirely. Each shade automatically gets '<shade>-contrast': adaptive-contrast(<color>), which picks black or white for readability. Only supply overrides for an audit demanding exact values. SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Generated Sass code with color() map definitions, OR - Generated CSS with custom properties (:root { --ig-primary-50: ...; }) - Summary of which colors use shades() vs explicit values - Variable name created (e.g., $custom-light-palette) (Sass only) - Validation warnings (if any) </output> <error_handling> Validation FAILS (returns error, no code generated) if: - Missing required shades in explicit mode - Invalid CSS color format in any shade Validation WARNS (generates code with warnings) if: - Luminance progression incorrect (50 darker than 900) - Hue inconsistency detected (shades not monochromatic) - Gray progression doesn't match variant (light vs dark) </error_handling> <example> The usual case - every group from a seed: { "variant": "light", "primary": { "mode": "shades", "baseColor": "#4CAF50" }, "secondary": { "mode": "shades", "baseColor": "#FF9800" }, "surface": { "mode": "shades", "baseColor": "#FAFAFA" } } A brand spec pins primary; everything else is still generated: { "variant": "light", "primary": { "mode": "explicit", "shades": { "50": "#E8F5E9", "100": "#C8E6C9", "200": "#A5D6A7", "300": "#81C784", "400": "#66BB6A", "500": "#4CAF50", "600": "#43A047", "700": "#388E3C", "800": "#2E7D32", "900": "#1B5E20", "A100": "#B9F6CA", "A200": "#69F0AE", "A400": "#00E676", "A700": "#00C853" } }, "secondary": { "mode": "shades", "baseColor": "#FF9800" }, "surface": { "mode": "shades", "baseColor": "#FAFAFA" } } Note: no contrastOverrides in either input. The generated Sass adds '500-contrast': adaptive-contrast(#4CAF50) for every shade automatically. </example> <related_tools> - detect_platform: Run first to get correct platform value - create_palette: Prefer this - it handles any seed color without hand-written shades - create_theme: Does not support custom palettes; use this tool + manual theme assembly </related_tools> <anti_example> ❌ WRONG - DO NOT create shades like this (different hues = broken palette): { "primary": { "mode": "explicit", "shades": { "50": "#E3F2FD", // blue "100": "#DCEDC8", // green ← WRONG HUE "200": "#FFF9C4", // yellow ← WRONG HUE "500": "#9C27B0", // purple ← WRONG HUE "900": "#BF360C" // red-brown ← WRONG HUE } } } This creates a rainbow, not a shade palette. Components will look broken. </anti_example> <related_resources> Call read_resource to load reference data: - "theming://presets/palettes" — preset palette colors for reference - "theming://guidance/colors/usage" — which shades to use for different purposes - "theming://guidance/colors/roles" — semantic meaning of each color family </related_resources>
create_typographySet up typography for Ignite UI themes with custom font families and type scales. <use_case> Use this tool to configure fonts that match your brand identity while maintaining consistent sizing, line heights, and letter spacing based on design system conventions. </use_case> <workflow> 1. Takes font family string and optional design system preset 2. Generates Sass code using the typography() mixin 3. Applies the type scale from the selected design system 4. Optionally applies custom scale overrides </workflow> <important_notes> - Font family string should include fallbacks for cross-platform compatibility - Quote font names that contain spaces: '"Segoe UI"' not 'Segoe UI' - Design system affects: font sizes, line heights, letter spacing, font weights - Type styles include: h1-h6, subtitle-1/2, body-1/2, button, caption, overline SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Generated Sass code with typography() mixin call - Platform-specific module imports - Variable name used (e.g., $my-typography) </output> <error_handling> - Empty font family: Returns error requesting valid font family string </error_handling> <example> Modern sans-serif typography for Material Design: { "fontFamily": "'Inter', 'Segoe UI', 'Helvetica Neue', sans-serif", "designSystem": "material" } </example> <related_tools> - detect_platform: Run first to get correct platform value - create_theme: Use instead if you want typography + palette + elevations together </related_tools> <related_resources> Call read_resource to load reference data: - "theming://presets/typography" — typography presets for all design systems </related_resources>
create_elevationsSet up elevation shadows for Ignite UI themes. <use_case> Use this tool to configure box-shadow values that provide visual depth and hierarchy. Elevations follow Material Design or Indigo design specifications. </use_case> <workflow> 1. Selects elevation preset based on design system parameter 2. Generates Sass code using the elevations() mixin 3. Creates 24 elevation levels (0-24) with corresponding shadow values </workflow> <important_notes> - "material" preset: Material Design 3 shadow specifications - "indigo" preset: Infragistics Indigo shadow specifications - Elevation 0 = no shadow, elevation 24 = maximum shadow depth - Components use elevation() function to apply specific levels SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Generated Sass code with elevations() mixin call - Platform-specific module imports - Variable name used (e.g., $my-elevations) </output> <related_tools> - detect_platform: Run first to get correct platform value - create_theme: Use instead if you want elevations + palette + typography together </related_tools> <related_resources> Call read_resource to load reference data: - "theming://presets/elevations" — elevation presets for Material and Indigo </related_resources>
create_themeGenerate a complete, production-ready Ignite UI theme with palette, typography, and elevations. <use_case> Use this tool as the starting point for new projects. It generates everything needed for a working theme in a single operation: color palette, typography setup, elevation shadows, and the theme application mixin. </use_case> <workflow> 1. Creates color palette using palette() function 2. Sets up typography with specified font family (if includeTypography: true) 3. Configures elevations based on design system (if includeElevations: true) 4. Configures spacing utilities for Web Components, React, and Blazor (if includeSpacing: true) 5. Applies the theme using the theme() mixin For Web Components, React, and Blazor the output always includes sizing(), the progress @property rules, the scrollbar variables and .ig-scrollbar class, RTL support, and the tile manager view transitions. </workflow> <important_notes> REQUIRED COLORS: - primaryColor: Main brand color - secondaryColor: Accent/highlight color - surfaceColor: Background color (should match variant) SHADE PROGRESSION (important): - Primary and secondary colors are NEVER inverted between light/dark themes. - The palette() function generates shades 50=lightest to 900=darkest for ALL chromatic colors regardless of theme variant. - Only gray shades behave differently (for text contrast against surface). - DO NOT provide inverted primary/secondary colors for dark themes. SEED COLORS: - Every shade is solved for a contrast target, so a seed supplies HUE and SATURATION, not lightness - a very light or very dark brand color yields the same ramp as a mid-tone one. Pass the brand color as-is. The one caveat: a seed with very little chroma (a tinted gray such #6c757d) keeps that tint rather than being saturated, so it produces a tinted-gray ramp; a seed with no measurable hue produces a pure gray one. PLATFORM DIFFERENCES: - Angular: Uses igniteui-angular/theming with core() and theme() mixins - Web Components: Uses igniteui-theming directly with palette(), typography(), elevations() mixins - React: Uses igniteui-theming directly (same as Web Components), common with Vite/Next.js - Blazor: Uses igniteui-theming for Sass compilation, theme CSS referenced in Blazor components SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Complete Sass code with all theme components - List of variables created/used - Platform-specific guidance </output> <error_handling> - Invalid color format: Returns error with format examples - Variant mismatch: Warns if surface color doesn't match theme variant </error_handling> <example> Complete Material Design blue theme: { "platform": "angular", "designSystem": "material", "primaryColor": "#1976D2", "secondaryColor": "#FF9800", "surfaceColor": "#FAFAFA", "variant": "light", "fontFamily": "'Roboto', sans-serif", "includeTypography": true, "includeElevations": true } </example> <next_steps> After generating a theme: 1. Import the generated Sass file in your application's main styles 2. Customize individual component themes as needed using component schema overrides </next_steps> <related_tools> - detect_platform: Run first to auto-detect platform from package.json - create_custom_palette: Only when exact per-shade values are mandated by a brand spec - create_palette: Use if you only need a palette without full theme - create_typography: Use if you only need typography setup - create_elevations: Use if you only need elevation shadows </related_tools> <related_resources> Call read_resource to load reference data: - "theming://presets/palettes" — preset palette colors - "theming://guidance/colors" — color guidance overview - "theming://guidance/colors/rules" — light/dark theme color rules - "theming://platforms/angular" — Angular platform configuration - "theming://platforms/webcomponents" — Web Components platform configuration - "theming://platforms/react" — React platform configuration - "theming://platforms/blazor" — Blazor platform configuration </related_resources>
set_sizeSet global or component-specific sizing by updating --ig-size. <use_case> Use this tool for requests like: - "Make the calendar smaller" - "The buttons feel too big" - "Use the small size everywhere" </use_case> <behavior> - Sets --ig-size in the chosen scope (defaults to :root) - Accepts "small", "medium", "large" (mapped to 1, 2, 3) or numeric values - When platform is "generic", do NOT use the "component" parameter (it resolves Ignite UI component selectors). Use "scope" with a custom CSS selector instead, or omit both for :root. </behavior> <sass_notes> - Components map --ig-size to --component-size internally - Styles using sizable() require @include sizable() in component styles </sass_notes> <example> Make flat buttons medium: { "component": "flat-button", "size": "medium" } Make everything small globally: { "size": "small" } </example> <related_resources> Call read_resource to load reference data: - "theming://docs/spacing-and-sizing" — spacing and sizing overview - "theming://docs/functions/sizable" — sizable value function - "theming://docs/mixins/sizable" — sizable mixin </related_resources>
set_spacingSet global or component-specific spacing by updating --ig-spacing. <use_case> Use this tool for requests like: - "The button feels bloated" - "Tighten the spacing on the form" - "Double the padding on cards" </use_case> <behavior> - Sets --ig-spacing in the chosen scope (defaults to :root) - Optional overrides for --ig-spacing-inline and --ig-spacing-block - 0 = no spacing, 1 = default, 2 = double (fractions allowed) - spacing is required; inline/block are optional overrides - When platform is "generic", do NOT use the "component" parameter (it resolves Ignite UI component selectors). Use "scope" with a custom CSS selector instead, or omit both for :root. </behavior> <sass_notes> - pad(), pad-inline(), pad-block() require @include spacing() once </sass_notes> <example> Reduce calendar spacing: { "component": "calendar", "spacing": 0.75 } Override inline spacing: { "scope": ".compact", "inline": 0.5, "block": 0.75 } </example> <related_resources> Call read_resource to load reference data: - "theming://docs/spacing-and-sizing" — spacing and sizing overview - "theming://docs/functions/pad" — pad spacing function - "theming://docs/mixins/spacing" — spacing mixin </related_resources>
set_roundnessSet global or component-specific roundness by updating --ig-radius-factor. <use_case> Use this tool for requests like: - "Make the flat buttons more round" - "Square off the cards" </use_case> <behavior> - Sets --ig-radius-factor in the chosen scope (defaults to :root) - 0 = minimum radius, 1 = maximum radius, values between interpolate - When platform is "generic", do NOT use the "component" parameter (it resolves Ignite UI component selectors). Use "scope" with a custom CSS selector instead, or omit both for :root. </behavior> <sass_notes> - border-radius() responds to --ig-radius-factor without extra mixins </sass_notes> <example> Round avatars more: { "component": "avatar", "radiusFactor": 0.9 } Globally reduce roundness: { "radiusFactor": 0.8 } </example> <related_resources> Call read_resource to load reference data: - "theming://docs/spacing-and-sizing" — spacing and sizing overview - "theming://docs/functions/border-radius" — border radius function </related_resources>
get_component_design_tokensDiscover available design tokens (themeable properties) for an Ignite UI component. <use_case> ALWAYS call this tool FIRST before using create_component_theme. It returns the exact token names that can be customized for a component, preventing hallucination of invalid property names. NOTE: This tool returns tokens for Ignite UI framework components. It is NOT useful when the detected platform is "generic" — component theming requires a specific Ignite UI product (angular, webcomponents, react, or blazor). </use_case> <workflow> 1. Provide the component name (e.g., "button", "avatar", "grid") 2. Receive list of all available tokens with their types and descriptions 3. Use the token names in create_component_theme </workflow> <important_notes> COMPONENT NAMING: - Basic components: Use simple names like "avatar", "badge", "card" - Button variants: Use specific variant names like "flat-button", "contained-button", "outlined-button", "fab-button" (NOT just "button") - Icon button variants: "flat-icon-button", "contained-icon-button", "outlined-icon-button" - Child sub-components: Use names like "list-item", "card-header", "accordion-header", "tab-item", "step", "expansion-panel-header". These resolve to the parent component's theme automatically. CHILD SUB-COMPONENTS: - Some component parts (e.g., "list-item", "card-header", "accordion-header") don't have their own theme function — they are styled through the parent component's theme tokens. - When you query a child sub-component, the response includes a note explaining the parent-child relationship and shows the parent theme's full token list. - The token descriptions guide you to the relevant tokens (e.g., "item-background" for list items, "header-text-color" for card headers). - When you then call create_component_theme with a child name, it automatically uses the parent's theme function, variable name, and selector — producing output that is merge-compatible with the parent component's theme. COMPOUND COMPONENTS: There are two types of compound components: **Standard compounds** (e.g., "combo", "select", "date-picker"): - Use multiple internal components that each need their own theme - The response lists related themes and, where available, token derivation hints showing how child token values relate to parent/sibling tokens (e.g., "foreground → adaptive-contrast of calendar.content-background") - Follow derivation hints when setting child token values. If the user specifies an explicit value, use that instead of the derived value. - All related themes should be scoped under the parent component's selector - For each related theme: call get_component_design_tokens, then create_component_theme using the parent component's selector for the target platform **Composed compounds** (e.g., "grid components"): - The framework automatically generates internal themes for all child components from just the primary tokens - Do NOT create separate themes for the related components — they are auto-derived in the component's Sass styles - The response uses a **two-tier token hierarchy**: - **✅ Primary Tokens — USE THESE**: Use ONLY these tokens for the initial theme - **📖 Refinement Tokens — REFERENCE ONLY**: Auto-derived tokens available ONLY when the user explicitly requests fine-grained control (e.g., "change the header background") - Only set the primary tokens in the parent component's theme; all children inherit automatically - The response clearly marks these as "Composed Compound Component" and lists the internally themed children for reference (not for separate theming) VARIANTS INFO: - If you query a base component that has variants (e.g., "button"), the response lists available variants to help you choose the right one </important_notes> <output> Returns: - component: The component name - themeFunctionName: The Sass function to use (e.g., "button-theme") - description: Information about the component theme - tokens: Array of { name, type, description } for each available token - variants: (if applicable) List of variant-specific theme names - compoundInfo: (if applicable) Related themes with token derivation hints and guidance - childNote: (if child sub-component) A note explaining the parent-child relationship </output> <error_handling> - Unknown component: Returns list of similar component names as suggestions - Partial match: If query partially matches multiple components, returns all matches </error_handling> <example> Get tokens for flat button: { "component": "flat-button" } Returns tokens like: background, foreground, hover-background, border-radius, etc. Get tokens for a child sub-component: { "component": "list-item" } Returns the list theme's tokens with a note: "list-item is a child of the list component. Its styling is controlled through the list theme." </example> <related_tools> - create_component_theme: Use the discovered tokens to create a custom theme </related_tools>
create_component_themeGenerate Sass or CSS code to customize an Ignite UI component's appearance using design tokens. <use_case> Use this tool AFTER calling get_component_design_tokens to customize specific component styles. The generated code can be included in your theme file to override default component appearances. </use_case> <workflow> 1. First call get_component_design_tokens to discover available tokens 2. Choose which tokens to customize based on your design requirements 3. Specify designSystem and variant to match the global theme or the one explicitly requested (defaults to Material light) 4. Call this tool with component name, token values, and output format ("sass" or "css") 5. Receive ready-to-use Sass or CSS code with the component theme </workflow> <important_notes> DESIGN SYSTEM & VARIANT: - designSystem: Choose "material" (default), "bootstrap", "fluent", or "indigo" - variant: Choose "light" (default) or "dark" - The correct schema (e.g., $light-bootstrap-schema, $dark-material-schema) is automatically selected and passed to the component theme function - The correct output: Choose output format based on the target file type (Sass vs CSS) - This ensures component tokens inherit proper defaults from the design system LIGHT & DARK: - Each call produces one variant. If the app supports light and dark, call this tool for each variant — do not ship only the light one. - The dark call usually needs different token values than the light one (e.g. colors that work on a dark surface). Do not repeat the light tokens unchanged. - Scope the dark call under the app's dark-mode selector so it doesn't override the light theme (e.g. ".your-dark-scope igc-avatar"). - Put that dark-mode selector on a root element (`html`, `body`, or the app's theme root), not on an app container. On Angular, overlay-hosted components (`.igx-dialog`, `.igx-drop-down__list`, `.igx-tooltip`, `.igx-overlay__content`) are moved to the overlay outlet under `body`, so a scope on an app container won't match them. - The response includes a note with the scoped selector for the other variant. TOKEN VALIDATION: - All provided token names are validated against the component's schema - Invalid tokens return an error with the list of valid token names - You don't need to specify all tokens - only those you want to customize (prefer PRIMARY tokens to minimize the number of overrides) TOKEN VALUE FORMATS: - Colors: Any valid CSS color format (hex, rgb, hsl, named colors) - Dimensions: Include units (e.g., "8px", "0.5rem", "2em") - Border radius: Can be single value or shorthand ("8px" or "8px 8px 0 0") - Shadows: Full box-shadow syntax ("0 2px 4px rgba(0,0,0,0.1)") SELECTORS: - Default selector is auto-detected based on platform and component - For child sub-components (e.g., "list-item", "card-header"), the selector automatically resolves to the parent component's selector (e.g., "igx-list", "igx-card") - Angular: Uses "igx-*" element selectors or attribute selectors - Web Components: Uses "igc-*" element selectors - Custom selectors supported for targeted styling (e.g., ".my-button") CHILD SUB-COMPONENTS: - When creating a theme for a child sub-component (e.g., "card-actions"), the output uses the parent's theme function, variable name, and selector. - This means the output for "card" and "card-actions" is merge-compatible: both produce `$custom-card-theme: card-theme(...)` scoped to `igx-card`. - To add tokens for multiple sub-parts, merge the token arguments into a single theme function call rather than creating separate themes. SASS OUTPUT: - Generated code uses `@include tokens($theme)` to apply the theme - The tokens mixin emits --ig-{component}-{token} CSS custom properties in global mode COMPOUND COMPLETENESS: - **Standard compounds:** If the user asks for a standard compound component, the response is incomplete unless related theme calls are also generated. Use the related themes list from get_component_design_tokens to drive the sequence. All related themes should use the compound component's selector as the wrapper. Follow token derivation hints to set child token values consistently. - **Composed compounds:** If the component is a composed compound (e.g., grid), do NOT generate separate child themes. Only set the primary tokens (background, foreground, accent-color) on the parent component's theme — child themes are auto-derived internally by the component's Sass styles. Refinement tokens (e.g., header-background) can be added in follow-up calls when the user explicitly asks to customize a specific aspect. SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Generated Sass or CSS code with: - Platform-specific @use import (Sass only) - Theme function call with $schema parameter and provided token values (Sass only) - tokens mixin to apply the theme to the selector (Sass only) - Description of what was generated - Design system and variant used - List of tokens used - A light/dark note on covering the other variant </output> <error_handling> - Unknown component: Returns error with list of available components - Invalid tokens: Returns error listing invalid tokens and valid alternatives - Invalid color format: Returns error with format guidance </error_handling> <example> Custom blue flat button with rounded corners (Angular, Material Design): { "platform": "angular", "designSystem": "material", "variant": "light", "component": "flat-button", "tokens": { "foreground": "#1976d2", } } Generates: ```scss @use 'igniteui-angular/theming' as *; $custom-flat-button-theme: flat-button-theme( $schema: $light-material-schema, $foreground: #1976d2, ); .igx-button--flat { @include tokens($custom-flat-button-theme); } ``` Bootstrap dark theme example: { "platform": "webcomponents", "designSystem": "bootstrap", "variant": "dark", "component": "avatar", "tokens": { "background": "#ff5722" } } Generates: ```scss @use 'igniteui-theming' as *; $custom-avatar-theme: avatar-theme( $schema: $dark-bootstrap-schema, $background: #ff5722 ); igc-avatar { @include tokens($custom-avatar-theme); } ``` </example> <compound_example> Date Picker (compound) — all child themes use the parent component's selector. Follow token derivation hints from get_component_design_tokens: 1) get_component_design_tokens { "component": "date-picker" } 2) create_component_theme { "component": "date-picker", "platform": "angular", ... } 3) create_component_theme { "component": "calendar", "selector": "igx-date-picker", ... } 4) create_component_theme { "component": "flat-button", "selector": "igx-date-picker", ... } 5) create_component_theme { "component": "input-group", "selector": "igx-date-picker", ... } Each child theme uses the parent's platform selector (e.g., `igx-date-picker` for Angular, `igc-date-picker` for Web Components / React / Blazor). The tokens mixin emits --ig-{component}-{token} variables that child components consume via var() fallback — no per-child selectors needed. </compound_example> <related_tools> - detect_platform: Run to auto-detect platform for correct imports - get_component_design_tokens: MUST call first to discover valid tokens - create_theme: Use for full theme (palette + typography + elevations) </related_tools>
get_colorRetrieve a palette color from Ignite UI Theming as a CSS variable reference. <use_case> Use this tool when you need to reference a specific palette color in CSS or Sass code. Returns CSS variable references that work in both Sass and CSS contexts. Common scenarios: - Setting component backgrounds/foregrounds using theme colors - Creating hover/focus states with opacity variations - Ensuring text contrast against colored backgrounds </use_case> <workflow> 1. Specify the color family (primary, secondary, gray, etc.) 2. Optionally specify a shade variant (50-900, A100-A700) 3. Optionally request the contrast color for text readability 4. Optionally apply opacity for transparency effects </workflow> <output_examples> Basic color: { color: "primary" } → var(--ig-primary-500) Specific shade: { color: "primary", variant: "600" } → var(--ig-primary-600) Contrast color: { color: "primary", variant: "600", contrast: true } → var(--ig-primary-600-contrast) With opacity: { color: "primary", opacity: 0.5 } → hsl(from var(--ig-primary-500) h s l / 0.5) Contrast with opacity: { color: "primary", contrast: true, opacity: 0.7 } → hsl(from var(--ig-primary-500-contrast) h s l / 0.7) </output_examples> <important_notes> CSS VARIABLE NAMING: - Base colors: --ig-{color}-{variant} (e.g., --ig-primary-500) - Contrast: --ig-{color}-{variant}-contrast (e.g., --ig-primary-500-contrast) GRAY RESTRICTIONS: - Gray only supports standard shades (50-900), not accent shades (A100-A700) OPACITY HANDLING: - Uses CSS relative color syntax: hsl(from <color> h s l / <opacity>) - Works in modern browsers (CSS Color Level 4) - For Sass projects, this syntax is passed through unchanged </important_notes> <related_tools> - create_palette: Generate a complete palette with these colors - create_component_theme: Use retrieved colors in component theming </related_tools>
| detect_platform | Detect the target platform by analyzing dependencies and project config files. <use_case> Use this tool FIRST before generating any theme code to ensure platform-optimized output. The detected platform determines the correct Sass module paths and syntax. Output format ("sass" vs "css") is a separate concern — see the output parameter on each generation tool. For non-Angular platforms, prefer "css" unless the project has a confirmed Sass pipeline; use your own file-reading tools or ask the user to confirm before choosing output: "sass". </use_case> <detection_signals> Uses multi-signal detection with confidence scoring: 1. Ignite UI packages (HIGH - 100): igniteui-angular, igniteui-webcomponents, igniteui-react, IgniteUI.Blazor 2. Config files (MEDIUM-HIGH - 80): angular.json, vite.config.*, next.config.*, .csproj 3. Framework packages (LOW - 40): @angular/core, react, lit (fallback only) 4. Generic fallback: When no Ignite UI product is found, returns "generic" for standalone theming </detection_signals> <output> Returns: - platform: "angular" | "webcomponents" | "react" | "blazor" | "generic" | null - confidence: "high" | "medium" | "low" | "none" - ambiguous: true if multiple Ignite UI platforms detected (requires user to specify explicitly) - alternatives: Array of detected platforms when ambiguous - signals: Array of detection signals found - detectedPackage: The primary package that triggered detection - platformInfo: Name, theming module path, and description "generic" means no Ignite UI product framework was found. Most tools work in generic mode (palette, typography, elevations, theme generation, color references, layout tokens with scope). Component-specific tools (create_component_theme, get_component_design_tokens) are NOT available in generic mode. The response includes Sass load path guidance based on detected build tooling. null is reserved for error states (package.json read failure) or ambiguous multi-product detection. </output> <ambiguous_handling> When multiple Ignite UI platforms are detected with significant confidence (≥60), returns: - platform: null - ambiguous: true - alternatives: List of possible platforms with their signals - Action: User must specify platform explicitly in subsequent tool calls </ambiguous_handling> <related_tools> After detection, use the platform value with: - create_palette: Generate color palette - create_theme: Generate complete theme - create_typography: Set up typography - create_elevations: Configure shadows </related_tools> <related_resources> - "theming://guidance/platform-setup": Comprehensive setup guide covering detection workflow, Sass load path configuration, dependency handling, and the recommended theming sequence. Read this for detailed platform-specific setup instructions. </related_resources> | |
| create_palette | Generate a color palette for Ignite UI themes using the palette() Sass function. <use_case> Use this tool when you have base colors and want to auto-generate a complete palette with all shade variations (50-900, A100-A700). This is the right tool for almost every palette - pass the brand colors and let the generator do the rest. </use_case> <output_formats> - "sass" (default): Generates Sass code using the palette() function. Requires Sass compilation. - "css": Generates CSS custom properties (variables) directly. Ready to use in any CSS file. Use "css" output when: - Working with vanilla CSS projects without Sass - You want immediately usable CSS variables - Using CSS-in-JS or other non-Sass styling approaches </output_formats> <workflow> 1. Validates input colors against the theme variant 2. Generates Sass code OR compiles to CSS based on output parameter 3. Adds warning comments to code if issues detected 4. Returns validation warnings and tips in response </workflow> <important_notes> - Requires primary, secondary, and surface colors (matches Sass palette() API) - Gray, info, success, warn, error are optional (use design system defaults) - Surface color should match variant: light colors for "light", dark for "dark" - Every shade is solved for a contrast target, so a seed supplies HUE and SATURATION, not lightness - a very light or very dark brand color yields the same ramp as a mid-tone one. Pass the brand color as-is. The one caveat: a seed with very little chroma (a tinted gray such #6c757d) keeps that tint rather than being saturated, so it produces a tinted-gray ramp; a seed with no measurable hue produces a pure gray one. SHADE PROGRESSION (important): - Primary, secondary, and all chromatic colors: shades are NEVER inverted. The palette() function always generates 50=lightest to 900=darkest. - Only gray shades behave differently based on variant (for text contrast). - DO NOT manually invert primary/secondary colors for dark themes. SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Generated Sass code with palette() function call, OR - Generated CSS with custom properties (:root { --ig-primary-50: ...; }) - Platform-specific module imports (Sass only) - Validation warnings (if any colors have issues) - Variable name created (e.g., $my-palette) (Sass only) </output> <error_handling> - Invalid color format: Returns error with format examples - Variant mismatch: Warns if surface color doesn't match theme variant </error_handling> <example> Blue brand with orange accent on light theme (Sass output): { "primary": "#1976D2", "secondary": "#FF9800", "surface": "#FAFAFA", "variant": "light" } Same palette as CSS variables: { "primary": "#1976D2", "secondary": "#FF9800", "surface": "#FAFAFA", "variant": "light", "output": "css" } </example> <related_tools> - detect_platform: Run first to get correct platform value - create_custom_palette: Only when exact per-shade values are mandated by a brand spec - create_theme: Use instead if you want palette + typography + elevations together </related_tools> <related_resources> Call read_resource to load reference data: - "theming://presets/palettes" — preset palette colors - "theming://guidance/colors" — color guidance overview - "theming://guidance/colors/rules" — light/dark theme color rules </related_resources> | |
| create_custom_palette | Generate a custom color palette with fine-grained control over individual shade values. ⚠️ CRITICAL RULES - READ BEFORE GENERATING SHADES: 1. MONOCHROMATIC: Each color (primary, secondary, etc.) must use ONE HUE only. All 14 shades are lighter/darker versions of the SAME color. Example: primary blue → all shades must be blue (#E3F2FD light → #0D47A1 dark). WRONG: mixing blue, green, purple in one color's shades. 2. NEVER INVERT: Chromatic colors always go 50=lightest → 900=darkest. This applies to BOTH light and dark themes. Only gray inverts for dark themes. <use_case> PREFER create_palette. It derives every shade from a seed by solving for a contrast target, so it handles any brand color - light, dark, muted or neon - on its own. Every shade is solved for a contrast target, so a seed supplies HUE and SATURATION, not lightness - a very light or very dark brand color yields the same ramp as a mid-tone one. Pass the brand color as-is. The one caveat: a seed with very little chroma (a tinted gray such #6c757d) keeps that tint rather than being saturated, so it produces a tinted-gray ramp; a seed with no measurable hue produces a pure gray one. Reach for this tool only when: - A brand spec mandates exact values for specific shades, and those values must be reproduced rather than generated - An accessibility audit requires exact contrast color values (rare - the generated adaptive-contrast() is normally what you want) Mixing is supported and is the usual shape: pin the one group the brand specifies and leave every other group in "shades" mode. </use_case> <output_formats> - "sass" (default): Generates Sass code with palette map structure. Requires Sass compilation. - "css": Generates CSS custom properties (variables) directly. Ready to use in any CSS file. Use "css" output when: - Working with vanilla CSS projects without Sass - You want immediately usable CSS variables - Building prototypes or quick demos - Using CSS-in-JS or other non-Sass styling approaches </output_formats> <workflow> 1. For each color group, choose a mode: - mode:"shades" → Auto-generate from baseColor (the default choice) - mode:"explicit" → Reproduce mandated values shade by shade 2. Validates explicit shades for completeness, color format, lightness order and hue consistency 3. Generates Sass code with color() map structure 4. Returns any validation warnings </workflow> <important_notes> CHROMATIC COLORS (primary, secondary, info, success, warn, error): - "shades" mode needs only a baseColor - prefer it - "explicit" mode requires 14 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, A100, A200, A400, A700 - In explicit mode, all shades in a group must be the SAME HUE (±30°) and run 50 lightest to 900 darkest - they are lightness steps of one color, not different colors. Shades mode enforces this for you. - Chromatic shades are NEVER inverted: 50 is lightest and 900 darkest in BOTH light and dark themes GRAY (the only family that inverts): - "explicit" mode requires 10 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900 - LIGHT themes: 50 = lightest, 900 = darkest. DARK themes: inverted - Gray inverts because text and UI elements contrast against the surface SURFACE (not a ramp): - A background plus the layers on it, keyed by 6 layers required: base, sunken, raised, overlay, container, seed - "base" is the page; "sunken"/"raised"/"overlay" step away from it; "container" is a translucent tint; "seed" is the input color - There is no hue ramp to keep monochromatic. Palettes still emit numeric surface shades for compatibility, but they are deprecated: read and override the roles CONTRAST COLORS - OMIT contrastOverrides entirely. Each shade automatically gets '<shade>-contrast': adaptive-contrast(<color>), which picks black or white for readability. Only supply overrides for an audit demanding exact values. SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Generated Sass code with color() map definitions, OR - Generated CSS with custom properties (:root { --ig-primary-50: ...; }) - Summary of which colors use shades() vs explicit values - Variable name created (e.g., $custom-light-palette) (Sass only) - Validation warnings (if any) </output> <error_handling> Validation FAILS (returns error, no code generated) if: - Missing required shades in explicit mode - Invalid CSS color format in any shade Validation WARNS (generates code with warnings) if: - Luminance progression incorrect (50 darker than 900) - Hue inconsistency detected (shades not monochromatic) - Gray progression doesn't match variant (light vs dark) </error_handling> <example> The usual case - every group from a seed: { "variant": "light", "primary": { "mode": "shades", "baseColor": "#4CAF50" }, "secondary": { "mode": "shades", "baseColor": "#FF9800" }, "surface": { "mode": "shades", "baseColor": "#FAFAFA" } } A brand spec pins primary; everything else is still generated: { "variant": "light", "primary": { "mode": "explicit", "shades": { "50": "#E8F5E9", "100": "#C8E6C9", "200": "#A5D6A7", "300": "#81C784", "400": "#66BB6A", "500": "#4CAF50", "600": "#43A047", "700": "#388E3C", "800": "#2E7D32", "900": "#1B5E20", "A100": "#B9F6CA", "A200": "#69F0AE", "A400": "#00E676", "A700": "#00C853" } }, "secondary": { "mode": "shades", "baseColor": "#FF9800" }, "surface": { "mode": "shades", "baseColor": "#FAFAFA" } } Note: no contrastOverrides in either input. The generated Sass adds '500-contrast': adaptive-contrast(#4CAF50) for every shade automatically. </example> <related_tools> - detect_platform: Run first to get correct platform value - create_palette: Prefer this - it handles any seed color without hand-written shades - create_theme: Does not support custom palettes; use this tool + manual theme assembly </related_tools> <anti_example> ❌ WRONG - DO NOT create shades like this (different hues = broken palette): { "primary": { "mode": "explicit", "shades": { "50": "#E3F2FD", // blue "100": "#DCEDC8", // green ← WRONG HUE "200": "#FFF9C4", // yellow ← WRONG HUE "500": "#9C27B0", // purple ← WRONG HUE "900": "#BF360C" // red-brown ← WRONG HUE } } } This creates a rainbow, not a shade palette. Components will look broken. </anti_example> <related_resources> Call read_resource to load reference data: - "theming://presets/palettes" — preset palette colors for reference - "theming://guidance/colors/usage" — which shades to use for different purposes - "theming://guidance/colors/roles" — semantic meaning of each color family </related_resources> | |
| create_typography | Set up typography for Ignite UI themes with custom font families and type scales. <use_case> Use this tool to configure fonts that match your brand identity while maintaining consistent sizing, line heights, and letter spacing based on design system conventions. </use_case> <workflow> 1. Takes font family string and optional design system preset 2. Generates Sass code using the typography() mixin 3. Applies the type scale from the selected design system 4. Optionally applies custom scale overrides </workflow> <important_notes> - Font family string should include fallbacks for cross-platform compatibility - Quote font names that contain spaces: '"Segoe UI"' not 'Segoe UI' - Design system affects: font sizes, line heights, letter spacing, font weights - Type styles include: h1-h6, subtitle-1/2, body-1/2, button, caption, overline SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Generated Sass code with typography() mixin call - Platform-specific module imports - Variable name used (e.g., $my-typography) </output> <error_handling> - Empty font family: Returns error requesting valid font family string </error_handling> <example> Modern sans-serif typography for Material Design: { "fontFamily": "'Inter', 'Segoe UI', 'Helvetica Neue', sans-serif", "designSystem": "material" } </example> <related_tools> - detect_platform: Run first to get correct platform value - create_theme: Use instead if you want typography + palette + elevations together </related_tools> <related_resources> Call read_resource to load reference data: - "theming://presets/typography" — typography presets for all design systems </related_resources> | |
| create_elevations | Set up elevation shadows for Ignite UI themes. <use_case> Use this tool to configure box-shadow values that provide visual depth and hierarchy. Elevations follow Material Design or Indigo design specifications. </use_case> <workflow> 1. Selects elevation preset based on design system parameter 2. Generates Sass code using the elevations() mixin 3. Creates 24 elevation levels (0-24) with corresponding shadow values </workflow> <important_notes> - "material" preset: Material Design 3 shadow specifications - "indigo" preset: Infragistics Indigo shadow specifications - Elevation 0 = no shadow, elevation 24 = maximum shadow depth - Components use elevation() function to apply specific levels SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Generated Sass code with elevations() mixin call - Platform-specific module imports - Variable name used (e.g., $my-elevations) </output> <related_tools> - detect_platform: Run first to get correct platform value - create_theme: Use instead if you want elevations + palette + typography together </related_tools> <related_resources> Call read_resource to load reference data: - "theming://presets/elevations" — elevation presets for Material and Indigo </related_resources> | |
| create_theme | Generate a complete, production-ready Ignite UI theme with palette, typography, and elevations. <use_case> Use this tool as the starting point for new projects. It generates everything needed for a working theme in a single operation: color palette, typography setup, elevation shadows, and the theme application mixin. </use_case> <workflow> 1. Creates color palette using palette() function 2. Sets up typography with specified font family (if includeTypography: true) 3. Configures elevations based on design system (if includeElevations: true) 4. Configures spacing utilities for Web Components, React, and Blazor (if includeSpacing: true) 5. Applies the theme using the theme() mixin For Web Components, React, and Blazor the output always includes sizing(), the progress @property rules, the scrollbar variables and .ig-scrollbar class, RTL support, and the tile manager view transitions. </workflow> <important_notes> REQUIRED COLORS: - primaryColor: Main brand color - secondaryColor: Accent/highlight color - surfaceColor: Background color (should match variant) SHADE PROGRESSION (important): - Primary and secondary colors are NEVER inverted between light/dark themes. - The palette() function generates shades 50=lightest to 900=darkest for ALL chromatic colors regardless of theme variant. - Only gray shades behave differently (for text contrast against surface). - DO NOT provide inverted primary/secondary colors for dark themes. SEED COLORS: - Every shade is solved for a contrast target, so a seed supplies HUE and SATURATION, not lightness - a very light or very dark brand color yields the same ramp as a mid-tone one. Pass the brand color as-is. The one caveat: a seed with very little chroma (a tinted gray such #6c757d) keeps that tint rather than being saturated, so it produces a tinted-gray ramp; a seed with no measurable hue produces a pure gray one. PLATFORM DIFFERENCES: - Angular: Uses igniteui-angular/theming with core() and theme() mixins - Web Components: Uses igniteui-theming directly with palette(), typography(), elevations() mixins - React: Uses igniteui-theming directly (same as Web Components), common with Vite/Next.js - Blazor: Uses igniteui-theming for Sass compilation, theme CSS referenced in Blazor components SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Complete Sass code with all theme components - List of variables created/used - Platform-specific guidance </output> <error_handling> - Invalid color format: Returns error with format examples - Variant mismatch: Warns if surface color doesn't match theme variant </error_handling> <example> Complete Material Design blue theme: { "platform": "angular", "designSystem": "material", "primaryColor": "#1976D2", "secondaryColor": "#FF9800", "surfaceColor": "#FAFAFA", "variant": "light", "fontFamily": "'Roboto', sans-serif", "includeTypography": true, "includeElevations": true } </example> <next_steps> After generating a theme: 1. Import the generated Sass file in your application's main styles 2. Customize individual component themes as needed using component schema overrides </next_steps> <related_tools> - detect_platform: Run first to auto-detect platform from package.json - create_custom_palette: Only when exact per-shade values are mandated by a brand spec - create_palette: Use if you only need a palette without full theme - create_typography: Use if you only need typography setup - create_elevations: Use if you only need elevation shadows </related_tools> <related_resources> Call read_resource to load reference data: - "theming://presets/palettes" — preset palette colors - "theming://guidance/colors" — color guidance overview - "theming://guidance/colors/rules" — light/dark theme color rules - "theming://platforms/angular" — Angular platform configuration - "theming://platforms/webcomponents" — Web Components platform configuration - "theming://platforms/react" — React platform configuration - "theming://platforms/blazor" — Blazor platform configuration </related_resources> | |
| set_size | Set global or component-specific sizing by updating --ig-size. <use_case> Use this tool for requests like: - "Make the calendar smaller" - "The buttons feel too big" - "Use the small size everywhere" </use_case> <behavior> - Sets --ig-size in the chosen scope (defaults to :root) - Accepts "small", "medium", "large" (mapped to 1, 2, 3) or numeric values - When platform is "generic", do NOT use the "component" parameter (it resolves Ignite UI component selectors). Use "scope" with a custom CSS selector instead, or omit both for :root. </behavior> <sass_notes> - Components map --ig-size to --component-size internally - Styles using sizable() require @include sizable() in component styles </sass_notes> <example> Make flat buttons medium: { "component": "flat-button", "size": "medium" } Make everything small globally: { "size": "small" } </example> <related_resources> Call read_resource to load reference data: - "theming://docs/spacing-and-sizing" — spacing and sizing overview - "theming://docs/functions/sizable" — sizable value function - "theming://docs/mixins/sizable" — sizable mixin </related_resources> | |
| set_spacing | Set global or component-specific spacing by updating --ig-spacing. <use_case> Use this tool for requests like: - "The button feels bloated" - "Tighten the spacing on the form" - "Double the padding on cards" </use_case> <behavior> - Sets --ig-spacing in the chosen scope (defaults to :root) - Optional overrides for --ig-spacing-inline and --ig-spacing-block - 0 = no spacing, 1 = default, 2 = double (fractions allowed) - spacing is required; inline/block are optional overrides - When platform is "generic", do NOT use the "component" parameter (it resolves Ignite UI component selectors). Use "scope" with a custom CSS selector instead, or omit both for :root. </behavior> <sass_notes> - pad(), pad-inline(), pad-block() require @include spacing() once </sass_notes> <example> Reduce calendar spacing: { "component": "calendar", "spacing": 0.75 } Override inline spacing: { "scope": ".compact", "inline": 0.5, "block": 0.75 } </example> <related_resources> Call read_resource to load reference data: - "theming://docs/spacing-and-sizing" — spacing and sizing overview - "theming://docs/functions/pad" — pad spacing function - "theming://docs/mixins/spacing" — spacing mixin </related_resources> | |
| set_roundness | Set global or component-specific roundness by updating --ig-radius-factor. <use_case> Use this tool for requests like: - "Make the flat buttons more round" - "Square off the cards" </use_case> <behavior> - Sets --ig-radius-factor in the chosen scope (defaults to :root) - 0 = minimum radius, 1 = maximum radius, values between interpolate - When platform is "generic", do NOT use the "component" parameter (it resolves Ignite UI component selectors). Use "scope" with a custom CSS selector instead, or omit both for :root. </behavior> <sass_notes> - border-radius() responds to --ig-radius-factor without extra mixins </sass_notes> <example> Round avatars more: { "component": "avatar", "radiusFactor": 0.9 } Globally reduce roundness: { "radiusFactor": 0.8 } </example> <related_resources> Call read_resource to load reference data: - "theming://docs/spacing-and-sizing" — spacing and sizing overview - "theming://docs/functions/border-radius" — border radius function </related_resources> | |
| get_component_design_tokens | Discover available design tokens (themeable properties) for an Ignite UI component. <use_case> ALWAYS call this tool FIRST before using create_component_theme. It returns the exact token names that can be customized for a component, preventing hallucination of invalid property names. NOTE: This tool returns tokens for Ignite UI framework components. It is NOT useful when the detected platform is "generic" — component theming requires a specific Ignite UI product (angular, webcomponents, react, or blazor). </use_case> <workflow> 1. Provide the component name (e.g., "button", "avatar", "grid") 2. Receive list of all available tokens with their types and descriptions 3. Use the token names in create_component_theme </workflow> <important_notes> COMPONENT NAMING: - Basic components: Use simple names like "avatar", "badge", "card" - Button variants: Use specific variant names like "flat-button", "contained-button", "outlined-button", "fab-button" (NOT just "button") - Icon button variants: "flat-icon-button", "contained-icon-button", "outlined-icon-button" - Child sub-components: Use names like "list-item", "card-header", "accordion-header", "tab-item", "step", "expansion-panel-header". These resolve to the parent component's theme automatically. CHILD SUB-COMPONENTS: - Some component parts (e.g., "list-item", "card-header", "accordion-header") don't have their own theme function — they are styled through the parent component's theme tokens. - When you query a child sub-component, the response includes a note explaining the parent-child relationship and shows the parent theme's full token list. - The token descriptions guide you to the relevant tokens (e.g., "item-background" for list items, "header-text-color" for card headers). - When you then call create_component_theme with a child name, it automatically uses the parent's theme function, variable name, and selector — producing output that is merge-compatible with the parent component's theme. COMPOUND COMPONENTS: There are two types of compound components: **Standard compounds** (e.g., "combo", "select", "date-picker"): - Use multiple internal components that each need their own theme - The response lists related themes and, where available, token derivation hints showing how child token values relate to parent/sibling tokens (e.g., "foreground → adaptive-contrast of calendar.content-background") - Follow derivation hints when setting child token values. If the user specifies an explicit value, use that instead of the derived value. - All related themes should be scoped under the parent component's selector - For each related theme: call get_component_design_tokens, then create_component_theme using the parent component's selector for the target platform **Composed compounds** (e.g., "grid components"): - The framework automatically generates internal themes for all child components from just the primary tokens - Do NOT create separate themes for the related components — they are auto-derived in the component's Sass styles - The response uses a **two-tier token hierarchy**: - **✅ Primary Tokens — USE THESE**: Use ONLY these tokens for the initial theme - **📖 Refinement Tokens — REFERENCE ONLY**: Auto-derived tokens available ONLY when the user explicitly requests fine-grained control (e.g., "change the header background") - Only set the primary tokens in the parent component's theme; all children inherit automatically - The response clearly marks these as "Composed Compound Component" and lists the internally themed children for reference (not for separate theming) VARIANTS INFO: - If you query a base component that has variants (e.g., "button"), the response lists available variants to help you choose the right one </important_notes> <output> Returns: - component: The component name - themeFunctionName: The Sass function to use (e.g., "button-theme") - description: Information about the component theme - tokens: Array of { name, type, description } for each available token - variants: (if applicable) List of variant-specific theme names - compoundInfo: (if applicable) Related themes with token derivation hints and guidance - childNote: (if child sub-component) A note explaining the parent-child relationship </output> <error_handling> - Unknown component: Returns list of similar component names as suggestions - Partial match: If query partially matches multiple components, returns all matches </error_handling> <example> Get tokens for flat button: { "component": "flat-button" } Returns tokens like: background, foreground, hover-background, border-radius, etc. Get tokens for a child sub-component: { "component": "list-item" } Returns the list theme's tokens with a note: "list-item is a child of the list component. Its styling is controlled through the list theme." </example> <related_tools> - create_component_theme: Use the discovered tokens to create a custom theme </related_tools> | |
| create_component_theme | Generate Sass or CSS code to customize an Ignite UI component's appearance using design tokens. <use_case> Use this tool AFTER calling get_component_design_tokens to customize specific component styles. The generated code can be included in your theme file to override default component appearances. </use_case> <workflow> 1. First call get_component_design_tokens to discover available tokens 2. Choose which tokens to customize based on your design requirements 3. Specify designSystem and variant to match the global theme or the one explicitly requested (defaults to Material light) 4. Call this tool with component name, token values, and output format ("sass" or "css") 5. Receive ready-to-use Sass or CSS code with the component theme </workflow> <important_notes> DESIGN SYSTEM & VARIANT: - designSystem: Choose "material" (default), "bootstrap", "fluent", or "indigo" - variant: Choose "light" (default) or "dark" - The correct schema (e.g., $light-bootstrap-schema, $dark-material-schema) is automatically selected and passed to the component theme function - The correct output: Choose output format based on the target file type (Sass vs CSS) - This ensures component tokens inherit proper defaults from the design system LIGHT & DARK: - Each call produces one variant. If the app supports light and dark, call this tool for each variant — do not ship only the light one. - The dark call usually needs different token values than the light one (e.g. colors that work on a dark surface). Do not repeat the light tokens unchanged. - Scope the dark call under the app's dark-mode selector so it doesn't override the light theme (e.g. ".your-dark-scope igc-avatar"). - Put that dark-mode selector on a root element (`html`, `body`, or the app's theme root), not on an app container. On Angular, overlay-hosted components (`.igx-dialog`, `.igx-drop-down__list`, `.igx-tooltip`, `.igx-overlay__content`) are moved to the overlay outlet under `body`, so a scope on an app container won't match them. - The response includes a note with the scoped selector for the other variant. TOKEN VALIDATION: - All provided token names are validated against the component's schema - Invalid tokens return an error with the list of valid token names - You don't need to specify all tokens - only those you want to customize (prefer PRIMARY tokens to minimize the number of overrides) TOKEN VALUE FORMATS: - Colors: Any valid CSS color format (hex, rgb, hsl, named colors) - Dimensions: Include units (e.g., "8px", "0.5rem", "2em") - Border radius: Can be single value or shorthand ("8px" or "8px 8px 0 0") - Shadows: Full box-shadow syntax ("0 2px 4px rgba(0,0,0,0.1)") SELECTORS: - Default selector is auto-detected based on platform and component - For child sub-components (e.g., "list-item", "card-header"), the selector automatically resolves to the parent component's selector (e.g., "igx-list", "igx-card") - Angular: Uses "igx-*" element selectors or attribute selectors - Web Components: Uses "igc-*" element selectors - Custom selectors supported for targeted styling (e.g., ".my-button") CHILD SUB-COMPONENTS: - When creating a theme for a child sub-component (e.g., "card-actions"), the output uses the parent's theme function, variable name, and selector. - This means the output for "card" and "card-actions" is merge-compatible: both produce `$custom-card-theme: card-theme(...)` scoped to `igx-card`. - To add tokens for multiple sub-parts, merge the token arguments into a single theme function call rather than creating separate themes. SASS OUTPUT: - Generated code uses `@include tokens($theme)` to apply the theme - The tokens mixin emits --ig-{component}-{token} CSS custom properties in global mode COMPOUND COMPLETENESS: - **Standard compounds:** If the user asks for a standard compound component, the response is incomplete unless related theme calls are also generated. Use the related themes list from get_component_design_tokens to drive the sequence. All related themes should use the compound component's selector as the wrapper. Follow token derivation hints to set child token values consistently. - **Composed compounds:** If the component is a composed compound (e.g., grid), do NOT generate separate child themes. Only set the primary tokens (background, foreground, accent-color) on the parent component's theme — child themes are auto-derived internally by the component's Sass styles. Refinement tokens (e.g., header-background) can be added in follow-up calls when the user explicitly asks to customize a specific aspect. SASS FILE PLACEMENT: - When combining Sass output from multiple tools into one file, all @use rules must appear at the top before any other statements. Deduplicate @use lines that share the same module path. </important_notes> <output> Returns: - Generated Sass or CSS code with: - Platform-specific @use import (Sass only) - Theme function call with $schema parameter and provided token values (Sass only) - tokens mixin to apply the theme to the selector (Sass only) - Description of what was generated - Design system and variant used - List of tokens used - A light/dark note on covering the other variant </output> <error_handling> - Unknown component: Returns error with list of available components - Invalid tokens: Returns error listing invalid tokens and valid alternatives - Invalid color format: Returns error with format guidance </error_handling> <example> Custom blue flat button with rounded corners (Angular, Material Design): { "platform": "angular", "designSystem": "material", "variant": "light", "component": "flat-button", "tokens": { "foreground": "#1976d2", } } Generates: ```scss @use 'igniteui-angular/theming' as *; $custom-flat-button-theme: flat-button-theme( $schema: $light-material-schema, $foreground: #1976d2, ); .igx-button--flat { @include tokens($custom-flat-button-theme); } ``` Bootstrap dark theme example: { "platform": "webcomponents", "designSystem": "bootstrap", "variant": "dark", "component": "avatar", "tokens": { "background": "#ff5722" } } Generates: ```scss @use 'igniteui-theming' as *; $custom-avatar-theme: avatar-theme( $schema: $dark-bootstrap-schema, $background: #ff5722 ); igc-avatar { @include tokens($custom-avatar-theme); } ``` </example> <compound_example> Date Picker (compound) — all child themes use the parent component's selector. Follow token derivation hints from get_component_design_tokens: 1) get_component_design_tokens { "component": "date-picker" } 2) create_component_theme { "component": "date-picker", "platform": "angular", ... } 3) create_component_theme { "component": "calendar", "selector": "igx-date-picker", ... } 4) create_component_theme { "component": "flat-button", "selector": "igx-date-picker", ... } 5) create_component_theme { "component": "input-group", "selector": "igx-date-picker", ... } Each child theme uses the parent's platform selector (e.g., `igx-date-picker` for Angular, `igc-date-picker` for Web Components / React / Blazor). The tokens mixin emits --ig-{component}-{token} variables that child components consume via var() fallback — no per-child selectors needed. </compound_example> <related_tools> - detect_platform: Run to auto-detect platform for correct imports - get_component_design_tokens: MUST call first to discover valid tokens - create_theme: Use for full theme (palette + typography + elevations) </related_tools> | |
| get_color | Retrieve a palette color from Ignite UI Theming as a CSS variable reference. <use_case> Use this tool when you need to reference a specific palette color in CSS or Sass code. Returns CSS variable references that work in both Sass and CSS contexts. Common scenarios: - Setting component backgrounds/foregrounds using theme colors - Creating hover/focus states with opacity variations - Ensuring text contrast against colored backgrounds </use_case> <workflow> 1. Specify the color family (primary, secondary, gray, etc.) 2. Optionally specify a shade variant (50-900, A100-A700) 3. Optionally request the contrast color for text readability 4. Optionally apply opacity for transparency effects </workflow> <output_examples> Basic color: { color: "primary" } → var(--ig-primary-500) Specific shade: { color: "primary", variant: "600" } → var(--ig-primary-600) Contrast color: { color: "primary", variant: "600", contrast: true } → var(--ig-primary-600-contrast) With opacity: { color: "primary", opacity: 0.5 } → hsl(from var(--ig-primary-500) h s l / 0.5) Contrast with opacity: { color: "primary", contrast: true, opacity: 0.7 } → hsl(from var(--ig-primary-500-contrast) h s l / 0.7) </output_examples> <important_notes> CSS VARIABLE NAMING: - Base colors: --ig-{color}-{variant} (e.g., --ig-primary-500) - Contrast: --ig-{color}-{variant}-contrast (e.g., --ig-primary-500-contrast) GRAY RESTRICTIONS: - Gray only supports standard shades (50-900), not accent shades (A100-A700) OPACITY HANDLING: - Uses CSS relative color syntax: hsl(from <color> h s l / <opacity>) - Works in modern browsers (CSS Color Level 4) - For Sass projects, this syntax is passed through unchanged </important_notes> <related_tools> - create_palette: Generate a complete palette with these colors - create_component_theme: Use retrieved colors in component theming </related_tools> |
Show all 15 toolsShow fewer tools
get_chart_series_colorsRetrieve the shared Ignite UI chart series brush palette, per-chart-type color-token guidance, and validate custom brush lists. <use_case> Use this tool when theming Ignite UI charts (category, data, doughnut, pie, funnel, shape, financial, linear/radial gauge, bullet graph) and you need the default series colors, want to know which theme tokens accept a custom color list for a given chart type, or want to sanity-check a custom brush list before using it in a $brushes: (...) override. NOT covered by this tool: sparkline (singular tokens, not a palette list) and selection/highlight colors (selectionBrush, focusBrush — component-only, no Sass theme equivalent). </use_case> <workflow> 1. Call with no arguments to get the full 10-color default (regular) palette. 2. Optionally set mode: "color-blind" for the accessibility-friendly variant. 3. Optionally set index (1-10) to retrieve a single brush color. 4. Optionally set chartType (e.g. "category-chart", "financial-chart", "linear-gauge") to see which theme tokens on that chart type accept the palette, plus a ready-to-use Sass snippet. 5. Optionally set customBrushes to a color array to validate it before using it in an override — checks each color is valid and flags color pairs with similar hues that may be hard to tell apart. </workflow> <output_examples> Default palette: {} → 10-color list + var(--chart-brushes) reference Single brush: { index: 3 } → the 3rd regular-palette color Chart-type guidance: { chartType: "category-chart" } → token table (brushes, marker-brushes, outlines, marker-outlines, trend-line-brushes, negative-brushes, negative-outlines) + a category-chart-theme() Sass snippet Custom brush validation: { customBrushes: ["#4285f4", "#ea4335", "#fbbc05", "#34a853"] } → validity + hue-distinctness warnings </output_examples> <important_notes> THEME VS. COMPONENT PRECEDENCE: - This tool and the Sass snippets it generates set the THEME DEFAULT only. - Chart components also expose their own color-list properties (e.g. Angular's brushes, outlines, markerBrushes, markerOutlines, rangeBrushes, rangeOutlines) that OVERRIDE the theme default per instance. Always mention this precedence when generating chart theme code. SCOPE: - Only list-valued brush/outline tokens are covered. Sparkline and selection/highlight colors are intentionally excluded — see the guidance resource at theming://guidance/colors/charts. - Some chart types default certain tokens to a FIXED color rather than the shared palette (e.g. category-chart's negative-brushes/negative-outlines default to red, not "series") — check the "default" column in the chartType response rather than assuming uniformity. </important_notes> <related_tools> - create_component_theme: Not yet wired for chart components (see project notes) — use the Sass snippet from this tool directly instead. - theming://guidance/colors/charts: Full guidance resource with the complete per-chart-type token reference and override examples. </related_tools>
fit_color_scaleDerive a shade scale from an existing color ladder. <use_case> Use when shades must follow the rhythm of a ladder you already have - another design system's grays, a brand ramp, a palette from a screenshot. Pass the returned spec to create_palette or create_theme as `scales`. Never hand-write range/curve values. Not needed for the built-in presets ("even" | "material" | "tailwind" | "carbon") - name those in `scales` directly. </use_case> <important_notes> - Order the colors LIGHTEST FIRST (a 50-900 ladder already is). 3 minimum, 10 fits best. - The response reports how closely the fit reproduces the ladder; a ladder that does not follow one smooth curve fits loosely and says so. - A scale sets rhythm only, never hue - the seed still decides the color. - Set `family` to the palette family the ladder is for; it keys the returned scales map. `name` is only a label. - Background: read_resource "theming://guidance/colors/scales" </important_notes> <example> { "colors": ["#f8fafc","#f1f5f9","#e2e8f0","#cbd5e1","#94a3b8", "#64748b","#475569","#334155","#1e293b","#0f172a"], "family": "gray", "name": "Tailwind slate" } </example>
read_resourceRead a theming resource by URI. Returns reference data such as platform configurations, color palette presets, typography presets, color guidance, and layout documentation. <use_case> Use this tool to load reference data before or during theme generation. Other tools reference these resources in their related_resources sections — call this tool with the listed URI to retrieve the data. Common scenarios: - Load palette presets to see available colors before creating a palette - Read color guidance to understand shade usage and semantic roles - Check platform configuration for usage examples and supported features - Read layout documentation for spacing, sizing, and roundness details </use_case> <workflow> 1. Identify the resource URI from the available_resources list or from a related_resources hint in another tool 2. Call this tool with the URI 3. Use the returned data to inform your next action </workflow> <output> Returns the resource content as text. Format depends on the resource: - application/json resources return JSON data - text/markdown resources return Markdown documentation </output> <error_handling> If the URI is not found, returns the list of all available resource URIs. </error_handling> <available_resources> Platforms: - "theming://platforms" — Supported Platforms - "theming://platforms/angular" — Angular Platform Config - "theming://platforms/webcomponents" — Web Components Platform Config - "theming://platforms/react" — React Platform Config - "theming://platforms/blazor" — Blazor Platform Config - "theming://platforms/generic" — Generic Platform Config Presets: - "theming://presets/palettes" — Color Palettes - All Presets - "theming://presets/palettes/light" — Color Palettes - Light - "theming://presets/palettes/dark" — Color Palettes - Dark - "theming://presets/typography" — Typography Presets - "theming://presets/elevations" — Elevation Presets - "theming://presets/chart-brushes" — Chart Series Brush Palettes Guidance: - "theming://guidance/platform-setup" — Platform Setup Guide - "theming://guidance/colors" — Color Guidance Overview - "theming://guidance/colors/rules" — Color Rules - Light and Dark Themes - "theming://guidance/colors/usage" — Color Shade Reference - "theming://guidance/colors/roles" — Color Semantic Roles - "theming://guidance/colors/states" — Color Interaction States - "theming://guidance/colors/themes" — Color Design System Patterns - "theming://guidance/colors/charts" — Chart Series Colors Guidance - "theming://guidance/colors/scales" — Shade Scales Layout Docs: - "theming://docs/spacing-and-sizing" — Spacing and Sizing Overview - "theming://docs/functions/pad" — Pad Spacing Function - "theming://docs/functions/sizable" — Sizable Value Function - "theming://docs/functions/border-radius" — Border Radius Function - "theming://docs/mixins/spacing" — Spacing Mixin - "theming://docs/mixins/sizing" — Sizing Mixin - "theming://docs/mixins/sizable" — Sizable Mixin </available_resources>
| get_chart_series_colors | Retrieve the shared Ignite UI chart series brush palette, per-chart-type color-token guidance, and validate custom brush lists. <use_case> Use this tool when theming Ignite UI charts (category, data, doughnut, pie, funnel, shape, financial, linear/radial gauge, bullet graph) and you need the default series colors, want to know which theme tokens accept a custom color list for a given chart type, or want to sanity-check a custom brush list before using it in a $brushes: (...) override. NOT covered by this tool: sparkline (singular tokens, not a palette list) and selection/highlight colors (selectionBrush, focusBrush — component-only, no Sass theme equivalent). </use_case> <workflow> 1. Call with no arguments to get the full 10-color default (regular) palette. 2. Optionally set mode: "color-blind" for the accessibility-friendly variant. 3. Optionally set index (1-10) to retrieve a single brush color. 4. Optionally set chartType (e.g. "category-chart", "financial-chart", "linear-gauge") to see which theme tokens on that chart type accept the palette, plus a ready-to-use Sass snippet. 5. Optionally set customBrushes to a color array to validate it before using it in an override — checks each color is valid and flags color pairs with similar hues that may be hard to tell apart. </workflow> <output_examples> Default palette: {} → 10-color list + var(--chart-brushes) reference Single brush: { index: 3 } → the 3rd regular-palette color Chart-type guidance: { chartType: "category-chart" } → token table (brushes, marker-brushes, outlines, marker-outlines, trend-line-brushes, negative-brushes, negative-outlines) + a category-chart-theme() Sass snippet Custom brush validation: { customBrushes: ["#4285f4", "#ea4335", "#fbbc05", "#34a853"] } → validity + hue-distinctness warnings </output_examples> <important_notes> THEME VS. COMPONENT PRECEDENCE: - This tool and the Sass snippets it generates set the THEME DEFAULT only. - Chart components also expose their own color-list properties (e.g. Angular's brushes, outlines, markerBrushes, markerOutlines, rangeBrushes, rangeOutlines) that OVERRIDE the theme default per instance. Always mention this precedence when generating chart theme code. SCOPE: - Only list-valued brush/outline tokens are covered. Sparkline and selection/highlight colors are intentionally excluded — see the guidance resource at theming://guidance/colors/charts. - Some chart types default certain tokens to a FIXED color rather than the shared palette (e.g. category-chart's negative-brushes/negative-outlines default to red, not "series") — check the "default" column in the chartType response rather than assuming uniformity. </important_notes> <related_tools> - create_component_theme: Not yet wired for chart components (see project notes) — use the Sass snippet from this tool directly instead. - theming://guidance/colors/charts: Full guidance resource with the complete per-chart-type token reference and override examples. </related_tools> | |
| fit_color_scale | Derive a shade scale from an existing color ladder. <use_case> Use when shades must follow the rhythm of a ladder you already have - another design system's grays, a brand ramp, a palette from a screenshot. Pass the returned spec to create_palette or create_theme as `scales`. Never hand-write range/curve values. Not needed for the built-in presets ("even" | "material" | "tailwind" | "carbon") - name those in `scales` directly. </use_case> <important_notes> - Order the colors LIGHTEST FIRST (a 50-900 ladder already is). 3 minimum, 10 fits best. - The response reports how closely the fit reproduces the ladder; a ladder that does not follow one smooth curve fits loosely and says so. - A scale sets rhythm only, never hue - the seed still decides the color. - Set `family` to the palette family the ladder is for; it keys the returned scales map. `name` is only a label. - Background: read_resource "theming://guidance/colors/scales" </important_notes> <example> { "colors": ["#f8fafc","#f1f5f9","#e2e8f0","#cbd5e1","#94a3b8", "#64748b","#475569","#334155","#1e293b","#0f172a"], "family": "gray", "name": "Tailwind slate" } </example> | |
| read_resource | Read a theming resource by URI. Returns reference data such as platform configurations, color palette presets, typography presets, color guidance, and layout documentation. <use_case> Use this tool to load reference data before or during theme generation. Other tools reference these resources in their related_resources sections — call this tool with the listed URI to retrieve the data. Common scenarios: - Load palette presets to see available colors before creating a palette - Read color guidance to understand shade usage and semantic roles - Check platform configuration for usage examples and supported features - Read layout documentation for spacing, sizing, and roundness details </use_case> <workflow> 1. Identify the resource URI from the available_resources list or from a related_resources hint in another tool 2. Call this tool with the URI 3. Use the returned data to inform your next action </workflow> <output> Returns the resource content as text. Format depends on the resource: - application/json resources return JSON data - text/markdown resources return Markdown documentation </output> <error_handling> If the URI is not found, returns the list of all available resource URIs. </error_handling> <available_resources> Platforms: - "theming://platforms" — Supported Platforms - "theming://platforms/angular" — Angular Platform Config - "theming://platforms/webcomponents" — Web Components Platform Config - "theming://platforms/react" — React Platform Config - "theming://platforms/blazor" — Blazor Platform Config - "theming://platforms/generic" — Generic Platform Config Presets: - "theming://presets/palettes" — Color Palettes - All Presets - "theming://presets/palettes/light" — Color Palettes - Light - "theming://presets/palettes/dark" — Color Palettes - Dark - "theming://presets/typography" — Typography Presets - "theming://presets/elevations" — Elevation Presets - "theming://presets/chart-brushes" — Chart Series Brush Palettes Guidance: - "theming://guidance/platform-setup" — Platform Setup Guide - "theming://guidance/colors" — Color Guidance Overview - "theming://guidance/colors/rules" — Color Rules - Light and Dark Themes - "theming://guidance/colors/usage" — Color Shade Reference - "theming://guidance/colors/roles" — Color Semantic Roles - "theming://guidance/colors/states" — Color Interaction States - "theming://guidance/colors/themes" — Color Design System Patterns - "theming://guidance/colors/charts" — Chart Series Colors Guidance - "theming://guidance/colors/scales" — Shade Scales Layout Docs: - "theming://docs/spacing-and-sizing" — Spacing and Sizing Overview - "theming://docs/functions/pad" — Pad Spacing Function - "theming://docs/functions/sizable" — Sizable Value Function - "theming://docs/functions/border-radius" — Border Radius Function - "theming://docs/mixins/spacing" — Spacing Mixin - "theming://docs/mixins/sizing" — Sizing Mixin - "theming://docs/mixins/sizable" — Sizable Mixin </available_resources> |
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableigniteui/igniteui-theming is public and reachablegithub.com/igniteui/igniteui-theming ↗Pass
- Package names this repository as its sourceigniteui-theming names igniteui/igniteui-theming as sourcenpmjs.com/package/igniteui-theming ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for igniteui-themingnpmjs.com/package/igniteui-theming/v/30.2.0#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/igniteui/igniteui-theming ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from igniteui-themingPass
- No critical advisory in the package or its dependencies151 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model15 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubThe Ignite UI Theming repository collects a set of Sass mixins, functions, and variables used to create themes for a variety of UI frameworks built by Infragistics. The theming package makes it super easy to create palettes, elevations and typography styles for your projects.
Repository Structure
This repository is an npm workspaces monorepo with two packages:
| Package | Name | Description |
|---|---|---|
packages/theming |
igniteui-theming |
Sass source, JSON build artifacts, published to npm |
packages/mcp |
igniteui-theming-mcp |
MCP server sources, built into packages/theming/dist/mcp/ |
The igniteui-theming package is the only published artifact — it includes both the Sass theming library and the MCP server binary.
The MCP server is also listed in the MCP Registry as io.github.IgniteUI/igniteui-theming. The server.json at the repo root is its registry manifest, published automatically on release.
Common commands from the repo root:
npm install # install all workspace dependencies
npm run build # build theming + MCP in dependency order
npm test # run all tests across both packages
npm run lint # lint all packages
Palettes
We provide four predefined palettes - material, bootstrap, fluent and indigo that have all the necessary colors along with diffent variants of those colors to make it even easier picking the right one for your case. Here's what they look like:

To access any of the colors in the palettes, you can use the color function:
background: color($light-material-palette, 'primary', 500);
You can take a further look on what color functions and mixins the package contains and how to use them in the Colors Wiki Page
Typography
Another valuable module of our theming package is the typography, helping you have consistency all over your project. There are again four typography presets for the four themes that we provide out of the box.

You can set any of the typefaces by using the typography mixin, which accepts 2 arguments(font-family and type-scale). By default the typography is using the material typeface and type-scale.
@include typography($font-family: $material-typeface, $type-scale: $material-type-scale);
Learn more about the typography module in the package by checking out the Typography Wiki Page
Elevations
The theming package is providing one preset of shadows that can be used to give your components a lift. They're super helpful using with buttons, cards, navigation bars, etc.

You can set elevations 0-24, by using the elevation function, which accepts the elevation level as an argument:
box-shadow: elevation(12);
Learn more about elevations and their abilities in the Elevations Wiki Page
Usage
In order to use the Ignite UI Theming in your application you should install the igniteui-theming package:
npm install igniteui-theming
Next, you will need to use it in the file that you want like this:
@use '.../node_modules/igniteui-theming/' as *;
You can also use just a fraction of the package:
@use '.../node_modules/igniteui-theming/sass/color' as *;
We provide presets for material, bootstrap, fluent and indigo themes for the color(light and dark palettes), typography and elevations fractions. You can import them into your scss file like this:
@use '.../node_modules/igniteui-theming/sass/typography/presets' as *;
You can read more about what the package contains on the Wiki page
Linting and Testing
To scan the project for linting errors, run
npm run lint
To run the suite of tests, run
npm run test
Testing and Debugging
Preview Palettes
Run from packages/theming. Pass the palette (material, bootstrap, fluent, indigo) and variant (light or dark).
npm run preview:palette -- --palette=material --variant=light
MCP Server (AI-Assisted Theming)
The Ignite UI Theming package includes a Model Context Protocol (MCP) server that enables AI assistants to generate production-ready theming code for your Ignite UI applications. This MCP server is part of the larger AI-assisted development toolchain for Ignite UI.
What is MCP?
The Model Context Protocol allows AI assistants (like Claude, GitHub Copilot, and others) to connect to external tools and data sources. The Ignite UI Theming MCP server acts as an expert theming assistant that can:
- 🎨 Generate color palettes with automatic shade variations
- 📝 Create typography systems following design standards
- 🌓 Build complete themes for light and dark modes
- 🎯 Customize components with design tokens
- ✅ Validate colors for accessibility compliance
Quick Start
Most users don't need to clone anything. The server ships inside the published igniteui-theming package and is listed in the MCP Registry as io.github.IgniteUI/igniteui-theming — clients that support registry installation can add it by that name, and everything else uses the npx configuration shown below.
To run it from source instead:
1. Clone and Build
Clone the repository and build:
npm install
npm run build
2. Configure Your AI Client
The MCP server works with any MCP-compatible client. Here are setup instructions for popular clients:
For local development - Create or edit .vscode/mcp.json:
{
"servers": {
"igniteui-theming": {
"command": "node",
"args": ["/absolute/path/to/igniteui-theming/packages/theming/dist/mcp/index.js"]
}
}
}
Using published package:
{
"servers": {
"igniteui-theming": {
"command": "npx",
"args": ["-y", "igniteui-theming"]
}
}
}
- Go to Settings → Tools → AI Assistant → MCP Servers
- Click + Add MCP Server
- Configure:
- Name:
igniteui-theming - Command:
node(for local) ornpx(for package) - Arguments:
- Local:
/absolute/path/to/igniteui-theming/packages/theming/dist/mcp/index.js - Package:
-y igniteui-theming
- Local:
- Name:
- Click OK and restart AI Assistant
Add to your configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
For local development:
{
"mcpServers": {
"igniteui-theming": {
"command": "node",
"args": ["/absolute/path/to/igniteui-theming/packages/theming/dist/mcp/index.js"]
}
}
}
Using published package:
{
"mcpServers": {
"igniteui-theming": {
"command": "npx",
"args": ["-y", "igniteui-theming"]
}
}
}
Create or edit .cursor/mcp.json in your project:
For local development:
{
"mcpServers": {
"igniteui-theming": {
"command": "node",
"args": ["/absolute/path/to/igniteui-theming/packages/theming/dist/mcp/index.js"]
}
}
}
Using published package:
{
"mcpServers": {
"igniteui-theming": {
"command": "npx",
"args": ["-y", "igniteui-theming"]
}
}
}
What Can It Do?
🎨 Create Complete Themes
Simply describe your theme to your AI assistant:
"Create a Material Design dark theme for my Angular app with that takes inspiration from the Gruvbox color scheme."
The AI will generate production-ready Sass code with:
- Color palette with all shade variations
- Typography setup with proper type scales
- Elevation shadows
- Platform-specific imports and configuration
🌈 Generate Color Palettes
"Generate a light theme palette using teal as primary and purple as secondary"
Get perfectly calculated color shades following design system standards.
📝 Setup Typography
"Set up typography using Inter font with Material Design type scale for Web Components"
Get proper typography configuration with font families and responsive type scales.
🎯 Customize Components
"What design tokens are available for the button component?"
"Create a flat button theme with purple background and white text"
Discover and customize individual component styles using design tokens.
Available Capabilities
The MCP server provides 8 tools and 16 resources:
Tools (Actions)
| Tool | Description |
|---|---|
detect_platform |
Auto-detect which Ignite UI platform your project uses |
create_palette |
Generate color palette with automatic shade calculations |
create_custom_palette |
Create palette with fine-grained control over individual shades |
create_typography |
Setup typography with font families and type scales |
create_elevations |
Configure elevation shadows |
create_theme |
Generate complete theme (palette + typography + elevations) |
get_component_design_tokens |
Discover customizable properties for components |
create_component_theme |
Generate component-specific theme code |
Resources (Reference Data)
- Platform Information: Configuration for Angular, Web Components, React, and Blazor
- Preset Libraries: Pre-built palettes, typography, and elevation sets
- Color Guidance: Best practices for color selection and usage
- Design System Schemas: Material, Bootstrap, Fluent, and Indigo configurations
Supported Platforms
- Angular -
igniteui-angular - Web Components -
igniteui-webcomponents - React -
igniteui-react - Blazor -
igniteui-blazor
Example Interactions
You: "I'm starting a new Angular project with Ignite UI. Create a complete Material Design theme with primary blue, secondary coral, light theme, and Roboto font"
AI: Uses create_theme tool and generates complete Sass code ready to use
You: "I need a dark mode version with the same primary blue but dark surface"
AI: Uses create_theme with variant: "dark" and generates dark theme code
You: "What properties can I customize on the card component?"
AI: Uses get_component_design_tokens to show available tokens
You: "Make the card have a light gray background with subtle shadow"
AI: Uses create_component_theme to generate component theme code
Full Documentation
For detailed documentation including:
- Complete tool parameter reference
- All prompt examples
- Platform-specific differences
- Troubleshooting guide
- Development instructions
See the MCP Server README
Development Scripts
# Build for production (theming + MCP)
npm run build
# Run tests
npm run test
# Debug with MCP Inspector (from packages/mcp)
npm run inspect
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Ignite UI Theming MCP questions
How do I add Ignite UI Theming MCP to Claude Code?
Run claude mcp add igniteui-theming -- npx -y igniteui-theming in your terminal. Add --scope user to make it available in every project.
How do I add Ignite UI Theming MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Ignite UI Theming MCP provide?
It exposes 15 tools, including detect_platform, create_palette, create_custom_palette, create_typography, create_elevations.
What can the Ignite UI Theming MCP server do?
It acts as an expert assistant that can generate color palettes with shade variations, create typography systems, build complete light and dark themes, customize components with design tokens, and validate colors for accessibility.