Usage Rules: Leveling the Playing Field for AI-Assisted Development
Usage Rules: Leveling the Playing Field for AI-Assisted Development
How the OSS community can democratize LLM context management
11 Replies
mix usage_rules.sync ASH_USAGE_RULES.md $(mix deps | grep -E '^\* ash' | awk '{print $2}')
for when you only need ash and don't want to pollute your context window with everything else 👀
We could potentially support patterns in
mix usage_rules.sync
?
mix usage_rules.sync AGENTS.md "ash*"
or something
another thing you can do is add an alias
yeah but that one has to change every time I add a new package
the grep thingy is dirty but adaptable
makes sense
Question: what is the criteria for what information is included in the
usage_rules
of a package? Is it a human-curated list of "most important" stuff? I ask because in Ash there is nothing about polymorphic relationships for example. But I know that is a topic in the online docsyeah its just human curated/our intuition.
I'd suggest adding one line about using polymorphic relationships and listing the guide name that it can find it in might be good now that it has usage_rules.docs_search tasks 😄
I'd accept that PR
Something like this? Sorry for the basic q, this is my first time contributing to Ash

No problem, and TBH its not a basic question I'm actually not sure 😆
Hmm....I actually have to think about if we want to link to hexdocs or not 🤔
make that PR and I'll consider it more and let you know
ok perfect, thanks!
yeah, I would prefer to have the explanation right there in the offline docs, but I'm sure there is too much already to pack. LLMs are not there yet with their context windows
GitHub
Update usage-rules.md to include Polymorphic Relationships by M-Gon...
Oneliner with a link to hexdocs
Contributor checklist
Leave anything that you believe does not apply unchecked.
I accept the AI Policy, or AI was not used in the creation of this PR.
Bug fixes i...
Yeah I think the usage rules are a bit bloated already but I'm not sure