reference
Fetch model or pattern context for generation and reasoning.
tl;dr
referenceis the read tool. Use it to fetch model/pattern data, optionally withpathfor surgical reads. Code is opt-in.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
targetType | string | Yes | "model" or "pattern". |
modelId | string | No | Preferred model identifier. |
patternId | string | No | Preferred pattern identifier. |
name | string | No | Name fallback when ID is unavailable. |
collection | string | No | For models: "public" or "private". |
path | string | No | JSON Pointer path (e.g. /principles, /components/button, /page/components). |
includePage | boolean | No | Include page metadata (schema/version) in full model reads. |
includeCode | boolean | No | Explicitly include page implementation code in model responses. |
Examples
reference { targetType: "model", modelId: "pub_123" }reference { targetType: "model", modelId: "priv_7", includePage: true }reference { targetType: "model", modelId: "priv_7", includeCode: true }reference { targetType: "model", modelId: "priv_7", path: "/page/components" }reference { targetType: "pattern", patternId: "hero-centered" }
Notes
- Default model reads are lean and do not include page code.
- Use
includeCode: trueonly when code access is required. - Prefer
pathfor targeted reads to reduce payload size.
Related
Better prototypes with less prompting
Start creating