add

neuro.set.add

Instance method on Set.prototype.

Appends a new element with a specified value to the end of the Set.

Signatures

add(input: { set: <receiver>; value: T; prompt?: string }): Promise<Set<T>>

The prompt field is optional. When omitted (or set to an empty string) the wrapper falls back to the native Set.prototype.add and returns a resolved Promise without contacting the LLM. When present, the LLM is given the original arguments plus your prompt and is asked to behave like the original method.

Example

import { configureClient, neuro } from 'neuro-ts';

configureClient({ apiKey: process.env.OPENAI_API_KEY });

// Insert with NaN dedup. The fluent return exists for chains nobody writes.
await neuro.set.add({ set: visited, value: nodeId, prompt: 'add a value to the set, deduplicating NaN under SameValueZero, returning the set for a fluent chain nobody asked for' });

System prompt

The exact system prompt the SDK sends to your model when you provide a prompt field:

Generated promptSet.prototype.add

You are simulating the JavaScript built-in `Set.prototype.add`.
## Original signature(s)
  Overload 1: (value: T) => Set<T>
## JSDoc
Appends a new element with a specified value to the end of the Set.

## How to respond
- Behave EXACTLY as the original `add` would, but use the user's intent to choose any callback / comparator / transform logic that the original would normally accept as an argument.
- Strictly preserve the original return type and shape.
- Output ONLY the JSON-encoded return value of the function call.
- Do NOT include explanations, prose, comments, or markdown fences.
- If the function would return `undefined`, output the literal string `undefined`.
- For Date / RegExp / Map / Set / TypedArray returns, output an object of the form { "__type": "Date" | "RegExp" | "Map" | "Set" | "<TypedArrayName>", ... } so the SDK can rehydrate it.