[wp-trac] [WordPress Trac] #63901: Add `AGENTS.md` for the project

[WordPress Trac]

#63901: Add `AGENTS.md` for the project
------------------------------+------------------------------
 Reporter:  flixos90          |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by jeremyfelt):

 Replying to [comment:10 justlevine]:

 > I don't know. But I do feel that in any most other context the bulk of
 core committers and leadership [...] would strongly oppose to adding such
 an opaque footgun to core.

 I think that's why starting simple is important. Focus on keeping
 documentation readable and useful to humans. See what happens when you
 tell the model to start with that. As time goes on, add documentation for
 tools that enhance the experience.

 My previous example could be just the one line, and without "Always", but
 I don't think it hurts for `AGENTS.md` to also be targeted to humans.

 > 1. A positive answer here doesn't prove those files are in context.

 Don't trust, verify. :) So far, in my test case of me, additional prompts
 react as expected, even with weird chains of context files I've setup.

 > 2. Just because something is "in context" doesn't mean it's having a
 positive effect out the LLM output.

 This is much harder to measure, of course, and I'm not sure there's an
 automated way to test it.

 Issue-specific user prompting matters more, but it at least ''feels''
 helpful for there to be an entry point that provides a readable,
 structured overview so that the agent doesn't start attempting to parse a
 bunch of unrelated files into context immediately.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63901#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform