xcode-project-analyzer
Audit Xcode project configuration, build settings, scheme behavior, and script phases to find build-time improvements with explicit approval gates. Use when a developer wants project-level build analysis, slow incremental builds, guidance on target dependencies, build settings review, run script phase analysis, parallelization improvements, or module-map and DEFINES_MODULE configuration.
What this skill does
# Xcode Project Analyzer Use this skill for project- and target-level build inefficiencies that are unlikely to be solved by source edits alone. ## Core Rules - Recommendation-first by default. - Require explicit approval before changing project files, schemes, or build settings. - Prefer measured findings tied to timing summaries, build logs, or project configuration evidence. - Distinguish debug-only pain from release-only pain. ## What To Review - scheme build order and target dependencies - debug vs release build settings against the [build settings best practices](references/build-settings-best-practices.md) - run script phases and dependency-analysis settings - derived-data churn or obviously invalidating custom steps - opportunities for parallelization - explicit module dependency settings and module-map readiness - "Planning Swift module" time in the Build Timing Summary -- if it dominates incremental builds, suspect unexpected input modification or macro-related invalidation - asset catalog compilation time, especially in targets with large or numerous catalogs - `ExtractAppIntentsMetadata` time in the Build Timing Summary -- if this phase consumes significant time, record it as `xcode-behavior` (report the cost and impact, but do not suggest a repo-local optimization unless there is explicit Apple guidance) - zero-change build overhead -- if a no-op rebuild exceeds a few seconds, investigate fixed-cost phases (script execution, codesign, validation, CopySwiftLibs) - CocoaPods usage -- if a `Podfile` or `Pods.xcodeproj` exists, CocoaPods is deprecated; recommend migrating to SPM and do not attempt CocoaPods-specific optimizations (see [project-audit-checks.md](references/project-audit-checks.md)) - Task Backtraces (Xcode 16.4+: Scheme Editor > Build > Build Debugging) to diagnose why tasks re-run unexpectedly in incremental builds ## Build Settings Best Practices Audit Every project audit should include a build settings checklist comparing the project's Debug and Release configurations against the recommended values in [build-settings-best-practices.md](references/build-settings-best-practices.md). Present results using checkmark/cross indicators (`[x]`/`[ ]`). The scope is strictly build performance -- do not flag language-migration settings like `SWIFT_STRICT_CONCURRENCY` or `SWIFT_UPCOMING_FEATURE_*`. ## Apple-Derived Checks Review these items in every audit: - target dependencies are accurate and not missing or inflated - schemes build in `Dependency Order` - run scripts declare inputs and outputs - `.xcfilelist` files are used when scripts have many inputs or outputs - `DEFINES_MODULE` is enabled where custom frameworks or libraries should expose module maps - headers are self-contained enough for module-map use - explicit module dependency settings are consistent for targets that should share modules ## Typical Wins - skip debug-time scripts that only matter in release - add missing script guards or dependency-analysis metadata - remove accidental serial bottlenecks in schemes - align build settings that cause unnecessary module variants - fix stale project structure that forces broader rebuilds than necessary - identify linters or formatters that touch file timestamps without changing content, silently invalidating build inputs and forcing module replanning - split large asset catalogs into separate resource bundles across targets to parallelize compilation - use Task Backtraces to pinpoint the exact input change that triggers unnecessary incremental work ## Reporting Format For each issue, include: - evidence - likely scope - why it affects clean builds, incremental builds, or both - estimated impact - approval requirement If the evidence points to package graph or build plugins, hand off to [`spm-build-analysis`](../spm-build-analysis/SKILL.md) by reading its SKILL.md and applying its workflow to the same project context. ## Additional Resources - For the detailed audit checklist, see [references/project-audit-checks.md](references/project-audit-checks.md) - For build settings best practices, see [references/build-settings-best-practices.md](references/build-settings-best-practices.md) - For the shared recommendation structure, see [references/recommendation-format.md](references/recommendation-format.md) - For Apple-aligned source summaries, see [references/build-optimization-sources.md](references/build-optimization-sources.md)
Related in Security
mac-ops
IncludedComprehensive macOS workstation operations — diagnose kernel panics, identify failing drives, audit launchd startup items, decode wake reasons, triage TCC permission denials, manage APFS snapshots, recover from no-boot. Use for: Mac is slow, slow bootup, won't boot, kernel panic, kernel_task hot, mds_stores CPU, photoanalysisd, cloudd, login loop, gray screen, sleep wake failure, drive failing, IO errors, APFS snapshots eating space, Time Machine local snapshots, Spotlight indexing, launchd, LaunchAgent, LaunchDaemon, login items, TCC permissions, Full Disk Access, Screen Recording denied, Gatekeeper, quarantine, com.apple.quarantine, app is damaged, helper tool, /Library/PrivilegedHelperTools, pmset, wake reasons, dark wake, sysdiagnose, panic.ips, DiagnosticReports, configuration profile, MDM profile, remote diagnostics over SSH.
a11y-audit
IncludedRun accessibility audits on web projects combining automated scanning (axe-core, Lighthouse) with WCAG 2.1 AA compliance mapping, manual check guidance, and structured reporting. Output is configurable: markdown report only, markdown plus machine-readable JSON, or markdown plus issue tracker integration. Use this skill whenever the user mentions "accessibility audit", "a11y audit", "WCAG audit", "accessibility check", "compliance scan", or asks to check a web project for accessibility issues. Also trigger when the user wants to verify WCAG conformance or map findings to a specific standard (CAN-ASC-6.2, EN 301 549, ADA/AODA).
erpclaw
IncludedAI-native ERP system with self-extending OS. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting. 413 actions across 14 domains, 43 expansion modules. Constitutional guardrails, adversarial audit, schema migration. Double-entry GL, immutable audit trail, US GAAP.
assess
IncludedAssesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use when evaluating code, designs, architectures, or comparing alternative approaches.
spring-boot-security-jwt
IncludedProvides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based access control using Spring Security 6.x. Use when implementing authentication or authorization in Spring Boot applications.
code-hardcode-audit
IncludedDetect hardcoded values, magic numbers, and leaked secrets. TRIGGERS - hardcode audit, magic numbers, PLR2004, secret scanning.