Skip to content

docs(prompts): tell Prime Claude that .dict and .kbb are the KB source files - #207

Merged
ddehilster merged 1 commit into
VisualText:mainfrom
ddehilster:docs/prime-claude-kbb-dict
Aug 21, 2026
Merged

docs(prompts): tell Prime Claude that .dict and .kbb are the KB source files#207
ddehilster merged 1 commit into
VisualText:mainfrom
ddehilster:docs/prime-claude-kbb-dict

Conversation

@ddehilster

Copy link
Copy Markdown
Member

Priming a fresh Claude session on Prime Claude for NLP++ sent it straight into the Knowledge Base template's kb/user/*.kb files — attr.kb, hier.kb, phr.kb, word.kb — to "study the knowledge base." Those are the engine's runtime dump, not files anyone authors, and hier.kb alone is 33 KB, so it is the biggest and first thing an exploring agent finds in that folder.

Changes

  • The analyzer-structure paragraph now says kb/user/ holds the knowledge base sources, states that .dict dictionaries and .kbb knowledge base files are the only KB files to read or write, and names the four .kb files as engine output — not to be read as examples, copied, or hand-edited.
  • The engine-facts bullet becomes "Dictionaries and knowledge bases": it now describes what a .kbb is (indented concept hierarchy with attributes, paired with the .dict of the same stem) and repeats that .kb files are engine output.

Also folds in the pending "build on the libraries, never on hand-typed word lists" rules of thumb that were sitting uncommitted on the merged feat/english-nationalities branch: look in the language/misc libraries before hand-typing a vocabulary, wire one in by copying the .dict/.kbb pair into kb/user/, match on dictionary attributes rather than words, match _phrase as well as _xALPHA, join on a stable attribute rather than $text, and extend the library file (or its generator) instead of hard-coding missing words in a pass.

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

🤖 Generated with Claude Code

…e files
Priming a fresh session on this prompt sent Claude straight into the
Knowledge Base template's kb/user/*.kb files (attr.kb, hier.kb, phr.kb,
word.kb) to "study the knowledge base" — those are the engine's runtime
dump, not files anyone authors. hier.kb alone is 33 KB, so it is the
first thing an exploring agent finds.
Say it plainly instead: kb/user holds the KB *sources*, and .dict and
.kbb are the only KB files to read or write. Name the .kb files as
engine output that must not be read as examples or hand-edited, and
repeat the point in the engine-facts bullet, which now also describes
what a .kbb is and how it pairs with the .dict of the same stem.
Also folds in the pending "build on the libraries" rules of thumb: look
in the language/misc libraries before hand-typing a vocabulary, wire one
in by copying the .dict/.kbb pair into kb/user, match on dictionary
attributes rather than words, match _phrase as well as _xALPHA, join on
a stable attribute rather than $text, and extend the library file (or
its generator) instead of hard-coding missing words in a pass.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@ddehilster
ddehilster merged commit f8556b8 into VisualText:mainAug 21, 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