Vue 3 renderer that converts JSON specs into Vue component trees with data binding, visibility, and actions.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionvueExecute the skills CLI command in your project's root directory to begin installation:
Fetches vue from vercel-labs/json-render and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate vue. Access via /vue in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
14.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
14.0K
stars
Vue 3 renderer that converts JSON specs into Vue component trees with data binding, visibility, and actions.
npm install @json-render/vue @json-render/core zod
Peer dependencies: vue ^3.5.0 and zod ^4.0.0.
import { defineCatalog } from "@json-render/core";
import { schema } from "@json-render/vue/schema";
import { z } from "zod";
export const catalog = defineCatalog(schema, {
components: {
Card: {
props: z.object({ title: z.string(), description: z.string().nullable() }),
description: "A card container",
},
Button: {
props: z.object({ label: z.string(), action: z.string() }),
description: "A clickable button",
},
},
actions: {},
});
import { h } from "vue";
import { defineRegistry } from "@json-render/vue";
import { catalog } from "./catalog";
export const { registry } = defineRegistry(catalog, {
components: {
Card: ({ props, children }) =>
h("div", { class: "card" }, [
h("h3", null, props.title),
props.description ? h("p", null, props.description) : null,
children,
]),
Button: ({ props, emit }) =>
h("button", { onClick: () => emit("press") }, props.label),
},
});
<script setup lang="ts">
import { StateProvider, ActionProvider, Renderer } from "@json-render/vue";
import { registry } from "./registry";
const spec = { root: "card-1", elements: { /* ... */ } };
</script>
<template>
<StateProvider :initial-state="{ form: { name: '' } }">
<ActionProvider :handlers="{ submit: handleSubmit }">
<Renderer :spec="spec" :registry="registry" />
</ActionProvider>
</StateProvider>
</template>
| Provider | Purpose |
|---|---|
StateProvider |
Share state across components (JSON Pointer paths). Accepts initialState or store for controlled mode. |
ActionProvider |
Handle actions dispatched via the event system |
VisibilityProvider |
Enable conditional rendering based on state |
ValidationProvider |
Form field validation |
| Composable | Purpose |
|---|---|
useStateStore() |
Access state context (state as ShallowRef, get, set, update) |
useStateValue(path) |
Get single value from state |
useIsVisible(condition) |
Check if a visibility condition is met |
useActions() |
Access action context |
useAction(binding) |
Get a single action dispatch function |
useFieldValidation(path, config) |
Field validation state |
useBoundProp(propValue, bindingPath) |
Two-way binding for $bindState/$bindItem |
Note: useStateStore().state returns a ShallowRef<StateModel> — use state.value to access.
Pass a StateStore to StateProvider to wire json-render to Pinia, VueUse, or any state management:
import { createStateStore, type StateStore } from "@json-render/vue";
const store = createStateStore({ count: 0 });
<StateProvider :store="store">
<Renderer :spec="spec" :registry="registry" />
</StateProvider>
Props support $state, $bindState, $cond, $template, $computed. Use { "$bindState": "/path" } on the natural value prop for two-way binding.
{ "$state": "/user/isAdmin" }
{ "$state": "/status", "eq": "active" }
{ "$state": "/maintenance", "not": true }
[ cond1, cond2 ] // implicit AND
setState, pushState, removeState, and validateForm are built into the Vue schema and handled by ActionProvider:
{
"action": "setState",
"params": { "statePath": "/activeTab", "value": "settings" }
}
Components use emit(event) to fire events, or on(event) for metadata (shouldPreventDefault, bound).
useUIStream and useChatUI return Vue Refs for streaming specs from an API.
For catalog-agnostic reusable components:
import type { BaseComponentProps } from "@json-render/vue";
const Card = ({ props, children }: BaseComponentProps<{ title?: string }>) =>
h("div", null, [props.title, children]);
| Export | Purpose |
|---|---|
defineRegistry |
Create a type-safe component registry from a catalog |
Renderer |
Render a spec using a registry |
schema |
Element tree schema (from @json-render/vue/schema) |
StateProvider, ActionProvider, VisibilityProvider, ValidationProvider |
Context providers |
useStateStore, useStateValue, useBoundProp |
State composables |
useActions, useAction |
Action composables |
useFieldValidation, useIsVisible |
Validation and visibility |
useUIStream, useChatUI |
Streaming composables |
createStateStore |
Create in-memory StateStore |
BaseComponentProps |
Catalog-agnostic component props type |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
erichowens/some_claude_skills
Useful defaults in vue — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: vue is focused, and the summary matches what you get after install.
We added vue from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
vue is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend vue for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: vue is the kind of skill you can hand to a new teammate without a long onboarding doc.
vue is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in vue — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added vue from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend vue for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 71