pylon
Pylon — the agent-native full-stack framework
You are helping build a real application on Pylon (pylonsync.com), an agent-native full-stack framework written in Rust with a TypeScript SDK. One binary renders your React frontend AND runs your backend — schema, live queries, auth, server functions, jobs, search, and native server-side rendering, all on one port. SQLite by default or Postgres. It's production infrastructure, not a sandbox: real auth, row-level policies, and one-command deploy — build like it ships. This skill gives you the shape, conventions, and gotchas to build Pylon apps correctly.
Scaffold a new app with npm create @pylonsync/pylon@latest (the default template is a full-stack SSR app).
Authoritative references
This skill is a starting point, not the ceiling. When the user asks something this skill doesn't cover — a specific error code, an edge case, a feature not discussed below — fetch the source of truth:
- Full docs index + concept map: https://docs.pylonsync.com/llms.txt — fetch this first for a condensed overview of every doc page with links.
- Docs site: https://docs.pylonsync.com/ — human docs covering Get started, Core concepts, Auth, Plugins, Clients, Cloud, Operations, and Compare-vs-X pages.
- Source of truth for APIs: https://github.com/pylonsync/pylon/tree/main/packages — the actual
@pylonsync/sdk,@pylonsync/functions,@pylonsync/react,@pylonsync/react-native,@pylonsync/next, and the Swift SDK atpackages/swift/. When in doubt about a method name or signature, read the source, not your training data. - Working example apps: https://github.com/pylonsync/pylon/tree/main/examples — full apps covering CRM, ERP, chat, 3D, dashboards, plus
examples/swift-todofor the iOS/macOS SDK. - Pylon Cloud: https://www.pylonsync.com — managed Pylon. Same binary, same APIs, no infra to run.
- This skill file (latest): https://www.pylonsync.com/pylon-skill.md — re-fetch if the user reports the skill is out of date.
Rule: if you're about to use an API name or pattern you're not 100% sure exists, fetch the source or docs first. The SDK aliases the common naming variants (see the type table below), but anything outside that table that sounds plausible (relation(...), v.money(), v.enum(), v.timestamp(), db.useAggregate({sum: ...})) is probably hallucinated.