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/X140Yu/Developing_iOS_8_Apps_With_Swift 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.

AVOID — Stale and unlicensed — last commit 6y ago

• 20 active contributors
• Distributed ownership (top contributor 49% of recent commits)
• ⚠ Stale — last commit 6y ago
• ⚠ No license — legally unclear to depend on
• ⚠ No CI workflows detected
• ⚠ No test directory 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 X140Yu/Developing_iOS_8_Apps_With_Swift repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/X140Yu/Developing_iOS_8_Apps_With_Swift.

What it runs against: a local clone of X140Yu/Developing_iOS_8_Apps_With_Swift — 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 X140Yu/Developing_iOS_8_Apps_With_Swift | Confirms the artifact applies here, not a fork | | 2 | Default branch master exists | Catches branch renames | | 3 | Last commit ≤ 2353 days ago | Catches sudden abandonment since generation |

#!/usr/bin/env bash
# RepoPilot artifact verification.
#
# WHAT IT RUNS AGAINST: a local clone of X140Yu/Developing_iOS_8_Apps_With_Swift. If you don't
# have one yet, run these first:
#
#   git clone https://github.com/X140Yu/Developing_iOS_8_Apps_With_Swift.git
#   cd Developing_iOS_8_Apps_With_Swift
#
# 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 X140Yu/Developing_iOS_8_Apps_With_Swift and re-run."
  exit 2
fi

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

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

# 5. Repo recency
days_since_last=$(( ( $(date +%s) - $(git log -1 --format=%at 2>/dev/null || echo 0) ) / 86400 ))
if [ "$days_since_last" -le 2353 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~2323d)"
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/X140Yu/Developing_iOS_8_Apps_With_Swift"
  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 community-maintained Simplified Chinese subtitle translation project for Stanford's CS193P 'Developing iOS 8 Apps with Swift' course lecture videos. The repository hosts 17 complete .srt subtitle files covering core iOS development concepts, complementing the iTunes U course taught by Paul Hegarty. Flat file structure: /subtitles/ directory contains 17 numbered .srt files corresponding to 17 lecture segments (Logistics through Internationalization). Single utility script /tools/trim.rb (Ruby) for subtitle time-code processing. No build system or package structure needed.

Mandarin-speaking iOS developers and computer science students learning Swift and iOS 8 development who need subtitles synchronized with Stanford's official lecture videos; also contributors who proofread and improve subtitle accuracy and terminology.

Mature and feature-complete: translation of all 17 lectures is finished (as stated in README), with an established proofread-rules.md quality standard and active community contribution guidelines via QQ group (277542197) and GitHub Issues. No CI/test infrastructure visible, but this is expected for a subtitle project; last activity implied by acceptance of PRs for typo fixes.

Low risk for a subtitle translation project: single maintainer (X140Yu) creates potential bus factor, but translation is complete and community-reviewed via pull requests. No dependencies or code to break. Risk is primarily in outdated iOS 8 content becoming less relevant as newer iOS versions release, though course remains canonical for learning MVC/Swift fundamentals.

