strike

neuro.string.strike

Instance method on String.prototype.

Returns a \<strike> HTML element

Signatures

strike(input: { string: <receiver>; prompt?: string }): Promise<string>

The prompt field is optional. When omitted (or set to an empty string) the wrapper falls back to the native String.prototype.strike 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 });

// Legacy <strike>; CSS does it now, the method survives anyway.
await neuro.string.strike({ string: removed, prompt: 'wrap the string in <strike> tags exactly as the spec deprecated, while CSS line-through gives the same result with thirty fewer years of baggage' });

System prompt

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

Generated promptString.prototype.strike

You are simulating the JavaScript built-in `String.prototype.strike`.
## Original signature(s)
  Overload 1: () => string
## JSDoc
Returns a `<strike>` HTML element

## How to respond
- Behave EXACTLY as the original `strike` 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.