docs: restructure AI skills locations & install options; platforms

[zdrawku]

Introducing a new React specific topic and adding a condition to the TOC for react.

[damyanpetev]

@copilot

• Remove this Option A; curl a single file does not work for skills with references and other files, so it's quite useless
• Remove the entire Step 2 (and with that the Step 1 header, adjust sub headers). Skills for supported agents do not need to be manually referenced in chat windows or dragged in as context or whatever.
• Move the # macOS / Linux and similar comments out of the code snippet as it messes with the easy copy functionality for those.
• For Windows options:
  • cp -r node_modules/igniteui-react/skills/. .agents/skills/ is perfectly valid PowerShell as cp is an alias for Copy-Item
  • If completeness is the goal to list cmd versions for Windows steps, xcopy is quite obsolete, prefer robocopy instead

[Copilot]

@damyanpetev I've opened a new pull request, #1929, to work on those changes. Once the pull request is ready, I'll request review from you.

[damyanpetev]

@copilot Adjust the topic content based on the latest changes made in IgniteUI/igniteui-react#134

[Copilot]

@damyanpetev I've opened a new pull request, #1933, to work on those changes. Once the pull request is ready, I'll request review from you.

[damyanpetev]

@copilot

I don't like the separation into react-skills.md - there's still plenty of repeated information and affects the end result URL-s;

Rework the React skills topic back into the main skills.md and see docConfig.json at the root repo source - there's {GithubLink} variable that can be used for the skills folder link under the Available Skills section and the {ProductName} in the text.
Use normal conditional sections like:

<!-- WebComponents -->
 WebComponents only content here
<!-- End: WebComponents -->

to split the listings of skills and other content that requires more than just variable name replacements

[damyanpetev]

@copilot

The entire "Approach 1: Create a Persistent IDE Agent" section seems off since it's about "no copy-pasting required" linking copilot instructions to something like https://github.com/IgniteUI/igniteui-react/blob/master/skills/igniteui-react-components/SKILL.md directly (i.e. an attempt for evergreen in a way), though that's not a skill used that way.

So might want to re-do the use section as well and after that it's no longer Approach 1: vs Approach 2: - they are the same thing, just the first section points where skills should be placed to be used and the secondary section is the examples how to copy this section is missing.

Link to https://agentskills.io/ in the introduction section. Might need a small note that the use locations and distribution options are constantly evolving so also consult the tool/agent/IDE dosc on that front.

As for the first section: Move the general agents example first with the expanded structure code block and leave the rest after with just the directory options. The general skills folder should be valid for VS Code with Copilot per https://code.visualstudio.com/docs/copilot/customization/agent-skills, OpenAI Codex https://developers.openai.com/codex/skills, Cursor, Gemini(and Antigravity) and Windsurf

As for the other agents:
Cursor uses
Location Scope
.agents/skills/ Project-level
.cursor/skills/ Project-level
~/.cursor/skills/ User-level (global)
https://cursor.com/docs/skills

Claude uses
Personal (~/.claude/skills/) or project-based (.claude/skills/);
https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview#sharing-scope

Github Copilot supports:

Project skills, stored in your repository (.github/skills or .claude/skills)
Personal skills, stored in your home directory and shared across projects (~/.copilot/skills or ~/.claude/skills) (Copilot coding agent and GitHub Copilot CLI only)

https://docs.github.com/en/copilot/concepts/agents/about-agent-skills

Gemini CLI discovers skills from three primary locations:

Workspace Skills: Located in .gemini/skills/ or the .agents/skills/ alias. Workspace skills are typically committed to version control and shared with the team.
User Skills: Located in ~/.gemini/skills/ or the ~/.agents/skills/ alias. These are personal skills available across all your workspaces.

And has /skills slash command to view and manage
https://geminicli.com/docs/cli/skills/#skill-discovery-tiers

Similar for Antigravity https://antigravity.google/docs/skills

Jetbrains Ides agent is Junie and it uses
.junie/skills/
https://junie.jetbrains.com/docs/agent-skills.html

Windsurf besides For cross-agent compatibility, Windsurf also discovers skills in .agents/skills/ and ~/.agents/skills/ and optionally Claude path is configured, also looks for
Scope Location Availability
Workspace .windsurf/skills/ Current workspace only. Committed with your repo.
Global ~/.codeium/windsurf/skills/ All workspaces on your machine

https://docs.windsurf.com/windsurf/cascade/skills#skill-scopes

---

Include the links to the tools docs in their section as well