Agent skill · software engineering · jeremylongshore
runway-reference-architecture
Design a Runway integration that separates admission, provider execution, reconciliation, media storage, and governance. Use when reviewing system boundaries. Trigger with: "Runway architecture", "design Runway service", "Runway production topology".
Why this skill is useful
Provides specific implementation patterns and error handling for the Runway AI video generation platform that the AI wouldn't reliably generate on its own.
What it needs
Requires runwayml installed locally. Requires runway account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Runway Production Control-Plane Architecture Overview The stable architecture centers on an internal operation record rather than a provider request. It isolates credentials, models asynchronous task state, applies cost and concurrency admission, preserves media in owned storage, and makes provider/API drift reviewable. Prerequisites Workload, SLO, data-classification, and budget requirements Current Runway API, model, limits, pricing, and output contracts Owners for security, media rights, moderation, operations, and finance Instructions Step 1: Define trust zones Place clients outside the provider credential boundary. Put the admission API, task worker, reconciler, secret access, and provider egress in a server zone; isolate raw media and final assets by classification. Step 2: Make operation state authoritative Persist operation ID, actor, approval, request fingerprint, model or router policy, provider task ID, state timeline, budget, and output object. Enforce legal state transitions and unique provider IDs. Step 3: Separate control and data planes The control plane validates, queues, retrieves, cancels, and emits internal events. The data plane stages input, performs ephemeral upload when needed, validates output, and copies assets to owned storage. Step 4: Apply governance at admission Check rights, moderation policy, tenant quotas, credit ceiling, model allowlist, duration and ratio schema, and retention before creating billable work. Step 5: Reconcile asynchronously Workers honor per-model concurrency; reconcilers observe THROTTLED and terminal states with bounded polling. Internal consumers receive idempotent events derived from persisted transitions. Step 6: Design for change Pin SDK and API contracts, fingerprint official docs, use model-aware fixtures, canary upgrades, and support both direct model and approved router policies without scattering identifiers. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/runway-reference-architecture