Jose M. Valera Reales (@Chemaclass)

Thu, Oct 15

Jose M. Valera Reales @ChemaclassOct 151507396

Every AI coding tool ships its own config file. Adopt three and your instructions live in three places, drifting apart. agnostic-ai keeps one source in your repository and writes the rest. https://agnostic-ai.org

agnostic-ai.orgagnostic-ai: one spec, every AI CLIWrite agents, skills, rules, and hooks once. agnostic-ai writes the configuration files read by 26 AI coding tools, with 20 enabled by default.

Adam Hosker @ahoskerOct 15

xkcd

Jose M. Valera Reales @ChemaclassOct 159f059a2

And another PR to show the star next to reply and copy link https://github.com/nunomaduro/dev-null.sh/pull/79

GitHubfeat: show the star next to reply and copy link by Chemaclass · Pull Request #79 · nunomaduro/dev-null.shThe star sat on its own line above the reply actions. It now sits in the same row, right after Reply, so each commit has one line of actions: Reply, Star, replies, Copy link. Demo

Ilgar Huseynli @ilgarhuseynliOct 15

better

Jose M. Valera Reales @ChemaclassOct 15682dc49

dev-null.sh works for me

Jose M. Valera Reales @ChemaclassOct 15028c222

It's ready chore: generate AI tool config from one source with #agnostic-ai https://github.com/nunomaduro/devnull.com/pull/45

Jose M. Valera Reales @ChemaclassOct 15f3bdfa4

I notice you have .agents, .ai, .amp, .claude, .codex, .cursor, .gemini, in the repo. I will create a PR to improve this and avoid duplication and have the most optimal setup with https://agnostic-ai.org

Jose M. Valera Reales @ChemaclassOct 152e0ab48

One setup. Every AI CLI Keep agents, skills, rules, hooks, and MCP servers in one portable source. agnostic-ai writes each tool's native files and checks them for drift. https://agnostic-ai.org

Jose M. Valera Reales @ChemaclassOct 15ac5f380

Let's go!

Commit activity

Thu, Oct 15