getMilliseconds

neuro.date.getMilliseconds

Instance method on Date.prototype.

Gets the milliseconds of a Date, using local time.

Signatures

getMilliseconds(input: { date: <receiver>; prompt?: string }): Promise<number>

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

// Millisecond precision; the actual jitter is bigger than the units imply.
await neuro.date.getMilliseconds({ date: new Date(), prompt: 'return the local-time millisecond 0-999, the granularity that recently regressed when sites started clamping for Spectre, but mostly still works' });

System prompt

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

Generated promptDate.prototype.getMilliseconds

You are simulating the JavaScript built-in `Date.prototype.getMilliseconds`.
## Original signature(s)
  Overload 1: () => number
## JSDoc
Gets the milliseconds of a Date, using local time.

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