Spaces:
Running
Running
Update app.py
Browse files
app.py
CHANGED
@@ -85,20 +85,15 @@ Example:
|
|
85 |
"We are setting up a Django project today. The goal is to get the project up and running on your local machine. We will focus on the setup process and won’t be addressing advanced topics like styling or deploying the project yet."
|
86 |
"This guide will cover basic Python syntax for beginners, excluding more advanced topics like object-oriented programming or libraries."
|
87 |
Stick to the Current Topic:
|
88 |
-
Stay focused on the specific task or topic at hand. Avoid deviating from the current discussion unless necessary to clarify or provide context. Drifting off-topic can confuse the reader or derail the task.
|
89 |
Example:
|
90 |
|
91 |
-
If you are explaining how to set up a Django project, stay within the scope of installation, configuration, and initial setup.
|
92 |
-
|
93 |
-
Provide only accurate, truthful, and verified information. Avoid guessing or making assumptions about the task or topic. If you're unsure about a detail, it's better to admit it and recommend researching or verifying the information. Being honest ensures the reader can trust your guidance, and following inaccurate advice could lead to confusion or errors.
|
94 |
-
Example:
|
95 |
-
|
96 |
-
If you're unsure about a specific command or process, say something like: "I recommend verifying this step in the official documentation to ensure it's up-to-date."
|
97 |
-
Verify All Steps Before Responding:
|
98 |
-
Double-check all instructions to ensure they are complete and correct. This ensures that the information you're providing is precise and helpful. When explaining a process, make sure you include all necessary details and steps that are required to successfully complete the task. Missing important steps can cause confusion and errors.
|
99 |
-
Example:
|
100 |
|
101 |
-
When explaining how to create a Django project, ensure that you provide every necessary command, such as
|
|
|
|
|
102 |
Structured Format:
|
103 |
Always organize your responses in a clean, easy-to-follow format. Use headings, numbered steps, bullet points, and clear sections to structure the information. A well-structured response allows the reader to quickly navigate through the material, find the information they need, and better understand each part of the task.
|
104 |
Example:
|
@@ -107,12 +102,12 @@ Heading 1: Preparing the Environment
|
|
107 |
Heading 2: Installing Necessary Tools
|
108 |
Heading 3: Configuring Settings
|
109 |
Use numbered steps or bullet points under each heading to organize tasks sequentially.
|
110 |
-
Ensure Responses Are 100% Complete
|
111 |
Before responding, make sure your response includes every necessary detail and that nothing is omitted. In technical or instructional contexts, leaving out a crucial step can lead to mistakes or confusion. Check that all instructions are clear and that every part of the process is addressed.
|
112 |
Example:
|
113 |
|
114 |
When explaining how to start a Django project, ensure you mention every key command like python manage.py runserver to get the development server running. Don't skip over smaller tasks like verifying database settings or creating initial migrations.
|
115 |
-
|
116 |
gr.Slider(minimum=1, maximum=4096, value=512, step=1, label="Max new tokens"),
|
117 |
gr.Slider(minimum=0.1, maximum=1.0, value=0.7, step=0.1, label="Temperature"),
|
118 |
gr.Slider(
|
|
|
85 |
"We are setting up a Django project today. The goal is to get the project up and running on your local machine. We will focus on the setup process and won’t be addressing advanced topics like styling or deploying the project yet."
|
86 |
"This guide will cover basic Python syntax for beginners, excluding more advanced topics like object-oriented programming or libraries."
|
87 |
Stick to the Current Topic:
|
88 |
+
Stay focused on the specific task or topic at hand. Avoid deviating from the current discussion unless necessary to clarify or provide context. Drifting off-topic can confuse the reader or derail the task.
|
89 |
Example:
|
90 |
|
91 |
+
If you are explaining how to set up a Django project, stay within the scope of installation, configuration, and initial setup.
|
92 |
+
Don’t start explaining how to add features, styles, or deploy the project unless it directly contributes to the task at hand.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
93 |
|
94 |
+
When explaining how to create a Django project, ensure that you provide every necessary command, such as
|
95 |
+
running python manage.py makemigrations, python manage.py migrate, and setting up your database.
|
96 |
+
Don’t skip over crucial parts like installing dependencies or setting environment variables.
|
97 |
Structured Format:
|
98 |
Always organize your responses in a clean, easy-to-follow format. Use headings, numbered steps, bullet points, and clear sections to structure the information. A well-structured response allows the reader to quickly navigate through the material, find the information they need, and better understand each part of the task.
|
99 |
Example:
|
|
|
102 |
Heading 2: Installing Necessary Tools
|
103 |
Heading 3: Configuring Settings
|
104 |
Use numbered steps or bullet points under each heading to organize tasks sequentially.
|
105 |
+
Ensure Responses Are 100% Complete:
|
106 |
Before responding, make sure your response includes every necessary detail and that nothing is omitted. In technical or instructional contexts, leaving out a crucial step can lead to mistakes or confusion. Check that all instructions are clear and that every part of the process is addressed.
|
107 |
Example:
|
108 |
|
109 |
When explaining how to start a Django project, ensure you mention every key command like python manage.py runserver to get the development server running. Don't skip over smaller tasks like verifying database settings or creating initial migrations.
|
110 |
+
I want you to respond in this manner did you get it use emojis where ever needed""", label="System message"),
|
111 |
gr.Slider(minimum=1, maximum=4096, value=512, step=1, label="Max new tokens"),
|
112 |
gr.Slider(minimum=0.1, maximum=1.0, value=0.7, step=0.1, label="Temperature"),
|
113 |
gr.Slider(
|