Sasha Levin <[email protected]> writes: > Create a single source of truth for AI instructions in > Documentation/AI/main.md with symlinks for all major AI coding > assistants: > - CLAUDE.md (Claude Code) > - .github/copilot-instructions.md (GitHub Copilot) > - .cursorrules (Cursor) > - .codeium/instructions.md (Codeium) > - .continue/context.md (Continue) > - .windsurfrules (Windsurf) > - Documentation/AIder.conf.yml (Aider) > > Signed-off-by: Sasha Levin <[email protected]> > --- > .aider.conf.yml | 1 + > .codeium/instructions.md | 1 + > .continue/context.md | 1 + > .cursorrules | 1 + > .github/copilot-instructions.md | 1 + > .windsurfrules | 1 + > CLAUDE.md | 1 + > Documentation/AI/main.md | 5 +++++
So I'm gonna ignore (for now) the substantive issues here to ask: do we *really* need to introduce Markdown into Documentation/? Are these things really unable to understand RST? Why not add a file that can be part of the docs build so people can see the instructions that are being provided? Thanks, jon
