TypeScript, Python, or .axint definition. Public, browsable, copy-pasteable. Inspect before you install.
axint registry · 58 live packages
Apple-nativepackages, agent-ready.
Reusable App Intents, SwiftUI views, widgets, and full app scaffolds. Browse the source. Install with one command. Built with the open-source axint compiler.
the definition
The package layer for reusable Apple-native capabilities that agents can inspect, install, validate, and ship.
Not just a package — a capability with provenance. Every Registry entry ships source, generated Swift, install command, creator identity, bundle hash, and Cloud + Fix Packet compatibility. Bundle hashes verified on every install.
install — primary action
click to copy · or browse the catalog
Public packages
58 live
One-command install
axint add
Source visible
TS · Python · Swift
Cloud compatible
Fix Packet ready
distribution layer
How Apple-native capabilitiesbecome reusable.
The compiler proves a definition can become Swift. Registry proves the capability can be found, inspected, installed, and trusted by someone who did not write it.
01
Find a package
Start from a reusable Apple-native capability instead of asking every agent to rebuild the same integration from scratch.
@axint/create-event
02
Inspect before install
Package pages should expose source, generated Swift, compiler version, README, and install command before the package touches a project.
source + Swift + metadata
03
Check the trust layer
Validation history, creator identity, package status, and policy signals make reuse legible instead of anonymous.
compatibility + provenance
04
Carry it into Cloud
When output needs review, Cloud and Fix Packets should turn the package result into a concrete repair path.
check -> packet -> rerun
what every package ships
Reusable is not justcode sharing.
It's trust, provenance, validation, and repeatable install. Every Registry package surfaces seven attributes before the install runs — so the agent (and the human) can judge what they're about to ship.
The exact Swift the compiler emits. View it before you trust it. No black box between definition and output.
One line. axint add @namespace/package. Drop into terminal or hand to your agent.
GitHub-backed. Every package belongs to a real GitHub user or org. Anonymous publishing not supported.
SHA-256 of the published bundle. Verified on every install. If the source on the page differs from what installs, the install fails.
Compatibility log across axint versions and Apple OS releases. Drift detection. You see what's been validated and when.
Every package can be Cloud-checked and produce a Fix Packet on failure. The repair loop extends from the compiler into the registry.
The contrast against npm or GitHub templates: an npm package gives you code. A GitHub template gives you a scaffold. A Registry package gives you a verifiable Apple capability the agent can install, validate, and repair through the same loop the compiler uses locally.
A Registry package is not just code. It is an installable capability with proof attached.
Trending this week
Most installed packages
browse by surface
Every corner ofApple’s ecosystem.
We seed the obvious ones. The community fills the rest.
Seeded templates are starting points. Every Apple surface becomes publishable by the community — one axint publish away from agent-installable.
Top publishers
The developers publishing the strongest Apple-native packages.
ship a capability
Publish once.Every agent can install it.
One axint publish away from the front page. No account forms. No review queues.
GitHub OAuth, a quick --dry-run, and your template is live with source, generated Swift, install command, metadata, and validation history attached.