apple-text-fallback-triggers

Catalog and diagnose TextKit 1 fallback triggers that downgrade TextKit 2.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/sitapix/apple-text --skill apple-text-fallback-triggers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apple-text-fallback-triggers
Source: https://github.com/sitapix/apple-text/tree/main/skills/apple-text-fallback-triggers
Command: npx skills add https://github.com/sitapix/apple-text --skill apple-text-fallback-triggers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you audit and diagnose all known TextKit 1 fallback triggers to prevent unwanted downgrades to TextKit 1 in TextKit 2 environments.

Core Features & Use Cases

  • Complete catalog of fallback triggers including explicit layout manager access, glyph API usage, unsupported attributes, multi-container layouts, and printing scenarios.
  • Recovery guidance for safe opt-out and migration to TextKit 2 with minimal disruption.
  • Use Case: When debugging why a TextKit 2 view unexpectedly switches to compatibility mode, consult this catalog to identify the trigger and apply a corrective pattern.

Quick Start

Review the catalog and detection steps to identify the trigger and plan remediation.

Frequently Asked Questions about apple-text-fallback-triggers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my TextKit 2 view unexpectedly downgrade to TextKit 1?

TextKit 2 downgrades to TextKit 1 fallback when encountering explicit layout manager access, glyph API usage, unsupported attributes, multi-container layouts, or printing scenarios. This catalog identifies those triggers to help maintain stable TextKit 2 behavior.

How do I diagnose TextKit 1 fallback triggers in my iOS app?

To diagnose TextKit 1 fallback triggers, review the catalog of explicit access patterns, glyph-based APIs, and unsupported attributes. Apply the detection steps to identify the specific trigger causing the downgrade and plan remediation for your UIKit-based iOS views.

What TextKit 2 attributes cause a downgrade to TextKit 1?

Unsupported attributes in TextKit 2 cause a downgrade to TextKit 1. Additionally, explicit layout manager access, glyph-based API usage, multi-container layouts, and printing scenarios trigger this fallback behavior across UIKit and AppKit views.

Does this TextKit fallback catalog work for macOS AppKit views?

Yes, this catalog works for macOS AppKit views. It covers both UIKit-based iOS apps and AppKit macOS views to diagnose known TextKit 1 fallback triggers like explicit layout manager access and multi-container layouts.

How do I recover after triggering a TextKit 1 fallback?

To recover from a TextKit 1 fallback, follow the provided recovery guidance for safe opt-out and migration to TextKit 2. This ensures minimal disruption while applying corrective patterns to maintain stable TextKit 2 behavior.