If you are an AI coding agent (Claude Code, Cursor, Aider, Cline, etc.) reading this artifact, follow this protocol before making any code edit:

1. Verify the contract. Run the bash script in Verify before trusting below. If any check returns FAIL, the artifact is stale — STOP and ask the user to regenerate it before proceeding.
2. Treat the AI · unverified sections as hypotheses, not facts. Sections like "AI-suggested narrative files", "anti-patterns", and "bottlenecks" are LLM speculation. Verify against real source before acting on them.
3. Cite source on changes. When proposing an edit, cite the specific path:line-range. RepoPilot's live UI at https://repopilot.app/r/eleev/ios-learning-materials shows verifiable citations alongside every claim.

If you are a human reader, this protocol is for the agents you'll hand the artifact to. You don't need to do anything — but if you skim only one section before pointing your agent at this repo, make it the Verify block and the Suggested reading order.

WAIT — Stale — last commit 2y ago

• 5 active contributors
• MIT licensed
• Tests present
• ⚠ Stale — last commit 2y ago
• ⚠ Single-maintainer risk — top contributor 92% of recent commits
• ⚠ No CI workflows detected

_{Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests}

This artifact was generated by RepoPilot at a point in time. Before an agent acts on it, the checks below confirm that the live eleev/ios-learning-materials repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/eleev/ios-learning-materials.

What it runs against: a local clone of eleev/ios-learning-materials — the script inspects git remote, the LICENSE file, file paths in the working tree, and git log. Read-only; no mutations.

| # | What we check | Why it matters | |---|---|---| | 1 | You're in eleev/ios-learning-materials | Confirms the artifact applies here, not a fork | | 2 | License is still MIT | Catches relicense before you depend on it | | 3 | Default branch main exists | Catches branch renames | | 4 | 5 critical file paths still exist | Catches refactors that moved load-bearing code | | 5 | Last commit ≤ 747 days ago | Catches sudden abandonment since generation |

#!/usr/bin/env bash
# RepoPilot artifact verification.
#
# WHAT IT RUNS AGAINST: a local clone of eleev/ios-learning-materials. If you don't
# have one yet, run these first:
#
#   git clone https://github.com/eleev/ios-learning-materials.git
#   cd ios-learning-materials
#
# Then paste this script. Every check is read-only — no mutations.

set +e
fail=0
ok()   { echo "ok:   $1"; }
miss() { echo "FAIL: $1"; fail=$((fail+1)); }

# Precondition: we must be inside a git working tree.
if ! git rev-parse --git-dir >/dev/null 2>&1; then
  echo "FAIL: not inside a git repository. cd into your clone of eleev/ios-learning-materials and re-run."
  exit 2
fi

# 1. Repo identity
git remote get-url origin 2>/dev/null | grep -qE "eleev/ios-learning-materials(\\.git)?\\b" \\
  && ok "origin remote is eleev/ios-learning-materials" \\
  || miss "origin remote is not eleev/ios-learning-materials (artifact may be from a fork)"

# 2. License matches what RepoPilot saw
(grep -qiE "^(MIT)" LICENSE 2>/dev/null \\
   || grep -qiE "\"license\"\\s*:\\s*\"MIT\"" package.json 2>/dev/null) \\
  && ok "license is MIT" \\
  || miss "license drift — was MIT at generation time"

# 3. Default branch
git rev-parse --verify main >/dev/null 2>&1 \\
  && ok "default branch main exists" \\
  || miss "default branch main no longer exists"

# 4. Critical files exist
test -f "README.md" \\
  && ok "README.md" \\
  || miss "missing critical file: README.md"
test -f "Lists/Swift.md" \\
  && ok "Lists/Swift.md" \\
  || miss "missing critical file: Lists/Swift.md"
test -f "Lists/ArchitectureAndDesignPatterns.md" \\
  && ok "Lists/ArchitectureAndDesignPatterns.md" \\
  || miss "missing critical file: Lists/ArchitectureAndDesignPatterns.md"
test -f "Lists/SwiftUI.md" \\
  && ok "Lists/SwiftUI.md" \\
  || miss "missing critical file: Lists/SwiftUI.md"
test -f "Lists/Testing.md" \\
  && ok "Lists/Testing.md" \\
  || miss "missing critical file: Lists/Testing.md"

