Architectural Invariant Design: Compose Multiplatform Skiko Canvas CADisplayLink VSync Frame-Pacing Barrier
Compose Multiplatform Skiko Canvas CADisplayLink VSync Frame-Pacing Barrier defines an industrial-grade behavioral standard for mobile engineering. Enforces strict synchronization between Skiko rendering passes and Apple's CADisplayLink to eliminate micro-stuttering, tearing, and thermal throttling on iOS. Mandates explicit CAFrameRateRange configuration for 120Hz ProMotion displays and gates canvas redrawing on actual hardware VSync pulses rather than decoupled Kotlin coroutine timers. 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 | Decoupled Coroutine Timers and Unbounded Skiko Redraw Triggers Causing Frame Drops and Battery Drain | 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 drive Skiko custom canvas redraw passes through a native CADisplayLink registered with NSRunLoop.mainRunLoop in NSRunLoopCommonModes.
Engineers MUST ALWAYS drive Skiko custom canvas redraw passes through a native CADisplayLink registered with NSRunLoop.mainRunLoop in NSRunLoopCommonModes.
Engineers MUST configure preferredFrameRateRange (CAFrameRateRange) explicitly on CADisplayLink instances to support 120Hz ProMotion and prevent 60Hz lock-in.
Engineers MUST configure preferredFrameRateRange (CAFrameRateRange) explicitly on CADisplayLink instances to support 120Hz ProMotion and prevent 60Hz lock-in.
Engineers MUST NOT utilize CoroutineScope.launch with delay() or fixed-rate polling loops to simulate frame ticks or orchestrate canvas invalidations.
Engineers MUST NOT utilize CoroutineScope.launch with delay() or fixed-rate polling loops to simulate frame ticks or orchestrate canvas invalidations.
Services MUST gate Skiko redraw calls behind dirty-state flags to avoid firing zero-delta render passes on idle CADisplayLink ticks.
Services MUST gate Skiko redraw calls behind dirty-state flags to avoid firing zero-delta render passes on idle CADisplayLink ticks.
Components NEVER instantiate multiple uncoordinated CADisplayLink instances per UIViewController
Components NEVER instantiate multiple uncoordinated CADisplayLink instances per UIViewController; frame events must be centralized via a single presentation barrier.
Frequently Asked Technical Questions
Common questions developers face when configuring AI coding assistants for this stack:
Q:Why is Compose Multiplatform Skiko Canvas CADisplayLink VSync Frame-Pacing Barrier critical for AI coding assistants?
Enforces strict synchronization between Skiko rendering passes and Apple's CADisplayLink to eliminate micro-stuttering, tearing, and thermal throttling on iOS. Mandates explicit CAFrameRateRange configuration for 120Hz ProMotion displays and gates canvas redrawing on actual hardware VSync pulses rather than decoupled Kotlin coroutine timers. 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 (Decoupled Coroutine Timers and Unbounded Skiko Redraw Triggers Causing Frame Drops and Battery Drain) 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.