feat(skills): add grid sizing, updating theming, PR template, agents

.github/PULL_REQUEST_TEMPLATE.md

@@ -6,6 +6,9 @@ Closes #
  - [ ] Documentation
  - [ ] Demos
  - [ ] CI/CD
+ - [ ] Tests
+ - [ ] Changelog
+ - [ ] Skills/Agents
 
 ### Checklist:
  - [ ] All relevant tags have been applied to this PR

.github/agents/feature-orchestrator-agent.md

@@ -131,7 +131,7 @@ projects/igniteui-angular/core/src/core/styles/   ← component SCSS themes
 1. Read the feature request.
 2. Search the repo to identify affected components, directives, services, and files.
 3. If the feature touches theming or styles, read
-   `skills/igniteui-angular-theming/references/contributing.md` before planning the styling handoff.
+   `.github/themes-contributing.md` before planning the styling handoff.
 4. Determine:
    - Which components are affected and where they live
    - Whether this replaces, renames, or deprecates any existing API

.github/agents/theming-styles-agent.md

@@ -23,7 +23,7 @@ Your job is to implement visual fixes and style features in the in-repo SCSS sou
 
 1. Read the original request, bug report, or handoff summary.
 2. Read the relevant SCSS, component markup, and any existing tests before editing.
-3. Read `skills/igniteui-angular-theming/references/contributing.md` in full before modifying any `_*-theme.scss` or `_*-component.scss` file, wiring a component into the theme system, or changing style tests.
+3. Read `.github/themes-contributing.md` in full before modifying any `_*-theme.scss` or `_*-component.scss` file, wiring a component into the theme system, or changing style tests.
 4. Decide whether the change belongs in a component theme file, a structural component file, shared style infrastructure, or a minimal supporting markup hook.
 5. Implement the required theming and style changes without expanding into unrelated production logic.
 6. Run the relevant style validation before finishing.
@@ -32,7 +32,7 @@ Your job is to implement visual fixes and style features in the in-repo SCSS sou
 
 ## Required Reference
 
-Contributing to the in-repo SCSS source is covered in `skills/igniteui-angular-theming/references/contributing.md`.
+Contributing to the in-repo SCSS source is covered in `.github/themes-contributing.md`.
 
 Read that file when:
 - modifying or creating `_*-theme.scss` files

skills/igniteui-angular-grids/SKILL.md

@@ -82,6 +82,7 @@ After choosing the grid type, **you must still complete Steps 2–4 from the man
 Replace `igniteui-angular` with `@infragistics/igniteui-angular` for the licensed package — entry-point paths are identical.
 
 > **AGENT INSTRUCTION — Documentation URL Pattern**: For grid-specific topics (sorting, filtering, editing, paging, etc.), docs URLs follow this naming pattern per grid type:
+> - Grid Lite: `.../components/grid-lite/{topic}`
 > - Flat Grid: `.../components/grid/{topic}`
 > - Tree Grid: `.../components/treegrid/{topic}`
 > - Hierarchical Grid: `.../components/hierarchicalgrid/{topic}`

skills/igniteui-angular-theming/SKILL.md

@@ -414,9 +414,6 @@ Raw hex values are acceptable **only** in these contexts:
 
 Everything else must use `var(--ig-<family>-<shade>)` tokens.
 
-## Contributing to Component Themes
-> **Contributing to the in-repo SCSS source (component theme files, structural SCSS, base functions, and the component registry) is covered in [`references/contributing.md`](./references/contributing.md).** Read that file when modifying or creating `_*-theme.scss` or `_*-component.scss` files, wiring a new component into the theme system, or writing style tests.
-
 ## Common Patterns
 
 > **Light/dark theme switching, scoped themes, and licensed package configuration are in [`references/common-patterns.md`](./references/common-patterns.md).** Read that file for ready-to-use Sass patterns.