React/Web Components AI entry instructions do not surface package-specific Ignite UI guidance

[georgianastasov]

Ignite UI CLI Version

15.0.0-rc.1

Framework

React

Project Type

igr-ts (React)

CLI Command

new

Node.js Version

v22.14.0

Operating System

Windows

Package Manager

npm

Description

The scaffolded AI instructions for React and Web Components are too generic for package-split Ignite UI components. In practice, the top-level instructions tell the model to use igniteui-react or igniteui-webcomponents, but unlike Angular they do not clearly route the model to package-aware references before generating code.

Steps to Reproduce

1. Generate a new React project with ig new "IG Project" --framework=react --type=igr-ts
2. Generate a new Web Components project with ig new "IG Project" --framework=webcomponents --type=igc-ts
3. Inspect the generated AGENTS.md and .claude/skills content, or ask an AI agent to add an Ignite UI grid
4. Compare that with the Angular skill structure and package guidance

Actual Result

Actual Result
React and Web Components project entry instructions are generic and do not clearly force or route the model to the correct package-specific references before generating code.

Examples from the generated content:

• React AGENTS.md says only Use igniteui-react
• Web Components AGENTS.md says only Use igniteui-webcomponents
• Angular grid skills use a routing-hub pattern with mandatory reference loading and explicit import entry points

Expected Result

Expected Result
React and Web Components AI guidance should mirror Angular more closely:

• The entry instructions should explicitly tell the model to use the correct package for the requested component family
• The relevant skill entry files should behave like routing hubs and require reading the package/reference files before generating code
• Common package splits should be explicit up front, especially for grids, charts, gauges, maps, Grid Lite, and Dock Manager

Error Output / Logs

No terminal/runtime error. This is visible in the generated AI instruction/skill files.

Additional Context

No response