Skip to content

feat(skill): add Siemens Element skill - #2500

Open
mistrykaran91 wants to merge 2 commits into
mainfrom
feat/add-skill-for-element
Open

feat(skill): add Siemens Element skill#2500
mistrykaran91 wants to merge 2 commits into
mainfrom
feat/add-skill-for-element

Conversation

@mistrykaran91

@mistrykaran91 mistrykaran91 commented Aug 5, 2026

Copy link
Copy Markdown
Member
  • Add an Element-specific skill for component selection, integration, debugging, styling, theming, and migration tasks.
  • Use version-matched documentation to provide accurate package APIs, examples, icon guidance, and migration steps.

Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

Code Coverage

@mistrykaran91
mistrykaran91 force-pushed the feat/add-skill-for-element branch from ab4f254 to a0dc6fc Compare August 17, 2026 09:44
@mistrykaran91
mistrykaran91 marked this pull request as ready for review August 17, 2026 10:05
@mistrykaran91
mistrykaran91 requested a review from a team as a code owner August 17, 2026 10:05
@Killusions

Copy link
Copy Markdown
Member

@mistrykaran91 @spike-rabbit If we anyway have to instruct the model to run a command, we might as well tell it to just read the package.json to find the currently used element version, most Agents also always allow reads in the current working dir but not shell automatically.

@mistrykaran91

Copy link
Copy Markdown
Member Author

@mistrykaran91 @spike-rabbit If we anyway have to instruct the model to run a command, we might as well tell it to just read the package.json to find the currently used element version, most Agents also always allow reads in the current working dir but not shell automatically.

You mean to say if user does not allowing reading using shell then in that case we should ask agent to do so by itself ?

@spike-rabbit

Copy link
Copy Markdown
Member

After also talking with @Killusions I guess just pointing it by default to the / path is fine.
Then just add some quick instructions on how to find the correct version, but by default it should just use /.

@spike-rabbit

Copy link
Copy Markdown
Member

ix is also not planning to resolve the version at all BTW

@mistrykaran91
mistrykaran91 force-pushed the feat/add-skill-for-element branch 4 times, most recently from 04c4cbf to 4efca0e Compare August 26, 2026 06:59
- Add an Element-specific skill for component selection, integration, debugging, styling, theming, and migration tasks.
- Use version-matched documentation to provide accurate package APIs, examples, icon guidance, and migration steps.
@mistrykaran91
mistrykaran91 force-pushed the feat/add-skill-for-element branch from 4efca0e to 9092b4a Compare August 26, 2026 07:00
@mistrykaran91 mistrykaran91 changed the title feat(skill): add Siemens Element skill and version resolver script feat(skill): add Siemens Element skill Aug 26, 2026
@mistrykaran91

Copy link
Copy Markdown
Member Author

After also talking with @Killusions I guess just pointing it by default to the / path is fine. Then just add some quick instructions on how to find the correct version, but by default it should just use /.

@Killusions , @spike-rabbit : I have updated the skill file and remove the script.

Comment thread skills/element/SKILL.md
@@ -0,0 +1,52 @@
---
name: element
description: Manages Siemens Element Angular components and projects — selecting, adding, searching, fixing, debugging, styling, theming, migrating, and composing accessible UI. Provides version-matched project context, component APIs, design guidance, documentation, and usage examples. Use this skill whenever a task involves Siemens Element, an Element component, or any @siemens/element-ng, @siemens/dashboards-ng, @siemens/charts-ng, @siemens/maps-ng, @siemens/element-translate-ng, @siemens/element-theme, or @siemens/element-icons package, even when the user does not explicitly ask for this skill.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of "Use this skill whenever a task involves Siemens Element, an Element component" I would write "Use this skill whenever a task involves developing an Angular frontend, Siemens Element, an Element component"

@Killusions

Copy link
Copy Markdown
Member

After also talking with @Killusions I guess just pointing it by default to the / path is fine. Then just add some quick instructions on how to find the correct version, but by default it should just use /.

@Killusions , @spike-rabbit : I have updated the skill file and remove the script.

Just one comment, otherwise I like it 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants