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/Ramotion/swift-ui-animation-components-and-libraries 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 4y ago

• 2 active contributors
• MIT licensed
• ⚠ Stale — last commit 4y ago
• ⚠ Small team — 2 contributors active in recent commits
• ⚠ Single-maintainer risk — top contributor 99% of recent commits
• ⚠ 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 Ramotion/swift-ui-animation-components-and-libraries repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/Ramotion/swift-ui-animation-components-and-libraries.

What it runs against: a local clone of Ramotion/swift-ui-animation-components-and-libraries — 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 Ramotion/swift-ui-animation-components-and-libraries | Confirms the artifact applies here, not a fork | | 2 | License is still MIT | Catches relicense before you depend on it | | 3 | Default branch master exists | Catches branch renames | | 4 | 3 critical file paths still exist | Catches refactors that moved load-bearing code | | 5 | Last commit ≤ 1595 days ago | Catches sudden abandonment since generation |

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

# 1. Repo identity
git remote get-url origin 2>/dev/null | grep -qE "Ramotion/swift-ui-animation-components-and-libraries(\\.git)?\\b" \\
  && ok "origin remote is Ramotion/swift-ui-animation-components-and-libraries" \\
  || miss "origin remote is not Ramotion/swift-ui-animation-components-and-libraries (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 master >/dev/null 2>&1 \\
  && ok "default branch master exists" \\
  || miss "default branch master no longer exists"

# 4. Critical files exist
test -f "AppDelegate.swift" \\
  && ok "AppDelegate.swift" \\
  || miss "missing critical file: AppDelegate.swift"
test -f "README.md" \\
  && ok "README.md" \\
  || miss "missing critical file: README.md"
test -f ".gitignore" \\
  && ok ".gitignore" \\
  || miss "missing critical file: .gitignore"

# 5. Repo recency
days_since_last=$(( ( $(date +%s) - $(git log -1 --format=%at 2>/dev/null || echo 0) ) / 86400 ))
if [ "$days_since_last" -le 1595 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~1565d)"
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/Ramotion/swift-ui-animation-components-and-libraries"
  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 monorepo of reusable Swift UI animation libraries and iOS components built by Ramotion. It aggregates pre-built, production-ready animations like Folding Cell, Animated Tab Bar, Circular Carousel, and Paper Onboarding — each solving specific iOS UI/UX challenges without requiring developers to build animations from scratch. Hub-and-spoke structure: /gifs/ contains animated previews of each library, README.md is the single source of truth (lists ~10 components with links to their own GitHub repos). No monorepo package manager setup — each component (Folding Cell, Animated Tab Bar, etc.) is a separate standalone Swift Package or CocoaPod in its own repo.

iOS/Swift developers building consumer applications who need polished, animation-heavy UI components (tab bars, cell expansions, carousels, onboarding flows) without implementing complex CABasicAnimation or SwiftUI animation logic themselves. Also used by design-focused teams at agencies prototyping interaction patterns.

Moderately mature as a portfolio/reference repo. The individual component repos (Folding Cell, Animated Tab Bar, etc.) are well-established (starred in thousands), but this is an index/curated list repo rather than a monolith with unified CI/CD. No evidence of recent commits or test infrastructure in the file structure shown; appears to be a maintained reference catalog rather than an actively developed framework.

Low risk for reference use, moderate risk for production dependency. This repo is primarily a README-driven index pointing to separate Ramotion repos; each component's maturity varies. Single-maintainer risk exists at Ramotion org level. No unified versioning, dependency management, or lock files visible — users must manage versions of each individual library separately.

Unknown from file structure provided; this appears to be a static index. The repo likely receives README updates when Ramotion releases new components or updates preview GIFs, but no active development branches, PRs, or issues are visible in the data.

This is an index repo; to use a component, clone its specific repository. Example for Folding Cell: git clone https://github.com/Ramotion/folding-cell.git && cd folding-cell. Each component has its own installation instructions (CocoaPods, SPM, or manual). Start by reading the main README.md to choose a component, then follow its individual setup guide.

