What problem does it solve? Porting a text editor between macOS and iOS fails when developers assume NSTextView and UITextView are interchangeable; this Skill maps exactly which features exist on each side and classifies each gap as architectural, API-level, or stack-level so porting effort is scoped correctly. ## Core Features & Use Cases - Capability comparison: Catalogs AppKit-only features (text tables, formatting panels, grammar checking, Services menu, field editor, RTF I/O) and UIKit-only features (UITextInteraction, UITextItem interactions, UITextSelectionDisplayInteraction, UITextLoupeSession, declarative dataDetectorTypes). - Architectural guidance: Explains structural differences in inheritance, scrolling, text storage optionality, selection models, and delegate richness that shape every cross-platform editor. - Porting pitfalls: Documents common mistakes such as assuming NSTextView scrolls itself, touching shared field-editor properties, and silently triggering TextKit 1 fallback. - Use Case: When planning a Mac Catalyst version of an iOS text editor, use this Skill to determine which features need reimplementation versus simple API translation. ## Quick Start Ask the AI to compare NSTextView and UITextView support for a specific text editing feature you plan to port between macOS and iOS.