These days I always have a terminal open. We knew GenAI is not just for coding, but this has become more real than ever — I now use them for writing, brainstorming, meeting notes, task management, research, and more. It's addicting. I find myself switching between GitHub Copilot and Claude Code a lot, and the challenge is that they have different default folders for instructions, skills, agents, etc. This is a work in progress but this is how I structure my files so that it works whichever tool I use. Few people probably use both tools like me but if that's you, hope this helps: https://lnkd.in/g6ycERfv #githubcopilot #claudecode #crosscompatibility #vibing
Amjad S.
1mo
This is great. I think Claude agent file structure should be standardized everywhere.
Great post as usual Rafferty!
Rafferty Uy the thin wrapper pattern you landed on — keeping `.github/instructions/` as the source of truth and making `.claude/rules/` point there — is really smart. I went through a similar evolution and the thing that surprised me is how quickly those wrappers become their own maintenance surface: the moment a tool changes its frontmatter schema or adds a new feature, every wrapper needs updating. That's actually what pushed me toward treating it as a compilation problem — single source, compile to each tool's native format — which is the core of something I've been prototyping at github.com/microsoft/apm. Curious whether the dual `@import` + markdown link syntax in `CLAUDE.md` has bitten you yet when one tool resolves it differently than expected — that was one of the trickiest edge cases I ran into.