Architectural Invariant Design: Compose Multiplatform iOS CAMetalLayer CADisplayLink V-Sync Cadence Lock
Compose Multiplatform iOS CAMetalLayer CADisplayLink V-Sync Cadence Lock defines an industrial-grade behavioral standard for mobile engineering. Aligns Kotlin Multiplatform / Compose Multiplatform iOS rendering loop passes strictly with CoreAnimation CADisplayLink ticks on ProMotion (120Hz) and variable refresh rate displays. Prevents thread contention, main thread stalls, and dropped frame pacing by synchronizing CAMetalLayer drawable presentation calls with NSRunLoopCommonModes ticks rather than unbounded Kotlin coroutine dispatchers. 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 Coroutine Render Dispatches and Unsynchronized CAMetalLayer NextDrawable Calls Leading to ProMotion Jitter | 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 hook the Compose Multiplatform frame clock to a platform-native CADisplayLink attached to NSRunLoop.mainRunLoop in NSRunLoopCommonModes.
Engineers MUST ALWAYS hook the Compose Multiplatform frame clock to a platform-native CADisplayLink attached to NSRunLoop.mainRunLoop in NSRunLoopCommonModes.
Engineers MUST NOT trigger software-driven re-draws or metal render passes via unconstrained Kotlin Coroutine dispatchers (e.g., Dispatchers.Default or fixed-delay delay(16) loops).
Engineers MUST NOT trigger software-driven re-draws or metal render passes via unconstrained Kotlin Coroutine dispatchers (e.g., Dispatchers.Default or fixed-delay delay(16) loops).
Code MUST set `CAFrameRateRange(minimum
Code MUST set `CAFrameRateRange(minimum: 60.0, preferred: 120.0, maximum: 120.0)` on CADisplayLink when targeting high refresh rate ProMotion devices to avoid adaptive rate down-stepping hitch.
Services MUST acquire CAMetalDrawable instances only during the CADisplayLink callback or within a strictly bounded draw pass with `presentsWithTransaction = false` and non-blocking timeout handling.
Services MUST acquire CAMetalDrawable instances only during the CADisplayLink callback or within a strictly bounded draw pass with `presentsWithTransaction = false` and non-blocking timeout handling.
Components NEVER block the main RunLoop waiting for GPU command buffers
Components NEVER block the main RunLoop waiting for GPU command buffers; frame submission must use `MTLCommandBuffer.addCompletedHandler` or double/triple buffering dispatch semaphores with a depth of 2 or 3.
Frequently Asked Technical Questions
Common questions developers face when configuring AI coding assistants for this stack:
Q:Why is Compose Multiplatform iOS CAMetalLayer CADisplayLink V-Sync Cadence Lock critical for AI coding assistants?
Aligns Kotlin Multiplatform / Compose Multiplatform iOS rendering loop passes strictly with CoreAnimation CADisplayLink ticks on ProMotion (120Hz) and variable refresh rate displays. Prevents thread contention, main thread stalls, and dropped frame pacing by synchronizing CAMetalLayer drawable presentation calls with NSRunLoopCommonModes ticks rather than unbounded Kotlin coroutine dispatchers. 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 Coroutine Render Dispatches and Unsynchronized CAMetalLayer NextDrawable Calls Leading to ProMotion Jitter) 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.