Enter Effect

Opacity

0

Scale

1

Rotate

0

2D

3D

Skew

0°

X

0°

Y

Offset

0

X

12

Y

Transition

Ease

Enter & Exit

Abstract blue, green, and pink light patterns on a dark background
Abstract blue, green, and pink light patterns on a dark background
Abstract blue, green, and pink light patterns on a dark background
Abstract blue, green, and pink light patterns on a dark background
Abstract blue, green, and pink light patterns on a dark background
Framer’s Enter Effect settings over an image grid, showing opacity, scale, rotation, offset, and transition controls.

/

Design

Motion skill

Apply consistent appear and scroll effects across a page without overpowering the design. Group related content, keep timing calm, and respect reduced motion.

Copy skill

Copied

Copy skill

Copied

# Effects Apply smooth, restrained motion using native Framer effects. Preserve the design. Page-wide requests cover hero to footer; requests about “this,” “here,” or a named element stay within that target. ## Instructions 1. Inspect the full requested scope, existing effects, and all breakpoints. For page-wide work, address every eligible content section—not only the initial viewport. Preserve effects that meet these rules; replace conflicting effects rather than layering entrances. 2. Choose non-overlapping entrance groups: related heading, copy, and actions together; separate media and card collections independently. If one container includes all of them, animate either that container or its content groups, never both. Keep navigation, sticky controls, backgrounds, dividers, continuous long-form article text, and footer utility/legal links out of entrance groups. Footer promotional content is eligible. 3. Use tween `cubic-bezier(0.22, 1, 0.36, 1)` and opacity 0 to 1. Hero entrances last 0.8 seconds with no delay. Scroll reveals last 1 second with a 0.1-second delay measured from entering view, not page load. Rule 5 adds stagger offsets to these base delays. Copy, mixed-content groups, and card collections start 12px below rest; standalone media scales 0.98 to 1 without translation. Do not add blur, rotation, horizontal travel, bounce, or exit effects. 4. Start hero entrances on mount. Trigger other groups independently when 15% of the group is visible (threshold 0.15), with replay disabled. For groups taller than the viewport, use threshold 0 so the reveal remains reachable. Never schedule lower sections from page-load delays or reveal the entire page as one group. 5. Reveal each group together. Only for 2–4 sibling visuals or cards communicating steps or progression, animate the siblings instead of their parent, with 0.1 seconds between starts in reading order. Use the same entrance treatment for all siblings. Never stagger long lists, individual words, or related copy and actions. 6. Interaction feedback is separate from entrances: the restriction on nested entrances does not prohibit feedback on a button inside a revealing group. Preserve working hover and press feedback. On buttons and clickable cards without feedback, use scale 1.01 on hover, 0.99 on press, and a 0.25-second tween with the easing from rule 3 and no delay. If scale already drives the element’s entrance or another effect, use opacity 0.9 on hover and 0.8 on press instead. Leave inline links and noninteractive elements unscaled. 7. Check each group’s parent and visible siblings across breakpoints. Include each visible alternative only where it is shown; do not animate hidden copies. On phone, use 8px instead of 12px travel and remove only stagger offsets, retaining the 0.1-second scroll-reveal delay and the same groups, duration, and easing. Keep media scale unchanged. Preserve layout and prevent scaled feedback from clipping. 8. Reduced-motion preferences override all motion rules: keep content available without nonessential movement or sequencing, using supported native behavior. Do not introduce custom code. If available tools cannot configure or verify this, report the limitation rather than claiming compliance. 9. Verify the entire requested scope and every breakpoint for coverage, clipping, overlap, and readability. Preview load, scroll, and interrupted interactions when playback is available; screenshots verify layout, not timing. Report unverified behavior. Completion means all eligible groups were addressed, not that every element moves.

How to apply skills to your project
  1. Keep new pages consistent with your project’s typography, colors, spacing, and components.

    Skill copied

    # Design system

    Use this skill when you add pages or sections to a site that already has a look. You extend the system the team built. You don’t invent a new one.

    ## Before you start

    - Open the home page and two pages close to the new one.

    1. Copy the skill

    Use the Copy button above the skill to copy this skill’s instructions to your clipboard.

  2. /skills

    Turn these instructions into

    a reusable skill:

    GPT 6 Sol

    2. Add it in agent chat

    Type /skills in your agent chat and paste the skill, or add it in Settings / Skills.

  3. Use

    /design-system

    to build a new

    Careers page. Include a couple job openings and a form.

    GPT 6 Sol

    3. Use it in chat

    Type the skill’s command, such as /design-system, in your agent to use it.

  4. Title

    design-system

    Description

    Use components, styles, spacing, and layouts to create new

    Content

    Design system

    Use dark color scheme. Reuse existing styles and components; never invent new colors or text styles.


    Pages

    • Apply the Base layout template to every new page.

    • Set a meta title and meta description on every new page.

    • Sections fill the screen width (1fr) and contain an inner wrapper with maxWidth="1200px" that holds the content.


    Colors

    Container backgrounds: Color/Black.

    Text:

    • Primary headings: Color/White

    • Secondary/body text: Color/White 60

    Accent: Color/Red is the only accent. Use it very sparingly (one highlight per section at most).

    Borders and dividers: Color/Border Solid or Color/Border Transparent.

    Typography

    Always use these text styles, never inline type styles:

    • Set Text Balance to Yes for text layers.

    • Use sentence case; do not use all caps.

    • Do not use eyebrow text (small text above a heading).

    • In heroes, use Text/Body L for supporting text.

    • For every paragraph, adjust its text-box width to produce 50–75 characters per line, targeting 65. Round the width up to the nearest 5 or 10 pixels. If that width is wider than the parent container, set the text box to Fill. Verify at every breakpoint before finishing.

    • Text/H0: jumbo headings and hero treatments

    • Text/H1: blog post titles and secondary page titles

    • Text/H2, Text/H3, Text/H4, Text/H5, Text/H6: all other headings, in hierarchy order

    • Text/Body L: sub heads

    • Text/Body: main body text

    • Text/Body M: small supporting text

    • Text/Button: button labels only

    4. Edit your skill

    Open Settings / Skills whenever you want to make changes.

Your next idea starts here

GPT 6 Sol

Create personal portfolio

Build startup site

Launch landing page

Start company blog

Framer UI showing Pages, Layers and Assets panels titles
Framer UI showing Pages, Layers and Assets panels titles