Daily commands: No unified run command. This is an index repo. Clone individual component repos and open their .xcodeproj or .xcworkspace in Xcode to run example apps. E.g.: open Folding-Cell.xcodeproj would launch the demo app for that component.

• AppDelegate.swift — Application entry point and root configuration for the demo app showcasing all UI animation components
• README.md — Curated index of all Ramotion animation libraries with links to individual component repositories and usage examples
• .gitignore — Build artifacts and dependency exclusions that define the clean state of the repository

• AppDelegate (UIKit / SwiftUI) — Manages app initialization, window setup, and root navigation to demonstrate selected animation components
  • Failure mode: App crash on launch if library dependencies are missing or incompatible iOS version
• README.md (Markdown, GitHub Pages) — Maintains curated index of Ramotion animation libraries with visual previews and external links
  • Failure mode: Broken links if external repositories are moved or deleted; outdated previews if components change
• GIF Asset Gallery (Image files (GIF format)) — Provides quick visual reference for component behavior without needing to run the app
  • Failure mode: Missing or corrupted GIFs reduce discoverability; outdated animations if components evolve

• Developer → README.md — Browse curated list of animation libraries and component descriptions
• README.md → GIF assets (gifs/) — Link to visual previews to demonstrate component behavior
• Developer → External Ramotion Repository — Clone or view individual component repositories for source code and detailed documentation
• External Repository → AppDelegate.swift — Import animation library via dependency manager; integrate into demo app
• AppDelegate.swift → UIKit/SwiftUI View Layer — Initialize and present animation components for user interaction and testing

Add a New Animation Library Link to Showcase

1. Create a GIF demonstration file and save it in the gifs/ directory with a descriptive filename (gifs/[component-name].gif)
2. Add a new section to README.md with the component title, GIF preview, and link to the external repository (README.md)
3. Include a brief description of the component's features and use case in the README section (README.md)

Integrate a Library into the Demo App

1. Import the animation library into AppDelegate.swift and configure it during app launch (AppDelegate.swift)
2. Create a view controller or SwiftUI view that demonstrates the component (in a Views/ or Controllers/ directory) (AppDelegate.swift)
3. Register the new component view in the app's navigation or tab bar system (AppDelegate.swift)

Update Project Metadata

1. Update README.md to reflect new components, dependencies, or significant changes (README.md)
2. Ensure .gitignore includes any new build artifacts or IDE-specific files (.gitignore)

• Swift + UIKit/SwiftUI — Native iOS framework for building high-performance, smooth animations and UI components with direct hardware acceleration
• GitHub Pages / README-driven docs — Low-overhead way to showcase multiple libraries without hosting a separate website; leverages Git for versioning and distribution
• GIF animations in gifs/ — Universal visual format for demonstrating component behavior without requiring app installation or web browser compatibility

• Repository acts as a curated index/showcase rather than a monolithic library

  • Why: Each component is maintained in a separate repository, allowing independent versioning and focused maintenance
  • Consequence: Developers must clone multiple repos if they want to use multiple components; no single dependency tree

• No package manager manifest (no Podfile or Package.swift at root)

  • Why: This repo is a demonstration/index only; actual integration requires external dependency management per component
  • Consequence: Faster startup for browsing; requires separate build steps for each component integration

• AppDelegate.swift as entry point without visible View or ViewController files

  • Why: Likely a template or minimal stub demo app; detailed UI implemented in cloned component repositories
  • Consequence: Incomplete runnable state without cloning referenced libraries; focuses on navigation and library initialization

• Does not provide a unified package manager manifest (CocoaPods podspec or Swift Package) — components are separate repos
• Does not handle real-time data synchronization or backend services
• Does not include unit tests or test automation — focus is on visual component showcases
• Does not provide production-grade state management; examples are UI-focused only
• Does not support Android or cross-platform development