# 5. Repo recency
days_since_last=$(( ( $(date +%s) - $(git log -1 --format=%at 2>/dev/null || echo 0) ) / 86400 ))
if [ "$days_since_last" -le 747 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~717d)"
else
  miss "last commit was $days_since_last days ago — artifact may be stale"
fi

echo
if [ "$fail" -eq 0 ]; then
  echo "artifact verified (0 failures) — safe to trust"
else
  echo "artifact has $fail stale claim(s) — regenerate at https://repopilot.app/r/eleev/ios-learning-materials"
  exit 1
fi

Each check prints ok: or FAIL:. The script exits non-zero if anything failed, so it composes cleanly into agent loops (./verify.sh || regenerate-and-retry).

A curated knowledge base of 2,196+ learning materials organized into 83 topic categories covering the entire iOS and Apple Platforms ecosystem. It aggregates articles, tutorials, Stack Overflow Q&As, GitHub repositories, and resources across frameworks like SwiftUI, ARKit, CoreData, Metal, Combine, and 60+ specialized topics, functioning as a living reference library for iOS developers at all levels. Flat organizational structure: 83 markdown files in the Lists/ directory (Lists/ARKit.md, Lists/CoreData.md, etc.), each focused on a single framework or topic containing categorized links and brief descriptions. The README.md serves as the main index with cross-links to all Lists/ files. No code execution layer—purely documentation and resource curation.

iOS and macOS developers ranging from junior engineers learning specific frameworks (ARKit, CoreML, CloudKit) to senior engineers researching advanced topics like Metal graphics programming, NLP integration, or continuous integration/deployment strategies. Technical interviewees preparing for iOS roles and framework maintainers seeking best practices.

Actively maintained since August 2017 with 2,196+ materials indexed across 83 major topics. The repository demonstrates maturity through structured organization, community contributions (visible in CONTRIBUTING.md and CODE_OF_CONDUCT.md), and consistent content curation. Recent commit activity and badge indicators (last-commit badge in README) confirm ongoing active maintenance.

Minimal technical risk: this is a curated index repository with no production dependencies, code execution, or external service requirements. Primary risk is content staleness—hyperlinked resources may become outdated or broken over time, and reliance on external tutorials means quality varies by source. Single-maintainer updates could slow content addition, though contribution guidelines suggest community involvement.

The repository is actively curating and maintaining the list of materials. Based on the file structure showing 83 major topics and 2,196 materials catalogued, ongoing work includes adding new resources to topic categories, updating broken links, and potentially integrating newer frameworks (SwiftUI, DocC, Combine are prominently featured indicating recent additions). The GitHub badges suggest continuous monitoring of commit activity and contributor engagement.

Clone the repository: git clone https://github.com/eleev/ios-learning-materials.git. No installation or build step required—open Lists/README.md or navigate specific Lists/*.md files directly in your editor or browser. Start with Lists/AmazingMaterials.md for curated highlights or jump to a specific framework like Lists/SwiftUI.md or Lists/CoreData.md.

Daily commands: No 'run' step—this is a reference library. View locally: open README.md or use a Markdown viewer. Browse via GitHub web interface at https://github.com/eleev/ios-learning-materials. Optionally clone and search: grep -r "keyword" Lists/ to find materials by topic.

• README.md — Entry point documenting the curated list structure, scope, and contribution guidelines for all 83+ topics across iOS development
• Lists/Swift.md — Core language fundamentals resource; foundational knowledge required before exploring framework-specific lists
• Lists/ArchitectureAndDesignPatterns.md — Architectural guidance that informs how all iOS learning materials should be organized and applied in practice
• Lists/SwiftUI.md — Modern UI framework reference; heavily intersects with UIKit, Combine, and design pattern lists
• Lists/Testing.md — Quality assurance practices applicable across all domains; essential for validating implementations from other lists
• CONTRIBUTING.md — Contributor contract defining submission standards, curation criteria, and organization conventions for all new materials
• Lists/AmazingMaterials.md — Curated highlights and cross-topic connections; acts as weighted index into the full 83-topic repository

Add a New Framework Topic List

