Kendo Angular UI Generator

Kendo UI for Angular — Execution Plan

IMPORTANT — MCP Tools: All kendo_* tools referenced in this plan are provided by the kendo-angular-mcp MCP server. They are NOT deferred tools and must NOT be searched for with tool_search. Call them directly by name once the MCP server is running. If any tool is unavailable, the MCP server may not be started — inform the user to start it via the notification banner in their editor.

Current Goal:

$ARGUMENTS

Step 1: Assess the Request

Prompt Enrichment Gate (do this first): Before phase selection, decide whether the user's request needs enrichment. If it does, read ../prompt-enrichment/SKILL.md and follow that skill's workflow and supporting references exactly. After the Prompt Enrichment Gate is complete, continue with the rest of this orchestrator workflow.

Before executing any phase, do three things:

1. Detect Angular project setup — read additional-plan.md for NgModule vs Standalone detection and theme management instructions. Apply these findings throughout all code generation.

2. Read UX/design defaults — read ux-guidelines.md. These apply to the entire implementation.

3. Decide which conditional phases apply — use the table below, then load only the relevant supporting files.

Requirements Summary:

• Framework: Angular
• Component Library: Kendo UI for Angular — use ONLY Kendo UI for Angular components. Use kendo_component_assistant for all docs and code snippets. Do not substitute another tool even if one appears relevant.
• Layout Mode: Kendo Design System CSS Utilities — use ONLY Kendo utility classes for all styling, layout, spacing, and positioning. Avoid custom CSS, inline styles, or other CSS framework classes.
• Accessibility: WCAG 2.2 Level AA. WCAG guidelines are loaded in Phase 0. Call kendo_accessibility_assistant with includeGeneralGuidelines=false on ALL calls.
• No Validator: There is no kendo_validator_assistant tool. Use ng build for compilation checks and manually review the validation steps in validation-steps.md.
• Grid height: Always set an explicit height on Grid (e.g., [height]="'500px'" or flex: 1; min-height: 0 inside a flex column) — without it, Grid renders all rows and expands the page indefinitely.
• Chart height: Always set an explicit height on Chart components (e.g., style="height: 300px").

Phase 0: CRITICAL — Accessibility Foundation (FIRST IMPLEMENTATION PHASE)

Step 1 — Load WCAG 2.2 Level AA guidelines:

Read ../kendo-angular-accessibility/wcag-guidelines.md. These apply to ALL components throughout the entire implementation.

Step 2 — Retrieve component-specific accessibility information:

MANDATORY: Before implementing ANY components, call the accessibility assistant for each primary component you plan to use. The WCAG general guidelines are already loaded above, so always use includeGeneralGuidelines=false.

First component:

kendo_accessibility_assistant({
    query="What are the accessibility requirements for [COMPONENT_NAME]?",
    component="[COMPONENT_NAME]",
    includeGeneralGuidelines=false
})

Each additional component:

kendo_accessibility_assistant({
    query="What are the accessibility features and requirements for [COMPONENT_NAME]? Include ARIA attributes, keyboard navigation, and screen reader support.",
    component="[COMPONENT_NAME]",
    includeGeneralGuidelines=false
})

Conditional Phases

Load and execute only the files that matched your Step 1 assessment:

• Component docs needed → read phase-components.md
• Layout needed → read phase-layout.md
• Layout AND responsive needed → also read phase-responsive.md
• Custom theming needed → read phase-theming.md
• Icons needed → read phase-icons.md

Final Phase: Validation & Quality Assurance

Read validation-steps.md and execute all validation steps before considering the task complete.

✅ Completion Checklist

Before considering the task complete, ensure:

• Accessibility guidelines retrieved and applied to all components
• ng build compiles the application successfully without errors
• Kendo Design System utilities applied correctly (if layout phase ran)
• Custom theme implemented and applied (if theming phase ran)
• NgModule vs Standalone setup detected and consistently applied