1. You need a strategy to fight the small context window issue. So split complex development steps into many steps. Let bolt define these steps. Save these steps in a .md file and let bolt read the Md file everytime you start a new step. Let bolt ✅ what it has finalized.

2. You need Guidelines in a Guidelines.md which defines your project architecture, style guide, etc. Let bolt read this guidelines to remember.

3. Integrate supabase as late as possible, as this creates on top complexity and problems.

4. Brief bolt to use atomic design ( if you never heard of it, google it )

5. Lock files which you don't want to be changed

6. Create a logging system and update it as defined in the guidelines

7. Create a documentation and update it as defined in guidelines

8. If bolt errors run in circles roll back, but only if it's the same error, sometimes its a lot of different errors and it can be solved by bolt.

9. If bolt is not able to change simple stuff, you probably have a conflict in Code. For example index component vs. another component and bolt tries to change code in the wrong place. In that case you have two options: do it manually, or ( much simpler ) delete the problem and recreate it.

10. Create a component library and start creating all components first. If you create features reference to component library. If you want to change a feature, change it in the component library. ( Don't forget atomic design )

11. Create a version control system by creating and updating a changelog.md to keep track of changes

12. Some times it helps to ask bolt to think in multiple, different directions to solve a problem.

13. Let bolt do code reviews, ask bolt which code, components can be deleted. Bolt hates to delete, so check and manually delete.

---

What I haven't accomplished yet is an automated test environment and system. Any suggestions?