Use to verify MacMagazine module boundaries and system compliance are intact after adding/moving code or editing a Package.swift. Detects cross-feature imports, wrong dependency direction, card-system bypasses, raw WKWebView usage, and unregistered SwiftData models. Read-only.
Use this agent for ANY iOS code-related task in MacMagazine — feature implementation, bug fixes, architecture decisions, code reviews, test writing, or refactoring. It enforces all CLAUDE.md rules without exception and never requires reminders. Examples: Context: The user asks to implement a new feature. user: "Add…
Use to review Swift/SwiftUI changes in MacMagazine with a very high bar — after implementing a feature, editing a ViewModel/service/view, or before a PR. Reviews for correctness, Swift 6.2 concurrency, idiom, and fidelity to the MacMagazine card/WebView/search/theme systems. Review-only; never edits files.
Use to build MacMagazine and run the test suite (or a filtered subset) and report real results, isolating failures. Invoke after code changes or when asked whether tests pass. Returns pasted output, never a fabricated summary. Read-only diagnosis; never edits files.
MacMagazine design reference — theme tokens, card selection, typography, touch targets, accessibility, dark mode. Use when creating or restyling UI, choosing which card view renders content, picking colors or fonts, or when the user mentions "design", "theme", "card", "dark mode", or "accessibility".
Definition of Done verification for MacMagazine — build, test, lint, code-quality and git checks with real evidence. Use before marking any task complete, before committing, or when the user says "done", "verify", "is this finished", or "check the work".
Bug-fix and refactoring workflow for MacMagazine — root cause analysis, pattern-matching fix, regression verification. Use when fixing a crash or bug, resolving a GitHub issue, debugging unexpected behavior, refactoring, or when the user says "fix", "bug", "broken", "issue.
Complete feature-implementation workflow for MacMagazine with pattern matching, review gates, and quality verification. Use when implementing a new feature or module, adding a view/ViewModel/navigation flow, or when the user says "implement", "build", "add feature", or "create a screen". For bug fixes use ios-fix…
Read-only audit of the entire MacMagazine codebase for quality, consistency, and compliance with CLAUDE.md and .claude/rules standards. Use periodically, before releases, or when the user says "sanity check", "audit", "health check", or "how is the codebase".
Pre-flight checklist before writing any code in MacMagazine — requirements, reusable-component search, pattern study, branch setup. Use at the start of any feature or enhancement, before the first line of code, or when the user says "start", "new feature", "begin implementing", or "set up a branch".