Project is in maintenance mode post-completion: README states 'translation is fully complete' and invites pull requests for typo/quality fixes. Main ongoing work is proofreading per proofread-rules.md and fielding user issues (e.g., encoding problems in Issue #131). No active feature development.

Clone the repository: git clone https://github.com/X140Yu/Developing_iOS_8_Apps_With_Swift.git. No build or installation needed. To use subtitles, download the ZIP (archive/master.zip) and load .srt files into a video player like VLC alongside iTunes U course videos.

Daily commands: Not applicable—this is a subtitle translation repository, not executable code. To view/use: download all .srt files from /subtitles/ and load into VLC or another subtitle-capable video player alongside iTunes U course videos.

• [subtitles/1. Logistics, iOS 8 Overview.srt](https://github.com/X140Yu/Developing_iOS_8_Apps_With_Swift/blob/master/subtitles/1. Logistics, iOS 8 Overview.srt): Foundation lecture covering course structure and iOS 8 fundamentals; essential for onboarding learners
• [subtitles/3. Applying MVC.srt](https://github.com/X140Yu/Developing_iOS_8_Apps_With_Swift/blob/master/subtitles/3. Applying MVC.srt): Core MVC architecture lecture—the central architectural pattern taught throughout the course
• [subtitles/8. View Controller Lifecycle, Autolayout.srt](https://github.com/X140Yu/Developing_iOS_8_Apps_With_Swift/blob/master/subtitles/8. View Controller Lifecycle, Autolayout.srt): Covers iOS UIViewController lifecycle and AutoLayout—critical for iOS UI development
• proofread-rules.md: Quality/consistency standards for all subtitle contributions; defines acceptable terminology and style
• tools/trim.rb: Utility for adjusting subtitle timecodes programmatically if source videos need synchronization adjustments
• README.md: Documents project purpose, download links, usage instructions, and community contact (QQ group, Issues)

To contribute translations/fixes: (1) edit .srt files in /subtitles/ directly (SRT format: timecode HH:MM:SS,mmm --> HH:MM:SS,mmm then text); (2) follow proofread-rules.md for terminology and style consistency; (3) submit pull request. For time-code adjustments, consider using /tools/trim.rb (Ruby). For encoding issues, reference Issue #131 discussion.

Character encoding: users report Chinese character garbling (Issue #131); ensure UTF-8 encoding when editing .srt files in your editor. SRT format is whitespace-sensitive: blank lines between subtitle blocks are mandatory. iTunes U course videos may have regional availability; verify access before relying on links in README.

• MVC (Model-View-Controller) — Central architectural pattern taught in lectures 3, 7; foundational for iOS app structure and essential to understand before learning any iOS framework
• UIViewController Lifecycle — Covered in lecture 8; understanding viewDidLoad, viewWillAppear, viewDidAppear callbacks is mandatory for managing state and UI in iOS apps
• Delegation Pattern — Lecture 6 topic; the primary design pattern for callback/event handling in iOS (UITableViewDelegate, UITextFieldDelegate, etc.)
• AutoLayout Constraints — Lecture 8 covers this; constraint-based layout system replaces manual frame sizing and is essential for responsive iOS UI across devices
• Segues and Navigation — Lectures 7, 11, 15, 16 cover segues (unwind, modal, embed); the iOS mechanism for transitioning between view controllers and passing data
• Swift Optionals — Foundational Swift concept (lectures 2-4); nil-safety mechanism unique to Swift that prevents null pointer exceptions
• Core Data — Lecture 16 persistence topic; iOS framework for object graph persistence and data modeling on device

• X140Yu/Developing_iOS_9_Apps_With_Swift — Direct successor course (iOS 9 instead of iOS 8) from same Stanford CS193P series; users graduating from iOS 8 will want this
• sripathi/stanford-cs193p-uikit — Another Stanford CS193P resource collection; may contain supplementary code examples or notes for this course
• raywenderlich/swift-style-guide — Canonical Swift coding style reference; useful for maintainers reviewing code snippets in lecture subtitles
• Alamofire/Alamofire — Popular Swift networking library often taught as follow-up after Stanford fundamentals; learners completing this course often move here
• realm/realm-swift — Swift persistence library; course covers data persistence basics but Realm is industry-standard for advanced learners post-course

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 subtitle validation script to enforce proofread-rules.md

The repo has a proofread-rules.md file defining translation standards, but no automated enforcement mechanism. A validation script would catch rule violations (e.g., terminology inconsistencies, formatting issues) before merging PRs, reducing manual review burden and ensuring quality across all 17 subtitle files.

• [ ] Parse proofread-rules.md to extract all validation rules
• [ ] Create a Ruby/Python script in tools/ directory (alongside existing trim.rb) that scans all .srt files in subtitles/
• [ ] Implement checks for: consistent terminology, proper punctuation, timestamp formatting, and translation quality rules
• [ ] Add usage documentation in README.md with example: ruby tools/validate.rb
• [ ] Test against existing subtitle files to ensure no false positives

Build an .srt to Markdown documentation exporter for searchability

The subtitle content (lesson transcripts) is locked in binary .srt format, making it impossible to search, index, or reference specific concepts. Converting key lessons to Markdown would improve discoverability and allow contributors to quickly find which lesson discusses a topic (e.g., 'Autolayout' appears in lesson 8).

• [ ] Create tools/srt_to_markdown.rb to parse subtitle files and extract content
• [ ] Generate docs/ folder with one .md file per lesson (e.g., docs/08-view-controller-lifecycle-autolayout.md)
• [ ] Include in each .md file: lesson title, timestamps mapped to sections, and full transcript text
• [ ] Add a searchable index (docs/INDEX.md) listing all lessons with key topics
• [ ] Update README.md with link to docs/ and search instructions

Add automated SRT encoding and format validation via GitHub Actions

The README warns about Chinese encoding issues (Issue #131) but there's no CI to prevent encoding corruption on commits. A GitHub Actions workflow would verify all .srt files use UTF-8 encoding, pass SRT format validation, and match the style rules before PRs are merged.

• [ ] Create .github/workflows/subtitle-validation.yml GitHub Actions workflow
• [ ] Add step to verify UTF-8 encoding on all .srt files (catch encoding regression early)
• [ ] Integrate the validation script from PR idea #1 into the workflow
• [ ] Add step to validate .srt format compliance (proper timestamp/line breaks using a tool like ffsubsync or custom regex)
• [ ] Configure workflow to run on push to subtitles/ and on pull_request events, with clear failure messages for contributors

• Audit and fix Chinese terminology consistency across all 17 lectures for iOS-specific terms (e.g., ensure 'view controller' translation is uniform in all files); use proofread-rules.md as reference
• Add English-Chinese term glossary as /docs/glossary.md mapping key iOS/Swift concepts from lectures to both languages, helping maintainers and contributors stay consistent
• Create a /CONTRIBUTING.md with step-by-step guide for non-technical users to report subtitle errors via Issues (template for 'lecture #, timestamp HH:MM:SS, problem description')

This is a Stanford CS193P iOS development course subtitle translation project. It is a documentation/educational repository with no application code, dependencies, or infrastructure components. The repository contains only subtitle files (.srt), markdown documentation, and a simple Ruby script for trimming. No security vulnerabilities were identified. The project maintains good security hygiene by not including sensitive credentials, dependencies, or executable code that could introduce security risks.

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.