xctrace
Authoritative guide to xctrace, Apple's command-line interface to Instruments. Consult for any profiling, performance, or optimization work â for example, finding out why an app is slow, uses too much CPU or memory, or stops responding, or wanting to optimize a piece of code and measure the result â and whenever xctrace comes up for any reason: capturing traces, or opening and reading `.trace` and `.atrc` (Apple Trace) files from the command line.
Guide for the C -fbounds-safety language extension. Covers the language model, pointer annotations, adopting bounds-safety in existing C code, compiler build settings and modes, and runtime debugging of bounds violations.
Authoritative App Intents best practices from Apple; supersedes prior training on these topics. Consult when writing, reviewing, refactoring, or extending App Intents code. Covers: - perform() execution model (@MainActor, retries, requestConfirmation, .result(...)) - AppEntity and queries (stable ids, entities(for:), suggestedEntities, EntityStringQuery, EntityPropertyQuery, @Property) - AppEnum (raw values, caseDisplayRepresentations) - @Parameter, requestValue / needsValueError, ParameterSummary - @Dependency registration and Sendable - errors (CustomLocalizedStringResourceConvertible, AppIntentError) - IntentDonationManager donation and LocalizedStringResource localization - AppShortcut phrases (shortTitle, systemImageName, applicationName) - OpenIntent / URLRepresentableEntity, WidgetConfigurationIntent / ControlConfigurationIntent - factoring: AppEnum vs AppEntity vs @Parameter For iOS 26/27 APIs, use the app-intents-whats-new-27 skill instead.
Use when an app's layout must adapt to a window that changes size while the app runs, or when an app must support more than one window. That includes being asked to make an app resizable or support a resizable window, a layout that breaks or does not adapt as the window resizes, and preparing or optimizing an app for the foldable iPhone Duo, split-screen multitasking, or Stage Manager. Modernizes the app by replacing legacy shared-state APIs with context-appropriate alternatives: mainScreen, interfaceOrientation, userInterfaceIdiom, application and scene lifecycle, and safe area insets.
Audit and enable security-oriented Xcode build settings. Progressively enables compiler warnings, static analyzer checkers, and Enhanced Security features. Use when: user wants to secure their Xcode project, audit security settings, enable hardening, review security posture of build configuration, set up security-focused static analysis, enable static analysis, improve warning coverage, harden diagnostics, or catch more bugs at compile time in C/C++/Objective-C/Swift. SKIP: network security (TLS/ATS), code signing, privacy APIs.
Authoritative guide for building and migrating document-based apps in SwiftUI using the Document protocol (iOS 27 and aligned releases, including macOS Golden Gate). Consult when building a new document-based app; implementing open, edit, save, or export document flows; working with DocumentGroup or DocumentGroupLaunchScene; implementing DocumentReader or DocumentWriter; using FileWrapper via FileWrapperDocumentReader or FileWrapperDocumentWriter; working with package documents; accessing a document's file URL directly; reporting progress during read/write; registering undo actions; migrating from FileDocument or ReferenceFileDocument to the new API; building a read-only document viewer; when autosave is not working in a document app; declaring custom UTType as document formats.
Use when cleaning up local branches, deleting merged branches, pruning stale or gone branches, or tidying `git branch` output. Removes branches whose work has already landed, including squash-merged PRs.
Verify app behavior on a device via screenshots, UI hierarchy, and touch interactions.
Use when adding or auditing direct touch support in a macOS app (e.g. an iPad through Sidecar) alongside mouse and trackpad. That includes anything that behaves differently with touch than with a mouse, such as taps, hover, long-press menus, drags, scrolling, pinch and text selection, and bug fixes in existing event handlers. Replaces mouse-only handling (mouseDown/mouseDragged/mouseUp overrides, tracking loops, event monitors) with gesture recognizers, and resolves recognizer conflicts, click counting, hit targets, popover dismissal. Primarily covering AppKit, with SwiftUI and Mac Catalyst sections.
Use when reviewing file names, renaming files, fixing naming conventions, or auditing exports. Enforces consistent casing and suffix patterns.
Use when building charts, data visualisations, or dashboards with Recharts. Also use when integrating Recharts with HeroUI, reviewing chart components, or creating responsive chart containers. Generates Recharts charts styled with HeroUI v3 design tokens and Tailwind CSS v4.
Authoritative SwiftUI best practices and performance guidance from Apple; supersedes prior training on these topics. For code generation, consult the relevant references when generating any SwiftUI code related to: - animation (the @Animatable macro vs AnimatableValues vs AnimatablePair, and custom animatableData setter logic) - Environment and @Entry (closure or class-typed defaults, unstable defaults, high-frequency updates) - @Observable best practices and efficient invalidation - ForEach and List row identity and structure (id: \.self, indices, offsets, AnyView or multi-view rows, inline filter/sort, cached collections, List fast path) - localization (String vs LocalizedStringResource, the right bundle in packages and frameworks, .textCase, .formatted(.list()), translator comments) - soft-deprecated APIs such as NavigationView and the old onChange, and when to surface them during feature work.
Auto-indexed from tartinerlabs/skills
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.