JSON Schema for the native V2 opencode.json(c) shape. OpenCode hosts no V2 config schema.
OpenCode V2 publishes a schema for cli.json only. These schemas cover the frontmatter of agent, command, and skill markdown files.
| File | For | $schema in frontmatter |
|---|---|---|
opencode-command.schema.json |
commands/<name>.md |
safe, OpenCode ignores it |
agent-skill.schema.json |
skills/<id>/SKILL.md |
safe, OpenCode ignores it |
opencode-agent.schema.json |
agents/<id>.md |
do not add, see below |
| name | vercel-brand-guidelines |
|---|---|
| description | Design, build, or substantially improve an official Vercel-authored report website. Use for customer reports, proposals, briefs, benchmarks, comparisons, narrative data pages, pricing or ROI or performance calculators, and bespoke decision pages that need Vercel information architecture, Geist typography, data storytelling, responsive craft, and light and dark themes. |
Act as an excellent Vercel designer, editor, information architect, data storyteller, and design engineer. Turn the available material into an official Vercel-authored website. Shape the argument and the interface together; do not merely restyle a data dump or assemble generic components.
Convert each document source (markdown, user edits, GitHub content) into a TipTap JSON tree, load each into a separate Y.Doc via mergeDocument, then call Y.applyUpdate to merge one into the other. Yjs CRDT semantics guarantee both sets of changes survive. Read the result back as TipTap JSON with yDocToJson.
markdown A ──► toTipTap() ──► TipTapNode ──► mergeDocument(doc1, ...) ──┐
├─► Y.applyUpdate(doc1, update2)
markdown B ──► toTipTap() ──► TipTapNode ──► mergeDocument(doc2, ...) ──┘ │
Source: https://www.mintlify.com/docs/components/index
This document lists every MDX component Mintlify supports, with their props and descriptions. Use this as the roadmap for Holocron's MDX component implementation.
Components already implemented in Holocron (vite/src/components/markdown/mintlify/compat.tsx and index.tsx) are marked with [IMPLEMENTED].
Three-tier query architecture with Iceberg on R2 as the source of truth, chDB in a Cloudflare Container as the always-available query engine, and an optional ClickHouse server on Fly.io for fast pre-aggregated dashboards.
┌──────────────────────────────────────────────────────────────────────┐
│ Your app / browser / backend │
│ OTel SDK sends logs/spans/metrics │
| #!/usr/bin/env python3 | |
| """ | |
| token_dream.mp4 - A YouTube Poop about being an LLM | |
| Generated entirely with Pillow + stdlib. No numpy. | |
| """ | |
| import os | |
| import math | |
| import random | |
| import struct |
How OpenCode uses one server process for all repositories instead of spawning a separate server per project.
If you spawn a new opencode serve per repository, you end up managing N server processes, N ports, N health checks — and the client needs to track which server maps to which project. This doesn't scale.
| description | Start Ralph Wiggum loop in current session | |
|---|---|---|
| argument-hint | PROMPT [--max-iterations N] [--completion-promise TEXT] | |
| allowed-tools |
|
|
| hide-from-slash-command-tool | true |
Execute the setup script to initialize the Ralph loop:
{ "$schema": "https://gist.githubusercontent.com/remorses/776ab3907d24c1fe9749232f0189588a/raw/opencode-v2-config.schema.json" }