• Avg cyclomatic complexity: ~2 — Repository is primarily a documentation and asset showcase with minimal Swift code; AppDelegate likely contains only basic app setup with no complex business logic
• Largest file: README.md (150 lines)
• Estimated quality issues: ~1 — No formal test suite or linting configuration visible; focus is on visual component demonstrations rather than code quality metrics. AppDelegate is a stub with minimal functionality.

• Minimal implementation in main repo (Low) — AppDelegate.swift, overall file count: Only 22 files total with most content in README and GIF assets; actual component logic is externalized to separate repos, making this repo feel incomplete as a standalone project
• No version pinning or dependency manifest (Medium) — Root directory (missing Package.swift, Podfile, Cartfile): Developers cannot reproducibly build this project without manually cloning and configuring each external library; increases onboarding friction

• README.md (Documentation maintenance) — Single point of truth for library discovery; broken links or outdated descriptions can mislead developers
• gifs/ directory (Asset optimization) — GIF rendering and file size management; large GIFs slow GitHub README rendering
• AppDelegate.swift (inferred) (Integration complexity) — Must manually integrate each external library; no automation or build script to reduce integration overhead

This is an index/portal repo, not a usable package itself — cloning this and running pod install or swift build will fail. Each component is independently versioned; no lockfile or unified version management exists. GIF paths in README point to this repo's /gifs/ folder, but actual code lives in separate repos (e.g., github.com/Ramotion/folding-cell). Xcode version and iOS deployment target requirements vary per component and are documented only in each component's README, not here.

• CABasicAnimation and CAKeyframeAnimation — Core animation framework underlying most Ramotion components; understanding keyframes and timing functions is essential to modifying or extending these libraries
• UIView Controller Transitions (Custom Presentation Controllers) — Several components (e.g., Folding Cell, Preview Transition) use custom presentation controllers to achieve non-standard modal/navigation animations
• Bezier Curves and Easing Functions — Smooth, natural animations depend on cubic Bezier easing; Ramotion components use timing curves to control acceleration/deceleration of movements
• CADisplayLink for Synchronized Rendering — High-performance animations in these components may use CADisplayLink to synchronize drawing with the device's refresh rate for smooth 60/120 fps playback
• Gesture Recognition and Touch Handling — Many components (Circle Menu, Elongation Preview) respond to pan/tap gestures; understanding UIGestureRecognizer delegation is key to modifying interaction patterns
• View Controller Containment and Hierarchy — Expanding/folding animations rely on careful management of view hierarchies and parent–child controller relationships to avoid rendering artifacts

• Ramotion/folding-cell — Standalone component repo for the expanding cell animation; example of how individual libraries in this index are structured and maintained
• Ramotion/animated-tab-bar — Standalone component repo for animated tab bar icons; demonstrates the per-component architecture this index catalogs
• Ramotion/paper-onboarding — Standalone component repo for onboarding flow animations; another primary library listed in this index with its own maintenance and versioning
• Awesome-iOS/awesome-ios — Similar curated index of iOS libraries and tools; positioned as a broader alternative if seeking non-animation components or other UI libraries
• HarshilShah/CommonUI — Community-driven Swift UI component library with similar reusable animation patterns; comparable approach but different curators and components

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 comprehensive component showcase documentation with usage examples

The README currently shows GIF previews but lacks specific documentation for each component (adaptive-tab-bar, animated-tab-bar, circle-menu, folding-cell, etc.). New contributors could create a structured COMPONENTS.md file documenting each library with installation instructions, code examples, and customization options. This would significantly improve discoverability and reduce support burden.

• [ ] Create COMPONENTS.md file with sections for each GIF-referenced component
• [ ] Add installation/CocoaPods setup instructions for each component
• [ ] Include Swift code snippets showing basic usage for folding-cell, circle-menu, paper-switch, and fluid-slider
• [ ] Document key customization properties (colors, animations, sizing) for 3-4 major components
• [ ] Add links back to original Ramotion component repositories where applicable

