agentleFS
soilmasssoilmass/motion-design-agent/skills/onboarding/SKILL.md

onboarding

Skill7 starsChanged 10 months agoMITView on GitHub

Onboarding flow animation patterns. Use when creating first-time user experiences, feature tours, tutorial sequences, or progressive disclosure animations.

100 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use paywalls, popups and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 19 projects that use this

  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 18 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

    Also in 13 projects that use this

  • roerohanSkill

    prospecting

    When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

    Also in 16 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 18 projects that use this

  • +7 more from Cesarjoquin

The file

Files
SKILL.md

Onboarding Animation

Motion patterns for user onboarding, tutorials, and first-run experiences.

Onboarding Types

TypeMotion StyleDuration
CarouselSwipe/slide300-400ms per slide
Feature TourSpotlight + tooltip200-300ms per step
ProgressiveStaged reveal150-250ms per element
StoryFull-screen narrative500-1000ms transitions

Carousel Onboarding

Slide Transitions

// Framer Motion carousel
<AnimatePresence mode="wait">
  <motion.div
    key={currentSlide}
    initial={{ x: direction > 0 ? 300 : -300, opacity: 0 }}
    animate={{ x: 0, opacity: 1 }}
    exit={{ x: direction > 0 ? -300 : 300, opacity: 0 }}
    transition={{
      x: { type: 'spring', stiffness: 300, damping: 30 },
      opacity: { duration: 0.2 }
    }}
  >
    <SlideContent {...slides[currentSlide]} />
  </motion.div>
</AnimatePresence>

Illustration Entrance

// Staggered illustration elements
const illustrationVariants = {
  hidden: { opacity: 0, y: 20 },
  visible: (i) => ({
    opacity: 1,
    y: 0,
    transition: {
      delay: i * 0.1,
      duration: 0.4,
      ease: [0.05, 0.7, 0.1, 1]
    }
  })
};

// Elements enter sequentially
{illustrationParts.map((part, i) => (
  <motion.div
    custom={i}
    variants={illustrationVariants}
    initial="hidden"
    animate="visible"
  >
    {part}
  </motion.div>
))}

Progress Indicators

/* Dot indicator transition */
.dot {
  width: 8px;
  height: 8px;
  border-radius: 50%;
  background: rgba(0, 0, 0, 0.2);
  transition: all 200ms ease-out;
}

.dot.active {
  width: 24px;
  border-radius: 4px;
  background: #000;
}

Feature Tour (Spotlight)

Spotlight Animation

// Animated spotlight mask
function animateSpotlight(target) {
  const rect = target.getBoundingClientRect();

  gsap.to('.spotlight', {
    '--x': rect.left + rect.width / 2,
    '--y': rect.top + rect.height / 2,
    '--size': Math.max(rect.width, rect.height) + 20,
    duration: 0.4,
    ease: 'power2.inOut'
  });
}
.spotlight-overlay {
  background: radial-gradient(
    circle at var(--x, 50%) var(--y, 50%),
    transparent 0,
    transparent calc(var(--size, 0) * 0.5px),
    rgba(0, 0, 0, 0.8) calc(var(--size, 0) * 0.5px + 1px)
  );
  transition: all 400ms ease-in-out;
}

Tooltip Positioning

const tooltipVariants = {
  hidden: {
    opacity: 0,
    scale: 0.95,
    y: 10
  },
  visible: {
    opacity: 1,
    scale: 1,
    y: 0,
    transition: {
      duration: 0.2,
      ease: [0.05, 0.7, 0.1, 1]
    }
  },
  exit: {
    opacity: 0,
    scale: 0.95,
    transition: {
      duration: 0.15
    }
  }
};

Step Transitions

// Sequential step animation
async function goToStep(stepIndex) {
  // 1. Exit current tooltip
  await animateOut(currentTooltip);

  // 2. Move spotlight
  await animateSpotlight(steps[stepIndex].target);

  // 3. Enter new tooltip
  await animateIn(steps[stepIndex].tooltip);

  currentStep = stepIndex;
}

Progressive Disclosure

Staged Content Reveal

