Architectural Invariant Design: Compose Multiplatform iOS CADisplayLink & ProMotion VSync Cadence Synchronization
Compose Multiplatform iOS CADisplayLink & ProMotion VSync Cadence Synchronization defines an industrial-grade behavioral standard for mobile engineering. Enforces rigid synchronization between Skiko's Metal rendering pipeline and iOS CADisplayLink VSync pulses. Prevents continuous unthrottled GPU render loops and frame pacing jitter by binding redraw invalidations strictly to ProMotion refresh rate targets and on-demand dirty state transitions. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.
Hazard Analysis: What Breaks Without This Rule
The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:
| Failure Mode | AI Symptom (The Anti-Pattern) | Severity | Production Impact & Remedy |
|---|---|---|---|
| AI Hallucination & Deprecation Drift | Free-Running Dispatch Loops and Unsynchronized VSync Invalidation in Skiko Metal ViewControllers | Critical | Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository. |
| Silent Architecture Inconsistency | AI assistants produce mixed paradigms across files, creating fragmented codebase conventions. | Medium | Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails. |
Step-by-Step Production Directives
Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:
Engineers MUST ALWAYS attach CADisplayLink instances to NSRunLoop.mainRunLoop using NSRunLoopCommonModes to ensure continuous rendering during touch tracking and scrolling.
Engineers MUST ALWAYS attach CADisplayLink instances to NSRunLoop.mainRunLoop using NSRunLoopCommonModes to ensure continuous rendering during touch tracking and scrolling.
Engineers MUST NOT invoke Skiko redraw routines via free-running coroutine loops, NSTimer, or unconstrained DispatchQueue calls.
Engineers MUST NOT invoke Skiko redraw routines via free-running coroutine loops, NSTimer, or unconstrained DispatchQueue calls.
Engineers MUST configure preferredFrameRateRange (minimum, preferred, maximum) via CAFrameRateRange on iOS 15+ to properly leverage Apple ProMotion high-refresh screens without locking the GPU to an inefficient static 60Hz or draining battery at static 120Hz.
Engineers MUST configure preferredFrameRateRange (minimum, preferred, maximum) via CAFrameRateRange on iOS 15+ to properly leverage Apple ProMotion high-refresh screens without locking the GPU to an inefficient static 60Hz or draining battery at static 120Hz.
Code MUST pause CADisplayLink (isPaused = true) whenever Compose reports no pending snapshot mutations, layout passes, or running animations.
Code MUST pause CADisplayLink (isPaused = true) whenever Compose reports no pending snapshot mutations, layout passes, or running animations.
Code MUST coordinate Metal command buffer presentation with CADisplayLink targetTimestamp to prevent presentation deadline misses and temporal jank.
Code MUST coordinate Metal command buffer presentation with CADisplayLink targetTimestamp to prevent presentation deadline misses and temporal jank.
Components NEVER trigger needRedraw() inside draw callbacks without an active transient animation state, preventing infinite invalidation loops.
Components NEVER trigger needRedraw() inside draw callbacks without an active transient animation state, preventing infinite invalidation loops.
Frequently Asked Technical Questions
Common questions developers face when configuring AI coding assistants for this stack:
Q:Why is Compose Multiplatform iOS CADisplayLink & ProMotion VSync Cadence Synchronization critical for AI coding assistants?
Enforces rigid synchronization between Skiko's Metal rendering pipeline and iOS CADisplayLink VSync pulses. Prevents continuous unthrottled GPU render loops and frame pacing jitter by binding redraw invalidations strictly to ProMotion refresh rate targets and on-demand dirty state transitions. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.
Q:How does adopting this rule prevent AI hallucinations?
This rule explicitly declares what the AI must avoid (Free-Running Dispatch Loops and Unsynchronized VSync Invalidation in Skiko Metal ViewControllers) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.
Q:Which AI coding environments are supported?
This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).
Q:Can I combine this rule with other technology stacks?
Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.