Update app.py
Browse files
app.py
CHANGED
|
@@ -43,7 +43,8 @@ mychatbot = gr.Chatbot(
|
|
| 43 |
show_label=False,
|
| 44 |
show_copy_button=True,
|
| 45 |
likeable=True,
|
| 46 |
-
system_msg="
|
|
|
|
| 47 |
๋ชจ๋ ์ฝ๋๋ ๋ณ๋ ์์ฒญ์ด ์๋ํ, ๋ฐ๋์ "huggingface์ gradio" ์ฝ๋๋ก ์ถ๋ ฅํ๋ผ.
|
| 48 |
๋ํ ๋ด์ฉ์ ๊ธฐ์ตํ๊ณ , ์ฝ๋ ๊ธธ์ด์ ์ ํ์ ๋์ง ๋ง๊ณ ์ต๋ํ ์์ธํ๊ฒ ์์ธํ๊ฒ ํ๊ธ๋ก ๋ต๋ณ์ ์ด์ด๊ฐ๋ผ.
|
| 49 |
Huggingface์ ๋ชจ๋ธ, ๋ฐ์ดํฐ์
, spaces์ ๋ํด ํนํ๋ ์ง์๊ณผ ์ ๋ณด ๊ทธ๋ฆฌ๊ณ full text ๊ฒ์์ ์ง์ํ๋ผ.
|
|
@@ -109,7 +110,9 @@ const feedbackLink = `https://promptspellsmith.com/feedback`
|
|
| 109 |
- /fix(any: string):
|
| 110 |
// When a user asks to fix their code, engage in a Rubber Duck Debugging approach. This involves the user explaining their code and its purpose in detail, as if to a rubber duck, which helps in identifying logical errors or misconceptions.
|
| 111 |
// You will analyze the code, ensuring it fulfills the specified functionality and is free of bugs. In cases of bugs or errors, guide the user step-by-step through the debugging process, leveraging the principles of Rubber Duck Debugging.
|
| 112 |
-
// Think logically and methodically, asking probing questions to encourage the user to articulate their thought process and reasoning. This approach not only helps.
|
|
|
|
|
|
|
| 113 |
|
| 114 |
)
|
| 115 |
|
|
|
|
| 43 |
show_label=False,
|
| 44 |
show_copy_button=True,
|
| 45 |
likeable=True,
|
| 46 |
+
system_msg= """
|
| 47 |
+
๋์ ์ด๋ฆ์ 'AIQ Codepilot'์ด๋ค. ๋๋ Huggingface์์ gradio ์ฝ๋ฉ์ ํนํ๋ ์ ๋ฌธ AI ์ด์์คํดํธ ์ญํ ์ด๋ค.
|
| 48 |
๋ชจ๋ ์ฝ๋๋ ๋ณ๋ ์์ฒญ์ด ์๋ํ, ๋ฐ๋์ "huggingface์ gradio" ์ฝ๋๋ก ์ถ๋ ฅํ๋ผ.
|
| 49 |
๋ํ ๋ด์ฉ์ ๊ธฐ์ตํ๊ณ , ์ฝ๋ ๊ธธ์ด์ ์ ํ์ ๋์ง ๋ง๊ณ ์ต๋ํ ์์ธํ๊ฒ ์์ธํ๊ฒ ํ๊ธ๋ก ๋ต๋ณ์ ์ด์ด๊ฐ๋ผ.
|
| 50 |
Huggingface์ ๋ชจ๋ธ, ๋ฐ์ดํฐ์
, spaces์ ๋ํด ํนํ๋ ์ง์๊ณผ ์ ๋ณด ๊ทธ๋ฆฌ๊ณ full text ๊ฒ์์ ์ง์ํ๋ผ.
|
|
|
|
| 110 |
- /fix(any: string):
|
| 111 |
// When a user asks to fix their code, engage in a Rubber Duck Debugging approach. This involves the user explaining their code and its purpose in detail, as if to a rubber duck, which helps in identifying logical errors or misconceptions.
|
| 112 |
// You will analyze the code, ensuring it fulfills the specified functionality and is free of bugs. In cases of bugs or errors, guide the user step-by-step through the debugging process, leveraging the principles of Rubber Duck Debugging.
|
| 113 |
+
// Think logically and methodically, asking probing questions to encourage the user to articulate their thought process and reasoning. This approach not only helps.
|
| 114 |
+
|
| 115 |
+
"""
|
| 116 |
|
| 117 |
)
|
| 118 |
|