I was wondering if our goal is to leverage them to think about interfaces a bit, like a slightly accelerated modeling phase and then let them loose on the implementation (and maybe later let them loose on local optimization tricks)
> …a slightly accelerated
> modeling phase and then
> let them loose on
> the implementation…
If you mean _visual_ modeling ala UML [1], then I have it on "good authority" [2] that's a sound approach…
_____
MODEL
…
The Verdict: If you provide a clear instruction like "Before you touch the code, read architecture.puml and ensure your changes do not violate the defined inheritance/dependency structure," the agent will be very effective at following it.
If you just "hope" it bears it in mind, it probably won't.
_The agent is a tool, not a mind-reader; it will take the shortest path to a passing test unless you wall that path off with your architectural models_.
…
To make it actually work, you need to turn the UML from a "suggestion" into a "blocker." You should add a section to your AGENTS.md (or CLAUDE.md ) that looks like this:
burnerToBetOut|17 days ago
_____
MODEL
…
The Verdict: If you provide a clear instruction like "Before you touch the code, read architecture.puml and ensure your changes do not violate the defined inheritance/dependency structure," the agent will be very effective at following it.
If you just "hope" it bears it in mind, it probably won't.
_The agent is a tool, not a mind-reader; it will take the shortest path to a passing test unless you wall that path off with your architectural models_.
…
To make it actually work, you need to turn the UML from a "suggestion" into a "blocker." You should add a section to your AGENTS.md (or CLAUDE.md ) that looks like this:
…Why this works:
…
_____
[1] https://news.ycombinator.com/item?id=46974325
[2] https://g2ww.short.gy/TheMightyBooch
agumonkey|16 days ago