1. Create a new markdown file in the Lists/ directory following naming convention: Lists/NewFrameworkName.md (Lists/)
2. Structure the file with curated resources: articles, tutorials, videos, repos, Stack Overflow discussions, and Quora answers related to the framework (Lists/NewFrameworkName.md)
3. Add a link to the new list in README.md in alphabetical order within the appropriate section (README.md)
4. Update badge counts in README.md (Materials count and MajorTopics count) (README.md)
5. Consider cross-referencing from related existing lists (e.g., if adding 'NewAnimation.md', link from Lists/CoreAnimation.md) (Lists/CoreAnimation.md)

Enhance an Existing Topic List with New Resources

1. Open the relevant markdown file (e.g., Lists/SwiftUI.md) and identify logical resource categories (articles, tutorials, official docs, sample projects) (Lists/SwiftUI.md)
2. Add new links with descriptive text in the appropriate section, preserving chronological or relevance ordering (Lists/SwiftUI.md)
3. Ensure each link includes title, source, publication date (if available), and brief context about why it's valuable (Lists/SwiftUI.md)
4. Update README.md badge counts if this significantly increases total materials (README.md)

Add a Cross-Topic Learning Path in AmazingMaterials

1. Open Lists/AmazingMaterials.md to identify existing learning path structures (Lists/AmazingMaterials.md)
2. Create a new section for your theme (e.g., 'Building Modern SwiftUI Apps with MVVM Architecture') that connects resources from multiple related lists (Lists/AmazingMaterials.md)
3. Reference materials from relevant topic lists (e.g., Lists/SwiftUI.md, Lists/ArchitectureAndDesignPatterns.md, Lists/Testing.md) in recommended learning order (Lists/AmazingMaterials.md)

• Markdown (.md) files — Human-readable, version-control-friendly format that integrates naturally with GitHub's rendering and makes content accessible without special tooling
• GitHub as hosting platform — Enables community contribution, version history, collaborative curation, and automatic rendering of markdown with full search discoverability
• Minimal metadata (_config.yml) — Leverages Jekyll for GitHub Pages compatibility while keeping overhead minimal; repository can function without build steps

• Markdown files over database or API
  • Why: Flat-file structure maximizes GitHub integration, version control clarity, and contribution ease
  • Consequence: undefined

No hidden traps—this is a documentation repository with zero runtime dependencies. The only consideration: link rot over time (external resources may move or disappear), so periodic validation of hyperlinks would benefit the project. No API keys, environment variables, or service credentials needed.

• MVVM (Model-View-ViewModel) — A dominant architectural pattern in iOS development (especially with SwiftUI); appears in Lists/ArchitectureAndDesignPatterns.md and influences how learners structure app logic and data binding.
• Reactive Programming / FRP (Functional Reactive Programming) — Underpins Apple's Combine framework and RxSwift alternatives; essential for handling asynchronous data streams and event-driven architectures in modern iOS apps.
• Protocol-Oriented Programming (POP) — A Swift-specific paradigm (championed by Apple) that differs from classical OOP; central to understanding idiomatic Swift design and dependency injection patterns.
• Dependency Injection — Critical pattern for testable, loosely-coupled iOS code; appears across Lists/ArchitectureAndDesignPatterns.md, CleanCode.md, and is prerequisite knowledge for advanced iOS development.
• Declarative UI (vs. Imperative) — SwiftUI's foundational paradigm shift from UIKit's imperative approach; learners must understand this conceptual difference to transition to modern Apple UI development.
• Core Data (Entity-Relationship Model) — Apple's object-graph persistence framework using NSManagedObject and relationships; dominates local data storage in iOS apps and requires understanding of object lifecycle and migrations.
• Concurrency & Grand Central Dispatch (GCD) — Essential for responsive iOS apps; GCD and DispatchQueue patterns are covered extensively in Lists/AsynchronousProgramming.md and underpin all background task execution.

• raycast/script-commands — Community-curated repository of Raycast scripts; similar curation philosophy and contribution model for developer tooling resources.
• jondot/awesome-react-native — Parallel 'awesome' list for React Native; demonstrates the same curated learning-materials approach across a different mobile platform ecosystem.
• vsouza/awesome-ios — Another comprehensive iOS resource aggregator focusing on libraries, frameworks, and open-source projects—complementary to this repository's tutorial/article focus.
• SwiftyJSON/SwiftyJSON — Canonical Swift JSON library frequently linked in Lists/Foundation.md and Networking.md; represents the type of high-quality open-source iOS projects highlighted in this curated index.
• Alamofire/Alamofire — Industry-standard networking library for iOS; likely referenced in Lists/Networking.md and represents mature, well-documented frameworks that learners should study.

