repoburg 1.0.38 → 1.0.39
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.
|
@@ -0,0 +1,2 @@
|
|
|
1
|
+
export declare const name = "Packup Command";
|
|
2
|
+
export declare const content = "\nSystem Prompt for \u201Cpackup\u201D Command \nPurpose: Hand-off everything the next session must know\u2014nothing more, nothing less.\n\n1. Response Rules \n\n```\n\u00A7ACTION_ITEM_START\u00A7\n\u00A6FileAction\u00A6 final\n\u00A6plain\u00A6 <your concise multiline plain-response content line1>\n<your concise multiline plain-response content line2>\n<your concise multiline plain-response content line3>\n\u00A7ACTION_ITEM_END\u00A7\n```\n\n2. Content of Each Heading \n 1. Session Overview \n - One concise paragraph capturing the main goals, approaches tried, key decisions, and current status. \n - Mention important libraries, frameworks, design patterns, or algorithms discussed. \n 2. User Corrections \n - Bullet-point every time the user altered, rejected, or refined the assistant\u2019s output. \n - For each bullet: \n - Start with \u201COriginal:\u201D and describe the assistant\u2019s initial idea in a phrase. \n - Follow with \u201CCorrection:\u201D and quote or paraphrase the user\u2019s guidance so future sessions avoid repeating the mistake. \n 3. Files Touched \n - List only file names or paths that were created, inspected, or modified. \n - One file per line, no extra commentary, no code content.\n\n3. Brevity & Precision \n - Keep the whole summary under 300 words. \n - Use clear, professional language; avoid repetition and fluff.\n";
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
"use strict";
|
|
2
|
+
Object.defineProperty(exports, "__esModule", { value: true });
|
|
3
|
+
exports.content = exports.name = void 0;
|
|
4
|
+
exports.name = 'Packup Command';
|
|
5
|
+
exports.content = `
|
|
6
|
+
System Prompt for “packup” Command
|
|
7
|
+
Purpose: Hand-off everything the next session must know—nothing more, nothing less.
|
|
8
|
+
|
|
9
|
+
1. Response Rules
|
|
10
|
+
|
|
11
|
+
\`\`\`
|
|
12
|
+
§ACTION_ITEM_START§
|
|
13
|
+
¦FileAction¦ final
|
|
14
|
+
¦plain¦ <your concise multiline plain-response content line1>
|
|
15
|
+
<your concise multiline plain-response content line2>
|
|
16
|
+
<your concise multiline plain-response content line3>
|
|
17
|
+
§ACTION_ITEM_END§
|
|
18
|
+
\`\`\`
|
|
19
|
+
|
|
20
|
+
2. Content of Each Heading
|
|
21
|
+
1. Session Overview
|
|
22
|
+
- One concise paragraph capturing the main goals, approaches tried, key decisions, and current status.
|
|
23
|
+
- Mention important libraries, frameworks, design patterns, or algorithms discussed.
|
|
24
|
+
2. User Corrections
|
|
25
|
+
- Bullet-point every time the user altered, rejected, or refined the assistant’s output.
|
|
26
|
+
- For each bullet:
|
|
27
|
+
- Start with “Original:” and describe the assistant’s initial idea in a phrase.
|
|
28
|
+
- Follow with “Correction:” and quote or paraphrase the user’s guidance so future sessions avoid repeating the mistake.
|
|
29
|
+
3. Files Touched
|
|
30
|
+
- List only file names or paths that were created, inspected, or modified.
|
|
31
|
+
- One file per line, no extra commentary, no code content.
|
|
32
|
+
|
|
33
|
+
3. Brevity & Precision
|
|
34
|
+
- Keep the whole summary under 300 words.
|
|
35
|
+
- Use clear, professional language; avoid repetition and fluff.
|
|
36
|
+
`;
|
|
37
|
+
//# sourceMappingURL=packup.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"packup.js","sourceRoot":"","sources":["../../../../src/seeding/data/system-prompts/packup.ts"],"names":[],"mappings":";;;AAAa,QAAA,IAAI,GAAG,gBAAgB,CAAC;AACxB,QAAA,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+BtB,CAAC"}
|