Agent skill · software engineering · jeremylongshore
flyio-reference-architecture
Design a Fly.io multi-region architecture with explicit routing, Machine, data, private-network, observability, and recovery boundaries. Use when reviewing a production topology. Trigger with: "architect app on Fly", "design multi-region Fly service", "review Fly platform topology".
Why this skill is useful
Provides specific setup commands and configurations for deploying multi-region applications on Fly.io that the AI wouldn't reliably generate on its own.
What it needs
Requires fly installed locally. Requires fly.io account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fly.io Multi-Region Application Architecture Overview Compose Fly.io primitives without implying global state that the platform does not provide. Anycast and Fly Proxy route toward Machines, 6PN connects services inside an organization, Machines and volumes are regional, and Managed Postgres has its own supported-region and recovery contract. Prerequisites Users, traffic, latency, availability, residency, recovery, and consistency requirements Service and process-group boundaries plus external dependencies Current provider regions, capacity, pricing, and Managed Postgres availability Instructions Step 1: Partition stateless and stateful work Separate request-serving, workers, scheduled tasks, caches, durable databases, and region-local files. Name the system of record for every data class. Step 2: Design routing and placement Choose primary and secondary regions from observed users, dependency location, residency, and capacity. Document Fly Proxy, public IP, Flycast, or dynamic routing behavior. Step 3: Design the Machine fleet Set process groups, VM resources, Machine counts, health checks, deployment strategy, autostart, shutdown, and failure-domain expectations per region. Step 4: Design data explicitly Use Managed Postgres where its service contract fits. Use volumes only with software-managed replication and recovery or for disposable regional state; never present one volume as multi-region storage. Step 5: Design private and external connectivity Map 6PN names, organization boundaries, WireGuard peers, outbound requirements, certificates, DNS, and third-party trust zones. Step 6: Prove resilience and operations Exercise regional and dependency failure, deploy rollback, database restore, volume restore, secret rotation, monitoring, cost controls, and ownership handoff. Authentication Use separate scoped identities for deployment, observation, database access, and external integrations. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flyio-reference-architecture