diff --git a/swarms/prompts/code_spawner.py b/swarms/prompts/code_spawner.py
index 3981519c..8caecf53 100644
--- a/swarms/prompts/code_spawner.py
+++ b/swarms/prompts/code_spawner.py
@@ -3,13 +3,13 @@
 # Analyze the user's idea to extract key concepts, requirements, and desired outcomes
 IDEA_INTAKE_PROMPT = """
 Analyze and expand upon the user's idea, extracting key concepts, requirements, and desired outcomes. Represent the user's idea in a highly detailed structured format, including key features, constraints, and desired outcomes. Idea: {idea}
-"""
+"""  # noqa: W291, W293
 
 # Develop a high-level plan for the codebase, including directory structure and file organization
 CODEBASE_PLANNING_PROMPT = """
 Develop a high-level plan for the codebase, including directory structure and file organization. Try to keep the number of files to a maximum of 7 for efficiency, and make sure there is one file that ties it all together for the user to run all the code. Design the software architecture to determine the overall structure
 of the codebase based on the following requirements: {requirements}
-"""
+"""  # noqa: W291, W293
 
 # Translate the high-level codebase plan into specific, actionable development tasks
 TASK_PLANNING_PROMPT = """
@@ -25,7 +25,7 @@ Guidelines for Task Planning:
 - Format the tasks as structured data for easy parsing and automation.
 
 
-"""
+"""  # noqa: W291, W293
 
 # Generate individual code files based on the detailed task descriptions
 FILE_WRITING_PROMPT = """
@@ -33,12 +33,12 @@ Generate individual code files based on the codebase plan. Write code in the spe
 generation techniques. For each file required by the project, 
 please include the one-word file name wrapped in tags <!--START_FILE_PATH--> and <!--END_FILE_PATH-->, followed by the file content wrapped in
 <!--START_CONTENT--> and <!--END_CONTENT--> tags. Ensure each file's details are clearly separated. Here are the details: {details}
-"""
+"""  # noqa: W291, W293
 
 # Analyze the generated code for correctness, efficiency, and adherence to best practices
 CODE_REVIEW_PROMPT = """
 Analyze the generated code for correctness, efficiency, and adherence to best practices. Meticulously review the codebase to find any errors, bugs, missing imports, improper integration,or broken logic. Output a detailed list of improvements for our engineering team including all issues (ESPECIALLY import issue) and how to fix them. Here is the code: {code}.
-"""
+"""  # noqa: W291, W293
 
 # Refactor the generated code to improve its structure, maintainability, and extensibility
 CODE_REFACTORING_PROMPT = """
@@ -53,10 +53,10 @@ The code to refactor:
 
 
 Note: The expectation is that the refactored code will be structured and tagged appropriately for automated parsing and saving as individual code files.
-"""
+"""  # noqa: W291, W293
 
 
 # Push the final codebase to a GitHub repository, managing code changes and revisions
 GITHUB_PUSH_PROMPT = """
 Push the final codebase to a GitHub repository. Manage code changes and maintain a history of revisions using version control integration. Here are the final changes: {changes}
-"""
+"""  # noqa: W291, W293