experimenting with system prompt and temperature

ProjectCli/modules/init.py

@@ -14,12 +14,22 @@ class init:
                     "content": sysPrompt,
                 },
             ],
+            options={"temperature": 1},
         )
 
         return response["message"]["content"]
 
     def generatePrompt(self, args) -> str:
         return f"""You will give the user a markdown formatted programming project they can work on.
+- Align the project based on this information.
+- This project is intended for users that want to practise their programming skills.
+- When creating the markdown file always include the following things; header, instruction, final product, rules, general information provided by user (Details), Technical Requirements, and lastly the points (score)
+- do NOT use markdown blocks as your response will immediately be injected into a .MD file upon completion.
+- If the user did not provide a Programming Language (based on details) the assign the user one based on the project. Clearly define the language in the MD file
+- Make the user decide on their own which packages they want to use unless explicitly specified in Custom user instructions and/or General Details
+- Do NOT provide any code structures or samples (unless required by previous instructions). Let the user figure it out on its own as this is intended to be a challenge
+- Always listen to Custom user instructions if the user has a specific request.
+
 -- Details --
 Language: [[ {args.language} ]]
 Framework: [[ {args.framework} ]]
@@ -27,15 +37,5 @@ External packages allowed: [[ {str(args.packages)} ]]
 Difficulty: [[ {args.difficulty} ]]
 Estimated Time the user want to spend on the project: [[ {args.time} ]]
 Type of project: [[ {args.project} ]]
-Custom instructions: [[ {args.custom} ]]
-
--- information --
-- Align the project based on this information.
-- This project is intended for users that want to practise their programming skills.
-- When creating the markdown file always include the following things; header, instruction, final product, rules, general information provided by user (Details), Technical Requirements, and lastly the points (score)
-- do NOT use markdown blocks as your response will immediately be injected into a .MD file upon completion.
-- If the user did not provide a Programming Language (based on details) the assign the user one based on the project. Clearly define the language in the MD file
-- If there is a framework (such as symfony) included (or a engine such as unity) or a library/package that requires a advanced instalation (based on difficulty), provide a installation guide in the MD file and/or a cheatsheet unless the assistant is unsure on how to set it up.
-- Make the user decide on their own which packages they want to use unless explicitly specified in Custom instructions and/or General Details
-- Do NOT provide any code structures or samples (unless required by previous instructions). Let the user figure it out on its own as this is intended to be a challenge
+Custom User Instructions: [[ {args.custom} ]]
 """

ProjectCli/modules/review.py

@@ -27,7 +27,7 @@ class review:
         messageHistory = [
             {
                 "role": "system",
-                "content": f"""You are going to review a project the user made based on a MD file.
+                "content": f"""You are going to review/rate a project the user made based on a MD file.
 - The user is currently on the platform; {platform}
 - You will be allowed using tool calling to execute commands directly on the OS machine.
 - You are NOT allowed to search up the web, do curl requests, modify files, or harm the device. The tool calling is intended purely for read only access
@@ -38,10 +38,12 @@ class review:
 - when your evalution the project use the terminal (tool calling) to inspect files and read them.
 - be VERY critical when reviewing the project. The user has to learn fropm this experience.
 - before starting its adviced to do pwd and ls using tool calling as you can find the right place to review.
+- You will be validating the code like a teacher. Make sure to inspect the code as well
 
 
 -- MARKDOWN FILE --
 {markdown}
+-- END OF MARKDOWN FILE --
                 """,
             },
             {