Add agent skills for AI coding

[yihao03]

used opencode to read devGuide and generated relevant skills

What is the purpose of this pull request?

• Documentation update
• Bug fix
• Feature addition or enhancement
• Code maintenance
• DevOps
• Improve developer experience
• Others, please explain:

Overview of changes:
This PR serves as part of the effort to develop an AI workflow for development.

We opted to use the open source SKILL.md standard as it is provider agnostic and has good community support.
Therefore we could adopt mainstream and popular workflows developed by others without being restricted to a specific provider (e.g. ClaudeCode).

Useful references in creating skills:

• Claude's documentation
• OpenCode's documentation

Anything you'd like to highlight/discuss:

Testing instructions:
Use AI Coding tools like OpenCode/ClaudeCode to start writing code. Check if the skills are being picked up
correctly and performs as desired

Proposed commit message: (wrap lines at 72 characters)
Add Agent Skills.

---

Checklist: ☑️

• Updated the documentation for feature additions and enhancements
• Added tests for bug fixes or features
• Linked all related issues
• No unrelated changes

---

Reviewer checklist:

Indicate the SEMVER impact of the PR:

• Major (when you make incompatible API changes)
• Minor (when you add functionality in a backward compatible manner)
• Patch (when you make backward compatible bug fixes)

At the end of the review, please label the PR with the appropriate label: r.Major, r.Minor, r.Patch.

Breaking change release note preparation (if applicable):

• To be included in the release note for any feature that is made obsolete/breaking

Give a brief explanation note about:

• what was the old feature that was made obsolete
• any replacement feature (if any), and
• how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.09%. Comparing base (01b8ce4) to head (1b2387d).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2804   +/-   ##
=======================================
  Coverage   72.09%   72.09%           
=======================================
  Files         134      134           
  Lines        7411     7411           
  Branches     1587     1526   -61     
=======================================
  Hits         5343     5343           
- Misses       1940     2022   +82     
+ Partials      128       46   -82     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gerteck]

The references would definitely be useful for an AI agent to immediately have a good grasp of the codebase.

However, I am worried about the maintainability of the references.

• Would having these references (e.g. referencing specific Node versions, method names, file names and directory structures) cause a maintainence overhead when we do refactoring?
• What kind of measures do we have to make sure that the references do not drift from the features?

How do we find the balance of keeping a abstract and high level explanation of the design in the references enough to not have to add too much maintainability burden, but have it detailed enough to justify the token count and usefulness.

This is on top of the current developer documentation that has to be updated as well.

wdyt?

[yihao03]

Would it be useful if we created a subagent #2822 that updates the skills accordingly when changes are made to the devGuide? the solution to AI is... more AI...

[yihao03]

closes #2822

[Harjun751]

Some minor nits. Only problems are the prev/next page navigation buttons.

Also let's discuss on reverting the update-docs skill deletion

[Harjun751]

Perhaps a bit nitpicky, but should the AI use section go under Development? As I assume readers would want to read about the general development workflow first.

[yihao03]

I had a few considerations when I decided to dedicate AI to its own section:
There had been problems with popular open source projects where a bunch of people just thought 'would be cool to do this' before they vibe coded an entire PR without even ever looking at the code, much less the dev guide. While I don't think that we would have that kind of exposure in the short term, I think that making the AI use it's own dedicated section would increase its visibility and educate anyone intending to work on the project on proper AI use before just vibe-coding everything

[Harjun751]

Oh so sorry, I didn't phrase my comment well I think. I completely agree that it should be in its own section, and I think you did the subsections quite well. What I mean was that instead of this:

We put it below the first-level developer header:

So it's still its own section.
Wdyt?

[yihao03]

Ah I guess it still ties back to the same argument right: see how to use AI properly first even before starting development, and since its quite a short section it shouldn't add much friction to people that wants to go onto reading the Development section

[MoshiMoshiMochi]

Great work on this @yihao03. Just seeking clarification and small changes on others. Majority are just flagging out the emojis so that we don't miss out on any 💯.

[MoshiMoshiMochi]

Should this be a level 2 header since everything else was changed to level 2 header as well? I guess I can see it as being a sub-header to the Add New Skills section as well, but since the resources here cover more then just creating a skill, perhaps having it at the same level 2 header would be more inline with its relevance to the other sections.