Prompting best practices documentation

[neubig]

We should add some documentation of prompting best practices by:

1. adding a file describing best practices in docs/modules/usage
2. modifying docs/sidebars.ts

It should provide examples of good prompts and bad prompts to the OpenHands AI software developer, expanding on the text below.

---

Good prompts are:

• Concrete: explaining exactly what functionality should be added, what error occurred that needs to be fixed, etc.
• Explain file locations: if known, explain the locations in the code base that should be fixed
• Appropriately scoped: they should be the size of a single feature, probably not too much more than 100 lines of code

In general, you can think about the directions that you would give to a junior developer who is not super familiar with the code base, and these will improve the probability of success.

[github-actions]

OpenHands started fixing the issue! You can monitor the progress here.

[github-actions]

A potential fix has been generated and a draft PR #4182 has been created. Please review the changes.

[github-actions]

OpenHands started fixing the issue! You can monitor the progress here.

[github-actions]

An attempt was made to automatically fix this issue, but it was unsuccessful. A branch named 'openhands-fix-issue-4181' has been created with the attempted changes. You can view the branch here. Manual intervention may be required.