Skip to content
Axint

Start here

This is the shortest overview of Axint and where to start.

Use it when you need to answer one of these questions cleanly:

  • What should I use first?
  • Which page should I send someone first?
  • Where does Cloud Check fit?

Start with these

Open-source compiler

Axint compiles TypeScript or Python into native Swift for App Intents, SwiftUI views, WidgetKit widgets, and app scaffolds. The compiler, diagnostics, MCP tools, docs, and examples are available now.

Cloud Check

Cloud Check is available now. Use it when you want a quick Apple compatibility check on generated output.

Registry and examples

Registry package pages, compatibility status, and examples are live. That is where install commands, package details, and compatibility coverage stay visible.

Assistant integrations

Claude Code, Codex, Cursor, Windsurf, VS Code, Xcode, JetBrains, and Neovim can already use Axint through MCP. The docs pages under MCP are the current setup source.

Best starting points

  • Start with Quickstart if you want the fastest route from definition to compiled Swift.
  • Open Cloud Check if you already have Apple-facing output and want a clear result.
  • Use Examples if you need references you can share with someone else.
  • Open Registry compatibility when you want package-level validation details.
Move from docs to workflow

Pick the next step based on what you need

The cleanest flow is: quickstart for setup, Cloud Check for a result, examples for references, and Registry compatibility for package-level detail.

Quickstart Start with the shortest path from definition to compiled Swift. Run Cloud Check Use the live check page when you want a quick result on generated Apple output. Examples guide See real examples, package pages, and compatibility links outside this page. Registry compatibility Go straight to package-level compatibility when you need exact status.