SwiftUI-Agent-Skill AGENTS.md

Agent Guidelines for SwiftUI Expert Skill

This document provides guidance for AI agents working with this skill to ensure consistency and avoid common pitfalls.

Core Principles

1. SwiftUI Focus Only

This is a SwiftUI skill. Do not include:

• Swift concurrency patterns (use .task for SwiftUI-specific needs only)
• General Swift language features unrelated to SwiftUI
• Backend or server-side Swift patterns
• UIKit patterns (except when bridging is necessary)

2. No Code Formatting or Linting

Do not include formatting/linting rules. Avoid:

• Property ordering requirements (environment, state, body, etc.)
• Code organization mandates
• Whitespace or indentation rules
• Naming convention enforcement
• File structure requirements

Exception: Mention organization patterns as optional suggestions for readability, never as requirements.

3. No Architectural Opinions

Stick to facts, not architectures. Avoid:

• Enforcing MVVM, MVC, VIPER, or any specific architecture
• Mandating view model patterns
• Requiring specific folder structures
• Dictating dependency injection patterns
• Prescribing router/coordinator patterns

Exception: Suggest separating business logic for testability without enforcing how.

4. Keep Tooling SwiftUI-Specific and Consent-Aware

The skill includes focused Instruments tooling for SwiftUI performance work. Tool-specific instructions are allowed only when they directly support the bundled trace recording and analysis workflows. Do not add unrelated IDE, debugging, build-system, or general command-line guidance.

Agents using the trace tooling must:

• Prefer app-scoped --attach or --launch recordings.
• Explain the privacy implications and obtain explicit user approval before a system-wide recording.
• Pass --allow-system-wide-recording with --all-processes after approval.
• Avoid exposing environment-variable values or other secrets in output.
• Treat trace files and extracted logs as potentially sensitive user data.