developer-tools Static interface comparison

Ignite UI Theming MCP Server

30.1.0 30.2.0

PASSAutomated static analysis

No policy-significant interface change detected.

View the upgrade review as Markdown

A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.

Tools15 → 15
Added0
Removed0
Schema changes0
Input schema changes0
Output schema changes0
Unclassified schema changes0
Description changes1
New write authority0
New destructive authority0
New unknown authority0
AnalysisPASS

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

1 tool with recorded changes

  1. create_component_themeModifiedDescriptionINFO

    What changed

    • create_component_theme: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    unknown → unknown
    Description
    PreviousGenerate 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 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 </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>
    CurrentGenerate 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>

    Input schema

    Input schema unchanged.

    10 unchanged entries
    • (schema root)
    • component
    • designSystem
    • licensed
    • name
    • output
    • platform
    • selector
    • tokens
    • variant

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
14 tools with no recorded change
  • create_custom_palette
  • create_elevations
  • create_palette
  • create_theme
  • create_typography
  • detect_platform
  • fit_color_scale
  • get_chart_series_colors
  • get_color
  • get_component_design_tokens
  • read_resource
  • set_roundness
  • set_size
  • set_spacing

Evidence and provenance

Static findings
PASS from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
Human review
Automated static analysis. No reviewer decision is recorded for this comparison.
Published evidence
Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
Comparison
igniteui-theming/30.1.0~30.2.0The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 9:58 PM UTC.
Distribution
npm
Previous release
igniteui-theming@30.1.015 tools · published by the registry Nov 3, 2026, 8:02 AM UTCArtifact integritysha512-3UEK2p4Aw5fu9v0MNlyqauapx99oBVoPmYp/A3IA71Y3FhKHnfEhnPshwxLR4qHi7XRSpAO84Nekmo4gSH1ZoA==Interface fingerprintsha256:5c8de285c65caa5dffea200b5932c2bcf240c0c59ed3748244229a90f099310eExact interface snapshot (JSON)
Current release
igniteui-theming@30.2.015 tools · published by the registry Nov 10, 2026, 9:26 AM UTCArtifact integritysha512-nYdHKYG1FjuzB3rpz6sLlc2sYTR4HOABB3wuWokQwZj8i/cfvoBbJrsH9JESXGwcyYuq++3ZaaFG4yWBWEZG7Q==Interface fingerprintsha256:0ccde05ca26ab29450138fadbb7de81ac742790acf56679747bda0cb0e2ccb90Exact interface snapshot (JSON)

The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.

MODELARA ANALYSIS OUTPUT

Interface findings

Analyzed with Modelara v0.1.8 · Nov 16, 2026

Informational

1 finding
  • create_component_themeINFOChanged

    Description changed

    Authority
    UNKNOWNUNKNOWN
    Authority unchanged
What do these results mean?
PASS
No policy-significant interface change detected.
REVIEW
Interface changes require inspection.
FAIL
A policy-significant change was detected.
INVALID
The comparison could not be evaluated reliably.
← Back to Ignite UI Theming MCP Server release history