points by yokuze 16 hours ago

I commit my standard set of agent configuration (including Skills) to this repo, similar to how many people have a "dotfiles" repo: https://github.com/yokuze/aix-config

Then, I use this tool:

https://github.com/a1st-dev/aix

to keep my Claude, Codex, and OpenCode in sync with my config.

The major benefits are that my adoption/deletion of skills, rules, hooks, MCP servers, etc. are deliberate, versioned, and shareable.

And since aix allows you to create extensible configs, that aix-config public GitHub repo is my base set of rules, and my internal/employer-specific rules are just a small layer on top of that.

It also makes trying out different subscriptions easy: you define your config in one place (one source of truth), and write to Claude, Codex, Devin, etc. with one command.

veb 16 hours ago

interesting project mate. I have struggled with this as I built my workflow to rely on Claude, but when I put Codex into the mix it became a bit of a hassle, will check it out.

  • yokuze 16 hours ago

    Cheers!

    There's also a command you can run to convert your Claude config to what Codex expects: `aix sync claude-code --to codex --dry-run` (just drop the --dry-run flag if the result looks good to you).

    More here: https://aix.a1st.dev/editors/migrations/how-to-migrate-from-...

    Feel free to suggest any improvements or features you'd like to see, or let me know if you find any bugs.