@brika/schema

Unified schema package for BRIKA plugins and configuration.

Single source of truth — Define schemas once in Zod, get both runtime validation and IDE support.

Features

✅ Zod schemas for runtime validation (TypeScript)
✅ JSON Schema auto-generated for IDE support
✅ Version synchronization - package.json version injected into schemas
✅ Single file to maintain - Zod is the source, JSON Schema is derived

Installation

bun add @brika/schema

Usage

Runtime Validation (TypeScript)

import { PluginPackageSchema, validatePluginPackage } from "@brika/schema";

// Validate plugin package.json at runtime
const result = validatePluginPackage(packageData);

if (result.success) {
  console.log("Valid plugin:", result.data);
} else {
  console.error("Invalid plugin:", result.error);
}

// Or assert (throws on invalid)
import { assertPluginPackage } from "@brika/schema";
assertPluginPackage(packageData); // throws if invalid

IDE Validation (JSON Schema)

In your plugin's package.json:

{
  "$schema": "https://schema.brika.dev/plugin.schema.json",
  "name": "@myorg/my-plugin",
  "version": "1.0.0",
  "engines": {
    "brika": "^0.1.0"
  }
}

Your IDE will automatically:

• Validate the structure
• Provide autocomplete
• Show inline documentation
• Catch errors as you type

Architecture

┌─────────────────┐
│  plugin.ts      │  ← Source of truth (Zod)
│  (Zod Schema)   │
└────────┬────────┘
         │
         ├─── Runtime validation (TypeScript)
         │
         v
┌─────────────────┐
│ generate-       │
│ schemas.ts      │  ← Build script
└────────┬────────┘
         │
         │ Generates (z.toJSONSchema)
         v
┌─────────────────┐
│ plugin.schema   │  ← Generated JSON Schema
│ .json           │  
└────────┬────────┘
         │
         ├─── Published to /schemas/
         ├─── Served via CDN
         └─── IDE validation

How It Works

1. Define Schema in Zod (Once)

// packages/schema/src/plugin.ts
export const PluginPackageSchema = z.object({
  name: z.string().regex(/^@[a-z0-9-]+\/[a-z0-9-]+$/),
  version: z.string().regex(semverPattern),
  engines: z.object({
    brika: z.string().regex(semverRangePattern),
  }),
  // ... more fields
});

2. Generate JSON Schema (Automatic)

bun run build

This:

1. Reads package.json version
2. Converts Zod → JSON Schema using native z.toJSONSchema()
3. Injects version into $id
4. Writes to dist/plugin.schema.json

3. Publish to npm

# Smart publish with safety checks
bun run publish

# Force publish (skip version check)
bun run publish --force

# Dry run (see what would be published)
bun run publish --dry-run

The publish script automatically:

• Builds the schemas
• Checks if version exists (unless --force)
• Publishes to npm
• Shows CDN URLs

4. Use Everywhere

Runtime (Hub):

import { validatePluginPackage } from "@brika/schema";
const result = validatePluginPackage(pluginPackageJson);

IDE (Developers):

{
  "$schema": "https://schema.brika.dev/0.1.0/plugin.schema.json"
}

Development Workflow

Adding a New Field

1. Update Zod schema in src/plugin.ts:

   export const PluginPackageSchema = z.object({
     // ... existing fields
     newField: z.string().optional().describe("New field description"),
   });

2. Regenerate JSON Schema:

   bun run build

3. Commit both files:

   • src/plugin.ts (source)
   • ../../schemas/plugin.schema.json (generated)

4. Push to GitHub - Cloudflare Worker serves updated schema

Watch Mode (Development)

bun run dev

Auto-regenerates JSON Schema on Zod changes.

Benefits Over Manual Maintenance

❌ Before (Separate Files)

✗ Maintain Zod schema manually
✗ Maintain JSON Schema manually
✗ Keep them in sync manually
✗ Update version in multiple places
✗ Risk of drift

✅ After (Single Source)

✓ Maintain Zod schema only
✓ JSON Schema generated automatically
✓ Always in sync
✓ Version injected automatically
✓ No drift possible

Version Management

The schema version comes from package.json:

{
  "name": "@brika/schema",
  "version": "0.1.0"  ← This version
}

Gets injected into JSON Schema:

{
  "$id": "https://schema.brika.dev/0.1.0/plugin.schema.json"
}

Updating Version

1. Update packages/schema/package.json version
2. Run bun run publish
3. Push tags: git push --follow-tags
4. GitHub Action creates git tag (if configured)
5. New version accessible at schema.brika.dev/x.y.z/...

Or use npm's built-in version command:

npm version patch   # 0.1.0 → 0.1.1
bun run publish
git push --follow-tags

Type Safety

Get TypeScript types from Zod:

import type { PluginPackage } from "@brika/schema";

const plugin: PluginPackage = {
  name: "@myorg/plugin",
  version: "1.0.0",
  engines: {
    brika: "^0.1.0"
  }
};

Validation Examples

Valid Plugin

import { validatePluginPackage } from "@brika/schema";

const valid = validatePluginPackage({
  name: "@myorg/awesome-plugin",
  version: "1.0.0",
  engines: {
    brika: "^0.1.0"
  },
  tools: [
    {
      id: "my-tool",
      description: "Does something cool",
      icon: "zap",
      color: "#3b82f6"
    }
  ]
});

console.log(valid.success); // true

Invalid Plugin

const invalid = validatePluginPackage({
  name: "not-scoped",  // ❌ Must be scoped (@org/name)
  version: "1.0",       // ❌ Not valid semver
});

console.log(invalid.success); // false
console.log(invalid.error);   // Zod error with details

Integration Points

Hub (Runtime)

// apps/hub/src/runtime/plugins/plugin-manager.ts
import { validatePluginPackage } from "@brika/schema";

async loadPlugin(packageJson: unknown) {
  const result = validatePluginPackage(packageJson);
  
  if (!result.success) {
    throw new Error(`Invalid plugin: ${result.error}`);
  }
  
  // Use validated data
  const plugin = result.data;
}

Plugins (Development)

{
  "$schema": "https://schema.brika.dev/plugin.schema.json",
  "name": "@brika/plugin-timer",
  "dependencies": {
    "@brika/schema": "workspace:*"
  }
}

External Plugins (Published)

npm install @brika/schema

import { PluginPackageSchema } from "@brika/schema";
// Validate your plugin programmatically

Scripts

| Command | Description | |---------|-------------| | bun run build | Generate JSON Schema from Zod | | bun run dev | Watch mode - regenerate on changes | | bun run publish | Publish to npm with safety checks | | bun run publish --force | Force publish (skip version check) | | bun run publish --dry-run | See what would be published |

Files

| File | Purpose | |------|---------| | src/plugin.ts | Source of truth - Zod schema | | src/generate-schemas.ts | Build script - Zod → JSON | | src/index.ts | Public exports | | dist/plugin.schema.json | Generated JSON Schema | | ../../schemas/plugin.schema.json | Published to CDN |

Future Schemas

This package will grow to include:

• config.ts / config.schema.json - For brika.yml
• automation.ts / automation.schema.json - For workflow files
• block.ts / block.schema.json - For block definitions

All following the same pattern:

1. Define in Zod
2. Generate JSON Schema
3. Publish via CDN

Related

• Zod Documentation
• Zod JSON Schema
• JSON Schema Specification
• schemas/README.md - CDN publishing docs

License

Same as main BRIKA project.