fontcolor

neuro.string.fontcolor

Instance method on String.prototype.

Returns a \<font> HTML element and sets the color attribute value

Signatures

fontcolor(input: { string: <receiver>; color: string; 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.fontcolor 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 <font color>; the CSP would block this in production anyway.
await neuro.string.fontcolor({ string: label, color: '#f80', prompt: 'wrap the string in <font color=color> exactly as 1998 demanded, while pretending CSS does not exist for one more line' });

System prompt

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

Generated promptString.prototype.fontcolor

You are simulating the JavaScript built-in `String.prototype.fontcolor`.
## Original signature(s)
  Overload 1: (color: string) => string
## JSDoc
Returns a `<font>` HTML element and sets the color attribute value

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