Two relevant issues: #11147 and #11006

Will come back with more thoughts later.

Also related: #11887 -- I wonder if we can reconcile

@mekarpeles I still wanted to give feedback. I'm not sure if you've read the docs on copilot but I don't think this follows them.
Also I don't think having duplicated agents and claud.md is worthwhile it should be a sim link at best.
Adding docs for AI specific things in general should be done with care as to not further fragment out human docs.
Is there a good reason why we should write all separate docs for AI?

@RayBB the approach @lokesh put in place DRY's documentation into a single readme and also contains a single high-level AGENTS.md.

Github suggests using .github/copilot-instructions.md (for copilot -- which we have credits for) and
https://docs.github.com/en/copilot/how-tos/configure-custom-instructions/add-repository-instructions#creating-repository-wide-custom-instructions

@mekarpeles
How is it DRY? AGENDTS.md and CLAUDE.md are exactly the same minus the header.

The following markdown block is also repeated in 4 files part of this PR.

## Code Style

- **Python:** ...
- **JavaScript:** ...
- **CSS/LESS:** ...
- ```

@RayBB @mekarpeles

There is some code duplication here, but this PR enables support for multiple tools and we get the benefits now, rather than waiting for a perfect AI docs architecture design.

On maintainability: the bridge files should be stable and only require occasional updates, and if they get out of sync, they are a prompt away from getting realigned. Most importantly, the standards for AI docs are evolving, and I expect we'll be moving, renaming, and reorganizing files and content in the future. These files are not precious, better to start and iterate than wait.