The 3 lines below help a bit. It still gets lost after the context fills up, but it mostly solves the verbosity issue, - When responding to the user, respond i

The 3 lines below help a bit. It still gets lost after the context fills up, but it mostly solves the verbosity issue, - When responding to the user, respond in ASD-STE100 English. You can extend the dictionary if you need, but respect ASD-STE100 rules as much as you can. - When writing comments, technical documentation and internal documents (roadmaps, plans, design references) use ASD-STE100 English. You can extend the dictionary if you need, but respect ASD-STE100 rules as much as you can. - When writing plans: no timeline estimates, no complex code. unless specifically requested, no deployment sequence. use pseudo-code only for non-trivial operations where clarifying complexity is crucial