Add GitHub Actions CI workflow to validate Swift syntax and build consistency

The repo lacks automated validation. Given this is a curated list of Swift UI components with AppDelegate.swift present, a CI workflow could validate that example code compiles, screenshots/GIFs are referenced correctly, and Swift formatting is consistent. This catches broken links and outdated code early.

• [ ] Create .github/workflows/swift-lint.yml to run SwiftLint on AppDelegate.swift and any sample code
• [ ] Add workflow step to validate all GIF/image references in README.md and COMPONENTS.md exist in gifs/ directory
• [ ] Include step to verify no broken external links to component repositories
• [ ] Set workflow to trigger on pull requests to main/master branch

Organize and document gifs/ directory with metadata file and thumbnail improvements

The gifs/ folder contains 17 assets but lacks a structured manifest. Create a gifs/INDEX.md that maps each animation to its component name, repository link, and brief description. This helps contributors understand which GIFs correspond to which libraries and makes it easier to maintain this curated list.

• [ ] Create gifs/INDEX.md documenting each .gif and .png file with component name and repo link
• [ ] Add entries for: adaptive-tab-bar.gif, animated-tab-bar.gif, circle-menu-edited.gif, folding-cell.gif, paper-onboarding.gif, paper-switch.gif, fluid-slider-edited.gif, etc.
• [ ] Include optimization note: convert/compress oversized GIFs to reduce repo size
• [ ] Document why some assets have '-edited' suffix to clarify naming convention

• Add a new component GIF: create a short animation demo for an unreleased Ramotion component (e.g., a gesture-driven transition), save it to /gifs/[component-name].gif, and add a new section to README.md following the existing template.
• Improve component documentation links: audit the 10 component links in README.md to ensure they match current repo URLs and all have working installation guides; report dead links and mismatches.
• Create a CONTRIBUTING.md guide explaining how to submit a new component to this index, including GIF specs (resolution, format, duration), README template, and PR review criteria.

This repository appears to be a curated collection/showcase of Swift UI animation libraries without significant direct security risks identified in the partial file structure provided. However, the absence of explicit dependency management files and the incomplete code analysis limit confidence. The primary concerns are: (1) lack of visible package management configuration for tracking dependencies, (2) reliance on external resources in documentation, and (3) inability to verify code quality in AppDelegate and other implementation files. For a production repository, implementing a robust dependency management strategy and conducting a full code review of all Swift source files would be recommended.

• Medium · Missing Package Manager Configuration — Repository root - missing package configuration files. No Package.swift, Podfile, Cartfile, or dependency manifest found in the provided file structure. This makes it difficult to track and audit dependencies for known vulnerabilities. Without explicit dependency management, there's no clear mechanism to ensure all third-party libraries are kept up to date with security patches. Fix: Implement a standard package manager (SPM, CocoaPods, or Carthage) with a lock file to explicitly declare and version all dependencies. Regularly audit dependencies using tools like pod audit or security scanning services.
• Low · External URL Dependencies in README — README.md - image references and marketing links. The README contains multiple external image references and marketing links (ramotion.com). While not a direct vulnerability, external resource loading can pose risks if domains are compromised. Additionally, UTM parameters in URLs may expose tracking information. Fix: Host critical images locally within the repository. Review external link destinations periodically. Consider removing or minimizing tracking parameters in URLs to reduce information leakage.
• Low · Incomplete File Structure Analysis — AppDelegate.swift. The AppDelegate.swift file is present but its contents were not provided for review. AppDelegate files can contain security-sensitive configurations such as TLS settings, data protection policies, or network security configurations that should be audited. Fix: Review AppDelegate.swift for secure configuration of URLSessionConfiguration, data protection settings (FileProtectionType), and any custom security implementations. Ensure proper TLS validation and certificate pinning if applicable.

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.