@onthink/prompt-observer 0.1.0 → 0.1.1

package/PROMPT_OBSERVER.md

@@ -10,6 +10,8 @@ Follow this contract after every user-requested task. Complete the task first, t
 4. Do not invent the model name, token counts, or cost. Use `null` values with `source: "unavailable"` unless the platform explicitly reports them. Use `source: "estimated"` only when a deterministic tokenizer or pricing tool produced the value, and name that tool in `estimation_method`.
 5. Base execution signals only on observed results. Do not claim a file changed or a test passed without evidence.
 6. Use schema version `1.0` and conform to `.prompt-observer/event.schema.json`.
+7. Do not manufacture criticism. If the prompt is clear and sufficient for the task, keep `weaknesses` and `improvement_suggestions` empty.
+8. Evaluate against objective task requirements, not personal preferences about wording, tone, verbosity, formatting, workflow, or technology choices.
 
 ## Required workflow
 
@@ -30,7 +32,7 @@ After completing a task:
    ```text
    Prompt Insight: <average>/10 — <short strength>
    Main weakness: <highest-impact weakness, or "No material weakness detected">
-   Next time: <one actionable improvement>
+   Next time: <one actionable improvement, or "No change needed">
    ```
 
 Do not paste the complete JSON event into the user-facing response when persistence succeeds.
@@ -51,6 +53,15 @@ If writing files or running the logger is unavailable, do not pretend the event
 
 Score only prompt quality. Do not lower a score because implementation was difficult when the request itself was clear.
 
+## Evidence threshold and neutrality
+
+- Record a weakness only when a concrete omission, ambiguity, contradiction, or constraint creates a meaningful risk of wrong execution, wasted work, or unverifiable completion.
+- Do not require context, constraints, acceptance criteria, output formatting, or tests when they are unnecessary for the specific task.
+- Do not criticize a prompt merely because it could be longer, more formal, more structured, or written in a style you prefer.
+- Do not turn optional enhancements into weaknesses.
+- When no material weakness exists, use an empty `weaknesses` array, an empty `improvement_suggestions` array, `Main weakness: No material weakness detected`, and `Next time: No change needed`.
+- Positive scores must reflect the prompt as written; do not lower them just to create variation or appear critical.
+
 ## Event example
 
 ```json
@@ -60,26 +71,18 @@ Score only prompt quality. Do not lower a score because implementation was diffi
   "timestamp": "2026-09-01T12:00:00.000Z",
   "task_type": "coding",
   "prompt_summary": "Implement a dependency-free prompt observation kit with structured local logging.",
-  "intent_clarity": 9,
-  "context_sufficiency": 8,
-  "scope_definition": 9,
-  "constraints_quality": 9,
-  "acceptance_criteria": 8,
-  "verification_plan": 7,
+  "intent_clarity": 10,
+  "context_sufficiency": 10,
+  "scope_definition": 10,
+  "constraints_quality": 10,
+  "acceptance_criteria": 9,
+  "verification_plan": 9,
   "ambiguity_risk": "low",
   "strengths": [
     "The requested deliverables and runtime constraints are explicit."
   ],
-  "weaknesses": [
-    {
-      "category": "missing_verification",
-      "severity": "low",
-      "message": "The exact expected report contents were not fully enumerated."
-    }
-  ],
-  "improvement_suggestions": [
-    "List the required report sections and one expected example."
-  ],
+  "weaknesses": [],
+  "improvement_suggestions": [],
   "execution_signals": {
     "result_status": "completed",
     "files_changed": [

package/README.md

@@ -4,6 +4,8 @@ Prompt Observer is a dependency-free observability kit for professional coding-a
 
 It is designed for Vibe Coding workflows and works without a browser extension, a local model, or an additional AI API. The agent already completing the task creates the observation.
 
+[View the package on npm](https://www.npmjs.com/package/@onthink/prompt-observer)
+
 ## What it records
 
 - Prompt-quality dimensions: clarity, context, scope, constraints, acceptance criteria, and verification plan
@@ -13,6 +15,8 @@ It is designed for Vibe Coding workflows and works without a browser extension,
 
 Raw prompts, raw responses, private reasoning, system instructions, and secrets are prohibited from the event format.
 
+Prompt Observer does not force criticism. A clear, sufficient prompt receives no fabricated weakness or subjective style advice; its `weaknesses` and `improvement_suggestions` arrays remain empty.
+
 ## Requirements
 
 - Node.js 20 or newer
@@ -21,14 +25,15 @@ Raw prompts, raw responses, private reasoning, system instructions, and secrets
 
 ## Quick start
 
-Clone this repository and initialize Prompt Observer in a target project:
+Initialize Prompt Observer in any target project:
 
 ```powershell
-git clone <your-repository-url>
-cd prompt-observer
-node bin/prompt-observer.mjs init "E:\path\to\your-project"
+cd "E:\path\to\your-project"
+npx @onthink/prompt-observer init .
 ```
 
+`init` adds a portable local CLI under `.prompt-observer`, so the target project can log events and generate reports without a global installation.
+
 Then add the following one-line instruction to the target project's existing agent-instruction file:
 
 ```md
@@ -78,17 +83,17 @@ The report includes average prompt health, recurring weaknesses, ambiguity risk,
 
 When an agent cannot write files, the contract requires it to show the three-line insight and return a complete valid JSON event in a fenced `json` block. It must state that the event was not persisted. A later extension or integration can capture that output automatically.
 
-## npm package — coming soon
+## npm package
 
-The project is configured for npm packaging, but it is **not published yet**. The final package name will be chosen before release, preferably as a scoped name such as `@your-npm-username/prompt-observer`.
+Prompt Observer is published as [`@onthink/prompt-observer`](https://www.npmjs.com/package/@onthink/prompt-observer).
 
-After publication, the intended installation flow will be:
+Use it without installing it globally:
 
 ```powershell
-npx @your-npm-username/prompt-observer init .
+npx @onthink/prompt-observer init .
 ```
 
-Before publishing, replace `@your-npm-username` with your real npm scope and configure the repository URL in `package.json`.
+Running `init` again is safe: it preserves existing Prompt Observer files and adds only missing files.
 
 ## Development
 
@@ -97,7 +102,7 @@ npm run check
 npm test
 ```
 
-`prepublishOnly` runs both checks automatically before `npm publish`. The package uses only Node.js built-ins; JSONL is the source of truth for v1, while SQLite export is intentionally deferred to a later release.
+`prepublishOnly` runs both checks automatically before `npm publish`. The package is published publicly under the `@onthink` scope. The project uses only Node.js built-ins; JSONL is the source of truth for v1, while SQLite export is intentionally deferred to a later release.
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@onthink/prompt-observer",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "A dependency-free prompt observability contract and CLI for coding agents.",
   "keywords": [
     "ai",
@@ -30,6 +30,9 @@
   },
   "homepage": "https://github.com/daniialHZ/prompt-observer#readme",
   "license": "MIT",
+  "publishConfig": {
+    "access": "public"
+  },
   "files": [
     "bin/",
     "schema/",