mcpField
A
apple-design-backend

apple-design-backend

github.com/s1gmamale1Cloud & DevOps3149 installsUpdated 22w ago
Repository

About apple-design-backend

An analysis skill for developers studying Apple's delivery patterns and backend design, including apple.com-style asset delivery and public Apple services. It distinguishes observed behavior and documented services from inference, which it warns against treating as fact.

Key features

  1. 01Examine CDNs, image transforms, and caching
  2. 02Describe HLS video delivery and HTTP protocols
  3. 03Survey public services such as CloudKit and APNs
  4. 04Explain privacy-first architecture principles
  5. 05Label observed, documented, and inferred claims

Use cases

  1. 01Plan responsive images and static asset caching
  2. 02Study multi-bitrate video delivery
  3. 03Review Apple public services for client integration
  4. 04Assess privacy, sync, and data-residency design

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/s1gmamale1/apple-design-skills --skill apple-design-backend

After installing, type/apple-design-backendin Claude Code to confirm it loaded.

Bundled filesreferences/inferred-backend-architecture.mdreferences/web-delivery-infra.md

Details

From the project README

Apple Design — Delivery & (Inferred) Backend

⚠️ Reverse-engineered, not official. Apple does not publish its server architecture. The delivery layer here is mostly [observed] (real headers, DNS, URL shapes); the backend architecture is largely [inferred]/[speculative]. Developer-facing services (CloudKit, APNs, StoreKit, Sign in with Apple, PCC) are [documented]. Treat inference as analysis, never ground truth — and never repeat it to a user as fact.

When to use

  • Designing apple.com-grade asset delivery (CDN, responsive images, adaptive video, caching).
  • Understanding the public Apple services a client app integrates with.
  • Reasoning about a privacy-first, sync-capable backend "the Apple way."

Core rules

  • Delivery (observed): multi-CDN edge; an image-transform service (mzstatic {W}x{H}{modifier}-{quality}.{fmt} URL params) → serve <picture>/srcset per device; content-hashed immutable assets with long Cache-Control; HLS multi-bitrate video; HTTP/2-3, Brotli.
  • Public services (documented): CloudKit (public/private/shared DBs, CKRecord, sync), APNs (HTTP/2 + JWT), Sign in with Apple (OIDC, rotating client secret, email relay), StoreKit 2 (JWS receipts, Server API + Notifications V2), Private Cloud Compute (stateless, verifiable, OHTTP-routed).
  • Privacy-by-architecture: on-device first, end-to-end encryption as a tier, server never trusts client claims, data residency (China/GDPR). Replicate the invariants, not the guesswork.

References

FileUse for
references/web-delivery-infra.md[observed] CDN/image-transform/HLS/caching/HTTP — with replication recipes
references/inferred-backend-architecture.md[documented] public services + [inferred] server topology (banner-led, every claim labeled)

Common mistakes

  • Presenting inference as fact (the #1 anti-pattern of this skill).
  • Giant unoptimized images, no edge cache, mutable cached URLs, single-bitrate video.
  • Server trusting client claims; no e2e/offline path; ignoring data residency.

Related: the page that consumes these assets → apple-design-web; how current apple.com delivers scroll-hero media specifically (video-first reverse-spec, content-hash asset URLs, KTX/WebGL textures, frame-sequence createImageBitmap decode + sliding window, video keyint=5 scrub encoding, asset-sourcing IP guardrails) → apple-design-web/references/media-assets-and-delivery.md.

Comments

Markdown supported