Canonical Mosvera public aesthetic

Aesthetic infrastructure you can bring into your own tools.

Mosvera turns named aesthetic intent into portable packs, local registries, design tokens, CSS variables, and provider payloads without a hosted runtime dependency.

Warm Mosvera public aesthetic with tessera blocks, color tokens, and schema panes arranged across a technical workspace.
Mosvera Public The canonical Mosvera public-site aesthetic.

Declare

Author templates, palettes, modifiers, and compositions as portable JSON documents.

Resolve

Fold inheritance and modifiers into a canonical aesthetic model with explicit precedence.

Compile

Lower that model into your platform: site tokens, design systems, prompts, and provider payloads.

What is Mosvera?

An open contract for aesthetic intent.

Mosvera gives AI-native products a shared way to describe, exchange, resolve, and compile aesthetic direction. Teams keep named aesthetics in local registries, share them as `.mosvera.json` packs, and compile them into design tokens, CSS variables, MCP tool results, or provider-specific payloads.

Open source specification

The public contract lives in schemas, compliance vectors, terminology, and implementation guides.

github.com/mosvera/spec

Local runtimes

Use the TypeScript runtime, Python runtime, or local MCP server inside your own tools.

@mosvera/runtime on npm

Portable aesthetic packs

Download public packs, preview imports, and bring named aesthetics into a user-owned registry.

mosvera/examples packs

10-minute quickstart

Start in Claude Desktop, then verify the developer paths.

Install the Claude bundle first, list the seeded aesthetics, preview and import a pack, then try the same resolve/compile flow through npm/MCP, TypeScript, and Python. AI agents can start with the LLM-readable index or the install router.

Open the quickstart

Package map

Use the piece that matches the job.

JS/TS engine

@mosvera/runtime

Load a local registry, resolve named aesthetics, and produce tokens inside a JavaScript or TypeScript app.

Python engine

mosvera

Use the same runtime contract from Python with the PyPI package.

Provider translators

@mosvera/provider-*

Compile resolved intent into provider payloads for image, video, audio, and 3D providers including OpenAI, FLUX, SDXL, Google, Runway, ElevenLabs, Firefly, and Meshy.

Tool surface

@mosvera/mcp

Run a local Claude Desktop-friendly MCP server that lists, resolves, saves, exports, and imports aesthetics from your registry.

Exchange file

.mosvera.json

Share a named aesthetic as a portable pack that carries registry documents, not secrets or hosted runtime state.

Public contract

mosvera/spec

Read schemas, conformance vectors, MEPs, and implementation guidance.

What just happened?

You moved an aesthetic from a file into something your tools can use.

Mosvera did not ask your site or agent to depend on a hosted runtime. It used portable files and local tools to turn a named aesthetic into outputs your own platform can consume.

  1. Pack .mosvera.json
  2. Local registry your files
  3. Named aesthetic claymation-playful-builder
  4. Resolved model canonical JSON
  5. Tokens / CSS variables usable output

local registry

A user-owned folder where Mosvera stores templates, palettes, modifiers, composition documents, and merge rules.

named aesthetic

The friendly id you ask for, like claymation-playful-builder.

composition document

The technical document that points to a base template, optional modifiers, and overrides.

aesthetic pack

The portable pack exchange file used to preview, import, and export a named aesthetic.

tokens / CSS variables

The compiled output a website, app, agent, or design system can apply.

no hosted runtime dependency

mosvera.io hosts docs, schemas, and examples. Production usage runs inside your own tools.

Reference demonstrator

This site consumes the idea it explains.

The selected composition is pre-resolved for this static v1. A small site adapter compiles the canonical model into CSS variables, so the page changes without pretending that production users depend on this domain at runtime.

Agents use Mosvera the same way: the MCP server runs locally, reads and writes a user-owned registry, imports and exports aesthetic packs, and never sends provider requests by itself.

Package @mosvera/runtime
Schema /schema/0.1/composition
Demo mode mosvera-public
npm install @mosvera/runtime
pip install mosvera
npm install -g @mosvera/mcp
curl -O https://mosvera.io/packs/claymation-playful-builder.mosvera.json
View composition
View compiled tokens