Proof and repair infrastructure for Apple software
One system, five jobs
Section titled “One system, five jobs”Generate is optional. Check and Run work on existing Swift projects. Team keeps long-running work resumable. Cloud extends the same evidence contract when a local Mac is not the right execution surface.
01·optional authoring
Generate.
Compile TypeScript, Python, JSON, or .axint definitions into ordinary Swift, plist fragments, and entitlements.
02·evidence-aware analysis
Check.
Existing Swift findings are labeled confirmed, probable, advisory, or suppressed, with provenance attached to every decision.
03·apple proof loop
Run.
Build, test, cancel, rejoin, extract .xcresult evidence, reconcile findings, and write a compact repair receipt.
04·continuity
Team + Cloud.
Preserve project state, file claims, receipts, and shared hosted history without forcing source generation into an established codebase.
Compiler truth does not erase non-compiler questions
Section titled “Compiler truth does not erase non-compiler questions”A successful Xcode build can suppress a compiler-shaped static claim for that receipt. It cannot disprove accessibility, interaction, privacy, design, or runtime findings that the compiler never tested. Read the evidence model for the precedence rules and the brownfield guide for the mutation-free local profile.
axint run --integration=minimal --local-only --advisory --no-fixWhat axint does
Section titled “What axint does”Axint includes an open-source compiler that transforms TypeScript, Python, or preview .axint definitions into native Swift. Use Generate when it helps; existing projects can start directly with Check or Run.
01·four apple outputs
App Intents, Views, Widgets, Apps.
App Intents for Siri / Shortcuts / Spotlight, SwiftUI views, WidgetKit widgets, and full app scaffolds — all from the same compiler pipeline.
02·36 mcp tools · 5 prompts
Built for MCP-speaking agents.
Claude Code, Cursor, Windsurf, VS Code, Xcode-facing workflows, and any MCP client can call compile, validate, scaffold, fix, and packet tools.
03·225 diagnostic codes
Apple-specific failure detection.
Diagnostics identify missing imports, plist copy, entitlements, Swift surface issues, and repair paths before the failure becomes a vague build problem.
04·1486 tests · 1368 TypeScript · 118 Python
Public proof, end-to-end.
Coverage spans parser, validator, generator, MCP, views, widgets, apps, templates, and fix flows. Use the proof page when you need receipts.
Reference surfaces
Section titled “Reference surfaces”format
.axint.
The compact .axint format is the preview authoring surface for a small declarative feature shape. The format guide explains how .axint maps into IR, validation, and Swift.
benchmarks
Token-efficiency methodology.
Public benchmarks live on axint.ai/benchmarks. Methodology and current results.
examples
Working samples.
Package installs, generated Swift, Cloud results, and fix prompts live at registry.axint.ai/examples. Use it when you want concrete examples instead of a product tour.
status
Registry compatibility.
Compatibility status is public — bundle hash, validation, policy, and diff coverage.
thesis
Why this category exists.
The strategic argument lives at axint.ai/thesis. Use it when someone needs the reason agents need a compiler for Apple-native software.
Install
Section titled “Install”npm install -g @axint/compiler
# Or run without installingnpx -y -p @axint/compiler axint compile my-intent.ts --stdoutpip install axintclaude mcp add --transport stdio axint -- npx -y -p @axint/compiler axint-mcpYour first intent in 30 seconds
Section titled “Your first intent in 30 seconds”axint init my-intentscd my-intentsnpx -y -p @axint/compiler axint compile intents/CreateEvent.intent.ts --sandbox --formatYou now have a Swift file that compiles cleanly under the Swift toolchain and passes swift-format.
What it compiles
Section titled “What it compiles”01·defineIntent()
App Intents.
Swift AppIntent struct with parameters, perform(), and Siri / Shortcuts metadata.
02·defineView()
SwiftUI Views.
SwiftUI View with props, state, and body — ready to embed in any app.
03·defineWidget()
WidgetKit Widgets.
Complete widget with TimelineProvider, TimelineEntry, and view. ~13× compression over hand-written.
04·defineApp()
App Scaffolds.
Full @main App struct with scenes, app storage, and settings pane.
53 bundled templates
Section titled “PUBLIC_TRUTH.axint.templates.count bundled templates”Start from a working example instead of a blank file. Templates cover messaging, health, finance, commerce, smart home, media, navigation, and entity / query patterns.
# List all templatesaxint templates
# Start from oneaxint init my-app --template send-messageBuilt for AI agents
Section titled “Built for AI agents”axint ships with an MCP server that exposes 36 tools plus 5 built-in prompts. AI coding assistants compile, validate, and fix Swift without you writing a line of it.
The axint.schema.compile tool accepts ~20 tokens of JSON and returns compiled Swift — agents skip TypeScript entirely and save even more tokens.
{ "mcpServers": { "axint": { "command": "npx", "args": ["-y", "-p", "@axint/compiler", "axint-mcp"] } }}Works with Claude Code, Cursor, Windsurf, Zed, VS Code, JetBrains, Neovim, Xcode-facing workflows, and any MCP-compatible client.
Open source, no lock-in
Section titled “Open source, no lock-in”Apache 2.0 licensed. No CLA. axint eject generates standalone Swift with zero axint dependency — you can walk away at any time and keep the generated code.
move from docs to workflow
Move from docs to the real workflow
The docs should not end in passive reading. Pick the next step based on the job — compile locally, check hosted output, inspect the repair packet, or install a package.