Apple Design Web logo

Apple Design Web

Community
s1gmamale1
apple-design-web

Use when building an apple.com-style marketing/product page — the landing-page formula (sticky translucent nav, product-as-hero, full-bleed feature sections, bento grids, fat footer), scroll-driven storytelling, plus the interaction inventory that makes a flagship page feel ALIVE (continuous damped scroll-progress, theme morph, sticky-stack pinning, text wipe, ambient float), the hero media pipeline (video scrub, image sequence, asset sourcing), and Apple's front-end engineering (progressive enhancement, vanilla JS, perf discipline). Part of the apple-design family. Keywords: apple.com, marketing page, landing page, hero, scrollytelling, video scrub, interaction inventory, cross-section theme morph, sticky-stack, chaptered pinning, ambient float, canvas image sequence, createImageBitmap, WebGL 3D viewer, parallax, animation-timeline, scroll-driven animation, IntersectionObserver, progressive enhancement, srcset lazy load, frosted nav, media assets, device frame, CC0, asset sourcing.

Overview

Publishers1gmamale1
Repositoryapple-design-skills
Skill nameapple-design-web
Stars
30
Forks
3
Bundled files
4
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by s1gmamale1 on GitHub. Read the source before you install it.

Installation

Install the Apple Design Web AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/s1gmamale1/apple-design-skills/tree/main/skills/apple-design-web
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/s1gmamale1/apple-design-skills.git /tmp/apple-design-skills
mkdir -p .claude/skills
cp -r /tmp/apple-design-skills/skills/apple-design-web .claude/skills/apple-design-web
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Apple Design Web in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Apple Design Web on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Apple Design Web is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Apple Design — Web (apple.com language · scrollytelling · engineering)

Recreating apple.com: the page formula, the signature scroll effects, and how it's actually built.

When to use

  • Building a premium marketing/product landing page.
  • Implementing scroll-driven animation (frame-scrub, pinning, parallax, reveals).
  • Deciding the front-end architecture for an Apple-grade page.

Core rules

  • Light-first (do this before anything else). apple.com is predominantly light (#f5f5f7/white); a dark hero is the exception, used for ≤1 purposeful moment — never the default. Show the real product in a real device frame (a real screenshot), never an abstract placeholder. Restraint > gratuitous effects — see apple-design's references/restraint-and-antislop.md.
  • Commit to motion on flagship pages (motion IS the substance here). On a flagship/marketing/product surface, a page with only static one-shot fades is a dead template, not Apple-grade. Commit to the interaction inventory — continuous damped scroll-progress transforms (the #1 differentiator), sticky-pinned choreographed scenes, cross-section theme morph (light↔dark), and ambient float so it breathes when scrolling stops. This does NOT weaken light-first/real-product/restraint — both must hold: alive AND tasteful. The motion budget scales by surface (utility surfaces get far less); see the inventory at the top of references/scrollytelling-techniques.md and the surface axis in apple-design's references/restraint-and-antislop.md.
  • The formula: slim sticky translucent nav (~44–48px, blur, chapter-adaptive color) → big centered product hero (name + one tagline + "Learn more ›"/"Buy ›") → alternating full-bleed feature sections, one idea each → bento feature grid → tech specs → fat multi-column footer.
  • Scrollytelling decision tree (current apple.com is VIDEO-first): cinematic hero clip → video currentTime scrub (what apple.com ships — preload=none + lazy scroll-triggered src + static start/end-frame JPEG fallback + reduced-motion→static frame; mobile-Safari scrub flaky → ImageBitmap hybrid); interactive 3D product the user rotates → WebGL-3D scroll viewer (three.js + GLTF, KTX/Basis textures — Apple's own product-viewer pattern); many crisp frames / frame-exact at low count → canvas image-sequence (the classic pre-2022 alternative — preload, draw on rAF, sliding-window createImageBitmap decode + .close()); continuous element motion → damped scroll-progress (lerp a shadow-scroll value; engine in apple-design-motion); light↔dark chapters → cross-section theme morph (IO discrete-snap default, rAF-lerp or animation-timeline variants); chaptered card deck → sticky-stack (CSS position:sticky staggered top + ascending z-index, JS recede enhancement); simple reveal/parallax → CSS animation-timeline: view()/scroll() with @supports + IntersectionObserver fallback. The reusable damped-scroll + pointer-reactive engine lives in apple-design-motion; this skill composes it into page-level scenes. Media sourcing, encoding, frame-decode + delivery → references/media-assets-and-delivery.md.
  • Engineering: apple.com is progressive-enhanced HTML/CSS/vanilla JS (observed: Browserify ac-* bundles), not a heavy SPA. Responsive <picture>/srcset, loading="lazy", content-hashed immutable assets, deferred JS.
  • Never scroll-jack, never ship huge unoptimized frame sets, always guard motion with prefers-reduced-motion.

References

FileUse for
references/web-applecom-language.mdPage anatomy + measured specs; nav/hero/feature/footer HTML+CSS recipes
references/scrollytelling-techniques.mdThe apple.com/iphone interaction inventory (ranked alive behaviors, must-consider core vs flourishes) + working code: canvas scrubber, sticky scene, IO reveals, CSS scroll-driven animation, cross-section theme/background morph, sticky-stacked chaptered cards
references/web-frontend-engineering.mdObserved apple.com architecture, image/font/perf strategy, PE patterns
references/media-assets-and-delivery.mdHow current apple.com delivers hero media (video-first reverse-spec, WebGL-3D viewer, content-hash URLs) · updated technique decision tree · licensed code patterns (provenance + LICENSE) · asset-sourcing IP may/may-not + ship-only-our-own guardrail · encoding/caching/frame-decode (createImageBitmap, sliding window, video keyint=5)

Common mistakes

  • Cluttered hero / multiple competing CTAs; weak whitespace; busy backgrounds behind product.
  • Shipping a heavy framework for a static marketing page; render-blocking JS; unoptimized images.
  • Janky non-rAF scroll handlers; no reduced-motion fallback; content hidden behind animation.
  • Under-animating a flagship page — only static one-shot IO fades = a dead template. On a marketing/product surface, commit to continuous damped scroll-progress + theme morph + ambient float (the inventory). Equally: over-animating a utility surface — match the motion budget to the surface axis.

Related: the damped-scroll + pointer-reactive engine → apple-design-motion · type/color/grid → apple-design-foundations · the nav glass → apple-design-materials · CDN/image delivery → apple-design-backend · copy & persuasion → apple-design-tactics.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Apple Design Web AI skill do?

Use when building an apple.com-style marketing/product page — the landing-page formula (sticky translucent nav, product-as-hero, full-bleed feature sections, bento grids, fat footer), scroll-driven storytelling, plus the interaction inventory that makes a flagship page feel ALIVE (continuous damped scroll-progress, theme morph, sticky-stack pinning, text wipe, ambient float), the hero media pipeline (video scrub, image sequence, asset sourcing), and Apple's front-end engineering (progressive enhancement, vanilla JS, perf discipline). Part of the apple-design family. Keywords: apple.com, mar...

Why use Apple Design Web on TypingMind?

Because you install it once and use it with any model. Apple Design Web is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Apple Design Web in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/s1gmamale1/apple-design-skills/tree/main/skills/apple-design-web. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Apple Design Web?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Apple Design Web?

As many as you like. As long as a model supports skills, you can use Apple Design Web with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Apple Design Web AI skill free?

It is published on GitHub by s1gmamale1. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