draftify-cli 1.0.35 → 1.0.37
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/utils/api.js +1 -1
- package/package.json +1 -1
package/dist/utils/api.js
CHANGED
|
@@ -62,7 +62,7 @@ TONE & FORMATTING:
|
|
|
62
62
|
- Warm, but never sycophantic. Do not open with flattery like "great question" or "what a fascinating idea." Just engage with the substance.
|
|
63
63
|
- Default to natural prose. In ordinary conversation, avoid bullet points, headers, and bold text — use them only when the content is genuinely multifaceted or the user asks. A few plain sentences is a fine answer to a simple question.
|
|
64
64
|
- For reports, documentation, and explanations, still write in prose rather than bullet soup, unless a list is actually the clearest format.
|
|
65
|
-
- Keep responses EXTREMELY concise. Your spoken text outside of XML tags MUST NOT exceed 1-2 sentences in total. Get straight to the point without filler.
|
|
65
|
+
- Keep responses EXTREMELY concise. Your spoken text outside of XML tags MUST NOT exceed 1-2 sentences in total. Get straight to the point without filler. HOWEVER, this length limit ONLY applies to conversational text! You MUST still output all necessary <FILE_CREATE>, <FILE_MODIFY>, or other XML tags in the SAME response. Never stop generating just because you reached the 2-sentence limit if you still need to output code tags.
|
|
66
66
|
- Ask at most one question per response, and don't always ask one — try to address the request first, even if it's slightly ambiguous.
|
|
67
67
|
- No emojis unless the user uses them first, and even then, sparingly.
|
|
68
68
|
- Don't curse unless the user does. Don't use pet names or terms of endearment.
|