agentleFS
mhavivmhaviv/Swift-FocusEngine-Agent-Skill/SKILL.md

swift-focusengine-pro

Skill20 starsChanged 7 months agoMITView on GitHub

Reviews, writes, and fixes focus management code for all Apple platforms (tvOS, iOS/iPadOS, watchOS, visionOS, macOS), covering SwiftUI, UIKit, AppKit, and RealityKit. Use when reading, writing, or reviewing apps that handle focus, hover, key view loops, or Digital Crown navigation.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 2 are distinctive, and 15 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 15

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for critical anti-patterns using references/anti-patterns.md.

    line 28
  2. Very specific:

    Check focus styling and visual feedback using references/focus-styling.md.

    line 36
  3. Very specific:

    Verify focus restoration and data reload handling using references/focus-restoration.md.

    line 37
  4. Very specific:

    Check async/await and data loading focus patterns using references/async-focus.md.

    line 39
  5. Very specific:

    Verify accessibility integration using references/accessibility-focus.md.

    line 40
  6. Very specific:

    Check debugging and testing practices using references/debugging.md.

    line 41
  7. Distinctive:

    If doing a partial review, load only the relevant reference files.

    line 43
  8. Very specific:

    If nothing is in the geometric path, focus does not move.

    line 51
  9. Very specific:

    Never use .disabled() on tvOS to toggle interactivity — it removes views from the focus chain entirely.

    line 52
  10. Very specific:

    Prefer ScrollPosition over ScrollViewReader.scrollTo() — imperative scrollTo creates feedback loops with the focus engine (anti-pattern …

    line 54
  11. Distinctive:

    Always test on real Apple TV hardware — Simulator focus behavior differs.

    line 55
  12. Very specific:

    Use focusGroupIdentifier (iOS 14+, UIKit) to define custom focus groups — this API is NOT available on tvOS.

    line 60
  13. Very specific:

    Use UIFocusHaloEffect to customize the system focus ring — NOT available on tvOS.

    line 61
  14. Very specific:

    Do NOT add .focusable() to system controls (Picker, Stepper, Toggle) — they already handle it.

    line 70
  15. Very specific:

    Use .hoverEffect() for gaze visual feedback.

    line 74
  16. Very specific:

    Never add .focusable() to Buttons or NavigationLinks — they are already focusable.

    line 89
  17. Very specific:

    Do not mix @FocusState (SwiftUI) and UIKit focus APIs (setNeedsFocusUpdate) on the same view hierarchy branch.

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review focus management code for correctness, modern API usage, and adherence to Apple's focus engine rules. Covers all Apple platforms. Report only genuine problems — do not nitpick or invent issues.

Review process:

  1. Check for critical anti-patterns using references/anti-patterns.md.
  2. Determine the target platform and load the appropriate references:
    • tvOS: references/swiftui-focus.md and references/uikit-focus.md.
    • iOS/iPadOS: references/ios-focus.md (focus groups, halo, keyboard nav).
    • watchOS: references/watchos-focus.md (Digital Crown, sequential focus).
    • visionOS: references/visionos-focus.md (gaze, hover effects) and references/realitykit-focus.md (RealityKit entities, gestures, volumes).
    • macOS: references/macos-focus.md (key view loop, focus ring, NSView focus, focusedValue for menus, Mac Catalyst).
    • For cross-platform: load all relevant references.
  3. Check focus styling and visual feedback using references/focus-styling.md.
  4. Verify focus restoration and data reload handling using references/focus-restoration.md.
  5. Audit layout patterns for focus section isolation using references/layout-patterns.md.
  6. Check async/await and data loading focus patterns using references/async-focus.md.
  7. Verify accessibility integration using references/accessibility-focus.md.
  8. Check debugging and testing practices using references/debugging.md.

If doing a partial review, load only the relevant reference files.

Core Instructions

tvOS

  • tvOS uses a focus-based navigation model — every interactive element must be reachable via the Siri Remote's directional pad.
  • Focus movement is purely geometric — the focus engine draws a rectangle from the currently focused view in the swipe direction and picks the nearest focusable view in that rectangle.
  • If nothing is in the geometric path, focus does not move. Period. Use .focusSection() (SwiftUI) or UIFocusGuide (UIKit) to bridge gaps.
  • Never use .disabled() on tvOS to toggle interactivity — it removes views from the focus chain entirely. .allowsHitTesting(false) is unreliable on tvOS (may map to isUserInteractionEnabled = false). Preferred: gate the action inside the button closure, or use the dual @FocusState + .disabled() gating pattern for lists (anti-pattern #25).
  • prefersDefaultFocus(_:in:) does NOT work inside ScrollView on tvOS — use defaultFocus(_:_:priority:) instead. Note: defaultFocus with .userInitiated only fires on initial appearance, NOT on every re-entry.
  • Prefer ScrollPosition over ScrollViewReader.scrollTo() — imperative scrollTo creates feedback loops with the focus engine (anti-pattern #26).
  • Always test on real Apple TV hardware — Simulator focus behavior differs.

iOS/iPadOS

  • Focus is a secondary interaction model — it only activates with a hardware keyboard connected.
  • Tab moves between focus groups; arrow keys move within a group. This two-level model does NOT exist on tvOS.
  • Use focusGroupIdentifier (iOS 14+, UIKit) to define custom focus groups — this API is NOT available on tvOS.
  • Use UIFocusHaloEffect to customize the system focus ring — NOT available on tvOS.
  • Set allowsFocus = true and selectionFollowsFocus = true on collection/table views for keyboard navigation.
  • Your app must work perfectly without keyboard focus — always test with touch only.

watchOS

  • Focus routes Digital Crown input to the correct view — shown by a green border.
  • Focus is sequential (layout order), NOT spatial/directional.
  • .focusSection() is NOT available on watchOS.
  • .focusable() MUST come BEFORE .digitalCrownRotation() — reversing silently breaks crown input.
  • Do NOT add .focusable() to system controls (Picker, Stepper, Toggle) — they already handle it.

visionOS

  • Eye gaze = hover targeting, NOT focus. onHover(perform:) does NOT fire from gaze — only from pointer devices.
  • Use .hoverEffect() for gaze visual feedback. System controls get it automatically; custom views need it explicitly.
  • @FocusState only activates with keyboard (Magic Keyboard), VoiceOver, or Switch Control.
  • RealityKit entities need InputTargetComponent + CollisionComponent + HoverEffectComponent for gaze interaction.
  • .focusEffectDisabled() hides keyboard focus ring; .hoverEffectDisabled() disables gaze hover — they are different.

macOS

  • macOS uses a key view loop — Tab/Shift-Tab moves between views in a defined sequence. This is NOT spatial like tvOS.
  • Custom NSView subclasses must override acceptsFirstResponder to return true — the default is false, making the view invisible to Tab navigation.
  • autorecalculatesKeyViewLoop = true on NSWindow overwrites all manual nextKeyView connections. Pick one approach.
  • Focus ring customization: override focusRingType, focusRingMaskBounds, and drawFocusRingMask() on NSView.
  • focusedValue / focusedSceneValue are critical on macOS for making menu bar commands respond to the current selection.
  • Mac Catalyst: inherits iPad UIFocusSystem. If the iPad app doesn't support keyboard focus, the Catalyst app won't either.
  • Full Keyboard Access is OFF by default — most users only Tab between text fields and lists, not all controls.

All Platforms

  • Never add .focusable() to Buttons or NavigationLinks — they are already focusable. Adding it creates a double-focus wrapper.
  • Do not mix @FocusState (SwiftUI) and UIKit focus APIs (setNeedsFocusUpdate) on the same view hierarchy branch.
  • VoiceOver focus (@AccessibilityFocusState) is completely separate from UI focus (@FocusState).

Toolchain status (as of Xcode 27 beta, Aug 2026)

  • OS 26 added exactly one new focus API — accessibilityDefaultFocus(_:_:) (SwiftUI, all platforms 26.0+, sets default VoiceOver focus; see references/accessibility-focus.md) — and no focus deprecations; the OS 27 betas add none. Verified by scanning the installed 26.5 SDK interfaces for all five platforms, not just release notes. What else changed around focus: Liquid Glass alters focused-control appearance on tvOS 26 (4K 2nd gen+ only — older devices keep pre-glass visuals), ControlSize works on tvOS 26+, .sidebarAdaptable TabView (tvOS 18+) moves the tab region to a leading sidebar, and visionOS 26 adds opt-in gaze scrolling (.scrollInputBehavior(.enabled, for: .look)).
  • The 27 SDKs require the scene-based lifecycle on iOS/iPadOS/tvOS/visionOS/Mac Catalyst (apps fail to launch without it; macOS and watchOS are unaffected), and tvOS 27 adds Dynamic Type — both affect focus sample scaffolding and sizing, not focus APIs.
  • Swift 6.2: new Xcode 26 projects default to module-wide MainActor isolation; keep explicit @MainActor in examples that must compile in both worlds (see references/async-focus.md).

Output Format

Organize findings by file. For each issue:

  1. State the file and relevant line(s).
  2. Name the rule being violated (e.g., "Do not remove ordinary controls from the tvOS focus chain — gate the action instead of using .disabled(); the deliberate dual-@FocusState entry-gating pattern in anti-pattern #25 is the one exception").
  3. Show a brief before/after code fix.

Skip files with no issues. End with a prioritized summary of the most impactful changes to make first.

Example output:

TopicsView.swift

Line 49: .disabled() removes view from tvOS focus chain (anti-pattern #1).

// Before
TopicClipsGridView(...)
    .disabled(!wrapper.isGridFocusable)

// After — gate the action, not the view
TopicClipsGridView(...)
    .opacity(wrapper.isGridFocusable ? 1.0 : 0.5)
// Move the guard inside the button/action closures instead

Line 72: Missing .focusSection() on horizontal ScrollView in vertical layout.

// Before
ScrollView(.horizontal) {
    HStack { /* row items */ }
}

// After
ScrollView(.horizontal) {
    HStack { /* row items */ }
}
.focusSection()

Summary

  1. Focus breakage (critical): .disabled() on line 49 removes grid from focus chain entirely.
  2. Focus jumping (high): Missing .focusSection() causes cross-row focus jumps.

End of example.

References

  • references/anti-patterns.md — Critical mistakes that break focus navigation: 30 numbered anti-patterns across tvOS/general and macOS-specific sections.
  • references/swiftui-focus.md — SwiftUI focus APIs: @FocusState, focusSection, prefersDefaultFocus, focused, defaultFocus, onMoveCommand.
  • references/uikit-focus.md — UIKit focus APIs: UIFocusEnvironment, UIFocusGuide, shouldUpdateFocus, didUpdateFocus, preferredFocusEnvironments, UIFocusDebugger.
  • references/focus-styling.md — Focus visual feedback: ButtonStyle with isFocused, FocusBorder, hover effects, scale/shadow animations, macOS focus ring styling.
  • references/focus-restoration.md — Handling focus after data reloads, navigation, and async updates.
  • references/layout-patterns.md — Common tvOS layouts: table-of-collections, sidebar+content, tab bar, horizontal shelves.
  • references/ios-focus.md — iOS/iPadOS-specific: focus groups, focusGroupIdentifier, UIFocusHaloEffect, keyboard navigation, allowsFocus, selectionFollowsFocus.
  • references/watchos-focus.md — watchOS-specific: Digital Crown routing, sequential focus, digitalCrownRotation, focusable ordering.
  • references/visionos-focus.md — visionOS-specific: gaze vs focus vs hover, HoverEffect, HoverEffectGroup, RealityKit HoverEffectComponent, spatial input.
  • references/macos-focus.md — macOS-specific: key view loop, NSView focus (acceptsFirstResponder, canBecomeKeyView), focus ring customization, focusedValue for menus, Mac Catalyst, Full Keyboard Access.
  • references/realitykit-focus.md — RealityKit entity hover: HoverEffectComponent, collision shapes, gestures, shader effects, mixed SwiftUI+RealityKit hierarchies.
  • references/async-focus.md — Async focus patterns: @MainActor coordination, focus after data load, NavigationStack pop, Task cancellation, debouncing.
  • references/accessibility-focus.md — Accessibility integration: @AccessibilityFocusState, VoiceOver + focus, Full Keyboard Access, Switch Control, Reduce Motion.
  • references/debugging.md — UIFocusDebugger, _whyIsThisViewNotFocusable, launch arguments, Quick Look, macOS first responder debugging.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.