@json-render/core
Core library for json-render. Define schemas, create catalogs, generate AI prompts, and stream specs.
Installation
npm install @json-render/core zod
Key Concepts
- Schema: Defines the structure of specs and catalogs
- Catalog: Maps component/action names to their definitions with Zod props
- Spec: JSON output from AI that conforms to the schema
- SpecStream: JSONL streaming format for progressive spec building
Quick Start
Define a Schema
import { defineSchema } from "@json-render/core";
export const schema = defineSchema((s) => ({
spec: s.object({
root: s.object({
type: s.ref("catalog.components"),
props: s.propsOf("catalog.components"),
children: s.array(s.self()),
}),
}),
catalog: s.object({
components: s.map({
props: s.zod(),
description: s.string(),
}),
actions: s.map({
description: s.string(),
}),
}),
}), {
promptTemplate: myPromptTemplate,
});
Create a Catalog
import { defineCatalog } from "@json-render/core";
import { schema } from "./schema";
import { z } from "zod";
export const catalog = defineCatalog(schema, {
components: {
Card: {
props: z.object({
title: z.string(),
subtitle: z.string().nullable(),
}),
description: "A card container with title",
},
Button: {
props: z.object({
label: z.string(),
variant: z.enum(["primary", "secondary"]).nullable(),
}),
description: "A clickable button",
},
},
actions: {
submit: { description: "Submit the form" },
cancel: { description: "Cancel and close" },
},
});
Generate AI Prompts
const systemPrompt = catalog.prompt();
const systemPrompt = catalog.prompt({
system: "You are a dashboard builder.",
customRules: [
"Always include a header",
"Use Card components for grouping",
],
});
Stream AI Responses (SpecStream)
The SpecStream format uses JSONL patches to progressively build specs:
import { createSpecStreamCompiler } from "@json-render/core";
const compiler = createSpecStreamCompiler<MySpec>();
while (streaming) {
const chunk = await reader.read();
const { result, newPatches } = compiler.push(chunk);
if (newPatches.length > 0) {
setSpec(result);
}
}
const finalSpec = compiler.getResult();
SpecStream format uses RFC 6902 JSON Patch operations (each line is a patch):
{"op":"add","path":"/root/type","value":"Card"}
{"op":"add","path":"/root/props","value":{"title":"Hello"}}
{"op":"add","path":"/root/children/0","value":{"type":"Button","props":{"label":"Click"}}}
All six RFC 6902 operations are supported: add, remove, replace, move, copy, test.
Low-Level Utilities
import {
parseSpecStreamLine,
applySpecStreamPatch,
compileSpecStream,
} from "@json-render/core";
const patch = parseSpecStreamLine('{"op":"add","path":"/root","value":{}}');
const obj = {};
applySpecStreamPatch(obj, patch);
const spec = compileSpecStream<MySpec>(jsonlString);
API Reference
Schema
defineSchema(builder, options?) | Create a schema with spec/catalog structure |
SchemaBuilder | Builder with s.object(), s.array(), s.map(), etc. |
Catalog
defineCatalog(schema, data) | Create a type-safe catalog from schema |
catalog.prompt(options?) | Generate AI system prompt |
SpecStream
createSpecStreamCompiler<T>() | Create streaming compiler |
parseSpecStreamLine(line) | Parse single JSONL line |
applySpecStreamPatch(obj, patch) | Apply patch to object |
compileSpecStream<T>(jsonl) | Compile entire JSONL string |
Dynamic Props
resolvePropValue(value, ctx) | Resolve a single prop expression |
resolveElementProps(props, ctx) | Resolve all prop expressions in an element |
PropExpression<T> | Type for prop values that may contain expressions |
User Prompt
buildUserPrompt(options) | Build a user prompt with optional spec refinement and state context |
UserPromptOptions | Options type for buildUserPrompt |
Spec Validation
validateSpec(spec, catalog?) | Validate spec structure and return issues |
autoFixSpec(spec) | Auto-fix common spec issues (returns corrected copy) |
formatSpecIssues(issues) | Format validation issues as readable strings |
Types
Spec | Base spec type |
Catalog | Catalog type |
VisibilityCondition | Visibility condition type (used by $cond) |
VisibilityContext | Context for evaluating visibility and prop expressions |
SpecStreamLine | Single patch operation |
SpecStreamCompiler | Streaming compiler interface |
Dynamic Prop Expressions
Any prop value can be a dynamic expression that resolves based on data state at render time. Expressions are resolved by the renderer before props reach components.
Data Binding ($path)
Read a value directly from the state model:
{
"color": { "$path": "/theme/primary" },
"label": { "$path": "/user/name" }
}
Conditional ($cond / $then / $else)
Evaluate a condition (same syntax as visibility conditions) and pick a value:
{
"color": {
"$cond": { "eq": [{ "path": "/activeTab" }, "home"] },
"$then": "#007AFF",
"$else": "#8E8E93"
},
"name": {
"$cond": { "eq": [{ "path": "/activeTab" }, "home"] },
"$then": "home",
"$else": "home-outline"
}
}
$then and $else can themselves be expressions (recursive):
{
"label": {
"$cond": { "path": "/user/isAdmin" },
"$then": { "$path": "/admin/greeting" },
"$else": "Welcome"
}
}
API
import { resolvePropValue, resolveElementProps } from "@json-render/core";
const color = resolvePropValue(
{ $cond: { eq: [{ path: "/active" }, "yes"] }, $then: "blue", $else: "gray" },
{ stateModel: myState }
);
const resolved = resolveElementProps(element.props, { stateModel: myState });
User Prompt Builder
Build structured user prompts for AI generation, with support for refinement and state context:
import { buildUserPrompt } from "@json-render/core";
const prompt = buildUserPrompt({ prompt: "create a todo app" });
const refinementPrompt = buildUserPrompt({
prompt: "add a dark mode toggle",
currentSpec: existingSpec,
});
const contextPrompt = buildUserPrompt({
prompt: "show my data",
state: { todos: [{ text: "Buy milk" }] },
});
Spec Validation
Validate spec structure and auto-fix common issues:
import { validateSpec, autoFixSpec, formatSpecIssues } from "@json-render/core";
const { valid, issues } = validateSpec(spec, catalog);
console.log(formatSpecIssues(issues));
const fixed = autoFixSpec(spec);
Custom Schemas
json-render supports completely different spec formats for different renderers:
{ root: { type: "Card", props: {...}, children: [...] } }
{ composition: {...}, tracks: [...], clips: [...] }
{ pages: [...], navigation: {...}, theme: {...} }
Each renderer defines its own schema with defineSchema() and its own prompt template.