There is a significant increase of LLM use among third party developers and the code more often than not is not up to standards. This is reinforced by the Core itself being somewhat in a bad state (for example, loose comparisons, empty() and other hot garbage). There are modernization efforts in place to improve this in 6.3 but it remains an ongoing issue.
We can improve the situation by adding an AGENTS.md which formalize these requirements to generate better code and to clarify the runtime behavior. For example, an option defined in option.xml will always be available as a constant, removing the need to slap define() calls on everything. Should use caveman-style instructions to minimize token usage.
This should possibly be deployed in the Core directory too because a typical use case is referencing an existing installation rather than the bare repository.
There is a significant increase of LLM use among third party developers and the code more often than not is not up to standards. This is reinforced by the Core itself being somewhat in a bad state (for example, loose comparisons,
empty()and other hot garbage). There are modernization efforts in place to improve this in 6.3 but it remains an ongoing issue.We can improve the situation by adding an
AGENTS.mdwhich formalize these requirements to generate better code and to clarify the runtime behavior. For example, an option defined inoption.xmlwill always be available as a constant, removing the need to slapdefine()calls on everything. Should use caveman-style instructions to minimize token usage.This should possibly be deployed in the Core directory too because a typical use case is referencing an existing installation rather than the bare repository.