Skip to content

docs(prompts): tell Prime Claude never to edit KBFuncs.nlp - #209

Merged
ddehilster merged 1 commit into
VisualText:mainfrom
ddehilster:docs/prime-claude-dont-edit-kbfuncs
Aug 24, 2026
Merged

docs(prompts): tell Prime Claude never to edit KBFuncs.nlp#209
ddehilster merged 1 commit into
VisualText:mainfrom
ddehilster:docs/prime-claude-dont-edit-kbfuncs

Conversation

@ddehilster

Copy link
Copy Markdown
Member

spec/KBFuncs.nlp is VisualText's shared knowledge base function library — it ships in the engine's spec/ library and in seven of the analyzer templates (Address Parser, Email Addresses, Knowledge Base, NLPPlus Interface, parse-en-us, Telephone Numbers, URLs), and SaveKB, JsonKB, AddUniqueCon and the rest all live there.

An analyzer is not the place to change it. An edit there is invisible to anyone reading your passes, drifts from the copy everyone else has, and is lost the moment the analyzer is recreated from the template.

The primer already told Claude to keep the Knowledge Base template's scaffolding, but never said the library file itself is off limits, and never said where new functions should go instead. It now says both: put your own functions in your own @DECL pass and add a nlp MyFuncs line to analyzer.seq after KBFuncs, calling the library's functions from there. The rule extends to the other shared library passes in the VisualText spec/ directory.

Placed as its own bullet directly after the "keep its scaffolding" bullet in the Knowledge Base template section.

Prompt text only — no engine, analyzer, or library files touched.

🤖 Generated with Claude Code

KBFuncs.nlp is VisualText's shared knowledge base function library —
it ships in the engine's spec/ library and in seven analyzer templates,
and SaveKB, JsonKB and AddUniqueCon all live there. An analyzer is not
the place to change it: the edit is invisible to anyone reading the
passes, drifts from the copy everyone else has, and is lost when the
analyzer is recreated from the template.
The primer already said to keep the scaffolding; it did not say the
library file is off limits or where new functions should go. It now
says both — add your own @decl pass and a `nlp MyFuncs` line to
analyzer.seq after KBFuncs — and extends the rule to the other shared
library passes in the VisualText spec/ directory.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@ddehilster
ddehilster merged commit 497ddbc into VisualText:mainAug 24, 2026
1 check passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@ddehilster