Swift Package Manager 의존성, 패키지 플러그인, 모듈 변형 및 CI 지향 빌드 오버헤드를 분석하여 Xcode 빌드를 느리게 하는 원인을 파악합니다.
이 스킬은 Swift Package Manager(SPM) 기반 프로젝트에서 빌드 성능 저하를 유발하는 의존성 그래프, 패키지 플러그인, 모듈 변형 및 CI 환경의 빌드 오버헤드를 심층 분석합니다. 개발자가 SPM 의존성 해결 시간, 플러그인 오버헤드, 설정 차이로 인한 중복 모듈 빌드, 모듈 간 순환 의존성, 분할이 필요한 과도하게 큰 모듈, 또는 모듈화 모범 사례에 대한 문제를 제기할 때 사용할 수 있습니다. 이 스킬은 Xcode 빌드 환경(로컬 및 CI)에서 작동하며, Package.swift, Package.resolved, Xcode 빌드 로그, DerivedData 경로를 분석하여 구체적인 개선점을 제시합니다. 주요 기능으로는 SPM 의존성 그래프 시각화, 플러그인 빌드 시간 측정, 모듈 변형(configuration variant) 비교, CI 빌드에서의 패키지 재해석 시간 분석, 그리고 순환 의존성 및 모듈 크기 진단이 포함됩니다. 결과적으로 개발자는 패키지 선택, 플러그인 사용, 모듈 구조 및 CI 설정을 최적화하여 빌드 시간을 단축할 수 있습니다.
npx skills add https://github.com/avdlee/xcode-build-optimization-agent-skill/tree/main/skills/spm-build-analysisInstalled? Explore more 연구 & 데이터 분석 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
Swift Package Manager 의존성, 패키지 플러그인, 모듈 변형 및 CI 지향 빌드 오버헤드를 분석하여 Xcode 빌드를 느리게 하는 원인을 파악합니다. 개발자가 패키지, 플러그인, 또는 의존성 그래프 형태가 클린 또는 증분 빌드 성능을 저하시킨다고 의심되거나, SPM 속도 저하, 패키지 해석 시간, 빌드 플러그인 오버헤드, 설정 차이로 인한 중복 모듈 빌드, 모듈 간 순환 의존성, 분할이 필요한 과도하게 큰 모듈, 또는 모듈화 모범 사례를 언급할 때 사용하세요.
This repo contains 5 individual skills — each has its own dedicated page.
Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped `.build-benchmark/` artifacts. Use when a developer wants a baseline, wants to compare before and after changes, asks to measure build performance, mentions build times, build duration, how long builds take, or wants to know if builds got faster or slower.
Apply approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement. Use when a developer has an approved optimization plan from xcode-build-orchestrator, wants to apply specific build fixes, needs help implementing build setting changes, script phase guards, source-level compilation fixes, or SPM restructuring that was recommended by an analysis skill.
Orchestrate Xcode build optimization by benchmarking first, running the specialist analysis skills, prioritizing findings, requesting explicit approval, delegating approved fixes to xcode-build-fixer, and re-benchmarking after changes. Use when a developer wants an end-to-end build optimization workflow, asks to speed up Xcode builds, wants a full build audit, or needs a recommend-first optimization pass covering compilation, project settings, and packages.
Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks, warn-long-function-bodies output, or wants to speed up Swift type checking.
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.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.