axiom-audit-textkit

Analyze TextKit architecture and detect legacy anti-patterns in UIKit and AppKit text views.

34|2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-textkit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: axiom-audit-textkit
Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/axiom-audit-textkit
Command: npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-textkit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies critical TextKit 1 anti-patterns and missing configurations that cause silent fallback to legacy layout engines, resulting in the loss of modern Writing Tools support and broken text rendering for international languages.

Core Features & Use Cases

  • Architecture Mapping: Automatically inventories text views and identifies the active TextKit version (1 vs 2).
  • Anti-Pattern Detection: Scans for deprecated glyph APIs, direct layout manager access, and missing Writing Tools lifecycle guards.
  • Use Case: Use this tool when refactoring a legacy macOS or iOS text editor to ensure full compatibility with iOS 18/macOS 15 Writing Tools and to prevent layout regressions in complex scripts like Arabic or Indic languages.

Quick Start

Run the axiom-audit-textkit skill to perform a full architectural scan and identify all TextKit 1 fallback triggers in the current repository.

Frequently Asked Questions about axiom-audit-textkit

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

FAQPage Schema
How do I migrate from TextKit 1 to TextKit 2 in my iOS app?▼

To migrate to TextKit 2, you must replace legacy layout manager access and deprecated glyph APIs with NSTextLayoutManager. An architectural scan detects these anti-patterns to prevent silent fallback to the legacy engine.

Why does my UITextView silently fall back to the legacy TextKit layout engine?▼

Silent fallback to the legacy TextKit engine is triggered by TextKit 1 anti-patterns like direct layout manager access or missing Writing Tools lifecycle guards. Scanning the codebase identifies these configuration gaps.

How do I add Apple Writing Tools support to a macOS or iOS text editor?▼

Adding Writing Tools support requires migrating text views to TextKit 2 and implementing Writing Tools coordinators. An architecture audit validates this integration and checks for missing lifecycle guards to ensure full compatibility.

Does TextKit 2 migration affect text rendering for international languages?▼

TextKit 2 migration improves international text layout for complex scripts like Arabic and Indic languages. Removing legacy anti-patterns prevents layout regressions and ensures proper rendering.

What are common TextKit 1 anti-patterns when refactoring UIKit text views?▼

Common TextKit 1 anti-patterns include using deprecated glyph APIs, direct layout manager access, and missing Writing Tools lifecycle guards. Detecting these issues is required for TextKit 2 migration.