whitesmith 0.0.6 → 0.0.7
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/prompts.d.ts.map +1 -1
- package/dist/prompts.js +27 -7
- package/dist/prompts.js.map +1 -1
- package/package.json +1 -1
- package/src/prompts.ts +27 -7
package/dist/prompts.d.ts.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAC,KAAK,EAAE,IAAI,EAAC,MAAM,YAAY,CAAC;AAE5C;;;GAGG;AACH,wBAAgB,sBAAsB,CAAC,KAAK,EAAE,KAAK,EAAE,aAAa,EAAE,MAAM,GAAG,MAAM,
|
|
1
|
+
{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAC,KAAK,EAAE,IAAI,EAAC,MAAM,YAAY,CAAC;AAE5C;;;GAGG;AACH,wBAAgB,sBAAsB,CAAC,KAAK,EAAE,KAAK,EAAE,aAAa,EAAE,MAAM,GAAG,MAAM,CAuGlF;AAID,MAAM,WAAW,sBAAsB;IACtC,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,EAAE,MAAM,CAAC;IACnB,SAAS,EAAE,MAAM,CAAC;IAClB,QAAQ,EAAE,MAAM,CAAC;IACjB,KAAK,EAAE,KAAK,CAAC;QAAC,EAAE,EAAE,MAAM,CAAC;QAAC,KAAK,EAAE,MAAM,CAAC;QAAC,OAAO,EAAE,MAAM,CAAC;QAAC,QAAQ,EAAE,MAAM,CAAA;KAAC,CAAC,CAAC;IAC7E,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,YAAY,EAAE,MAAM,CAAC;CACrB;AAED;;;GAGG;AACH,wBAAgB,6BAA6B,CAAC,IAAI,EAAE,sBAAsB,GAAG,MAAM,CA+DlF;AAED,MAAM,WAAW,0BAA0B;IAC1C,QAAQ,EAAE,MAAM,CAAC;IACjB,OAAO,EAAE,MAAM,CAAC;IAChB,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,CAAC;IACjB,KAAK,EAAE,MAAM,CAAC;IACd,WAAW,CAAC,EAAE;QACb,MAAM,EAAE,MAAM,CAAC;QACf,KAAK,EAAE,MAAM,CAAC;QACd,IAAI,EAAE,MAAM,CAAC;QACb,GAAG,EAAE,MAAM,CAAC;KACZ,CAAC;IACF,YAAY,EAAE,MAAM,CAAC;CACrB;AAED;;;GAGG;AACH,wBAAgB,iCAAiC,CAAC,IAAI,EAAE,0BAA0B,GAAG,MAAM,CA+D1F;AAED,MAAM,WAAW,wBAAwB;IACxC,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,EAAE,MAAM,CAAC;IACnB,SAAS,EAAE,MAAM,CAAC;IAClB,QAAQ,EAAE,MAAM,CAAC;IACjB,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,UAAU,EAAE,MAAM,CAAC;IACnB,YAAY,EAAE,MAAM,CAAC;CACrB;AAED;;;GAGG;AACH,wBAAgB,+BAA+B,CAAC,IAAI,EAAE,wBAAwB,GAAG,MAAM,CA0DtF;AAED;;;GAGG;AACH,wBAAgB,sBAAsB,IAAI,MAAM,CAS/C;AAED;;;GAGG;AACH,wBAAgB,yBAAyB,CAAC,iBAAiB,EAAE,MAAM,GAAG,MAAM,CAW3E;AAED;;;GAGG;AACH,wBAAgB,oBAAoB,CAAC,IAAI,EAAE,IAAI,EAAE,KAAK,EAAE,KAAK,GAAG,MAAM,CAwCrE"}
|
package/dist/prompts.js
CHANGED
|
@@ -15,9 +15,10 @@ ${issue.body}
|
|
|
15
15
|
## Your Job
|
|
16
16
|
|
|
17
17
|
You are an AI assistant helping break down a GitHub issue into concrete implementation tasks.
|
|
18
|
+
**Important:** The agent implementing these tasks will start with a fresh context — no knowledge of the issue discussion or your investigation. Each task must be **fully self-contained** with enough detail that the implementer can work without guessing.
|
|
18
19
|
|
|
19
20
|
1. **Read and understand** the issue above.
|
|
20
|
-
2. **Explore the codebase** to understand the architecture, conventions, and relevant code.
|
|
21
|
+
2. **Explore the codebase thoroughly** to understand the architecture, conventions, and relevant code. Identify the specific files, functions, and patterns that will need to change.
|
|
21
22
|
3. **Break the issue down** into 1 or more tasks. Each task should represent a single, reviewable PR's worth of work.
|
|
22
23
|
4. **Write task files** to the \`${issueTasksDir}\` directory.
|
|
23
24
|
|
|
@@ -34,14 +35,22 @@ depends_on: []
|
|
|
34
35
|
---
|
|
35
36
|
|
|
36
37
|
## Description
|
|
37
|
-
<
|
|
38
|
+
<Detailed description of what needs to be done. Include:
|
|
39
|
+
- The specific behavior to add/change/fix and WHY
|
|
40
|
+
- Which files and functions to modify (use exact paths from your codebase exploration)
|
|
41
|
+
- How the change fits into the existing architecture
|
|
42
|
+
- Any edge cases or constraints to handle>
|
|
38
43
|
|
|
39
44
|
## Acceptance Criteria
|
|
40
|
-
- <criterion
|
|
41
|
-
- <criterion
|
|
45
|
+
- <Specific, verifiable criterion — e.g., "calling X with Y returns Z" not "works correctly">
|
|
46
|
+
- <Another criterion>
|
|
42
47
|
|
|
43
48
|
## Implementation Notes
|
|
44
|
-
<
|
|
49
|
+
<Concrete guidance for the implementer:
|
|
50
|
+
- Exact file paths to create or modify
|
|
51
|
+
- Existing patterns or utilities to reuse (with file paths)
|
|
52
|
+
- Code snippets or signatures when helpful for clarity
|
|
53
|
+
- Any gotchas, non-obvious conventions, or things to avoid>
|
|
45
54
|
\`\`\`
|
|
46
55
|
|
|
47
56
|
## Rules
|
|
@@ -50,7 +59,12 @@ depends_on: []
|
|
|
50
59
|
- The \`id\` field must be \`"${issue.number}-<seq>"\` (e.g., "${issue.number}-001").
|
|
51
60
|
- Use \`depends_on\` to list task IDs that must be completed before this task. For example, if task 002 depends on task 001, set \`depends_on: ["${issue.number}-001"]\`.
|
|
52
61
|
- Each task should be a meaningful, self-contained unit of work that results in one PR.
|
|
53
|
-
- Be specific
|
|
62
|
+
- **Be extremely specific.** The implementing agent starts with zero context. Include:
|
|
63
|
+
- Exact file paths discovered during your codebase exploration
|
|
64
|
+
- Function/class names to modify or create
|
|
65
|
+
- Existing patterns to follow (reference specific files as examples)
|
|
66
|
+
- Expected behavior changes with concrete examples
|
|
67
|
+
- Acceptance criteria must be **verifiable** — not vague ("works correctly") but testable ("function X returns Y when given Z").
|
|
54
68
|
- Consider the existing codebase patterns and conventions.
|
|
55
69
|
- Create the \`${issueTasksDir}\` directory if it doesn't exist.
|
|
56
70
|
|
|
@@ -73,7 +87,13 @@ If the issue is **ambiguous, unclear, or needs more information** before you can
|
|
|
73
87
|
|
|
74
88
|
The file should contain a brief summary of what was understood, followed by numbered questions that need to be answered before tasks can be generated.
|
|
75
89
|
|
|
76
|
-
|
|
90
|
+
**When to use this escape hatch:** If you find yourself needing to make significant assumptions about the desired behavior, scope, or approach — ask rather than guess. Specifically:
|
|
91
|
+
- The issue describes a problem but not the desired solution, and multiple valid approaches exist
|
|
92
|
+
- Key details are missing (e.g., which API format, what error behavior, which edge cases matter)
|
|
93
|
+
- The issue references context you cannot find in the codebase
|
|
94
|
+
- You cannot produce acceptance criteria that are concrete and verifiable without guessing
|
|
95
|
+
|
|
96
|
+
If the issue is reasonably clear and you can produce detailed, actionable tasks, generate them.
|
|
77
97
|
|
|
78
98
|
## When Done
|
|
79
99
|
|
package/dist/prompts.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAEA;;;GAGG;AACH,MAAM,UAAU,sBAAsB,CAAC,KAAY,EAAE,aAAqB;IACzE,OAAO,oDAAoD,KAAK,CAAC,MAAM;;;aAG3D,KAAK,CAAC,KAAK;WACb,KAAK,CAAC,GAAG;;;EAGlB,KAAK,CAAC,IAAI
|
|
1
|
+
{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAEA;;;GAGG;AACH,MAAM,UAAU,sBAAsB,CAAC,KAAY,EAAE,aAAqB;IACzE,OAAO,oDAAoD,KAAK,CAAC,MAAM;;;aAG3D,KAAK,CAAC,KAAK;WACb,KAAK,CAAC,GAAG;;;EAGlB,KAAK,CAAC,IAAI;;;;;;;;;;mCAUuB,aAAa;;;;;;;;OAQzC,KAAK,CAAC,MAAM;SACV,KAAK,CAAC,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;gCA2BW,KAAK,CAAC,MAAM,qBAAqB,KAAK,CAAC,MAAM;mJACsE,KAAK,CAAC,MAAM;;;;;;;;;iBAS9I,aAAa;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;wBAkCN,KAAK,CAAC,MAAM;;;;CAInC,CAAC;AACF,CAAC;AAcD;;;GAGG;AACH,MAAM,UAAU,6BAA6B,CAAC,IAA4B;IACzE,MAAM,QAAQ,GAAG,IAAI,CAAC,KAAK;SACzB,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,YAAY,CAAC,CAAC,EAAE,KAAK,CAAC,CAAC,KAAK,mBAAmB,CAAC,CAAC,QAAQ,SAAS,CAAC,CAAC,OAAO,EAAE,CAAC;SACzF,IAAI,CAAC,aAAa,CAAC,CAAC;IAEtB,OAAO,sCAAsC,IAAI,CAAC,WAAW;;;aAGjD,IAAI,CAAC,UAAU;WACjB,IAAI,CAAC,QAAQ;;;EAGtB,IAAI,CAAC,SAAS;EACd,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC,kBAAkB,IAAI,CAAC,SAAS,IAAI,CAAC,CAAC,CAAC,EAAE;;;EAG1D,QAAQ,IAAI,wBAAwB;;;;;;;;;;;;;;;;;;;;;;gCAsBN,IAAI,CAAC,YAAY;;;;;;;;;;;;;;;;;;;;;;uCAsBV,IAAI,CAAC,YAAY;;CAEvD,CAAC;AACF,CAAC;AAiBD;;;GAGG;AACH,MAAM,UAAU,iCAAiC,CAAC,IAAgC;IACjF,MAAM,YAAY,GAAG,IAAI,CAAC,WAAW;QACpC,CAAC,CAAC,yBAAyB,IAAI,CAAC,WAAW,CAAC,MAAM,OAAO,IAAI,CAAC,WAAW,CAAC,KAAK,cAAc,IAAI,CAAC,WAAW,CAAC,GAAG,8BAA8B,IAAI,CAAC,WAAW,CAAC,IAAI,IAAI;QACxK,CAAC,CAAC,EAAE,CAAC;IAEN,OAAO,2BAA2B,IAAI,CAAC,QAAQ;;;aAGnC,IAAI,CAAC,OAAO;WACd,IAAI,CAAC,KAAK;cACP,IAAI,CAAC,QAAQ;;;EAGzB,IAAI,CAAC,MAAM;EACX,YAAY;;;;KAIT,IAAI,CAAC,QAAQ;;;;;;;;;;;;;;;;;;;;gCAoBc,IAAI,CAAC,YAAY;;;;;;;;;;;;;;;;;;;;;;uCAsBV,IAAI,CAAC,YAAY;;CAEvD,CAAC;AACF,CAAC;AAYD;;;GAGG;AACH,MAAM,UAAU,+BAA+B,CAAC,IAA8B;IAC7E,OAAO,wCAAwC,IAAI,CAAC,WAAW;;;aAGnD,IAAI,CAAC,UAAU;WACjB,IAAI,CAAC,QAAQ;EACtB,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC,0BAA0B,IAAI,CAAC,SAAS,IAAI,CAAC,CAAC,CAAC,EAAE;;EAElE,IAAI,CAAC,SAAS;;;;;uBAKO,IAAI,CAAC,UAAU;;;;;;;;;;;;;;;;;;yEAkBmC,IAAI,CAAC,WAAW;;gCAEzD,IAAI,CAAC,YAAY;;;;;;;;;;;;;;;;;;;;;;uCAsBV,IAAI,CAAC,YAAY;;CAEvD,CAAC;AACF,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,sBAAsB;IACrC,OAAO;;;;;;;yEAOiE,CAAC;AAC1E,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,yBAAyB,CAAC,iBAAyB;IAClE,OAAO;;EAEN,iBAAiB,CAAC,IAAI,EAAE;;;;;;;qEAO2C,CAAC;AACtE,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,oBAAoB,CAAC,IAAU,EAAE,KAAY;IAC5D,OAAO,sBAAsB,IAAI,CAAC,KAAK;;;;2DAImB,KAAK,CAAC,MAAM,MAAM,KAAK,CAAC,KAAK;;iBAEvE,KAAK,CAAC,GAAG;eACX,IAAI,CAAC,EAAE;iBACL,IAAI,CAAC,QAAQ;;;;EAI5B,IAAI,CAAC,OAAO;;;;;;;;mCAQqB,IAAI,CAAC,QAAQ;iDACC,IAAI,CAAC,KAAK;;;;;uBAKpC,KAAK,CAAC,MAAM,MAAM,IAAI,CAAC,KAAK;;;;;;;;;sBAS7B,IAAI,CAAC,QAAQ;mBAChB,IAAI,CAAC,KAAK;;CAE5B,CAAC;AACF,CAAC"}
|
package/package.json
CHANGED
package/src/prompts.ts
CHANGED
|
@@ -17,9 +17,10 @@ ${issue.body}
|
|
|
17
17
|
## Your Job
|
|
18
18
|
|
|
19
19
|
You are an AI assistant helping break down a GitHub issue into concrete implementation tasks.
|
|
20
|
+
**Important:** The agent implementing these tasks will start with a fresh context — no knowledge of the issue discussion or your investigation. Each task must be **fully self-contained** with enough detail that the implementer can work without guessing.
|
|
20
21
|
|
|
21
22
|
1. **Read and understand** the issue above.
|
|
22
|
-
2. **Explore the codebase** to understand the architecture, conventions, and relevant code.
|
|
23
|
+
2. **Explore the codebase thoroughly** to understand the architecture, conventions, and relevant code. Identify the specific files, functions, and patterns that will need to change.
|
|
23
24
|
3. **Break the issue down** into 1 or more tasks. Each task should represent a single, reviewable PR's worth of work.
|
|
24
25
|
4. **Write task files** to the \`${issueTasksDir}\` directory.
|
|
25
26
|
|
|
@@ -36,14 +37,22 @@ depends_on: []
|
|
|
36
37
|
---
|
|
37
38
|
|
|
38
39
|
## Description
|
|
39
|
-
<
|
|
40
|
+
<Detailed description of what needs to be done. Include:
|
|
41
|
+
- The specific behavior to add/change/fix and WHY
|
|
42
|
+
- Which files and functions to modify (use exact paths from your codebase exploration)
|
|
43
|
+
- How the change fits into the existing architecture
|
|
44
|
+
- Any edge cases or constraints to handle>
|
|
40
45
|
|
|
41
46
|
## Acceptance Criteria
|
|
42
|
-
- <criterion
|
|
43
|
-
- <criterion
|
|
47
|
+
- <Specific, verifiable criterion — e.g., "calling X with Y returns Z" not "works correctly">
|
|
48
|
+
- <Another criterion>
|
|
44
49
|
|
|
45
50
|
## Implementation Notes
|
|
46
|
-
<
|
|
51
|
+
<Concrete guidance for the implementer:
|
|
52
|
+
- Exact file paths to create or modify
|
|
53
|
+
- Existing patterns or utilities to reuse (with file paths)
|
|
54
|
+
- Code snippets or signatures when helpful for clarity
|
|
55
|
+
- Any gotchas, non-obvious conventions, or things to avoid>
|
|
47
56
|
\`\`\`
|
|
48
57
|
|
|
49
58
|
## Rules
|
|
@@ -52,7 +61,12 @@ depends_on: []
|
|
|
52
61
|
- The \`id\` field must be \`"${issue.number}-<seq>"\` (e.g., "${issue.number}-001").
|
|
53
62
|
- Use \`depends_on\` to list task IDs that must be completed before this task. For example, if task 002 depends on task 001, set \`depends_on: ["${issue.number}-001"]\`.
|
|
54
63
|
- Each task should be a meaningful, self-contained unit of work that results in one PR.
|
|
55
|
-
- Be specific
|
|
64
|
+
- **Be extremely specific.** The implementing agent starts with zero context. Include:
|
|
65
|
+
- Exact file paths discovered during your codebase exploration
|
|
66
|
+
- Function/class names to modify or create
|
|
67
|
+
- Existing patterns to follow (reference specific files as examples)
|
|
68
|
+
- Expected behavior changes with concrete examples
|
|
69
|
+
- Acceptance criteria must be **verifiable** — not vague ("works correctly") but testable ("function X returns Y when given Z").
|
|
56
70
|
- Consider the existing codebase patterns and conventions.
|
|
57
71
|
- Create the \`${issueTasksDir}\` directory if it doesn't exist.
|
|
58
72
|
|
|
@@ -75,7 +89,13 @@ If the issue is **ambiguous, unclear, or needs more information** before you can
|
|
|
75
89
|
|
|
76
90
|
The file should contain a brief summary of what was understood, followed by numbered questions that need to be answered before tasks can be generated.
|
|
77
91
|
|
|
78
|
-
|
|
92
|
+
**When to use this escape hatch:** If you find yourself needing to make significant assumptions about the desired behavior, scope, or approach — ask rather than guess. Specifically:
|
|
93
|
+
- The issue describes a problem but not the desired solution, and multiple valid approaches exist
|
|
94
|
+
- Key details are missing (e.g., which API format, what error behavior, which edge cases matter)
|
|
95
|
+
- The issue references context you cannot find in the codebase
|
|
96
|
+
- You cannot produce acceptance criteria that are concrete and verifiable without guessing
|
|
97
|
+
|
|
98
|
+
If the issue is reasonably clear and you can produce detailed, actionable tasks, generate them.
|
|
79
99
|
|
|
80
100
|
## When Done
|
|
81
101
|
|