4 Comments
User's avatar
Rodolfo Torres's avatar

Proud user of `usage_rules` in my ash/phoenix application.

I miss it every time I have to work on my employer’s rails codebase. At least we still have tidewave MCP in ruby land.

Expand full comment
Kenneth Kostrešević's avatar

In regards to recent AI policy & something you mentioned on Elixir Mentor: the usage rules are intended for usage of a given library, not for working on a given library. Although I'm sure they can help there as well (since it has general elixir rules also), but I'm wondering about having 'Dev Rules'? i.e. specific context for working on a library that doesn't need to be syncable. For instance, you streamed vibing on igniter the other day; did you use any rules along side usage rules that helped you in that? Maybe there could be some rules that align with AI policy? Or it might just be guidlines for a developer on how to approach a given task using agents? Just some thoughts. As always great post, rising the tide like a Poseidon! 💪

Expand full comment
Zach Daniel's avatar

That would just be AGENTS.md inside the repo itself. I'm mulling this over but haven't made my mind up if these belong in the Ash repos.

Expand full comment
Kenneth Kostrešević's avatar

Still cooking I see (let him cook!). Makes sense. I feel, the way things are going, it will be needed. Seems like usage rules will become a standard as well. Must. Contain. The magic text box!

Expand full comment