nimai-core 0.5.7 → 0.5.9
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 +22 -3
- package/dist/prompts.js.map +1 -1
- package/package.json +1 -1
package/dist/prompts.d.ts.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH;;;;;;;;;GASG;AACH,wBAAgB,iBAAiB,CAC/B,OAAO,EAAE,MAAM,EACf,QAAQ,EAAE,MAAM,EAChB,YAAY,EAAE,MAAM,EACpB,YAAY,EAAE,MAAM,GACnB,MAAM,
|
|
1
|
+
{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH;;;;;;;;;GASG;AACH,wBAAgB,iBAAiB,CAC/B,OAAO,EAAE,MAAM,EACf,QAAQ,EAAE,MAAM,EAChB,YAAY,EAAE,MAAM,EACpB,YAAY,EAAE,MAAM,GACnB,MAAM,CA8JR;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,aAAa,CAAC,WAAW,EAAE,MAAM,GAAG,MAAM,CAgHzD;AAED;;;;GAIG;AACH,wBAAgB,YAAY,CAAC,WAAW,EAAE,MAAM,GAAG,MAAM,CAgBxD"}
|
package/dist/prompts.js
CHANGED
|
@@ -154,10 +154,25 @@ PHASE 4 — GATE
|
|
|
154
154
|
1. Run nimai_validate on the spec (CLI: nimai validate <path>). Fix
|
|
155
155
|
structural issues and re-run until it passes.
|
|
156
156
|
2. Run nimai_review with target "spec" (CLI: nimai review <path>
|
|
157
|
-
--target spec).
|
|
158
|
-
|
|
157
|
+
--target spec). The reviewer must be independent of you, the drafter.
|
|
158
|
+
If your host supports sub-agents (a Task/agent tool), you MUST run the
|
|
159
|
+
review as a separate sub-agent given ONLY the spec and the reviewer
|
|
160
|
+
prompt — never your own drafting reasoning. A sub-agent is the
|
|
161
|
+
automatic way to get a clean-context reviewer; do not review in your
|
|
162
|
+
own context. If no sub-agent capability exists, ask the user to open
|
|
163
|
+
a fresh session. A sub-agent shares your model and therefore your
|
|
164
|
+
blind spots, so when your host can reach a different or more capable
|
|
165
|
+
model, prefer it for the review seat — independence of context AND of
|
|
166
|
+
model is the strongest gate.
|
|
159
167
|
3. Read the reviewer's verdict (the last fenced JSON block). If it has
|
|
160
|
-
|
|
168
|
+
FAIL issues, never leave the user wondering what to do next: name the
|
|
169
|
+
next step and recommend it — apply the remediation list, re-validate,
|
|
170
|
+
re-review. Asking for a simple go-ahead is fine ("Apply these and
|
|
171
|
+
re-review? (recommended)"); stopping with an open "what now?" that
|
|
172
|
+
strands a non-technical user is not. On a yes, apply the fixes and
|
|
173
|
+
return to step 1; repeat until the verdict passes. Pause for a real
|
|
174
|
+
decision only when it is genuinely the user's (a product or outcome
|
|
175
|
+
choice the fix list cannot settle on its own).
|
|
161
176
|
4. When the verdict passes, tell the user: "purification complete —
|
|
162
177
|
the spec is build-ready", and where it is saved. Your job ends here
|
|
163
178
|
— building is a separate session with a separate agent.
|
|
@@ -280,6 +295,10 @@ Write one actionable fix instruction per issue, in order. Each line must include
|
|
|
280
295
|
- exact section(s) to edit,
|
|
281
296
|
- concrete replacement/addition text direction.
|
|
282
297
|
|
|
298
|
+
## After this review — always know and name the next step
|
|
299
|
+
|
|
300
|
+
Never leave the user wondering what happens next. If the verdict has FAIL issues, the next step is: apply the remediation list above to the spec, re-run \`nimai_validate\`, then get a fresh re-review — repeated until the verdict passes. State that next step plainly and recommend it. Asking for a simple go-ahead is fine ("Apply these fixes and re-review? (recommended)") — what is not fine is stopping with an open "what do we do?" that strands a non-technical user. Name the step and your recommendation; proceed on a yes. Pause for a real decision only when it is genuinely the user's (a product or outcome choice a fix cannot settle). When the verdict passes, tell the user the spec is build-ready and where it is saved.
|
|
301
|
+
|
|
283
302
|
---
|
|
284
303
|
|
|
285
304
|
## Draft spec to review
|
package/dist/prompts.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":";AAAA;;;;;;;GAOG;;AAYH,
|
|
1
|
+
{"version":3,"file":"prompts.js","sourceRoot":"","sources":["../src/prompts.ts"],"names":[],"mappings":";AAAA;;;;;;;GAOG;;AAYH,8CAmKC;AAeD,sCAgHC;AAOD,oCAgBC;AAnUD;;;;;;;;;GASG;AACH,SAAgB,iBAAiB,CAC/B,OAAe,EACf,QAAgB,EAChB,YAAoB,EACpB,YAAoB;IAEpB,MAAM,UAAU,GAAG,+BAA+B,YAAY,iCAAiC,YAAY,EAAE,CAAC;IAE9G,OAAO;;;;WAIE,OAAO;cACJ,QAAQ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAqJpB,UAAU,EAAE,CAAC;AACf,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,SAAgB,aAAa,CAAC,WAAmB;IAC/C,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA8GP,WAAW,EAAE,CAAC;AAChB,CAAC;AAED;;;;GAIG;AACH,SAAgB,YAAY,CAAC,WAAmB;IAC9C,OAAO;;;;;;;;;;;;;;EAcP,WAAW,EAAE,CAAC;AAChB,CAAC"}
|