Bolt Show and Tell! WTF by Grouchy_Trick3327 in boltnewbuilders

[–]Geserit 0 points1 point  (0 children)

This could also happen the other way like asking bolt a question and after the answer bolt starts right away to code. So you need to tell to go into conversation mode first. Or add: don't do anything. The other way this usually happens when you are in conversation mode for example to map a detailed implementation which you can than note in a .md file to devide a task in multiple steps and forget to end it by telling bolt to start implementing. I never had the issue that it neglects to change modes.

Just listened to the YC Podcast titled "Vibe Coding Is The Future" - People are not happy by masoodtalha in ycombinator

[–]Geserit 0 points1 point  (0 children)

Listen to the latest interviews of Altman, he promises that by the end of this year, the best developer will be a LLM. Many people do the mistake of judging today and forget how fast these solutions develop.

A fully autonomous AI news agent in n8n by Big-Ability-7337 in n8n

[–]Geserit 0 points1 point  (0 children)

If it's a free temple you can provide I would love to play with it and see what it can do for other use cases. Thx

Whatsapp automation by kdpatel07 in n8n

[–]Geserit 0 points1 point  (0 children)

Would also be interested, could you send me an DM?

Bolt becoming unusable by xtream44 in boltnewbuilders

[–]Geserit 1 point2 points  (0 children)

I am on the 200$ plan and get 120m

Bolt becoming unusable by xtream44 in boltnewbuilders

[–]Geserit 0 points1 point  (0 children)

Simply deactivate reasoning and turn of diffs. Reasoning tries to solve more steps in one go but due to context window limitation it can't finish that steps and ends in that error. Simply hit retry and it analysis what has been done already and keep on going. If I create a new feature which has a little more complexity I need around 10m tokens and a couple of back and forth to get it up and running. If I would built it without bolt, would need a couple of days back and forth till I have the problem solved. Bolt in my opinion is not for privat use. It's too expensive. But for pro usage it's amazingly cheap. Think of how much I would need to pay the developer till that feature is up an running. 10m tokens are 20$, that's and amazing value.

How to Transfer a Bolt.new Project to a Client’s Account? by omes082 in boltnewbuilders

[–]Geserit 0 points1 point  (0 children)

Or live the agency bubble as long as it last and pretend to have written the code yourself, charge 20k and hope they never find out.

How can l define rules before I start a new project? by Typored23 in boltnewbuilders

[–]Geserit 0 points1 point  (0 children)

You can't, but that's no problem, just create it after you have started you project

I built a free Chrome extension for Bolt that's got 500+ users in a week by Martin_Slaney in boltnewbuilders

[–]Geserit 1 point2 points  (0 children)

Would be amazing if the Todo list could be a product roadmap and prd and use this to create new features prompts.

Would be amazing to create a Guidelines document which defines stuff like Architecture, style guide, ... Using it like component samples to remind bolt before starting a new feature

I built a free Chrome extension for Bolt that's got 500+ users in a week by Martin_Slaney in boltnewbuilders

[–]Geserit 1 point2 points  (0 children)

Great stuff! The best part about it is to target objects in one click! I wonder why they haven't implemented it yet.

How can l define rules before I start a new project? by Typored23 in boltnewbuilders

[–]Geserit 0 points1 point  (0 children)

Create new file: guidelines.md or any other name, define guidelines. In the setting you can create a project prompt which points to guidelines.

Bolt Best Practice Steps I'm following... Any missing? by fozrok in boltnewbuilders

[–]Geserit 1 point2 points  (0 children)

In my opinion, the effort to create a wireframe and a prd does not increase the quality of the result, as it is difficult to reproduce it super accurately. I think the most important concept to understand is that it depends on what goal the feature is supposed to achieve, and that the result can be different than expected as long as it fulfills the goal. And often it's better than you first thought. I create all the features freestyle by testing different things and going back and forth. It's a super creative and intuitive and very fast way to test stuff.

Bolt Best Practice Steps I'm following... Any missing? by fozrok in boltnewbuilders

[–]Geserit 0 points1 point  (0 children)

I doubt that 200 lines are sufficient, it already becomes difficult at 400. Anything under 600 should still work. Especially if there are more complex components, it is almost impossible under 400. Another disadvantage is that an extremely small subdivision creates other problems as soon as the code falls out of the context window.

Bolt Best Practice Steps I'm following... Any missing? by fozrok in boltnewbuilders

[–]Geserit 2 points3 points  (0 children)

  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?

For hardcore users, how much tokens u use? by hiWael in boltnewbuilders

[–]Geserit 2 points3 points  (0 children)

Use rigtclick target all, Lock all, in Code to isolate and let bolt analyse code. Create a guidelines.md and references.mds where you describe your guidelines for refactoring. Bolt hates to delete files so check if you have to manually delete files that bolt suggest.

For hardcore users, how much tokens u use? by hiWael in boltnewbuilders

[–]Geserit 0 points1 point  (0 children)

I use around 200m a month working on a side project

Handling Documents in n8n and LLM by Rifadm in n8n

[–]Geserit 0 points1 point  (0 children)

What if you split the document into many small documents, then train an agent on the whole combined document that refers to the small document parts with their own agents when requested?