|
Like with humans, unspecific requirements, too large or too small a context, or addressing the wrong domain can cause issues. My current workflow with Mistral or Claude to implement features is to write a playbook (like a developer guide) with them first on how to implement features in the current repository/source/project. For example, something like: Implement the feature using a, b, c as a blueprint (architecture, tests, code, documentation, and other things like styleguides, commands for checks or tests, linter, formatter, frameworks / versions and standards etc.). On features: Write the tests for xyz first. Then implement x, run the test for x, should now be green - and so on. Implement a feature means: Write tests, the code, documentation - and so on. Feature complete means: Tests are green, code is formatted and linted, documentation is available - and so on. Good code means ... The playbook approach works, even if the chat context becomes too large after some time. If I notice that, I have the model reread the playbook.
The playbook is also a living document; usually, I ask the LLM at the end if it wants to add any changes or additions. But the playbook thingy might become an issues, if it get to long. 200-500 lines works best for me atm. |