function OnboardingForm() {
  const [stage, setStage] = useState(0);

  return (
    <div>
      {/* Always visible */}
      <motion.div layout>
        <NameInput />
      </motion.div>

      {/* Stage 1: After name entered */}
      <AnimatePresence>
        {stage >= 1 && (
          <motion.div
            initial={{ opacity: 0, height: 0 }}
            animate={{ opacity: 1, height: 'auto' }}
            exit={{ opacity: 0, height: 0 }}
            transition={{ duration: 0.3 }}
          >
            <EmailInput />
          </motion.div>
        )}
      </AnimatePresence>

      {/* Stage 2: After email entered */}
      <AnimatePresence>
        {stage >= 2 && (
          <motion.div
            initial={{ opacity: 0, height: 0 }}
            animate={{ opacity: 1, height: 'auto' }}
            exit={{ opacity: 0, height: 0 }}
          >
            <PreferencesInput />
          </motion.div>
        )}
      </AnimatePresence>
    </div>
  );
}

Celebration on Completion

// Onboarding complete celebration
function celebrateCompletion() {
  // 1. Success icon animation
  gsap.fromTo('.success-icon', {
    scale: 0,
    rotation: -180
  }, {
    scale: 1,
    rotation: 0,
    duration: 0.5,
    ease: 'back.out(1.5)'
  });

  // 2. Confetti burst
  confetti({
    particleCount: 100,
    spread: 70,
    origin: { y: 0.6 }
  });

  // 3. Text reveal
  gsap.from('.completion-text', {
    y: 20,
    opacity: 0,
    duration: 0.4,
    delay: 0.3
  });
}

Story Onboarding

Full-Screen Transitions

// Narrative transitions between screens
const pageVariants = {
  initial: { opacity: 0, scale: 1.1 },
  enter: {
    opacity: 1,
    scale: 1,
    transition: {
      duration: 0.6,
      ease: [0.2, 0, 0, 1]
    }
  },
  exit: {
    opacity: 0,
    scale: 0.95,
    transition: {
      duration: 0.4,
      ease: [0.3, 0, 0.8, 0.15]
    }
  }
};

Lottie Illustrations

import Lottie from 'lottie-react';
import onboardingAnimation from './onboarding.json';

function OnboardingSlide() {
  const [animationData] = useState(onboardingAnimation);
  const lottieRef = useRef();

  // Play on slide entry
  useEffect(() => {
    lottieRef.current?.goToAndPlay(0);
  }, []);

  return (
    <Lottie
      lottieRef={lottieRef}
      animationData={animationData}
      loop={false}
      autoplay={false}
    />
  );
}

Skip/Dismiss Patterns

Skip Button

<motion.button
  whileHover={{ opacity: 0.8 }}
  whileTap={{ scale: 0.95 }}
  onClick={skipOnboarding}
>
  Skip
</motion.button>

Swipe to Dismiss

const swipeConfidenceThreshold = 10000;
const swipePower = (offset, velocity) =>
  Math.abs(offset) * velocity;

const onDragEnd = (e, { offset, velocity }) => {
  if (swipePower(offset.x, velocity.x) > swipeConfidenceThreshold) {
    // Skip onboarding
    skipOnboarding();
  }
};

Timing Guidelines

ElementDurationEasing
Slide transition300-400msemphasized
Element entrance150-250msemphasized-decelerate
Spotlight move400msease-in-out
Tooltip appear200msemphasized-decelerate
Progress dot200msease-out

Accessibility

Reduced Motion

@media (prefers-reduced-motion: reduce) {
  .onboarding-slide {
    transition: opacity 150ms ease;
  }

  /* Disable slide motion */
  .onboarding-slide[data-direction="next"],
  .onboarding-slide[data-direction="prev"] {
    transform: none;
  }
}

Skip Option

// Always provide skip
<button
  className="skip-button"
  onClick={skipOnboarding}
  aria-label="Skip introduction"
>
  Skip
</button>

Screen Reader

<div
  role="region"
  aria-label={`Onboarding step ${currentStep} of ${totalSteps}`}
  aria-live="polite"
>
  {slideContent}
</div>

Related Skills

  • Dependencies: easing, duration, sequencing, entrance-patterns
  • See also: attention-choreography, particles, celebrations
  • Patterns: Carousel, spotlight, progressive disclosure

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.