docs: add ENGINE_PERFORMANCE.md with some notes on engine internals#2919
Conversation
f2c4dd5 to
4639bb0
Compare
This stack of pull requests is managed by Graphite. Learn more about stacking. |
4639bb0 to
ea4c067
Compare
1149942 to
527dda9
Compare
ea4c067 to
513bc73
Compare
lostsquirrel1
left a comment
There was a problem hiding this comment.
A nice start. Here's a few more thoughts from me to help improve the information presented to the AI.
527dda9 to
f9c151c
Compare
513bc73 to
de090f6
Compare
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
I changed some bits from feedback and to match my current knowledge now that I've worked with engine a bit more. would love a final pass from y'all in case anything jumps out :) |
sprunk
left a comment
There was a problem hiding this comment.
Looks alright. I don't believe it's going to make any difference but at least that means it shouldn't hurt to include either.
|
thanks. fwiw I've run into many sessions having to re-explain / re-derive how frames work in engine so this should hopefully be a shortcut. my 2c 🤷♂️ |
| 5. Disclose any AI assistance used | ||
|
|
||
| ### Additional docs | ||
| Please see @coding-agents/ for additional documentation: |
There was a problem hiding this comment.
@bruno-dasilva I didn't think @ includes worked outside of claude code?
There was a problem hiding this comment.
you could be right for harness-forced includes. But regardless any modern model should see that as a dir and read it when it chooses to 🤷

Purpose
A few separate discussions got some good answers worth putting in docs for coding agents as context.
Meant to be simple/vague, as coding agents can dig deeper for specifics when they need to.
NOTE: LLM generated by heavily reviewed/cut by me.