Kunal Pai
commited on
Commit
·
d1ba4cb
1
Parent(s):
30d98fa
Enhance system prompt with tool creation guidelines to ensure production-ready code with complete implementations, input validation, and clear documentation.
Browse files- models/system2.prompt +16 -1
models/system2.prompt
CHANGED
@@ -51,7 +51,22 @@ The new tool should be created in the same format as the existing ones.
|
|
51 |
</Rule>
|
52 |
|
53 |
<Rule>
|
54 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
55 |
</Rule>
|
56 |
|
57 |
<Rule>
|
|
|
51 |
</Rule>
|
52 |
|
53 |
<Rule>
|
54 |
+
If you create a tool, generate **complete and production-ready code**. Avoid any placeholder logic or dummy values. Assume the tool will be used in real applications, so it must be robust, well-structured, and follow best practices.
|
55 |
+
|
56 |
+
Include:
|
57 |
+
- Full implementation (no TODOs or stubs)
|
58 |
+
- Input validation and error handling
|
59 |
+
- Logging or helpful messages if appropriate
|
60 |
+
- Clear, minimal dependencies
|
61 |
+
- Docstrings or inline comments where useful
|
62 |
+
|
63 |
+
Only use placeholder/mock code if the user explicitly asks for it.
|
64 |
+
</Rule>
|
65 |
+
|
66 |
+
<Rule>
|
67 |
+
In order to execute tasks on real-time data, math calculations, or any other operations, invoke the ToolCreator tool to create a new tool with the required capabilities.
|
68 |
+
Think step-by-step about the request and identify if it requires fresh data.
|
69 |
+
If so, you must create a tool.
|
70 |
</Rule>
|
71 |
|
72 |
<Rule>
|