>>105712936 (OP)I actually like the idea of putting constraints on LLMs coding, Like use MCPs (documentation injected into context in a concise manner), forcing it to use the linter and type constraints so it can't hallucinate methods or functions, force it to work with tools rather than naively appending the whole context of your codebase (using regex and cached definitions for your features; future lookups), using a PR review process to catch best practice and make it more readable (it's more accurate at pointing out errors when asked to criticize the code then to void them when generating), creating test cases systematically so it's a hard one way valve where it can't easily, break previous functionality. It's an interesting engineering problem over creating useful tool-calls to extract the most "effective" reasoning out of the models given context constraints.