Language guide

TypeScript guide.

TypeScript is the most direct authoring path for Axint packages today. It maps cleanly onto the compiler, MCP surface, and registry publish flow.

01 · section

Recommended path

Use TypeScript when you want the shortest line from editor to compile to publish. It is also the easiest language to demo in-browser today.

Use defineIntent, defineView, defineWidget, and defineApp surfaces as needed.
Keep source readable because package pages may expose it directly.
Pair source with a README that explains permissions and setup.

02 · section

Package-ready example

A good registry package has a clean source definition, a useful description, and enough metadata to be trustworthy on its own page.

TypeScript intent

import { defineIntent, param } from "@axint/compiler";

export default defineIntent({
  name: "CreateEvent",
  title: "Create calendar event",
  params: {
    title: param.string("Event title"),
    startsAt: param.date("When it starts"),
  },
});

related guides

Keep going

Parameters Dialog responses Publish to Registry

Back to docs Compiler source