/**
* Centralized descriptions for MCP tools and their parameters.
*
* Uses XML-like tags for structured content that helps AI models
* understand tool purpose, workflows, and constraints.
*
* Structure:
* - FRAGMENTS: Reusable text snippets for common concepts
* - TOOL_DESCRIPTIONS: Full tool descriptions with XML sections
* - PARAM_DESCRIPTIONS: Individual parameter descriptions
*/
/**
* Reusable text fragments for common concepts.
* Used to maintain consistency across descriptions.
*/
export declare const FRAGMENTS: {
/** Platform parameter description */
readonly PLATFORM: "Target platform: \"angular\" for Ignite UI for Angular, \"webcomponents\" for Ignite UI for Web Components, \"react\" for Ignite UI for React, \"blazor\" for Ignite UI for Blazor, or \"generic\" for platform-agnostic output (standalone igniteui-theming usage). If omitted, generates generic code. Use detect_platform tool first to auto-detect from project files.";
/** Color format examples - CSS Color Level 4 */
readonly COLOR_FORMAT: "Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
/** Variant parameter description */
readonly VARIANT: "Theme variant: \"light\" (light backgrounds, dark text) or \"dark\" (dark backgrounds, light text). Defaults to \"light\".";
/** Design system parameter description */
readonly DESIGN_SYSTEM: "Design system preset: \"material\" (Material Design), \"bootstrap\" (Bootstrap), \"fluent\" (Microsoft Fluent), or \"indigo\" (Infragistics Indigo). Defaults to \"material\".";
/** Chromatic shade levels */
readonly CHROMATIC_SHADES: "14 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, A100, A200, A400, A700";
/** Gray shade levels */
readonly GRAY_SHADES: "10 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900";
/** Surface layer roles */
readonly SURFACE_ROLES: "6 layers required: base, sunken, raised, overlay, container, seed";
/** What a seed color does and does not control */
readonly SEED_BEHAVIOUR: "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.";
/** Monochromatic requirement - only applies to hand-written explicit shades */
readonly MONOCHROMATIC_RULE: "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.";
/** Sass @use placement guidance for tools that generate Sass output */
readonly SASS_FILE_PLACEMENT: "SASS FILE PLACEMENT:\n - When combining Sass output from multiple tools into one file, all @use rules\n must appear at the top before any other statements. Deduplicate @use lines\n that share the same module path.";
/** Resource scheme */
readonly RESOURCE_SCHEME: "theming://";
};
/**
* Comprehensive tool descriptions with XML-structured sections.
* These are shown to AI models when listing available tools.
*/
export declare const TOOL_DESCRIPTIONS: {
readonly detect_platform: "Detect the target platform by analyzing dependencies and project config files.\n\n\n Use this tool FIRST before generating any theme code to ensure platform-optimized output.\n The detected platform determines the correct Sass module paths and syntax.\n Output format (\"sass\" vs \"css\") is a separate concern — see the output parameter on each\n generation tool. For non-Angular platforms, prefer \"css\" unless the project has a confirmed\n Sass pipeline; use your own file-reading tools or ask the user to confirm before choosing\n output: \"sass\".\n\n\n\n Uses multi-signal detection with confidence scoring:\n 1. Ignite UI packages (HIGH - 100): igniteui-angular, igniteui-webcomponents, igniteui-react, IgniteUI.Blazor\n 2. Config files (MEDIUM-HIGH - 80): angular.json, vite.config.*, next.config.*, .csproj\n 3. Framework packages (LOW - 40): @angular/core, react, lit (fallback only)\n 4. Generic fallback: When no Ignite UI product is found, returns \"generic\" for standalone theming\n\n\n\n\n\n When multiple Ignite UI platforms are detected with significant confidence (≥60), returns:\n - platform: null\n - ambiguous: true\n - alternatives: List of possible platforms with their signals\n - Action: User must specify platform explicitly in subsequent tool calls\n\n\n\n After detection, use the platform value with:\n - create_palette: Generate color palette\n - create_theme: Generate complete theme\n - create_typography: Set up typography\n - create_elevations: Configure shadows\n\n\n\n - \"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.\n";
readonly create_palette: "Generate a color palette for Ignite UI themes using the palette() Sass function.\n\n\n Use this tool when you have base colors and want to auto-generate a complete palette\n with all shade variations (50-900, A100-A700). This is the right tool for almost every\n palette - pass the brand colors and let the generator do the rest.\n\n\n\n - \"sass\" (default): Generates Sass code using the palette() function. Requires Sass compilation.\n - \"css\": Generates CSS custom properties (variables) directly. Ready to use in any CSS file.\n\n Use \"css\" output when:\n - Working with vanilla CSS projects without Sass\n - You want immediately usable CSS variables\n - Using CSS-in-JS or other non-Sass styling approaches\n\n\n\n 1. Validates input colors against the theme variant\n 2. Generates Sass code OR compiles to CSS based on output parameter\n 3. Adds warning comments to code if issues detected\n 4. Returns validation warnings and tips in response\n\n\n\n - Requires primary, secondary, and surface colors (matches Sass palette() API)\n - Gray, info, success, warn, error are optional (use design system defaults)\n - Surface color should match variant: light colors for \"light\", dark for \"dark\"\n - 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.\n\n SHADE PROGRESSION (important):\n - Primary, secondary, and all chromatic colors: shades are NEVER inverted.\n The palette() function always generates 50=lightest to 900=darkest.\n - Only gray shades behave differently based on variant (for text contrast).\n - DO NOT manually invert primary/secondary colors for dark themes.\n\n SASS FILE PLACEMENT:\n - When combining Sass output from multiple tools into one file, all @use rules\n must appear at the top before any other statements. Deduplicate @use lines\n that share the same module path.\n\n\n\n\n\n - Invalid color format: Returns error with format examples\n - Variant mismatch: Warns if surface color doesn't match theme variant\n\n\n\n Blue brand with orange accent on light theme (Sass output):\n {\n \"primary\": \"#1976D2\",\n \"secondary\": \"#FF9800\",\n \"surface\": \"#FAFAFA\",\n \"variant\": \"light\"\n }\n\n Same palette as CSS variables:\n {\n \"primary\": \"#1976D2\",\n \"secondary\": \"#FF9800\",\n \"surface\": \"#FAFAFA\",\n \"variant\": \"light\",\n \"output\": \"css\"\n }\n\n\n\n - detect_platform: Run first to get correct platform value\n - create_custom_palette: Only when exact per-shade values are mandated by a brand spec\n - create_theme: Use instead if you want palette + typography + elevations together\n\n\n\n Call read_resource to load reference data:\n - \"theming://presets/palettes\" — preset palette colors\n - \"theming://guidance/colors\" — color guidance overview\n - \"theming://guidance/colors/rules\" — light/dark theme color rules\n";
readonly create_custom_palette: "Generate a custom color palette with fine-grained control over individual shade values.\n\n⚠️ CRITICAL RULES - READ BEFORE GENERATING SHADES:\n1. MONOCHROMATIC: Each color (primary, secondary, etc.) must use ONE HUE only.\n All 14 shades are lighter/darker versions of the SAME color.\n Example: primary blue → all shades must be blue (#E3F2FD light → #0D47A1 dark).\n WRONG: mixing blue, green, purple in one color's shades.\n2. NEVER INVERT: Chromatic colors always go 50=lightest → 900=darkest.\n This applies to BOTH light and dark themes. Only gray inverts for dark themes.\n\n\n PREFER create_palette. It derives every shade from a seed by solving for a contrast\n target, so it handles any brand color - light, dark, muted or neon - on its own.\n 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.\n\n Reach for this tool only when:\n - A brand spec mandates exact values for specific shades, and those values must be\n reproduced rather than generated\n - An accessibility audit requires exact contrast color values (rare - the generated\n adaptive-contrast() is normally what you want)\n\n Mixing is supported and is the usual shape: pin the one group the brand specifies and\n leave every other group in \"shades\" mode.\n\n\n\n - \"sass\" (default): Generates Sass code with palette map structure. Requires Sass compilation.\n - \"css\": Generates CSS custom properties (variables) directly. Ready to use in any CSS file.\n\n Use \"css\" output when:\n - Working with vanilla CSS projects without Sass\n - You want immediately usable CSS variables\n - Building prototypes or quick demos\n - Using CSS-in-JS or other non-Sass styling approaches\n\n\n\n 1. For each color group, choose a mode:\n - mode:\"shades\" → Auto-generate from baseColor (the default choice)\n - mode:\"explicit\" → Reproduce mandated values shade by shade\n 2. Validates explicit shades for completeness, color format, lightness order and hue\n consistency\n 3. Generates Sass code with color() map structure\n 4. Returns any validation warnings\n\n\n\n CHROMATIC COLORS (primary, secondary, info, success, warn, error):\n - \"shades\" mode needs only a baseColor - prefer it\n - \"explicit\" mode requires 14 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, A100, A200, A400, A700\n - 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.\n - Chromatic shades are NEVER inverted: 50 is lightest and 900 darkest in BOTH light\n and dark themes\n\n GRAY (the only family that inverts):\n - \"explicit\" mode requires 10 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900\n - LIGHT themes: 50 = lightest, 900 = darkest. DARK themes: inverted\n - Gray inverts because text and UI elements contrast against the surface\n\n SURFACE (not a ramp):\n - A background plus the layers on it, keyed by 6 layers required: base, sunken, raised, overlay, container, seed\n - \"base\" is the page; \"sunken\"/\"raised\"/\"overlay\" step away from it; \"container\" is a\n translucent tint; \"seed\" is the input color\n - There is no hue ramp to keep monochromatic. Palettes still emit numeric surface shades\n for compatibility, but they are deprecated: read and override the roles\n\n CONTRAST COLORS - OMIT contrastOverrides entirely. Each shade automatically gets\n '-contrast': adaptive-contrast(), which picks black or white for\n readability. Only supply overrides for an audit demanding exact values.\n\n SASS FILE PLACEMENT:\n - When combining Sass output from multiple tools into one file, all @use rules\n must appear at the top before any other statements. Deduplicate @use lines\n that share the same module path.\n\n\n\n\n\n Validation FAILS (returns error, no code generated) if:\n - Missing required shades in explicit mode\n - Invalid CSS color format in any shade\n\n Validation WARNS (generates code with warnings) if:\n - Luminance progression incorrect (50 darker than 900)\n - Hue inconsistency detected (shades not monochromatic)\n - Gray progression doesn't match variant (light vs dark)\n\n\n\n The usual case - every group from a seed:\n {\n \"variant\": \"light\",\n \"primary\": { \"mode\": \"shades\", \"baseColor\": \"#4CAF50\" },\n \"secondary\": { \"mode\": \"shades\", \"baseColor\": \"#FF9800\" },\n \"surface\": { \"mode\": \"shades\", \"baseColor\": \"#FAFAFA\" }\n }\n\n A brand spec pins primary; everything else is still generated:\n {\n \"variant\": \"light\",\n \"primary\": {\n \"mode\": \"explicit\",\n \"shades\": {\n \"50\": \"#E8F5E9\", \"100\": \"#C8E6C9\", \"200\": \"#A5D6A7\", \"300\": \"#81C784\",\n \"400\": \"#66BB6A\", \"500\": \"#4CAF50\", \"600\": \"#43A047\", \"700\": \"#388E3C\",\n \"800\": \"#2E7D32\", \"900\": \"#1B5E20\",\n \"A100\": \"#B9F6CA\", \"A200\": \"#69F0AE\", \"A400\": \"#00E676\", \"A700\": \"#00C853\"\n }\n },\n \"secondary\": { \"mode\": \"shades\", \"baseColor\": \"#FF9800\" },\n \"surface\": { \"mode\": \"shades\", \"baseColor\": \"#FAFAFA\" }\n }\n\n Note: no contrastOverrides in either input. The generated Sass adds\n '500-contrast': adaptive-contrast(#4CAF50) for every shade automatically.\n\n\n\n - detect_platform: Run first to get correct platform value\n - create_palette: Prefer this - it handles any seed color without hand-written shades\n - create_theme: Does not support custom palettes; use this tool + manual theme assembly\n\n\n\n ❌ WRONG - DO NOT create shades like this (different hues = broken palette):\n {\n \"primary\": {\n \"mode\": \"explicit\",\n \"shades\": {\n \"50\": \"#E3F2FD\", // blue\n \"100\": \"#DCEDC8\", // green ← WRONG HUE\n \"200\": \"#FFF9C4\", // yellow ← WRONG HUE\n \"500\": \"#9C27B0\", // purple ← WRONG HUE\n \"900\": \"#BF360C\" // red-brown ← WRONG HUE\n }\n }\n }\n This creates a rainbow, not a shade palette. Components will look broken.\n\n\n\n Call read_resource to load reference data:\n - \"theming://presets/palettes\" — preset palette colors for reference\n - \"theming://guidance/colors/usage\" — which shades to use for different purposes\n - \"theming://guidance/colors/roles\" — semantic meaning of each color family\n";
readonly fit_color_scale: "Derive a shade scale from an existing color ladder.\n\n\n Use when shades must follow the rhythm of a ladder you already have - another design\n system's grays, a brand ramp, a palette from a screenshot. Pass the returned spec to\n create_palette or create_theme as `scales`. Never hand-write range/curve values.\n\n Not needed for the built-in presets (\"even\" | \"material\" | \"tailwind\" | \"carbon\") -\n name those in `scales` directly.\n\n\n\n - Order the colors LIGHTEST FIRST (a 50-900 ladder already is). 3 minimum, 10 fits best.\n - The response reports how closely the fit reproduces the ladder; a ladder that does not\n follow one smooth curve fits loosely and says so.\n - A scale sets rhythm only, never hue - the seed still decides the color.\n - Set `family` to the palette family the ladder is for; it keys the returned scales map.\n `name` is only a label.\n - Background: read_resource \"theming://guidance/colors/scales\"\n\n\n\n { \"colors\": [\"#f8fafc\",\"#f1f5f9\",\"#e2e8f0\",\"#cbd5e1\",\"#94a3b8\",\n \"#64748b\",\"#475569\",\"#334155\",\"#1e293b\",\"#0f172a\"], \"family\": \"gray\", \"name\": \"Tailwind slate\" }\n";
readonly create_typography: "Set up typography for Ignite UI themes with custom font families and type scales.\n\n\n Use this tool to configure fonts that match your brand identity while maintaining\n consistent sizing, line heights, and letter spacing based on design system conventions.\n\n\n\n 1. Takes font family string and optional design system preset\n 2. Generates Sass code using the typography() mixin\n 3. Applies the type scale from the selected design system\n 4. Optionally applies custom scale overrides\n\n\n\n - Font family string should include fallbacks for cross-platform compatibility\n - Quote font names that contain spaces: '\"Segoe UI\"' not 'Segoe UI'\n - Design system affects: font sizes, line heights, letter spacing, font weights\n - Type styles include: h1-h6, subtitle-1/2, body-1/2, button, caption, overline\n\n SASS FILE PLACEMENT:\n - When combining Sass output from multiple tools into one file, all @use rules\n must appear at the top before any other statements. Deduplicate @use lines\n that share the same module path.\n\n\n\n\n\n - Empty font family: Returns error requesting valid font family string\n\n\n\n Modern sans-serif typography for Material Design:\n {\n \"fontFamily\": \"'Inter', 'Segoe UI', 'Helvetica Neue', sans-serif\",\n \"designSystem\": \"material\"\n }\n\n\n\n - detect_platform: Run first to get correct platform value\n - create_theme: Use instead if you want typography + palette + elevations together\n\n\n\n Call read_resource to load reference data:\n - \"theming://presets/typography\" — typography presets for all design systems\n";
readonly create_elevations: "Set up elevation shadows for Ignite UI themes.\n\n\n Use this tool to configure box-shadow values that provide visual depth and hierarchy.\n Elevations follow Material Design or Indigo design specifications.\n\n\n\n 1. Selects elevation preset based on design system parameter\n 2. Generates Sass code using the elevations() mixin\n 3. Creates 24 elevation levels (0-24) with corresponding shadow values\n\n\n\n - \"material\" preset: Material Design 3 shadow specifications\n - \"indigo\" preset: Infragistics Indigo shadow specifications\n - Elevation 0 = no shadow, elevation 24 = maximum shadow depth\n - Components use elevation() function to apply specific levels\n\n SASS FILE PLACEMENT:\n - When combining Sass output from multiple tools into one file, all @use rules\n must appear at the top before any other statements. Deduplicate @use lines\n that share the same module path.\n\n\n\n\n\n - detect_platform: Run first to get correct platform value\n - create_theme: Use instead if you want elevations + palette + typography together\n\n\n\n Call read_resource to load reference data:\n - \"theming://presets/elevations\" — elevation presets for Material and Indigo\n";
readonly create_theme: "Generate a complete, production-ready Ignite UI theme with palette, typography, and elevations.\n\n\n Use this tool as the starting point for new projects. It generates everything needed\n for a working theme in a single operation: color palette, typography setup, elevation\n shadows, and the theme application mixin.\n\n\n\n 1. Creates color palette using palette() function\n 2. Sets up typography with specified font family (if includeTypography: true)\n 3. Configures elevations based on design system (if includeElevations: true)\n 4. Configures spacing utilities for Web Components, React, and Blazor (if includeSpacing: true)\n 5. Applies the theme using the theme() mixin\n\n For Web Components, React, and Blazor the output always includes sizing(), the progress\n @property rules, the scrollbar variables and .ig-scrollbar class, RTL support, and the tile\n manager view transitions.\n\n\n\n REQUIRED COLORS:\n - primaryColor: Main brand color\n - secondaryColor: Accent/highlight color\n - surfaceColor: Background color (should match variant)\n\n SHADE PROGRESSION (important):\n - Primary and secondary colors are NEVER inverted between light/dark themes.\n - The palette() function generates shades 50=lightest to 900=darkest for ALL\n chromatic colors regardless of theme variant.\n - Only gray shades behave differently (for text contrast against surface).\n - DO NOT provide inverted primary/secondary colors for dark themes.\n\n SEED COLORS:\n - 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.\n\n PLATFORM DIFFERENCES:\n - Angular: Uses igniteui-angular/theming with core() and theme() mixins\n - Web Components: Uses igniteui-theming directly with palette(), typography(), elevations() mixins\n - React: Uses igniteui-theming directly (same as Web Components), common with Vite/Next.js\n - Blazor: Uses igniteui-theming for Sass compilation, theme CSS referenced in Blazor components\n\n SASS FILE PLACEMENT:\n - When combining Sass output from multiple tools into one file, all @use rules\n must appear at the top before any other statements. Deduplicate @use lines\n that share the same module path.\n\n\n\n\n\n - Invalid color format: Returns error with format examples\n - Variant mismatch: Warns if surface color doesn't match theme variant\n\n\n\n Complete Material Design blue theme:\n {\n \"platform\": \"angular\",\n \"designSystem\": \"material\",\n \"primaryColor\": \"#1976D2\",\n \"secondaryColor\": \"#FF9800\",\n \"surfaceColor\": \"#FAFAFA\",\n \"variant\": \"light\",\n \"fontFamily\": \"'Roboto', sans-serif\",\n \"includeTypography\": true,\n \"includeElevations\": true\n }\n\n\n\n After generating a theme:\n 1. Import the generated Sass file in your application's main styles\n 2. Customize individual component themes as needed using component schema overrides\n\n\n\n - detect_platform: Run first to auto-detect platform from package.json\n - create_custom_palette: Only when exact per-shade values are mandated by a brand spec\n - create_palette: Use if you only need a palette without full theme\n - create_typography: Use if you only need typography setup\n - create_elevations: Use if you only need elevation shadows\n\n\n \n Call read_resource to load reference data:\n - \"theming://presets/palettes\" — preset palette colors\n - \"theming://guidance/colors\" — color guidance overview\n - \"theming://guidance/colors/rules\" — light/dark theme color rules\n - \"theming://platforms/angular\" — Angular platform configuration\n - \"theming://platforms/webcomponents\" — Web Components platform configuration\n - \"theming://platforms/react\" — React platform configuration\n - \"theming://platforms/blazor\" — Blazor platform configuration\n ";
readonly set_size: "Set global or component-specific sizing by updating --ig-size.\n\n\n Use this tool for requests like:\n - \"Make the calendar smaller\"\n - \"The buttons feel too big\"\n - \"Use the small size everywhere\"\n\n\n\n - Sets --ig-size in the chosen scope (defaults to :root)\n - Accepts \"small\", \"medium\", \"large\" (mapped to 1, 2, 3) or numeric values\n - 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.\n\n\n\n - Components map --ig-size to --component-size internally\n - Styles using sizable() require @include sizable() in component styles\n\n\n\n Make flat buttons medium:\n {\n \"component\": \"flat-button\",\n \"size\": \"medium\"\n }\n\n Make everything small globally:\n {\n \"size\": \"small\"\n }\n\n\n\n Call read_resource to load reference data:\n - \"theming://docs/spacing-and-sizing\" — spacing and sizing overview\n - \"theming://docs/functions/sizable\" — sizable value function\n - \"theming://docs/mixins/sizable\" — sizable mixin\n";
readonly set_spacing: "Set global or component-specific spacing by updating --ig-spacing.\n\n\n Use this tool for requests like:\n - \"The button feels bloated\"\n - \"Tighten the spacing on the form\"\n - \"Double the padding on cards\"\n\n\n\n - Sets --ig-spacing in the chosen scope (defaults to :root)\n - Optional overrides for --ig-spacing-inline and --ig-spacing-block\n - 0 = no spacing, 1 = default, 2 = double (fractions allowed)\n - spacing is required; inline/block are optional overrides\n - 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.\n\n\n\n - pad(), pad-inline(), pad-block() require @include spacing() once\n\n\n\n Reduce calendar spacing:\n {\n \"component\": \"calendar\",\n \"spacing\": 0.75\n }\n\n Override inline spacing:\n {\n \"scope\": \".compact\",\n \"inline\": 0.5,\n \"block\": 0.75\n }\n\n\n\n Call read_resource to load reference data:\n - \"theming://docs/spacing-and-sizing\" — spacing and sizing overview\n - \"theming://docs/functions/pad\" — pad spacing function\n - \"theming://docs/mixins/spacing\" — spacing mixin\n";
readonly set_roundness: "Set global or component-specific roundness by updating --ig-radius-factor.\n\n\n Use this tool for requests like:\n - \"Make the flat buttons more round\"\n - \"Square off the cards\"\n\n\n\n - Sets --ig-radius-factor in the chosen scope (defaults to :root)\n - 0 = minimum radius, 1 = maximum radius, values between interpolate\n - 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.\n\n\n\n - border-radius() responds to --ig-radius-factor without extra mixins\n\n\n\n Round avatars more:\n {\n \"component\": \"avatar\",\n \"radiusFactor\": 0.9\n }\n\n Globally reduce roundness:\n {\n \"radiusFactor\": 0.8\n }\n\n\n\n Call read_resource to load reference data:\n - \"theming://docs/spacing-and-sizing\" — spacing and sizing overview\n - \"theming://docs/functions/border-radius\" — border radius function\n";
readonly get_component_design_tokens: "Discover available design tokens (themeable properties) for an Ignite UI component.\n\n\n ALWAYS call this tool FIRST before using create_component_theme. It returns the\n exact token names that can be customized for a component, preventing hallucination\n of invalid property names.\n\n NOTE: This tool returns tokens for Ignite UI framework components. It is NOT useful\n when the detected platform is \"generic\" — component theming requires a specific\n Ignite UI product (angular, webcomponents, react, or blazor).\n\n\n\n 1. Provide the component name (e.g., \"button\", \"avatar\", \"grid\")\n 2. Receive list of all available tokens with their types and descriptions\n 3. Use the token names in create_component_theme\n\n\n\n COMPONENT NAMING:\n - Basic components: Use simple names like \"avatar\", \"badge\", \"card\"\n - Button variants: Use specific variant names like \"flat-button\", \"contained-button\",\n \"outlined-button\", \"fab-button\" (NOT just \"button\")\n - Icon button variants: \"flat-icon-button\", \"contained-icon-button\", \"outlined-icon-button\"\n - Child sub-components: Use names like \"list-item\", \"card-header\", \"accordion-header\",\n \"tab-item\", \"step\", \"expansion-panel-header\". These resolve to the parent component's\n theme automatically.\n\n CHILD SUB-COMPONENTS:\n - Some component parts (e.g., \"list-item\", \"card-header\", \"accordion-header\") don't have\n their own theme function — they are styled through the parent component's theme tokens.\n - When you query a child sub-component, the response includes a note explaining the\n parent-child relationship and shows the parent theme's full token list.\n - The token descriptions guide you to the relevant tokens (e.g., \"item-background\"\n for list items, \"header-text-color\" for card headers).\n - When you then call create_component_theme with a child name, it automatically\n uses the parent's theme function, variable name, and selector — producing output\n that is merge-compatible with the parent component's theme.\n\n COMPOUND COMPONENTS:\n There are two types of compound components:\n\n **Standard compounds** (e.g., \"combo\", \"select\", \"date-picker\"):\n - Use multiple internal components that each need their own theme\n - The response lists related themes and, where available, token derivation hints\n showing how child token values relate to parent/sibling tokens\n (e.g., \"foreground → adaptive-contrast of calendar.content-background\")\n - Follow derivation hints when setting child token values. If the user specifies an\n explicit value, use that instead of the derived value.\n - All related themes should be scoped under the parent component's selector\n - For each related theme: call get_component_design_tokens, then create_component_theme\n using the parent component's selector for the target platform\n\n **Composed compounds** (e.g., \"grid components\"):\n - The framework automatically generates internal themes for all child components from just the primary tokens\n - Do NOT create separate themes for the related components — they are auto-derived\n in the component's Sass styles\n - The response uses a **two-tier token hierarchy**:\n - **✅ Primary Tokens — USE THESE**: Use ONLY these tokens for the initial theme\n - **📖 Refinement Tokens — REFERENCE ONLY**: Auto-derived tokens available ONLY when\n the user explicitly requests fine-grained control (e.g., \"change the header background\")\n - Only set the primary tokens in the parent component's theme; all children inherit automatically\n - The response clearly marks these as \"Composed Compound Component\" and lists the\n internally themed children for reference (not for separate theming)\n\n VARIANTS INFO:\n - If you query a base component that has variants (e.g., \"button\"), the response\n lists available variants to help you choose the right one\n\n\n\n\n\n - Unknown component: Returns list of similar component names as suggestions\n - Partial match: If query partially matches multiple components, returns all matches\n\n\n\n Get tokens for flat button:\n {\n \"component\": \"flat-button\"\n }\n\n Returns tokens like: background, foreground, hover-background, border-radius, etc.\n\n Get tokens for a child sub-component:\n {\n \"component\": \"list-item\"\n }\n\n Returns the list theme's tokens with a note: \"list-item is a child of the list component.\n Its styling is controlled through the list theme.\"\n\n\n\n - create_component_theme: Use the discovered tokens to create a custom theme\n";
readonly create_component_theme: "Generate Sass or CSS code to customize an Ignite UI component's appearance using design tokens.\n\n\n Use this tool AFTER calling get_component_design_tokens to customize specific\n component styles. The generated code can be included in your theme file to\n override default component appearances.\n\n\n\n 1. First call get_component_design_tokens to discover available tokens\n 2. Choose which tokens to customize based on your design requirements\n 3. Specify designSystem and variant to match the global theme or the one explicitly requested (defaults to Material light)\n 4. Call this tool with component name, token values, and output format (\"sass\" or \"css\")\n 5. Receive ready-to-use Sass or CSS code with the component theme\n\n\n\n DESIGN SYSTEM & VARIANT:\n - designSystem: Choose \"material\" (default), \"bootstrap\", \"fluent\", or \"indigo\"\n - variant: Choose \"light\" (default) or \"dark\"\n - The correct schema (e.g., $light-bootstrap-schema, $dark-material-schema) is\n automatically selected and passed to the component theme function\n - The correct output: Choose output format based on the target file type (Sass vs CSS)\n - This ensures component tokens inherit proper defaults from the design system\n\n LIGHT & DARK:\n - Each call produces one variant. If the app supports light and dark, call this tool\n for each variant — do not ship only the light one.\n - The dark call usually needs different token values than the light one (e.g. colors\n that work on a dark surface). Do not repeat the light tokens unchanged.\n - Scope the dark call under the app's dark-mode selector so it doesn't override the\n light theme (e.g. \".your-dark-scope igc-avatar\").\n - Put that dark-mode selector on a root element (`html`, `body`, or the app's theme\n root), not on an app container. On Angular, overlay-hosted components\n (`.igx-dialog`, `.igx-drop-down__list`, `.igx-tooltip`, `.igx-overlay__content`)\n are moved to the overlay outlet under `body`, so a scope on an app container\n won't match them.\n - The response includes a note with the scoped selector for the other variant.\n\n TOKEN VALIDATION:\n - All provided token names are validated against the component's schema\n - Invalid tokens return an error with the list of valid token names\n - You don't need to specify all tokens - only those you want to customize (prefer PRIMARY tokens to minimize the number of overrides)\n\n TOKEN VALUE FORMATS:\n - Colors: Any valid CSS color format (hex, rgb, hsl, named colors)\n - Dimensions: Include units (e.g., \"8px\", \"0.5rem\", \"2em\")\n - Border radius: Can be single value or shorthand (\"8px\" or \"8px 8px 0 0\")\n - Shadows: Full box-shadow syntax (\"0 2px 4px rgba(0,0,0,0.1)\")\n\n SELECTORS:\n - Default selector is auto-detected based on platform and component\n - For child sub-components (e.g., \"list-item\", \"card-header\"), the selector\n automatically resolves to the parent component's selector (e.g., \"igx-list\", \"igx-card\")\n - Angular: Uses \"igx-*\" element selectors or attribute selectors\n - Web Components: Uses \"igc-*\" element selectors\n - Custom selectors supported for targeted styling (e.g., \".my-button\")\n\n CHILD SUB-COMPONENTS:\n - When creating a theme for a child sub-component (e.g., \"card-actions\"), the output\n uses the parent's theme function, variable name, and selector.\n - This means the output for \"card\" and \"card-actions\" is merge-compatible:\n both produce `$custom-card-theme: card-theme(...)` scoped to `igx-card`.\n - To add tokens for multiple sub-parts, merge the token arguments into a single\n theme function call rather than creating separate themes.\n\n SASS OUTPUT:\n - Generated code uses `@include tokens($theme)` to apply the theme\n - The tokens mixin emits --ig-{component}-{token} CSS custom properties in global mode\n\n COMPOUND COMPLETENESS:\n - **Standard compounds:** If the user asks for a standard compound component,\n the response is incomplete unless related theme calls are also generated.\n Use the related themes list from get_component_design_tokens to drive the sequence.\n All related themes should use the compound component's selector as the wrapper.\n Follow token derivation hints to set child token values consistently.\n - **Composed compounds:** If the component is a composed compound (e.g., grid),\n do NOT generate separate child themes. Only set the primary tokens (background,\n foreground, accent-color) on the parent component's theme — child themes are\n auto-derived internally by the component's Sass styles.\n Refinement tokens (e.g., header-background) can be added in follow-up calls\n when the user explicitly asks to customize a specific aspect.\n\n SASS FILE PLACEMENT:\n - When combining Sass output from multiple tools into one file, all @use rules\n must appear at the top before any other statements. Deduplicate @use lines\n that share the same module path.\n\n\n\n\n\n - Unknown component: Returns error with list of available components\n - Invalid tokens: Returns error listing invalid tokens and valid alternatives\n - Invalid color format: Returns error with format guidance\n\n\n\n Custom blue flat button with rounded corners (Angular, Material Design):\n {\n \"platform\": \"angular\",\n \"designSystem\": \"material\",\n \"variant\": \"light\",\n \"component\": \"flat-button\",\n \"tokens\": {\n \"foreground\": \"#1976d2\",\n }\n }\n\n Generates:\n ```scss\n @use 'igniteui-angular/theming' as *;\n\n $custom-flat-button-theme: flat-button-theme(\n $schema: $light-material-schema,\n $foreground: #1976d2,\n );\n\n .igx-button--flat {\n @include tokens($custom-flat-button-theme);\n }\n ```\n\n Bootstrap dark theme example:\n {\n \"platform\": \"webcomponents\",\n \"designSystem\": \"bootstrap\",\n \"variant\": \"dark\",\n \"component\": \"avatar\",\n \"tokens\": {\n \"background\": \"#ff5722\"\n }\n }\n\n Generates:\n ```scss\n @use 'igniteui-theming' as *;\n\n $custom-avatar-theme: avatar-theme(\n $schema: $dark-bootstrap-schema,\n $background: #ff5722\n );\n\n igc-avatar {\n @include tokens($custom-avatar-theme);\n }\n ```\n\n\n\n Date Picker (compound) — all child themes use the parent component's selector.\n Follow token derivation hints from get_component_design_tokens:\n 1) get_component_design_tokens { \"component\": \"date-picker\" }\n 2) create_component_theme { \"component\": \"date-picker\", \"platform\": \"angular\", ... }\n 3) create_component_theme { \"component\": \"calendar\", \"selector\": \"igx-date-picker\", ... }\n 4) create_component_theme { \"component\": \"flat-button\", \"selector\": \"igx-date-picker\", ... }\n 5) create_component_theme { \"component\": \"input-group\", \"selector\": \"igx-date-picker\", ... }\n\n Each child theme uses the parent's platform selector (e.g., `igx-date-picker` for Angular,\n `igc-date-picker` for Web Components / React / Blazor).\n The tokens mixin emits --ig-{component}-{token} variables that child components\n consume via var() fallback — no per-child selectors needed.\n\n\n\n - detect_platform: Run to auto-detect platform for correct imports\n - get_component_design_tokens: MUST call first to discover valid tokens\n - create_theme: Use for full theme (palette + typography + elevations)\n";
readonly get_color: "Retrieve a palette color from Ignite UI Theming as a CSS variable reference.\n\n\n Use this tool when you need to reference a specific palette color in CSS or Sass code.\n Returns CSS variable references that work in both Sass and CSS contexts.\n\n Common scenarios:\n - Setting component backgrounds/foregrounds using theme colors\n - Creating hover/focus states with opacity variations\n - Ensuring text contrast against colored backgrounds\n\n\n\n 1. Specify the color family (primary, secondary, gray, etc.)\n 2. Optionally specify a shade variant (50-900, A100-A700)\n 3. Optionally request the contrast color for text readability\n 4. Optionally apply opacity for transparency effects\n\n\n\n Basic color:\n { color: \"primary\" }\n → var(--ig-primary-500)\n\n Specific shade:\n { color: \"primary\", variant: \"600\" }\n → var(--ig-primary-600)\n\n Contrast color:\n { color: \"primary\", variant: \"600\", contrast: true }\n → var(--ig-primary-600-contrast)\n\n With opacity:\n { color: \"primary\", opacity: 0.5 }\n → hsl(from var(--ig-primary-500) h s l / 0.5)\n\n Contrast with opacity:\n { color: \"primary\", contrast: true, opacity: 0.7 }\n → hsl(from var(--ig-primary-500-contrast) h s l / 0.7)\n\n\n\n CSS VARIABLE NAMING:\n - Base colors: --ig-{color}-{variant} (e.g., --ig-primary-500)\n - Contrast: --ig-{color}-{variant}-contrast (e.g., --ig-primary-500-contrast)\n\n GRAY RESTRICTIONS:\n - Gray only supports standard shades (50-900), not accent shades (A100-A700)\n\n OPACITY HANDLING:\n - Uses CSS relative color syntax: hsl(from h s l / )\n - Works in modern browsers (CSS Color Level 4)\n - For Sass projects, this syntax is passed through unchanged\n\n\n\n - create_palette: Generate a complete palette with these colors\n - create_component_theme: Use retrieved colors in component theming\n";
readonly get_chart_series_colors: "Retrieve the shared Ignite UI chart series brush palette, per-chart-type color-token guidance, and validate custom brush lists.\n\n\n Use this tool when theming Ignite UI charts (category, data, doughnut, pie, funnel, shape,\n financial, linear/radial gauge, bullet graph) and you need the default series colors, want to\n know which theme tokens accept a custom color list for a given chart type, or want to sanity-check\n a custom brush list before using it in a $brushes: (...) override.\n\n NOT covered by this tool: sparkline (singular tokens, not a palette list) and\n selection/highlight colors (selectionBrush, focusBrush — component-only, no Sass theme equivalent).\n\n\n\n 1. Call with no arguments to get the full 10-color default (regular) palette.\n 2. Optionally set mode: \"color-blind\" for the accessibility-friendly variant.\n 3. Optionally set index (1-10) to retrieve a single brush color.\n 4. Optionally set chartType (e.g. \"category-chart\", \"financial-chart\", \"linear-gauge\") to see\n which theme tokens on that chart type accept the palette, plus a ready-to-use Sass snippet.\n 5. Optionally set customBrushes to a color array to validate it before using it in an override —\n checks each color is valid and flags color pairs with similar hues that may be hard to tell apart.\n\n\n\n Default palette:\n {}\n → 10-color list + var(--chart-brushes) reference\n\n Single brush:\n { index: 3 }\n → the 3rd regular-palette color\n\n Chart-type guidance:\n { chartType: \"category-chart\" }\n → token table (brushes, marker-brushes, outlines, marker-outlines, trend-line-brushes,\n negative-brushes, negative-outlines) + a category-chart-theme() Sass snippet\n\n Custom brush validation:\n { customBrushes: [\"#4285f4\", \"#ea4335\", \"#fbbc05\", \"#34a853\"] }\n → validity + hue-distinctness warnings\n\n\n\n THEME VS. COMPONENT PRECEDENCE:\n - This tool and the Sass snippets it generates set the THEME DEFAULT only.\n - Chart components also expose their own color-list properties (e.g. Angular's brushes,\n outlines, markerBrushes, markerOutlines, rangeBrushes, rangeOutlines) that OVERRIDE the\n theme default per instance. Always mention this precedence when generating chart theme code.\n\n SCOPE:\n - Only list-valued brush/outline tokens are covered. Sparkline and selection/highlight colors\n are intentionally excluded — see the guidance resource at theming://guidance/colors/charts.\n - Some chart types default certain tokens to a FIXED color rather than the shared palette\n (e.g. category-chart's negative-brushes/negative-outlines default to red, not \"series\") —\n check the \"default\" column in the chartType response rather than assuming uniformity.\n\n\n\n - create_component_theme: Not yet wired for chart components (see project notes) — use the\n Sass snippet from this tool directly instead.\n - theming://guidance/colors/charts: Full guidance resource with the complete per-chart-type\n token reference and override examples.\n";
readonly 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.\n\n\n Use this tool to load reference data before or during theme generation. Other tools\n reference these resources in their related_resources sections — call this tool with\n the listed URI to retrieve the data.\n\n Common scenarios:\n - Load palette presets to see available colors before creating a palette\n - Read color guidance to understand shade usage and semantic roles\n - Check platform configuration for usage examples and supported features\n - Read layout documentation for spacing, sizing, and roundness details\n\n\n\n 1. Identify the resource URI from the available_resources list or from a related_resources hint in another tool\n 2. Call this tool with the URI\n 3. Use the returned data to inform your next action\n\n\n\n\n\n If the URI is not found, returns the list of all available resource URIs.\n";
};
/**
* Individual parameter descriptions for schema fields.
* Include valid values, defaults, formats, and constraints.
*/
export declare const PARAM_DESCRIPTIONS: {
readonly platform: "Target platform: \"angular\" for Ignite UI for Angular, \"webcomponents\" for Ignite UI for Web Components, \"react\" for Ignite UI for React, \"blazor\" for Ignite UI for Blazor, or \"generic\" for platform-agnostic output (standalone igniteui-theming usage). If omitted, generates generic code. Use detect_platform tool first to auto-detect from project files.";
readonly licensed: "Use licensed @infragistics package (Angular only). Set to true if using @infragistics/igniteui-angular from private ProGet registry. Defaults to false (uses open-source igniteui-angular from npm). Note: igniteui-theming is always free/OSS for all other platforms.";
readonly variant: "Theme variant: \"light\" (light backgrounds, dark text) or \"dark\" (dark backgrounds, light text). Defaults to \"light\".";
readonly designSystem: "Design system preset: \"material\" (Material Design), \"bootstrap\" (Bootstrap), \"fluent\" (Microsoft Fluent), or \"indigo\" (Infragistics Indigo). Defaults to \"material\".";
readonly name: "Custom variable name (without $ prefix). If omitted, auto-generates based on tool and variant (e.g., \"custom-light\", \"my-theme\").";
readonly output: "Output format for the generated code.\n\n\"sass\" — Returns Sass source using igniteui-theming functions and mixins. Requires a Sass pipeline in the consuming project. Prefer for Angular (Angular CLI handles Sass compilation automatically).\n\n\"css\" — The MCP server compiles the Sass internally and returns ready-to-use CSS custom properties. No local Sass toolchain needed. Prefer for Web Components, React, and Blazor unless the project has a confirmed Sass setup (e.g. .scss files and a sass build step are present). When in doubt, use \"css\" or ask the user.\n\nLayout tools (set_size, set_spacing, set_roundness) default to \"css\". Generation tools (create_palette, create_theme, etc.) default to \"sass\" for Angular and \"css\" for all other platforms.";
readonly packageJsonPath: "Path to package.json file, relative to current working directory. Defaults to \"./package.json\".";
readonly primary: "Primary brand color - used for main actions, active states, and emphasis. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly secondary: "Secondary/accent color - used for FABs, selection controls, highlights. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly surface: "Surface/background color - should be light for \"light\" variant, dark for \"dark\" variant. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly gray: "Gray/neutral base color for text, borders, disabled states. Optional - defaults from design system preset. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly info: "Info state color (typically blue) for informational messages. Optional - defaults from design system. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly success: "Success state color (typically green) for success messages and positive actions. Optional - defaults from design system. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly warn: "Warning state color (typically orange/amber) for warning messages. Optional - defaults from design system. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly error: "Error state color (typically red) for error messages and destructive actions. Optional - defaults from design system. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly fontFamily: "Font family string with fallbacks. Quote names with spaces. Example: '\"Inter\", \"Helvetica Neue\", sans-serif'";
readonly customScale: "Custom type scale overrides. Object with type style names as keys (h1, h2, body-1, button, etc.) and style objects as values containing fontSize, fontWeight, lineHeight, letterSpacing, textTransform.";
readonly elevationPreset: "Elevation shadow preset: \"material\" (Material Design shadows) or \"indigo\" (Infragistics Indigo shadows). Defaults to \"material\".";
readonly primaryColor: "Primary brand color for the theme - used for main actions and emphasis. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly secondaryColor: "Secondary/accent color for the theme - used for highlights and selection. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly surfaceColor: "Surface/background color for the theme. Use light colors (#FAFAFA) for \"light\" variant, dark colors (#121212) for \"dark\" variant. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly includeTypography: "Include typography setup in the generated theme. Set to false if you want to configure typography separately. Defaults to true.";
readonly includeElevations: "Include elevation shadows in the generated theme. Set to false if you want to configure elevations separately. Defaults to true.";
readonly includeSpacing: "Include spacing CSS custom properties. Applies to Web Components, React, and Blazor. Has no effect on Angular. Defaults to true.";
readonly colorDefinition: "Color definition object with mode selection:\n• mode: \"shades\" + baseColor: Auto-generates all shades from one color - prefer this\n• mode: \"explicit\" + shades: Manually specify all 14 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, A100, A200, A400, A700\nIn 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.";
readonly surfaceDefinition: "Surface definition object with mode selection:\n• mode: \"shades\" + baseColor: Auto-generates the background and its layers from one color\n• mode: \"explicit\" + shades: Manually specify all 6 layers required: base, sunken, raised, overlay, container, seed\nIMPORTANT: A surface is a background plus the layers that sit on it, so it is addressed by ROLE, not by shade number. \"base\" is the page background; \"sunken\", \"raised\" and \"overlay\" step away from it; \"container\" is a translucent tint. A role with no room in its direction resolves back onto \"base\".";
readonly grayDefinition: "Gray color definition object with mode selection:\n• mode: \"shades\" + baseColor: Auto-generates all shades from one color\n• mode: \"explicit\" + shades: Manually specify all 10 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900\nImportant: Gray progression is INVERTED for dark themes (50=darkest, 900=lightest).";
readonly scales: "OPTIONAL - omit unless asked to match another system's rhythm. Preset name (\"even\" | \"material\" | \"tailwind\" | \"carbon\"), or a map keyed by family: {\"gray\": \"carbon\"}. To match a ladder you have seen, call fit_color_scale and pass back its spec - never hand-write a curve.";
readonly generator: "OPTIONAL - omit it. \"legacy\" reproduces the original multiplier-based ramps and exists only to keep an existing theme byte-identical while migrating.";
readonly ladderColors: "The ladder to fit, LIGHTEST FIRST (3-20 colors). Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly ladderFamily: "Palette family the scale applies to; it keys the returned scales map. Defaults to \"gray\". A surface takes no scale.";
readonly ladderName: "Optional label for the fitted scale, shown in the response and as a comment in the Sass. Does not change the scales map - use `family` for that.";
readonly baseColor: "Base color for automatic shade generation using shades() function. Pass the brand color as-is; its lightness does not need adjusting. Valid CSS color formats: hex (\"#3F51B5\", \"#3F51B5AA\"), rgb/rgba (\"rgb(63, 81, 181)\", \"rgb(63 81 181 / 0.5)\"), hsl/hsla (\"hsl(231, 48%, 48%)\", \"hsl(231 48% 48% / 0.5)\"), hwb (\"hwb(231 20% 30%)\"), lab/lch (\"lab(50% 40 59)\", \"lch(50% 80 30)\"), oklab/oklch (\"oklab(59% 0.1 0.1)\", \"oklch(60% 0.15 50)\"), color() for wide-gamut (\"color(display-p3 1 0.5 0)\"), or CSS named colors (\"indigo\", \"rebeccapurple\").";
readonly shades: "Object with all shade values. 14 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900, A100, A200, A400, A700. Luminance should decrease from 50 (lightest) to 900 (darkest). CRITICAL: All shades must be the SAME COLOR (same hue) at different lightness levels - do NOT use different colors for different shades.";
readonly surfaceRoles: "Object with all surface layer values. 6 layers required: base, sunken, raised, overlay, container, seed. \"base\" is the page background; \"sunken\" is darker, \"raised\" and \"overlay\" lighter (inverted for dark themes); \"container\" is a translucent black/white tint; \"seed\" is the original input color.";
readonly grayShades: "Object with all gray shade values. 10 shades required: 50, 100, 200, 300, 400, 500, 600, 700, 800, 900. For light themes: 50=lightest, 900=darkest. For dark themes: 50=darkest, 900=lightest.";
readonly contrastOverrides: "USUALLY OMIT THIS FIELD. Contrast colors are auto-generated using adaptive-contrast(). Only provide this if you have specific accessibility requirements with exact contrast values (rare). When omitted (recommended), the generated Sass code automatically includes adaptive-contrast(#shadeColor) for each shade, which auto-selects black or white for optimal readability.";
readonly component: "Component name to get design tokens for (e.g., \"button\", \"avatar\", \"grid\"). Use exact names like \"flat-button\" for button variants. Child sub-component names like \"list-item\", \"card-header\", \"accordion-header\", \"tab-item\", \"step\" are also supported — they resolve to the parent component's theme. Call this tool to discover available tokens BEFORE using create_component_theme.";
readonly componentTheme: "Component name to theme (e.g., \"button\", \"avatar\", \"flat-button\", \"grid\"). Must match a valid component from get_component_design_tokens. For button/icon-button variants, use specific names like \"flat-button\", \"contained-button\", \"outlined-button\", \"fab-button\". Child sub-component names (e.g., \"list-item\", \"card-header\") are supported and automatically resolve to the parent theme with the parent's selector and variable name.";
readonly tokens: "Object mapping token names to values. Token names must be valid for the component (use get_component_design_tokens to discover them). Values can be CSS colors, dimensions with units, or other Sass-compatible values. Example: { \"background\": \"#1976D2\", \"border-radius\": \"8px\" }";
readonly selector: "Optional CSS selector to scope the theme. If omitted, uses the platform's default selector for the component. For child sub-components (e.g., \"list-item\"), the default selector is the parent component's selector (e.g., \"igx-list\"). For Angular: \"igx-*\" selectors, for Web Components: \"igc-*\" selectors. You can specify custom selectors like \".my-custom-button\" for targeted styling.";
readonly themeName: "Optional name for the generated theme variable (without $ prefix). If omitted, auto-generates based on component name (e.g., \"$custom-button-theme\").";
readonly layoutComponent: "Optional component name to scope the layout change (e.g., \"flat-button\", \"calendar\", \"avatar\"). If omitted, the change applies globally via :root. Note: component targets Ignite UI framework selectors — do not use with platform \"generic\". Use \"scope\" instead for custom CSS selectors.";
readonly scope: "Optional CSS selector scope for the change (e.g., \".my-theme\", \":root\", \"#app\"). Ignored when component is provided.";
readonly sizeValue: "Size value to set for --ig-size. Accepts \"small\" (1), \"medium\" (2), \"large\" (3), or numeric 1, 2, 3 only.";
readonly spacing: "Spacing scale multiplier for --ig-spacing. 0 = none, 1 = default, 2 = double. Fractions allowed.";
readonly spacingInline: "Inline spacing scale multiplier for --ig-spacing-inline. Overrides inline spacing only.";
readonly spacingBlock: "Block spacing scale multiplier for --ig-spacing-block. Overrides block spacing only.";
readonly radiusFactor: "Roundness scale factor for --ig-radius-factor. 0 = minimum radius, 1 = maximum radius. Values must be between 0 and 1.";
readonly colorName: "Palette color family name: \"primary\" (brand color), \"secondary\" (accent), \"gray\" (neutrals), \"surface\" (backgrounds), \"info\" winformational), \"success\" (positive), \"warn\" (warnings), \"error\" (errors/destructive).";
readonly shadeVariant: "Color shade variant. Standard shades: 50 (lightest) through 900 (darkest). Accent shades: A100, A200, A400, A700 (more saturated). Default: \"500\" (base color). Note: Gray only supports standard shades (50-900).";
readonly contrastFlag: "If true, returns the contrast color for the specified shade instead of the shade itself. Contrast colors are pre-computed for optimal text readability. Default: false.";
readonly opacity: "Opacity value between 0 (fully transparent) and 1 (fully opaque). When provided, wraps the color in CSS relative color syntax: hsl(from var(...) h s l / opacity).";
readonly chartBrushMode: "Which series brush palette to use: \"regular\" (default, visually distinct colors) or \"color-blind\" (alternate palette for better distinguishability under common color vision deficiencies, activated via the configure-colors($enhanced-accessibility: true) Sass mixin). Default: \"regular\".";
readonly chartBrushIndex: "Optional 1-based index (1-10) to retrieve a single brush color from the palette instead of the full 10-color list.";
readonly chartType: "Optional chart type to get color-token guidance for (e.g., \"category-chart\", \"financial-chart\", \"linear-gauge\", \"bullet-graph\"). When provided, the response lists which theme tokens accept the series brush list for that chart type and a Sass usage snippet. Not all chart types are covered — sparkline and selection/highlight colors are out of scope (see the guidance resource for why).";
readonly customBrushes: "Optional array of CSS colors to validate as a custom series brush list before using them in a $brushes: (...) override. When provided, the tool checks each color is valid and flags any pair of colors that may be hard to visually distinguish (similar hue).";
readonly resourceUri: "URI of the theming resource to read (e.g., \"theming://presets/palettes\", \"theming://platforms/angular\"). See the available_resources list in the tool description for all valid URIs.";
};