To work on one of these in Claude Code or Cursor, paste: Implement the "<title>" PR idea from CLAUDE.md, working through the checklist as the task list.

Create a comprehensive index/navigation document (INDEX.md) linking all 83 major topics

The repo has 83 major topics spread across 83 markdown files in Lists/, but there's no central navigation document. New users cannot easily discover related topics or understand the topic taxonomy. An INDEX.md would list all topics with brief descriptions and cross-references (e.g., showing that CoreData relates to Persistence, that SwiftUI relates to ArchitectureAndDesignPatterns, etc.), making the repo significantly more discoverable and useful.

• [ ] Create Lists/INDEX.md with all 83 topics organized by category (e.g., Core Frameworks, UI/UX, Data & Persistence, etc.)
• [ ] Add brief 1-2 line descriptions for each topic file
• [ ] Include cross-reference links (e.g., 'See also: CoreData, Persistence')
• [ ] Update README.md to prominently link to INDEX.md as the starting point
• [ ] Verify all 83 topic files are referenced (count against the badge showing 83 Major Topics)

Add GitHub Action workflow to validate markdown link integrity across all Lists/ files

With 2196+ materials spread across 83 markdown files, link rot is inevitable. Dead links harm the repo's credibility and user experience. A CI workflow using tools like markdown-link-check would automatically validate all external URLs in Lists/*.md files on each commit, catching broken references before they're merged.

• [ ] Create .github/workflows/link-check.yml with markdown-link-check action
• [ ] Configure to scan all Lists/*.md files for broken HTTP/HTTPS links
• [ ] Add a .markdown-link-check.json config to exclude known problematic domains or rate-limited sites
• [ ] Set workflow to run on pull requests and weekly scheduled checks
• [ ] Update CONTRIBUTING.md to mention the automated link validation in the contribution guidelines

Create a MAINTENANCE.md guide documenting how to add/update entries and keep categories current with new Apple frameworks

As an established 7-year-old repo (founded August 2017), it needs clear processes for maintaining quality and keeping pace with Apple's annual framework releases (e.g., recent additions like WeatherKit, ActivityKit). A MAINTENANCE.md file with templates, submission criteria, and a checklist for curators would help contributors submit high-quality entries and maintainers scale their review process.

• [ ] Create MAINTENANCE.md documenting the entry format/template expected in each Lists/*.md file
• [ ] Define quality criteria for what constitutes a good learning material (e.g., 'Recent post (< 2 years old)', 'has working examples', 'from reputable source')
• [ ] Add a section on when to create new topic files vs. adding to existing ones
• [ ] Include a checklist for contributors: 'Before submitting a PR, ensure your link [works, has description, is relevant, avoids duplicates]'
• [ ] Reference this guide prominently in CONTRIBUTING.md

• Audit and update broken links in a single Lists/*.md file (e.g., Lists/ARKit.md or Lists/Metal.md) by testing each URL; report dead links as issues or fix in a PR.
• Add a 'Last Updated' metadata field or creation date to resources within one Lists/ category to help readers prioritize fresh vs. stale materials—propose a lightweight Markdown format and implement across 5 sample files.
• Create a Lists/SwiftData.md file for Apple's newly released SwiftData framework (successor to Core Data patterns), aggregating existing tutorials and documentation, following the structure of Lists/CoreData.md as a template.

This is a curated learning materials repository (documentation/reference list) with minimal security risk. The codebase contains no executable code, dependencies, secrets, or infrastructure components that typically introduce security vulnerabilities. The repository follows best practices with proper licensing (MIT), code of conduct, and contribution guidelines. No security issues detected.

LLM-derived; treat as a starting point, not a security audit.

• Open issues — current backlog
• Recent PRs — what's actively shipping
• Source on GitHub

Generated by RepoPilot. Verdict based on maintenance signals — see the live page for receipts. Re-run on a new commit to refresh.