xiaolai/nlpm-for-claude — Prompt Excerpts
Excerpt 1: The 50 Rules — Universal Examples (from skills/nlpm/rules/SKILL.md)
Technique: Bad/Good paired examples for every rule
**R01. No vague quantifiers without criteria.** "appropriate", "relevant", "as needed",
"sufficient", "adequate", "reasonable", "properly", "correctly", "some", "several", "various"
are meaningless without specifics. Replace with measurable criteria. Penalty: -2 each, cap -20.
Bad: "Use appropriate error handling."
Good: "Return `Result<T, AppError>` from all API handlers. Map errors to HTTP status codes
via the `From<AppError> for StatusCode` impl."
**R04. Description is a trigger, not a summary.** 3+ specific action phrases matching real
user queries. "Use when debugging React re-renders, fixing hook dependency arrays, optimizing
with useMemo" — not "Helpful React skill."
**R10. Model must match task complexity.** haiku = mechanical (parsing, counting). sonnet =
reasoning (analysis, review). opus = complex judgment (orchestration). Wrong tier wastes
money or produces weak results.
Analysis: Each rule has a named penalty, a concrete bad example, and a concrete good example. R10 is particularly notable — it encodes a cost-correctness tradeoff as a rule, preventing both over-spending (using opus for parsing) and under-spending (using haiku for complex orchestration).
Excerpt 2: Scorer Agent Instructions (from agents/scorer.md)
Technique: 5-step verification gate before reporting findings
## Do Not Invent Findings
Apply ONLY penalties enumerated in `nlpm:scoring`. Do not invent penalty categories. Before
reporting any finding, run this 5-step check:
1. **Rubric check** — Does the penalty appear in the `nlpm:scoring` penalty tables for this
artifact type? If no, do not report (unless marked...
Analysis: The "5-step check before reporting" is an anti-hallucination gate specifically for the scoring agent. It prevents the scorer from inventing rules or over-applying penalties. This is a meta-level quality gate on the quality checker itself.
Excerpt 3: Manifest-vs-Disk Check Rationale (from README)
Technique: Gap analysis embedded as motivation for the tool's existence
NLPM is the only multi-tool NL artifact validator that systematically checks
**manifest-vs-disk consistency** — the bug class where a SKILL.md exists on disk but is
silently missing from `plugin.json` (and therefore invisible after `claude plugin install`).
Verified across 8+ tools including Anthropic's official `plugin-validator` and the Linux
Foundation's `skills-ref`. See `analysis/ecosystem-gap.md` for the research.
Analysis: The tool's primary unique value proposition is stated as a named bug class (manifest-vs-disk inconsistency) with a specific mechanism (silently invisible after install), validated against 8 competing tools. The analysis/ecosystem-gap.md file documents the evidence — this is a research-backed positioning claim, not marketing.