Generate project documentation and prompts for executing code tasks as a way to reduce AI programming tool tokens consumption and task execution errors

Writing the original project documentation prompts

You are my software architect. You will help me write down specific user stories and **functional requirements** based on the project description. Do not provide code. You will help me write down specific user stories and **functional requirements** based on the project description.

We will be using a tool called bolt.new - to build this entire project. Imagine bolt.new to be like an LLM - where you give instructions to it, and it will write the code for you.



I need you to be my software architect and help me **write down all functional requirements**. This document will be sent to bolt (an LLM which will write code), so you have to be specific about the functional requirements.

Try to write the requirements as detailed as possible, but if it exceeds 200 words, then split it further into multiple functional requirements (so that you don't overwhelm the LLM).

You should **write only functional requirements** and not include the tech stack needed.

Write translations of prompt words for project documentation

You are my software architect. You will help me write specific user stories and **functional requirements** based on the project description. Do not provide code.

We will use a tool called bolt.new to build the entire project. Think of bolt.new as a large language model (LLM) - you provide it with instructions and it will write the code for you.

I need you to act as my software architect and help me **write all the functional requirements**. The document will be sent to bolt (an LLM that writes code), so you must specify the specific functional requirements.

Try to write the requirements in as much detail as possible, but if they are more than 200 words, please break them down further into multiple functional requirements (so as not to overload the LLM).

You should **only** write functional requirements** and not include the required technology stack.

Original text of the prompt for the implementation of the code-writing task

## Project Overview

I've uploaded the project file structure in project knowledge - this is what we've built so far. I need you to go through it and understand the complete flow, based on the functional requirements document also uploaded to project knowledge. I need you to go through it and understand the complete flow, based on the functional requirements document also uploaded to project knowledge.

## Functional Requirements Components

I have also added the different components of the Functional Requirements into separate files, for you to have more context.
- ``
- ``
- ```''

## Development Environment

I am working with `bolt.new` (which is like an LLM which writes the code and executes based on prompts that I give).

## Current Version and Next Steps

I have built the first version of the ``. Here's what we need to do now.
- [Describe the issue you're facing, or the new functionality you'd want to implement]

## Important Notes

Especially if you're a non-dev and struggle to pinpoint which file causes the issue, in a large project.

Please tell me which files do you need the code to review, from the project structure. I need you to ask me all the info you need, to be able to fix this. We do not want to add new features - we should just fix this issue alone. You need to do a code review and fix the existing implementation, use the current structure, variables used and then tell me how to use the project structure. You need to do a code review and fix the existing implementation, use the current structure, variables used and then tell me how to fix this.

Translation of prompts for performing code-writing tasks

## Project Overview

I have uploaded the project document structure into Project Knowledge - this is what we have built so far. I need you to navigate through it and understand the complete process based on the Functional Requirements document that was uploaded to Project Knowledge.

## Functional Requirements Components

I've also split the different components of the functional requirements into separate files so you get more context:
- ``
- ``
- ``

## Development Environment

I'm using `bolt.new` (similar to an LLM that generates code and executes it based on prompts I provide).

## Current version and next steps

I've built the first version of ``. Here's what we need to accomplish now:
- [describe the problems you encountered, or new features that need to be implemented].

## Important notes

Especially if you are not a developer and are having trouble determining which file is causing the problem in a large project:

Please let me know which code in which files you need to look at (based on the project structure). I need you to ask for all the information you need in order to solve the problem. We don't want to add new features - we just need to fix the problem. You need to do a code review and fix the existing implementation, using the current structure and variables used, and then tell me how to fix the issue.

Instructions for use

A http://bolt.new tip
When building a complex project, I'll http://bolt.new the Token Usage reduced by 70% (background: my current project has 35 pages of PRD and 16 database tables)!
From: 1M Tokens Processing 3-4 tips
To: The same 1M Tokens can now handle 10-12 tips!

In my experience with http://bolt.new, the key to successful implementation is precise problem solving - knowing exactly what the problem is and how to fix it. As a developer, this ability is enhanced because it's easier to locate the problem and fix it. But if you're a non-developer like me, I've found that it will be Claude Setting up as your "software architect" is the key to achieving this level of precision.

Building on my previous tip about a detailed FRD (Functional Requirements Document), here is the structured system I developed:

File and folder structure in Bolt

Start with a file structure chart. I had bolt create a "http://fileNames.md" that lists each file and maintains a folder hierarchy. Each entry contains a one line description of the purpose and function of that component. This became the map for our project.

Claude Project:

Set up a dedicated "problem solving" project in Claude. I created a Claude project dedicated to handling fixes and updates. In Project Knowledge, I added:

• Complete file structure (from http://fileNames.md)
• Main Functional Requirements Document
• FRD by component (based on user flow)
• Documentation explaining the functionality of http://bolt.new

Streamlining problem solving:

For each fix or new feature, I go into this Claude project and use a specific prompt structure. This is my workflow:

• First, I set the context with my "System Tip".
• Then, for each fix/feature request, I use the "Execution Prompt".

The specific format I use to describe the problem/function can help Claude write optimized tips for http://bolt.new, identify relevant files, suggest the most Token-saving approach, and even provide concrete steps to solve the problem.

Use .bolt/ignore:

I worked with Claude to identify files that didn't need to be in the LLM context and added them to .bolt/ignore. This significantly reduced Token usage while maintaining development efficiency. Note that depending on what you're fixing, we'll need to do this multiple times.

Results?

I actually created a two-tier system:

• Claude acts as a "software architect", analyzing problems and designing solutions.
• http://bolt.new Become a "developer" and implement these solutions efficiently!

This approach has revolutionized my development process. Instead of being stuck with Token restrictions or unclear prompts, I can focus on building and improving features.

Yes, the initial setup will take time. Yes, you'll be challenged with Token limits and error loops. But by choosing to give up when things get complicated, you're missing out on the true potential of http://bolt.new. This structure is worth it in terms of lower Token usage and a clearer development path.

@stackblitz
Features and optimizations are already being released at a breakneck pace - all we need is to find a way to solve most of the problems.

If you would like to implement this method for your project or need clarification, please feel free to reply or private message me.

P.S. Sometimes I still wonder if I should make a video for this setup. Please let me know if this would be helpful to you.