class: describe

register: terse

template: {subject}: {kind} in {location}.


register: friendly

template: {subject} is a {kind} living in {location}.


template: {subject} is a {kind} in {location} — "{doc}".


template: {subject} imports {objects}.


template: {subject} is imported by {objects}.


template: {subject} is called by {objects}.


template: {subject} calls {objects}.


template: {subject} contains {objects}.


template: {subject} inherits from {object}.


template: {subject} is exercised by {objects}.


template: I can't see any test that imports {subject} — that may just mean the coverage is indirect.


template: {subject} was last touched by {commit} ({when}): "{message}".


template: {subject} {predicate} {object}.


template: As I understand it, a {subject} is a kind of {object}.


class: count

template: There are {count} {noun} in {scope}.


template: There is exactly one {noun} in {scope}: {subject}.


template: I can't find any {noun} in {scope}.


template: {count} {noun} in {scope} — for example {examples}.


template: {count} {noun} — {comparison} for a codebase of this size.


class: miss

template: I couldn't ground "{query}" in anything I know. I'd rather say so than guess.


template: I don't recognise "{query}". If you name a module, function, or class I know about, I can work from there.


template: "{query}" didn't match anything. Try a shape like "{example}" — that's a question I can answer precisely.


template: Nothing matches "{query}" exactly. The nearest name I know is {nearest} — is that what you meant?


template: No "{query}". Nearest: {nearest}.


template: My graph is empty right now, so I can't answer "{query}" yet. Tell me things and I'll remember them.


template: That sounds like it's outside my patch — I only really know about {scope}. Ask me about the code and I'm much more useful.


class: ambiguity

template: That could go two ways. If you mean {a} then {aAnswer}; if you mean {b} then {bAnswer}.


template: {a}: {aAnswer} / {b}: {bAnswer}.


template: I see three readings. If you mean {a} then {aAnswer}; if you mean {b} then {bAnswer}; if you mean {c} then {cAnswer}.


template: "{query}" names more than one thing here: {candidates}. Which one do you mean?


template: "{query}" is ambiguous: {candidates}.


template: Reading "{query}" as a {a} gives one answer, reading it as a {b} gives another. Say which and I'll commit.


class: assumption

template: I'll assume you're asking about {assumed} — say otherwise and I'll drop that.


template: I read "{query}" as {assumed} (closest name I know). {answer}


template: I'm assuming "{query}" is about this repository. {answer}


template: You didn't say which {noun}, so I took the most recent one: {assumed}.


template: Several things match; I picked the strongest, {assumed}. The runners-up were {others}.


class: recall

template: You told me earlier that {fact}.


template: Earlier in this session ({when}) you said "{utterance}".


template: In a previous session you told me that {fact} — I'm going on that.


template: My corpus says {fact} — that's background knowledge, not something you told me.


template: Careful — you told me earlier that {fact}, which doesn't sit well with "{query}". Which should I keep?


template: You asked something similar before ("{utterance}") and the answer was: {answer}


template: You haven't told me anything about {subject} yet.


class: stored

template: Noted: {subject} {predicate} {object}. I'll remember that.


template: Stored: {subject} {predicate} {object}.


template: I already knew that {subject} {predicate} {object} — nothing new to store.


class: nudge

template: The closer you get to a shape like "{example}", the sharper my answer gets.


template: If prose fails you, the slash commands always work — try {command}.


template: That matched {count} things — too many to be useful. Narrow it with a module or class name.


class: conversational

template: Hi. Ask me about this codebase — imports, calls, definitions, history — or /help.


template: Hello there. Ask me about this codebase, or /help.


template: Good morning. Ask me about this codebase, or /help.


template: Good afternoon. Ask me about this codebase, or /help.


template: Good evening. Ask me about this codebase, or /help.


template: Any time. Ask another, or /help for what I can do.


template: Bye — flushing the session log. Come back with a question any time.


template: No worries. Ask another, or /help for what I can do.


class: orientation

template:
I'm tmct — a deterministic, offline code-graph assistant (no LLM). I answer questions about THIS codebase's structure — imports, calls, definitions,
history and counts. For example:
  which modules import {example1}
  what calls {example2}
  how many classes are there
/help for commands, /stats for an overview of the graph.


template: No previous answer to expand yet — ask me a question first, then say "why" or "say more".


template: Hi. I'm tmct. {vocabHint} Point me at a repo with `--repo <path>` for code-structure questions too (imports, calls, definitions). /help for commands.


template: Hi. I'm tmct. {vocabHint} /help for commands.


template:
I'm tmct — a deterministic, offline chat assistant (no LLM). {vocabHint} /memory for what I remember.
For code structure (imports, calls, definitions) point me at a repo: `--repo <path>`, or try the shipped example `npm run example:mini`. tmct reads graphs; it doesn't index code itself.
/help for commands.


template:
I'm tmct — a deterministic, offline chat assistant (no LLM). {vocabHint} /memory for what I remember, or ask about what's already loaded.
/help for commands.


template:
I'm tmct — a deterministic, offline chat assistant (no LLM). {vocabHint} /memory for what I remember.
/help for commands.


template: I'm tmct — a deterministic, offline chat assistant. No LLM: wink-nlp parsing over a seeded ontology/lexicon, plus a code graph when you point me at a repo with `--repo <path>`. /help for commands, /stats for an overview.


template: I'm tmct — a deterministic, offline chat assistant. No LLM: wink-nlp parsing over a seeded ontology/lexicon, plus a code graph when one is loaded. {vocabHint} /help for commands, /stats for an overview.


template: I'm tmct — a deterministic, offline chat assistant. No LLM: wink-nlp parsing over a seeded ontology/lexicon. {vocabHint} /help for commands, /stats for an overview.


template: No — no LLM involved. tmct is deterministic: wink-nlp parsing over a graph/ontology, not a language model. /help for commands.


template: No — I don't have feelings, opinions, or consciousness. tmct is deterministic: wink-nlp parsing over a graph/ontology, not a mind. /help for commands.


template: No — I never make up an answer. If a question doesn't ground to a taught fact or a real graph entity, I say so plainly instead of guessing. /help for commands.


register: technical

template: {subject} carries {count} {noun} across {scope} — a concentration well above what a codebase of this size typically sustains ({provenance}).


template: At {count} {noun}, {subject} sits {comparison} the comparable-project baseline, a divergence that reflects deliberate structure rather than measurement noise ({provenance}).


template: No {noun} in {scope} is more {metric} than {subject}; it leads the next candidate by a clear margin of {count} ({provenance}).


template: {subject} sustains a ratio of {count} {noun} per {unit}, placing it in the upper band for projects of comparable {scope} ({provenance}).


class: concept

template:
{definition}
{examples}{followups}