{"enrichment":{"faq":[{"a":"The core package lets you define JSON schemas for UI/spec generation with catalogs that map components and actions. You create type-safe component and action definitions, then use catalogs to organize them for dynamic UI rendering. This foundation enables state-driven spec generation and conditional rendering based on your application's needs.","q":"How do I define schemas and catalogs in json-render core?"},{"a":"json-render core supports spec streaming through JSONL compilation, allowing you to generate AI prompts and refine specs incrementally. The streaming approach lets you build dynamic, state-driven UI specs with conditional rendering, making it easy to integrate AI-powered refinement modes into your workflow.","q":"What is json-render spec streaming and how does it work?"},{"a":"The core package provides utilities to generate AI prompts directly from your schema definitions. By leveraging your component and action catalogs, you can automatically create structured prompts that guide AI models in generating or refining UI specs, streamlining the AI-assisted design process.","q":"How can I create AI prompts from a schema using core?"},{"a":"core enables dynamic prop expressions through state binding and visibility conditions. You define computed functions and template interpolation that reference state values, allowing props to update reactively. Combined with state watchers and action triggers, this creates fully responsive, state-driven UI specifications.","q":"How do dynamic prop expressions and state binding work in core?"},{"a":"The core package includes spec validation with cross-field checks using Zod validation for component props. It supports form validation, auto-fix capabilities, and ensures your specs conform to schema constraints before rendering, maintaining type safety throughout your UI generation pipeline.","q":"What validation capabilities does json-render core provide?"},{"a":"Yes, core supports integration with external state management through reactive watchers and action triggers. You can bind your specs to external state stores, enabling seamless synchronization between your UI specifications and application state while maintaining full reactivity and control.","q":"Can core integrate with external state management systems?"}],"shadow_tags":["schema-builder","state-management","dynamic-binding","spec-generation","form-validation","streaming-json","ui-specification","conditional-rendering","prompt-engineering","reactive-framework"],"summary_rewrite":"The core package provides schema definition, catalog mapping, and spec streaming utilities for json-render. Build type-safe component and action definitions, generate AI prompts, and handle dynamic prop expressions with state binding and visibility conditions."},"files":[{"bytes":9728,"path":"skills/core/SKILL.md","sha256":"db3c557127ac138b764e82d16a3c5a8ee810fa9c3fa1bc2a11be96561613c985","url":"https://skillfed.io/files/vercel-labs/json-render/core/d201bff9/SKILL.md"}],"id":"vercel-labs/json-render/core","links":{"html":"https://skillfed.io/vercel-labs/json-render/core","md":"https://skillfed.io/vercel-labs/json-render/core.md","repo":"https://github.com/vercel-labs/json-render"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":850,"language":"TypeScript","last_updated":"2026-07-08","license":"Apache-2.0","name":"core","publisher":"vercel-labs","stars":15776},"relations":{"similar":[{"id":"vercel-labs/json-render/vue"},{"id":"vercel-labs/json-render/react"},{"id":"vercel-labs/json-render/react-native"},{"id":"vercel-labs/json-render/ink"},{"id":"google-labs-code/design.md/ink"},{"id":"vercel-labs/json-render/svelte"},{"id":"vercel-labs/json-render/react-pdf"},{"id":"vercel-labs/json-render/jotai"},{"id":"vercel-labs/json-render/xstate"},{"id":"vercel-labs/json-render/zustand"}]},"slug":{"owner":"vercel-labs","repo":"json-render","skill":"core"},"version":"d201bff9"}