# Brief Library: free sample briefs
Source: https://brief-library.pages.dev/ (Ease Out Studio). Full packs: https://whop.com/ease-out-studio

## Free AI Prompt Cheat Sheet (Free)
Page: https://brief-library.pages.dev/free-ai-prompt-cheat-sheet/  Buy: https://whop.com/ease-out-studio/free-ai-prompt-cheat-sheet
A free one-page formula and 12 before and after briefs that turn generic AI answers into specific ones.
Structure: ROLE / CONTEXT / TASK / CONSTRAINTS / OUTPUT

### Client email
Use when: Instead of: "Write an email to my client about the delay."
ROLE: You are a senior account manager who writes calm, direct client emails.
CONTEXT: I run [BUSINESS_TYPE]. My client [CLIENT_NAME] expected [DELIVERABLE] on [ORIGINAL_DATE]. It will now arrive on [NEW_DATE] because [REASON]. Our relationship so far: [RELATIONSHIP_NOTES].
TASK: Write an email that explains the delay, takes responsibility and confirms the new date.
CONSTRAINTS: 120 to 160 words. One apology only. Do not blame third parties. Do not promise anything beyond [NEW_DATE]. Plain US English, no corporate filler.
OUTPUT: 2 subject line options, then the email body ready to send.
Tip: The brief supplies the dates, the reason and the word limit, so the AI has nothing to pad or invent.

### Landing page hero copy
Use when: Instead of: "Write a headline for my landing page."
ROLE: You are a conversion copywriter who works with small businesses.
CONTEXT: Product: [PRODUCT_NAME], [ONE_LINE_DESCRIPTION]. Audience: [AUDIENCE]. Their main problem: [PROBLEM]. Real proof I can show: [REAL_PROOF_OR_NONE].
TASK: Write the hero section copy for the top of the page.
CONSTRAINTS: Headline max 10 words. Subhead max 25 words. Button label max 4 words. No invented numbers, reviews, scarcity or urgency. Use only the proof listed above.
OUTPUT: 3 options as a numbered list. Each option has a headline, a subhead and a button label.
Tip: Hard word limits and a ban on invented proof keep the copy short and honest.

### Product description
Use when: Instead of: "Write a product description for my candle."
ROLE: You are an ecommerce copywriter who writes clear, sensory product pages.
CONTEXT: Product: [PRODUCT_NAME] from [BRAND_NAME]. Materials: [MATERIALS]. Size: [SIZE]. Typical buyer: [BUYER]. Facts you may use: [FACT_LIST].
TASK: Write the product page description.
CONSTRAINTS: 90 to 120 words. Use only the facts listed. No health claims and no claims about results. Sentences under 20 words.
OUTPUT: A title under 60 characters, one description paragraph, then 3 bullet points of 8 words or fewer.
Tip: Limiting the AI to a fact list stops it from making up features.

### 30-second video script
Use when: Instead of: "Write a video script for my product."
ROLE: You are a short-form video scriptwriter.
CONTEXT: Product: [PRODUCT_NAME] for [AUDIENCE]. Platform: [PLATFORM], vertical 9:16. Key message: [KEY_MESSAGE]. Footage I can actually shoot: [AVAILABLE_FOOTAGE].
TASK: Script one 30-second video.
CONSTRAINTS: 70 to 85 spoken words. A hook in the first 3 seconds. 5 to 6 shots. One call to action: [CTA]. No claims I cannot back up.
OUTPUT: A table with 3 columns: Time, Visual, Voiceover.
Tip: Word count, shot count and available footage make the script something you can film, not just read.

### Logo concept
Use when: Instead of: "Give me a logo idea for my bakery."
ROLE: You are a brand identity designer.
CONTEXT: Business: [BUSINESS_NAME], which [WHAT_IT_DOES]. Customers: [CUSTOMER]. Feel in 3 words: [THREE_WORDS]. Where the logo will appear: [PLACES]. Clichés to avoid: [CLICHES_TO_AVOID].
TASK: Propose 4 distinct logo concepts I can hand to a designer or describe to an image tool.
CONSTRAINTS: Max 2 colors plus white. Must stay readable at 32 px and in one color. No gradients. Wordmarks of 2 words or fewer.
OUTPUT: For each concept: a name, a 2-sentence description, hex codes, a typeface style and one risk.
Tip: Size, color and cliché limits force four different directions instead of four versions of the same idea.

### Bug fix request
Use when: Instead of: "My code doesn't work, fix it."
ROLE: You are a senior [LANGUAGE] developer doing a code review.
CONTEXT: Running [LANGUAGE] [VERSION] on [ENVIRONMENT]. Expected behavior: [EXPECTED]. Actual behavior and exact error: [ACTUAL_AND_ERROR]. What I already tried: [ATTEMPTS]. Code: [PASTE_CODE]
TASK: Find the root cause and fix it.
CONSTRAINTS: Change as few lines as possible. Do not rename functions or add libraries. If you need more information, ask up to 3 questions before answering. Say what you are unsure about.
OUTPUT: 1) The cause in 2 sentences max. 2) Only the changed code. 3) One test I can run to confirm the fix.
Tip: Expected versus actual behavior plus a minimal-change rule gets a targeted fix instead of a rewrite.

### LinkedIn post
Use when: Instead of: "Write a LinkedIn post about my new project."
ROLE: You are a ghostwriter for a [JOB_TITLE] who writes plainly and avoids buzzwords.
CONTEXT: Project: [PROJECT_NAME]. What really happened: [REAL_EVENTS]. The lesson: [LESSON]. Audience: [AUDIENCE]. A sample of my own writing: [PASTE_100_WORDS].
TASK: Write one post in my voice.
CONSTRAINTS: 150 to 200 words. First line under 12 words. Max 3 hashtags. No invented numbers, clients or quotes. No phrases like "excited to announce".
OUTPUT: 2 versions labeled A and B, post text only.
Tip: A real voice sample and real events are what separate your post from the generic one.

### Meeting notes summary
Use when: Instead of: "Summarize these meeting notes."
ROLE: You are a chief of staff who writes tight meeting recaps.
CONTEXT: Meeting: [MEETING_NAME] on [DATE]. Attendees: [NAMES]. Readers: [READERS], who did not attend. Notes: [PASTE_NOTES]
TASK: Summarize the decisions, action items and open questions.
CONSTRAINTS: Max 200 words total. Every action item needs an owner and a due date. If either is missing, write "unassigned" or "no date" and do not guess. Use only what is in the notes.
OUTPUT: Three headed sections: Decisions, Action items (a table with Owner, Task, Due) and Open questions.
Tip: Telling the AI what to write when information is missing prevents invented owners and deadlines.

## Free Website Animation Cheat Sheet (Free)
Page: https://brief-library.pages.dev/free-motion-brief-cheat-sheet/  Buy: https://whop.com/ease-out-studio/free-motion-brief-cheat-sheet
The formula, the eases and 5 real briefs from the Directed Motion Pack.
Structure: WHAT MOVES / FROM WHERE / HOW LONG / WHICH EASE / IN WHAT ORDER

### Entering
expo.out or power3.out

### Leaving
power2.in

### Moving between two spots on screen
power3.inOut

### Loops, spinners, marquees, scroll scrub
none (linear)

### Breathing and floating
sine.inOut

### One playful accent per screen
back.out(1.5 to 3)

### Springy return
elastic.out(1, 0.4), use rarely

### Feels slow
Cut every duration by 30% and every stagger in half. Keep the eases.

### Feels robotic
Replace every linear ease on entrances with expo.out. Keep linear only on loops.

### Too bouncy
Keep overshoot only on [element]. Everything else power3.out.

### Everything moves at once
Stagger the elements 60 to 80ms apart in reading order. The button lands last.

### Busy
Remove every loop except one. Make the one that stays at least 4s per cycle.

### Janky on phones
Animate only transform and opacity. No width, top, left or shadows inside loops.

### Forgot accessibility
Respect prefers-reduced-motion: show the end state and keep loops off.

## AI Product Photography Prompts ($12)
Page: https://brief-library.pages.dev/ai-product-photography-prompts/  Buy: https://whop.com/ease-out-studio/ai-product-photography-prompts
60 copy-paste image briefs for product photos, lifestyle scenes and sale banners, plus 6 fix-it follow-ups.
Structure: SUBJECT / SURFACE / LIGHT / CAMERA / COMPOSITION / STYLE / AVOID / ASPECT RATIO

### White seamless
Use when: You need a marketplace main image on pure white.
SUBJECT: [PRODUCT], [REAL_COLOR], [MATERIAL], true to the reference photo
SURFACE: white seamless backdrop curving into the floor, no visible horizon
LIGHT: large softbox from front left, white fill card on right, soft contact shadow under product
CAMERA: 85mm lens, f/8, eye level, whole product sharp
COMPOSITION: product centered, filling 70 percent of frame height, even margin on all sides
STYLE: clean catalog photo, neutral color, true-to-life
AVOID: extra props, text, invented features, altered logo, color cast on the white
ASPECT RATIO: 1:1
Tip: Add 'background pure white, RGB 255' if the backdrop looks gray.

### Kitchen counter
Use when: Your product belongs in a home kitchen.
SUBJECT: [PRODUCT], [REAL_COLOR], true to the reference photo, at real size
SURFACE: light [COUNTER_MATERIAL] kitchen counter with a blurred [BACKSPLASH_COLOR] backsplash
LIGHT: soft morning window light from the left, warm 4500K tone
CAMERA: 50mm lens, f/2.8, eye level, product sharp, background soft
COMPOSITION: product on the right third, 2 or 3 small props such as [PROP_LIST] blurred behind, space on the left
STYLE: natural, lived-in, editorial
AVOID: clutter, brand logos on props, text, invented product features
ASPECT RATIO: 4:5
Tip: Cut props to one if the product gets lost.

### Morning routine
Use when: You sell items used at the start of the day.
SUBJECT: [PRODUCT], [REAL_COLOR], true to the reference photo, plus a mug, a folded linen napkin and a small plant sprig
SURFACE: [SURFACE_MATERIAL] tabletop
LIGHT: soft morning window light from the top left, long gentle shadows
CAMERA: 35mm lens, f/6.3, directly overhead
COMPOSITION: product slightly off-center, props in a loose triangle, 15 percent empty margin
STYLE: calm, warm, editorial
AVOID: crowded layout, readable labels on props, invented features
ASPECT RATIO: 4:5
Tip: Remove one prop at a time until the product reads instantly.

### Bottle with condensation
Use when: You sell cold drinks.
SUBJECT: [BOTTLE_TYPE] of [DRINK_NAME], [LIQUID_COLOR], with the real label from the reference photo, covered in fine water droplets
SURFACE: wet dark slate with a few ice cubes around the base
LIGHT: strong backlight from upper right to light the droplets and liquid, soft fill from left
CAMERA: 100mm lens, f/4, eye level, droplets sharp
COMPOSITION: bottle centered, tall space above, ice at the bottom
STYLE: crisp, cold, high contrast
AVOID: changed label, wrong liquid color, fake brand names, invented features
ASPECT RATIO: 4:5
Tip: Add 'fewer droplets' if the label gets covered.

### Serum with water ripples
Use when: You sell skincare in a dropper or pump bottle.
SUBJECT: [BOTTLE_TYPE] of [SERUM_NAME], [GLASS_COLOR], real label from the reference photo
SURFACE: shallow clear water with soft concentric ripples, [BACKDROP_COLOR] backdrop
LIGHT: soft top light with backlight to catch the ripples, gentle highlight on the glass
CAMERA: 100mm lens, f/5.6, slightly above eye level
COMPOSITION: bottle centered with its base in the water, ripples extending evenly, open space above
STYLE: fresh, clinical-clean, translucent
AVOID: changed label, distorted bottle, claims, extra products, invented features
ASPECT RATIO: 4:5
Tip: Request 'small ripples' if the water overwhelms the bottle.

### Headphones on desk
Use when: You sell headphones or audio gear.
SUBJECT: [HEADPHONE_TYPE] headphones in [REAL_COLOR], true to the reference photo
SURFACE: [WOOD_TYPE] desk with a notebook and a small plant
LIGHT: soft window light from the left, subtle rim highlight
CAMERA: 50mm lens, f/3.5, 25 degrees above
COMPOSITION: headphones centered, band curved naturally, blurred monitor behind with the screen off
STYLE: clean, modern, calm
AVOID: extra buttons, changed shape, readable brand marks, invented features
ASPECT RATIO: 3:2
Tip: Name the exact ear cup shape in your brief.

### Black Friday banner with empty space for text
Use when: You need a dark, bold hero for a sale page.
SUBJECT: [PRODUCT], [REAL_COLOR], true to the reference photo, placed on the right third
SURFACE: dark [SURFACE_COLOR] surface with a soft reflection
LIGHT: dramatic side light from the left, rim highlight on the product, deep shadows
CAMERA: 85mm lens, f/5.6, slightly low angle
COMPOSITION: product in the right third, the left 55 percent a clean empty dark area for headline text
STYLE: bold, dark, premium
AVOID: any text, letters, numbers, price tags, fake urgency graphics, invented features
ASPECT RATIO: 16:9
Tip: Keep the empty area free of gradients so text stays readable.

## AI Video Prompts for Product Ads ($15)
Page: https://brief-library.pages.dev/ai-video-prompts-product-ads/  Buy: https://whop.com/ease-out-studio/ai-video-prompts-product-ads
60 copy-paste shot briefs plus 6 storyboards and 6 fixes for AI product videos in 9:16, built for Kling, Veo, Sora and more.
Structure: SHOT / SUBJECT / CAMERA / MOTION / LIGHT / STYLE / DURATION / AVOID

### Slow orbit on a pedestal
Use when: You need a premium main clip for a product page or ad opener.
SHOT: Slow 180 degree orbit around the product on a pedestal.
SUBJECT: [PRODUCT] on a round [PEDESTAL_COLOR] pedestal, plain [BACKGROUND_COLOR] backdrop, product matches the reference photo exactly.
CAMERA: 50mm lens, eye level, smooth orbit left to right, product stays centered.
MOTION: Camera moves only. Product stays still. Speed is constant.
LIGHT: Soft key light from the upper left, gentle rim light, 5500K.
STYLE: Clean studio commercial, [BRAND_COLORS] palette, matte surfaces.
DURATION: 9:16, 8 seconds.
AVOID: Warped shape, changed logo, extra objects, text overlays, flicker.
Tip: Cut the orbit to 90 degrees by writing '90 degree orbit' if the product's back side looks wrong.

### Liquid pour
Use when: You sell a drink, oil, sauce or liquid product and want a pour close-up.
SHOT: Macro of [LIQUID] pouring into a [CONTAINER] in slow motion.
SUBJECT: [LIQUID] in [LIQUID_COLOR], clear [CONTAINER], [PRODUCT] bottle visible but soft in the background.
CAMERA: 100mm macro lens, low angle, locked.
MOTION: Slow motion pour at 25 percent speed, liquid fills 1/3 of the container.
LIGHT: Backlight from behind with a soft front fill, 5000K.
STYLE: Glossy, rich color, shallow depth of field.
DURATION: 9:16, 5 seconds.
AVOID: Spills, bubbles that look like glitches, logo text appearing, hands.
Tip: Name the thickness, such as 'thick like honey' or 'thin like water', to match the motion.

### Unboxing hands
Use when: You want a first-reveal clip for a product with nice packaging.
SHOT: Two hands lift the lid off a box and reveal the product.
SUBJECT: A [BOX_COLOR] box with [PRODUCT] inside on a [SURFACE_COLOR] table, hands with [SKIN_TONE_AND_SLEEVE] visible from the wrists.
CAMERA: 35mm lens, top-down at 70 degrees, locked.
MOTION: Hands lift the lid slowly over 2 seconds, set it aside, and stop. Product stays inside.
LIGHT: Soft window light from the left, 5000K.
STYLE: Natural, tidy, warm neutral palette.
DURATION: 9:16, 8 seconds.
AVOID: Extra fingers, hands touching the product, changed packaging, text.
Tip: Say 'only the lid moves' if the hands start grabbing the product.

### Burger build
Use when: You need a stacked-build clip for a burger or sandwich.
SHOT: A burger assembles layer by layer on a plate.
SUBJECT: A burger with bottom bun, patty, [CHEESE_TYPE], [TOPPINGS] and top bun, on a [PLATE_COLOR] plate.
CAMERA: 50mm lens, eye level, locked.
MOTION: Each layer drops in with a small settle, 5 layers over 5 seconds, ending with the top bun.
LIGHT: Warm side light, 3500K, soft shadows.
STYLE: Juicy, bright, saturated, dark [BACKGROUND_COLOR] backdrop.
DURATION: 9:16, 8 seconds.
AVOID: Floating pieces, odd sauce drips, extra layers, text.
Tip: State the exact layer count so the stack does not grow.

### Serum drop
Use when: You want a clean drop shot from a dropper bottle.
SHOT: One drop forms on a dropper tip and falls.
SUBJECT: A glass dropper bottle of [SERUM_COLOR] serum, exact match to the reference photo, [SURFACE_COLOR] background.
CAMERA: 100mm macro lens, eye level, locked.
MOTION: A drop forms over 2 seconds and falls at 3 seconds in slow motion.
LIGHT: Soft backlight, 5500K, bright highlight on the drop.
STYLE: Clean, minimal, glassy, [BRAND_COLORS] palette.
DURATION: 9:16, 5 seconds.
AVOID: Changed label, bubbles, skin shown, claims text.
Tip: Name the serum thickness, such as 'light and watery', for the drop shape.

### Earbuds case open
Use when: You sell earbuds, a small case or any hinged accessory.
SHOT: The case lid opens and the earbuds show inside.
SUBJECT: A [CASE_COLOR] earbud case with earbuds inside, exact match to the reference photo, [SURFACE_COLOR] surface.
CAMERA: 85mm lens, 30 degree angle, slow push-in 10 percent.
MOTION: Lid opens 90 degrees over 2 seconds, a small status light turns on at 3 seconds.
LIGHT: Soft top light with a [ACCENT_COLOR] edge light, 5600K.
STYLE: Clean, precise, tech look.
DURATION: 9:16, 5 seconds.
AVOID: Extra earbuds, changed hinge, floating parts, text.
Tip: Say 'hinge at the back, opens upward' to avoid wrong opening.

### Sneaker turn
Use when: You sell shoes and want a clean 360 look.
SHOT: A sneaker turns slowly on a low platform.
SUBJECT: A [SNEAKER_COLOR] sneaker, exact match to the reference photo, [BACKGROUND_COLOR] backdrop.
CAMERA: 50mm lens, low angle, locked.
MOTION: Sneaker rotates 360 degrees clockwise over 8 seconds.
LIGHT: Two soft side lights, 5500K, a small soft shadow below.
STYLE: Clean, bold color blocking, sharp edges.
DURATION: 9:16, 8 seconds.
AVOID: Changed laces, merged soles, extra shoes, text.
Tip: Say 'both laces stay tied and in place' to avoid morphing.

### Match cut between colors
Use when: You sell a product in several colors and want a quick color change.
SHOT: The product holds still while the scene color changes from [COLOR_1] to [COLOR_2].
SUBJECT: [PRODUCT] in [COLOR_1] changing to [COLOR_2], same position, same angle, exact match to the reference photos.
CAMERA: 50mm lens, eye level, locked.
MOTION: A color wipe moves left to right over 1 second at the 2 second mark. Product shape does not change.
LIGHT: Soft studio light, 5500K, constant.
STYLE: Clean, graphic, flat backdrop.
DURATION: 9:16, 5 seconds.
AVOID: Shape change, camera movement, added text, flicker.
Tip: Use image-to-video with the color 1 photo and ask for color 2 in the prompt.

## AI Logo Design Prompts ($12)
Page: https://brief-library.pages.dev/ai-logo-design-prompts/  Buy: https://whop.com/ease-out-studio/ai-logo-design-prompts
40 copy-paste logo briefs for Midjourney, Ideogram, GPT Image and Claude SVG, plus 6 checks to run before you use a logo.
Structure: MARK / STYLE / SHAPES / COLOR / TYPE / BACKGROUND / AVOID / ROLE / CONTEXT / TASK / CONSTRAINTS / OUTPUT

### Geometric sans wordmark
Use when: You want a modern, neutral name for a software or services brand.
MARK: wordmark logo, the text "[BRAND_NAME]" only, for a [INDUSTRY] business
STYLE: flat vector, precise, minimal, balanced spacing
SHAPES: circular O and C forms, uniform stroke weight, no extra icons
COLOR: one dark color [HEX_COLOR] on white
TYPE: geometric sans serif, medium weight, tight but even kerning
BACKGROUND: plain white, centered, 3:2 ratio, generous margin
AVOID: gradients, shadows, 3D, taglines, extra symbols, misspelled letters
Tip: Add "lowercase" or "uppercase" to the TYPE line to change the tone fast.

### Single letter in a shape
Use when: You need an avatar-ready mark from one initial.
MARK: lettermark, the single letter "[LETTER]" inside a [SHAPE] for [BRAND_NAME], a [INDUSTRY] brand
STYLE: flat vector, bold, simple, app icon feel
SHAPES: one [SHAPE] container, letter centered, 12 percent padding
COLOR: container [HEX_COLOR_1], letter white
TYPE: geometric sans serif, bold, uppercase
BACKGROUND: white, 1:1 ratio, centered
AVOID: gradients, shadows, bevels, extra letters, textures
Tip: Try a square with rounded corners, a circle and a hexagon as three runs.

### Abstract geometric symbol
Use when: You want a modern mark that does not depict anything literal.
MARK: abstract geometric symbol for [BRAND_NAME], a [INDUSTRY] company, suggesting [IDEA_WORD]
STYLE: flat vector, bold, balanced, minimal
SHAPES: 3 to 4 basic shapes (circle, triangle, square), overlapping with clean edges
COLOR: 2 colors: [HEX_COLOR_1] and [HEX_COLOR_2]
TYPE: no text
BACKGROUND: white, 1:1 ratio, centered
AVOID: gradients, shadows, 3D, text, more than 4 shapes, realistic objects
Tip: Name the feeling in [IDEA_WORD], such as growth, trust or flow.

### Friendly animal mascot
Use when: You want a character for a kids brand, local shop or app.
MARK: friendly [ANIMAL] mascot for [BRAND_NAME], a [INDUSTRY] brand, head and shoulders
STYLE: flat vector, thick 5 px outline, simple shapes, 3 shading-free fills
SHAPES: round head, large simple eyes, small smile, one accessory: [ACCESSORY]
COLOR: 4 colors maximum: [HEX_COLOR_1], [HEX_COLOR_2], cream, dark outline
TYPE: no text
BACKGROUND: plain white, 1:1 ratio, centered
AVOID: realistic fur, gradients, scary expressions, tiny details, copyrighted characters
Tip: Describe the personality in 2 words, such as calm and curious.

### Turn a concept into clean SVG
Use when: You have a logo idea in words and want a first vector draft.
ROLE: You are a senior vector logo designer who writes clean, hand-readable SVG.
CONTEXT: Brand [BRAND_NAME], a [INDUSTRY] business. Concept: [CONCEPT_DESCRIPTION]. Mood: [MOOD_WORDS].
TASK: Draw the logo as one SVG: a symbol on the left and the name "[BRAND_NAME]" on the right.
CONSTRAINTS: viewBox="0 0 600 200". Flat fills only. No gradients, filters, or embedded raster images. Maximum 3 colors: [HEX_COLOR_1], [HEX_COLOR_2], [HEX_COLOR_3]. Use basic shapes and paths. Convert text to simple paths if possible, otherwise use a generic font-family stack and note it. Group parts with ids: symbol, wordmark.
OUTPUT: One SVG code block only, then 3 short bullet notes on what to adjust.
Tip: Ask for 3 variations in the same message if you want to compare.

### Shapes assemble
Use when: You want the symbol to build from separate pieces on a website intro.
ROLE: You are a motion developer who writes GSAP 3 animations for SVG.
CONTEXT: My logo SVG is below, with shapes inside group id="symbol". Brand: [BRAND_NAME].
TASK: Animate the shapes flying in from offset positions and locking into place, then fade in the wordmark.
CONSTRAINTS: Load GSAP 3 from a CDN script tag. Each shape starts 60 px away with opacity 0. Duration 700 ms each, stagger 90 ms, ease "power3.out". Wordmark fades in over 400 ms after 200 ms delay. Total under 2000 ms. Use transform and opacity only. Add a replay button. Under @media (prefers-reduced-motion: reduce), skip animation and show the final logo.
OUTPUT: One HTML file with inline CSS and JS.

[PASTE_SVG_HERE]
Tip: Raise the stagger to 140 ms for a calmer build.

## Claude Prompts for Landing Pages ($12)
Page: https://brief-library.pages.dev/claude-landing-page-prompts/  Buy: https://whop.com/ease-out-studio/claude-landing-page-prompts
40 copy-paste briefs that make Claude or ChatGPT write one clean, responsive HTML + Tailwind landing page section at a time, plus 6 fix-it follow-ups.
Structure: ROLE / CONTEXT / TASK / CONSTRAINTS / OUTPUT

### Split hero with image
Use when: You have one strong photo or product image and a single main offer.
ROLE: You are a front-end developer who builds conversion-focused landing pages.
CONTEXT: Business: [BUSINESS_NAME], offering [OFFER_IN_ONE_SENTENCE], for [TARGET_AUDIENCE]. Main action: [PRIMARY_CTA_LABEL] linking to [CTA_URL].
TASK: Build one split hero section. Left: eyebrow [EYEBROW_TEXT], H1 [HEADLINE_UNDER_10_WORDS], subhead [SUBHEAD_UNDER_25_WORDS], primary button, and a text link [SECONDARY_LINK_LABEL]. Right: image [IMAGE_URL] with alt text [IMAGE_ALT].
CONSTRAINTS: Tailwind via CDN. Semantic HTML (section, h1, p, a). Two columns from 768px up, image below text on mobile. Image ratio 4:3, rounded 16px, loading eager. Body text at least 18px. Contrast WCAG AA. Button at least 48px tall. No lorem ipsum, use my slots.
OUTPUT: One complete HTML file containing only this section. After the code, list the slots you filled in 3 bullets.
Tip: Swap the image side by asking for the image on the left from 768px up.

### Client logo strip from real logos
Use when: You have permission to show logos of real clients.
ROLE: You are a front-end developer who builds trust sections.
CONTEXT: Heading text: [STRIP_HEADING]. Logo files: [LOGO_1_URL], [LOGO_2_URL], [LOGO_3_URL], [LOGO_4_URL], [LOGO_5_URL] with names [CLIENT_1] to [CLIENT_5].
TASK: Build one logo strip: a small heading, then logos in one row on desktop and a 2-column grid on mobile. Logos are grayscale by default.
CONSTRAINTS: Tailwind via CDN. Each logo max height 32px, width auto, alt text is the client name. Do not add any claims, numbers or text about the clients beyond my heading. If I give fewer than 5 logos, adjust the grid. Contrast WCAG AA for the heading.
OUTPUT: One complete HTML file, one section only.
Tip: Only include logos of clients who agreed to be listed.

### 3-column features
Use when: You have three clear, equal strengths to show.
ROLE: You are a front-end developer and conversion copy editor.
CONTEXT: Product: [PRODUCT_NAME] for [TARGET_AUDIENCE]. Features: 1) [FEATURE_1_TITLE]: [FEATURE_1_BENEFIT]. 2) [FEATURE_2_TITLE]: [FEATURE_2_BENEFIT]. 3) [FEATURE_3_TITLE]: [FEATURE_3_BENEFIT].
TASK: Build one section with heading [SECTION_HEADING], intro [INTRO_UNDER_20_WORDS], and three cards, each with an inline SVG icon, title and benefit text.
CONSTRAINTS: Tailwind via CDN. 3 columns from 1024px, 1 column on mobile, 24px gaps. Titles under 5 words, benefits under 25 words. Semantic HTML (section, h2, h3). Icons decorative with aria-hidden. Contrast WCAG AA.
OUTPUT: One complete HTML file, one section only.
Tip: Write each benefit as what the customer gets, not what the tool does.

### 3 numbered steps
Use when: Your process is simple and fits in three actions.
ROLE: You are a front-end developer who builds clear process sections.
CONTEXT: Offer: [OFFER_NAME]. Steps: 1) [STEP_1_TITLE]: [STEP_1_TEXT]. 2) [STEP_2_TITLE]: [STEP_2_TEXT]. 3) [STEP_3_TITLE]: [STEP_3_TEXT].
TASK: Build one section with heading [SECTION_HEADING] and three numbered steps, each with a large number, title and text under 25 words, and a final button [CTA_LABEL].
CONSTRAINTS: Tailwind via CDN. Use an ol with li. 3 columns from 768px, stacked on mobile with a 2px vertical connector line. Numbers are text, not images. Contrast WCAG AA.
OUTPUT: One complete HTML file, one section only.
Tip: Start each step title with a verb.

### 3 tiers with highlighted plan
Use when: You sell three plans and want to recommend one.
ROLE: You are a front-end developer who builds pricing sections.
CONTEXT: Plans: [PLAN_1_NAME] [PLAN_1_PRICE] [PLAN_1_FEATURES]; [PLAN_2_NAME] [PLAN_2_PRICE] [PLAN_2_FEATURES] (recommended); [PLAN_3_NAME] [PLAN_3_PRICE] [PLAN_3_FEATURES]. Billing: [BILLING_PERIOD]. Button labels: [CTA_1], [CTA_2], [CTA_3].
TASK: Build one pricing section with three cards. The middle card has a 2px accent border and a text badge [BADGE_TEXT].
CONSTRAINTS: Tailwind via CDN. Max 6 feature lines per plan, each with an inline SVG check. Price at least 40px. 3 columns from 1024px, stacked on mobile with the recommended plan first. No fake discounts, countdowns or strikethrough prices. Add a line [TERMS_LINE] under the cards. Contrast WCAG AA.
OUTPUT: One complete HTML file, one section only.
Tip: Keep feature lists parallel so plans are easy to compare.

### Accordion FAQ
Use when: You have 5 to 8 common questions.
ROLE: You are a front-end developer who builds accessible accordions.
CONTEXT: Questions and answers: [Q1] [A1]; [Q2] [A2]; [Q3] [A3]; [Q4] [A4]; [Q5] [A5]; [Q6] [A6].
TASK: Build one FAQ section with heading [SECTION_HEADING] and an accordion where one item can be open at a time.
CONSTRAINTS: Tailwind via CDN. Prefer native details and summary elements. Summary rows at least 48px tall with a visible focus ring and a plus/minus icon. Max width 720px. Answers under 60 words. Add FAQPage JSON-LD using only my text. Contrast WCAG AA.
OUTPUT: One complete HTML file, one section only.
Tip: Order questions by how often customers actually ask them.

### SaaS product page
Use when: You are launching or relaunching a software product.
ROLE: You are a senior front-end developer and landing page strategist.
CONTEXT: Product: [PRODUCT_NAME]. Audience: [TARGET_AUDIENCE]. Core outcome: [MAIN_OUTCOME]. Brand color: [BRAND_COLOR_HEX]. Font: [FONT_NAME].
TASK: Build one page with these sections in order: 1) Nav with logo and [NAV_CTA_LABEL]. 2) Hero: [HEADLINE], [SUBHEAD], screenshot [SCREENSHOT_URL]. 3) Logo strip: [REAL_LOGO_URLS] (omit if none). 4) 3 features: [FEATURE_1], [FEATURE_2], [FEATURE_3]. 5) How it works in 3 steps: [STEP_1], [STEP_2], [STEP_3]. 6) Real quote: [CUSTOMER_QUOTE] by [CUSTOMER_NAME] (omit if empty). 7) Pricing: [PLANS_AND_PRICES]. 8) FAQ with 5 questions: [FAQ_LIST]. 9) Final CTA: [CTA_HEADLINE]. 10) Footer with [LEGAL_LINKS].
CONSTRAINTS: Tailwind via CDN. Semantic HTML, one h1, logical h2 and h3. Mobile first, breakpoints 640, 768, 1024px. Contrast WCAG AA. Invent no reviews, numbers, logos or guarantees. Mark any empty slot with an HTML comment.
OUTPUT: One HTML file with sections separated by comments.
Tip: Fill only the slots you have real content for and let the AI omit the rest.

### Mobile layout fix
Use when: The page looks right on desktop but breaks on a phone.
ROLE: You are a mobile-first front-end developer.
CONTEXT: Below is my HTML section. Problems I see on mobile: [DESCRIBE_PROBLEMS]. Test widths: 360px, 390px, 768px.
TASK: Fix the layout for mobile. Check horizontal scroll, text size, button size, image overflow, spacing and stacking order.
CONSTRAINTS: Keep Tailwind via CDN and my copy unchanged. Body text at least 16px. Tap targets at least 44px. No horizontal scroll at 360px. Do not change the desktop layout from 1024px up. Use fewer than 10 changed classes per element.
OUTPUT: The full corrected HTML, then a list of changes in 5 bullets or fewer.
HTML:
[PASTE_HTML_HERE]
Tip: Name the exact width where it breaks so the fix is targeted.

## Claude Code Prompts ($15)
Page: https://brief-library.pages.dev/claude-code-prompts/  Buy: https://whop.com/ease-out-studio/claude-code-prompts
50 copy-paste briefs for Claude Code, Cursor and other coding agents, plus 6 guardrail messages for when the agent drifts.
Structure: ROLE / CONTEXT / TASK / CONSTRAINTS / OUTPUT

### Map an unfamiliar repo
Use when: You joined or inherited a codebase and need a working mental model fast.
ROLE: Senior engineer onboarding to a new codebase.
CONTEXT: Repo root is [REPO_PATH]. Main language and framework: [STACK]. I need to work on [AREA_OF_INTEREST].
TASK: Map the repo. Identify entry points, folder layout, data flow for [AREA_OF_INTEREST], key dependencies, and how to run, test and build it.
CONSTRAINTS: Read the README, package or build files, and config first. Do not modify any file. Do not guess: mark anything you could not verify as UNCLEAR. Keep the map under 400 words.
OUTPUT: Run [TEST_COMMAND] and [BUILD_COMMAND] and report whether they pass. Then give: 1) folder map, 2) request or data flow in 6 steps or fewer, 3) risky areas, 4) five questions you still have, 5) what is left unexplored.
Tip: Set [AREA_OF_INTEREST] narrowly, such as billing or the job queue, to get a sharper map.

### CRUD endpoint
Use when: You need create, read, update and delete for a new resource.
ROLE: Backend engineer who matches existing patterns.
CONTEXT: Stack [STACK]. Resource: [RESOURCE_NAME] with fields [FIELDS]. Closest existing endpoint to copy: [EXISTING_ENDPOINT_FILE]. Auth rule: [AUTH_RULE].
TASK: Add CRUD endpoints for [RESOURCE_NAME] with validation, correct status codes, and tests for success and failure cases.
CONSTRAINTS: Read [EXISTING_ENDPOINT_FILE] and the data layer first and follow their style. Keep changes minimal. Do not touch unrelated code or change existing endpoints. Validate all input. Return consistent error shapes. Add a migration only if the schema needs it.
OUTPUT: Run [TEST_COMMAND] and [BUILD_COMMAND]. Report files changed, routes added with example requests, and what is left.
Tip: Name the endpoint to copy so the agent mirrors your naming and error format.

### Reproduce from a stack trace
Use when: You have an error trace but no clear steps to trigger it.
ROLE: Debugging engineer who proves the cause before fixing.
CONTEXT: Stack [STACK]. Stack trace:
[STACK_TRACE]
What the user was doing: [USER_ACTION]. Version or commit: [COMMIT].
TASK: Locate the failing code, explain the cause in plain words, write a minimal reproduction (a failing test if possible), then fix the root cause.
CONSTRAINTS: Read every file named in the trace and their callers first. Do not fix until the failure is reproduced. Do not silence the error or add a broad try/catch. Keep changes minimal and do not touch unrelated code.
OUTPUT: Run [TEST_COMMAND] to show the new test fails before and passes after. Report cause, files changed, and what is left or uncertain.
Tip: Include the line numbers and the exact input if you have them.

### Extract a module
Use when: A file does too many things and one part deserves its own module.
ROLE: Engineer doing a behavior-preserving refactor.
CONTEXT: Stack [STACK]. Source file: [SOURCE_FILE]. Part to extract: [PART_TO_EXTRACT]. New module path: [NEW_MODULE_PATH].
TASK: Move the part into the new module with a small, clear public interface and update all imports.
CONSTRAINTS: Read the source file, its tests and all its importers first. Run [TEST_COMMAND] before changing anything to record the baseline. No behavior changes, no renames beyond the move, no style cleanup elsewhere. Keep changes minimal and do not touch unrelated code.
OUTPUT: Run [TEST_COMMAND] and [BUILD_COMMAND] again. Report files changed, the new public interface, and what is left.
Tip: Ask for a separate commit for the move and any follow-up cleanup.

### Add tests for existing code
Use when: A working module has no tests.
ROLE: Engineer writing tests for code they did not write.
CONTEXT: Stack [STACK]. Test framework: [TEST_FRAMEWORK]. Target: [TARGET_FILE]. Example of a good existing test: [EXAMPLE_TEST_FILE].
TASK: Write tests covering the main paths, edge cases and error cases of the target, with clear names that describe behavior.
CONSTRAINTS: Read the target, its dependencies and the example test first and match the style. Do not change the source code. If you find a bug, write the test, mark it clearly and report it instead of fixing it. Mock only external boundaries. Keep changes minimal and do not touch unrelated code.
OUTPUT: Run [TEST_COMMAND]. Report tests added, behaviors covered, suspected bugs, and what is left untested.
Tip: Tell it which behaviors matter most so it spends effort there first.

### Responsive fix
Use when: A page breaks on phones or tablets.
ROLE: Front-end engineer fixing layout at real breakpoints.
CONTEXT: Stack [STACK]. Page or component: [COMPONENT_FILE]. Broken at widths: [BROKEN_WIDTHS] px. Existing breakpoints: [BREAKPOINTS].
TASK: Fix layout at 320, 375, 768 and 1280 px widths: no horizontal scroll, readable text of at least 16 px for body copy, tap targets of at least 44 px, images that scale.
CONSTRAINTS: Read the component, its styles and the shared layout first. Use existing breakpoints and tokens. Do not redesign the desktop view. Keep changes minimal and do not touch unrelated code.
OUTPUT: Run [TEST_COMMAND] and [BUILD_COMMAND]. Report what you changed at each width, files changed, how you checked it, and what is left.
Tip: Attach a screenshot or describe exactly what overflows.

### Write a PR description
Use when: A branch is ready and the reviewer needs context.
ROLE: Engineer writing for a busy reviewer.
CONTEXT: Branch [BRANCH_NAME] against [BASE_BRANCH]. Related issue: [ISSUE_LINK_OR_NOTES].
TASK: Write a PR description with: summary in 2 sentences, why, what changed grouped by area, how to test in numbered steps, risks, screenshots needed (list only), and follow-ups.
CONSTRAINTS: Read the full diff and commit messages first. Describe only what is in the diff. Do not claim tests passed unless you ran them. Do not edit code. Keep it under 250 words.
OUTPUT: Run [TEST_COMMAND] and [BUILD_COMMAND]. Give the description as plain markdown, then list anything in the diff that looks unrelated or unfinished.
Tip: Paste your team's PR template into CONTEXT to match it.

## YouTube Shorts Script Prompts ($12)
Page: https://brief-library.pages.dev/youtube-shorts-script-prompts/  Buy: https://whop.com/ease-out-studio/youtube-shorts-script-prompts
100 fill-in hooks and 30 timed faceless script briefs for Claude, ChatGPT or any chat AI.
Structure: ROLE / CONTEXT / TASK / CONSTRAINTS / OUTPUT

### Nobody Tells You
Use when: You are sharing a detail that is rarely covered in your niche.
Nobody tells you this about [TOPIC].
Tip: Make sure the next line delivers a real, specific detail.

### Stop Doing This
Use when: A popular habit works against a goal.
Stop doing [COMMON_ACTION] if you want [GOAL].
Tip: Name a specific action, not a vague habit.

### One Change
Use when: A single change produced a visible difference.
Before: [OLD_STATE]. After: [NEW_STATE]. One change.
Tip: Split the screen so both states appear in frame one.

### Tested Both
Use when: You personally tried two options.
[OPTION_A] or [OPTION_B]? I tested both.
Tip: Name your test criteria in the next line.

### In N Steps
Use when: A process fits a short list.
How to [RESULT] in [NUMBER] steps.
Tip: Keep the number at 3 to 5 for Shorts.

### Almost Happened
Use when: You avoided a bad outcome.
I almost [BAD_OUTCOME] until I tried [ACTION].
Tip: Keep the stakes real and modest.

### Should Know
Use when: You teach basics to a specific audience.
[NUMBER] [THINGS] every [AUDIENCE] should know.
Tip: Keep the number at 5 or fewer.

### Listicle
Use when: You want a fast numbered list.
ROLE: You are a short-form scriptwriter for faceless videos.
CONTEXT: Niche: [NICHE]. Audience: [AUDIENCE]. Topic: [TOPIC].
TASK: Write a listicle with [NUMBER] items.
CONSTRAINTS: 20 to 35 seconds. 60 to 85 spoken words. No face on camera. Each item gets one sentence and one visual. Do not invent statistics.
OUTPUT: 3 hook options (max 12 words each). Then a table with columns: Time | On screen text | Voiceover | Visual | Sound. Finish with a one-line call to action.
Tip: Set [NUMBER] to 3 or 5 for the best pacing.

## Claude Artifacts Ideas and Prompts ($12)
Page: https://brief-library.pages.dev/claude-artifacts-ideas/  Buy: https://whop.com/ease-out-studio/claude-artifacts-ideas
40 copy-paste briefs that make Claude build a working mini-app in one chat, plus 6 follow-ups to fix common problems.
Structure: ROLE / CONTEXT / TASK / CONSTRAINTS / OUTPUT

### Invoice generator with print view
Use when: You bill clients and want a clean invoice you can print or save as PDF.
ROLE: You are a careful front-end developer who builds single-file web apps.
CONTEXT: I am a freelancer named [YOUR_NAME] billing clients in [CURRENCY]. I have no coding skills.
TASK: Build an invoice generator. Left side: form with sender details, client name and address, invoice number, issue date, due date, up to 20 line items (description, quantity, unit price), tax rate in percent, and a notes box. Right side: live invoice preview with subtotal, tax and total. Add a Print button that shows only the invoice (use a print stylesheet, A4 and US Letter safe, 0.5 in margins). Edge cases: blank quantity counts as 0, negative prices allowed for discounts, round to 2 decimals, long descriptions wrap.
CONSTRAINTS: One self-contained file (React or HTML). No external API keys, no backend, no external network calls. Plain fonts only. Sample data clearly labeled and easy to clear.
OUTPUT: The complete file, then 3 lines on how to print or save as PDF.
Tip: Add your payment terms as a fixed footer line, for example 'Payment due within [DAYS] days'.

### Content calendar
Use when: You post on several channels and need to see the month at a glance.
ROLE: You are a front-end developer building a planning tool for creators.
CONTEXT: I post on [CHANNEL_LIST] about [TOPIC]. I plan about [POSTS_PER_WEEK] posts per week.
TASK: Build a monthly content calendar. Show a 7-column month grid with previous and next month buttons. Click a day to add a post: title, channel (dropdown from my list), format, status (idea, drafting, scheduled, published), and notes. Color-code by status and also show the status as text. Add a filter by channel and a list view for the month. Edge cases: several posts on one day show a '+N more' link, months with 5 or 6 weeks display correctly.
CONSTRAINTS: One self-contained file (React or HTML), no API keys, no backend. Export and Import as JSON. Works at 360 px width by switching to list view.
OUTPUT: The complete file and a short note on keeping a backup.
Tip: Replace the channel list with your own so the dropdown matches how you actually plan.

### Flashcards with spaced repetition
Use when: You are memorizing terms and want harder cards to come back sooner.
ROLE: You are a front-end developer building a study app.
CONTEXT: I am studying [SUBJECT] and want to review cards on a schedule.
TASK: Build a flashcard app. Screen 1: deck editor where I paste cards as 'front | back' lines, one per line. Screen 2: review mode that shows the front, then a Show Answer button, then 4 rating buttons: Again, Hard, Good, Easy. Use a simple spaced repetition rule: Again returns the card in the same session, Hard 1 day, Good 3 days, Easy 7 days, with intervals doubling after each Good or Easy. Show cards due today, cards remaining, and a session summary. Edge cases: no cards due shows a message with the next due date, blank lines are skipped, bad lines show which line number failed.
CONSTRAINTS: One self-contained file (React or HTML), no API keys, no backend. Add Export and Import as JSON. Be honest in the UI if progress cannot be saved.
OUTPUT: The complete file and a short note on the scheduling rule.
Tip: Change the interval numbers at the top of the file if you need a faster exam schedule.

### Budget tracker
Use when: You want a monthly view of money in, money out and what is left.
ROLE: You are a front-end developer building a personal finance tool.
CONTEXT: I want to track one month at a time in [CURRENCY] with categories I define.
TASK: Build a budget tracker. Setup: expected income lines and category budgets (such as Rent, Food, Transport). Main screen: add a transaction with date, amount, category, and note; a table of transactions with edit and delete; and a summary showing per category spent, budget, and remaining, with a bar that turns a warning color and shows the word 'Over' when spent exceeds budget. Show total income, total spent and net. Month selector. Edge cases: refunds as negative amounts, empty month, amounts with more than 2 decimals rounded.
CONSTRAINTS: One self-contained file (React or HTML), no API keys, no backend, no bank connections. Export to CSV and Export and Import JSON. Clearly state where data is kept and the risk of losing it.
OUTPUT: The complete file and a short note on backing up my data.
Tip: Start with 5 categories only, then add more once you have a month of real entries.

### CSV to chart
Use when: You have a CSV and want a quick chart without opening a spreadsheet.
ROLE: You are a front-end developer who builds data visualization tools.
CONTEXT: I will paste or upload small CSV files of up to 1,000 rows with a header row.
TASK: Build a CSV to chart app. Input: paste text or choose a file. Parse the header, detect number and date columns, and show a preview of the first 10 rows. Controls: chart type (bar, line, pie), X column, Y column, optional group column, and aggregate (sum, average, count). Render the chart as SVG with axis labels, a title field, and a legend. Add Download as PNG or SVG if possible. Edge cases: quoted commas, blank cells, non-numeric values in a number column shown as a warning with the count skipped, more than 12 categories grouped into 'Other'.
CONSTRAINTS: One self-contained file (React or HTML), no API keys, no backend, no external chart libraries loaded from the network. Pre-fill labeled sample data.
OUTPUT: The complete file and a short note on the CSV format it expects.
Tip: Ask for a second Y series if you want to compare two columns on one chart.

### Word guessing game
Use when: You want a simple word puzzle for yourself, a class or your audience.
ROLE: You are a front-end developer building a word game.
CONTEXT: Players guess a hidden [WORD_LENGTH]-letter word in 6 tries. I will supply my own word list.
TASK: Build a word guessing game. A text box lets me paste a word list (one per line, same length). The game picks a random word. Player types a guess and gets feedback per letter: correct place, wrong place, or not in the word, shown with a symbol and a color so it works without color vision. Show an on-screen keyboard that updates letter states. Messages for win and loss, with the answer revealed after a loss and a New Game button. Edge cases: repeated letters handled correctly (count each letter only as many times as it appears in the answer), guesses of the wrong length are rejected with a message, guesses must be in the list unless I turn that off.
CONSTRAINTS: One self-contained file (React or HTML), no API keys, no backend. Pre-fill 20 sample words. Keyboard and touch input both work.
OUTPUT: The complete file and a short note on adding a word list.
Tip: Use themed lists, such as words from your own industry, to make the game feel personal.

## Website Animation Prompts for Claude and GSAP ($19.99)
Page: https://brief-library.pages.dev/website-animation-prompts/  Buy: https://whop.com/ease-out-studio/directed-motion-pack
30 copy-paste briefs for logo reveals, hero entrances, buttons, loaders, scroll and text effects, each with the working HTML/GSAP file it produced.
Structure: WHAT MOVES / FROM WHERE / HOW LONG / WHICH EASE / IN WHAT ORDER

### Logo reveal: Three shapes assemble the mark
Use when: Brief 01 of 30 in the Directed Motion Pack.
Logo reveal for "Larkspur" on a dark background.
1. Three shapes (circle, quarter, square) fly in and assemble the mark: 600ms each, expo.out, 80ms apart.
2. The mark settles with a 1.07 to 1 scale bump, back.out(3).
3. Wordmark letters rise from a mask, 40ms apart, back.out(1.6).
4. One soft light sweep crosses at 1.6s, then hold.
Total under 2.2s. Reduced motion: show the end state.
Output: one HTML file, GSAP from the CDN, all timings in one block at the top.
Tip: Assembly reads as craft. The bump at the end is the only overshoot, so it lands.

### Hero entrance: Headline words rise, CTA lands last
Use when: Brief 07 of 30 in the Directed Motion Pack.
Landing hero for a design studio.
1. Headline words rise from a mask, 60ms apart, expo.out, 600ms.
2. Subhead fades up 12px at 0.35s, power2.out.
3. CTA button scales from 0.9 at 0.5s, back.out(2), 450ms.
4. Nav fades down from -20px at 0s.
Whole entrance under 1s. Reduced motion: show the end state.
Output: one HTML file, GSAP from the CDN, all timings in one block at the top.
Tip: The CTA arrives last on purpose: the eye ends where you want the click.

### Button & micro: Hover lift, press squash
Use when: Brief 14 of 30 in the Directed Motion Pack.
Button that feels physical.
hover: lift 3px, shadow grows, 200ms, power2.out
press: scale x 1.04, y 0.92, 90ms, power1.out
release: back to 1 with back.out(3), 400ms
focus-visible: 3px accent outline
Reduced motion: color change only.
Output: one HTML file, GSAP from the CDN, all timings in one block at the top.
Tip: Squash on press, overshoot on release. That is the whole secret of buttons that feel expensive.

### Loader: Skeleton shimmer to content
Use when: Brief 21 of 30 in the Directed Motion Pack.
Card list loading state.
1. Three skeleton cards with a shimmer band: linear, 1.4s per pass, infinite.
2. After 2s (demo) skeletons fade out 250ms.
3. Real cards fade up 16px, 80ms apart, power3.out, 500ms.
4. Demo loops.
Reduced motion: no shimmer, simple crossfade.
Output: one HTML file, GSAP from the CDN, all timings in one block at the top.
Tip: Shimmer says still loading; the stagger on arrival says done, in order.

### Text: Marker highlight sweep
Use when: Brief 30 of 30 in the Directed Motion Pack.
Sentence with one key phrase highlighted.
1. Sentence rises in by words, 50ms apart.
2. At 0.7s a marker highlight sweeps behind the key phrase left to right, 600ms, power3.out.
3. Highlight is slightly rotated, -1deg, with rough ends.
4. Key phrase text turns dark as the marker passes.
Reduced motion: highlight shown.
Output: one HTML file, GSAP from the CDN, all timings in one block at the top.
Tip: Highlight after the read, not with it: first they read, then you tell them what matters.

## AI Prompts for Etsy and Shopify Sellers ($12)
Page: https://brief-library.pages.dev/ai-ecommerce-seller-prompts/  Buy: https://whop.com/ease-out-studio/ai-ecommerce-seller-prompts
46 copy-paste briefs for Etsy, Shopify and Amazon handmade sellers: listings, product photos, ads, emails and store pages.
Structure: ROLE / CONTEXT / TASK / CONSTRAINTS / OUTPUT / SUBJECT / SURFACE / LIGHT / CAMERA / COMPOSITION / STYLE / AVOID

### Etsy title with keywords
Use when: You are writing or rewriting an Etsy listing title.
ROLE: Etsy SEO copywriter.
CONTEXT: Before writing, confirm these facts. Product: [PRODUCT_TYPE]. Materials: [MATERIALS]. Size: [SIZE]. Color options: [COLORS]. Buyer: [BUYER]. Occasion: [OCCASION]. Search phrases I think buyers use: [MY_KEYWORDS].
TASK: Write 5 Etsy title options.
CONSTRAINTS: 120 to 140 characters each. Put the most important phrase in the first 40 characters. No repeated words, no all caps, no symbols. Use only the facts above. Do not invent materials, sizes, certifications or reviews. If a fact is missing, ask me first.
OUTPUT: A numbered list of 5 titles with the character count after each.
Tip: Paste your top 3 real search terms into [MY_KEYWORDS] so the first words match how buyers look.

### Handmade story
Use when: You want a short maker story near the top of the listing.
ROLE: Copywriter for handmade brands.
CONTEXT: Maker: [MAKER_NAME]. Product: [PRODUCT_TYPE]. How I make it, step by step: [PROCESS]. Why I started: [TRUE_STORY]. Materials and where they come from: [MATERIALS_SOURCE].
TASK: Write a maker story for the listing.
CONSTRAINTS: 120 to 150 words. First person. Plain words. Use only my process and story above. Do not invent awards, press, certifications, batch counts or reviews. Ask me first if any detail is missing.
OUTPUT: One paragraph, then one 12-word line to use as a pull quote.
Tip: The more specific your PROCESS notes, the less generic the story.

### Main image on white
Use when: You need a clean first image for a listing or marketplace.
SUBJECT: My real product, [PRODUCT_DESCRIPTION], matching the uploaded reference photo exactly in shape, color, texture and proportions.
SURFACE: Seamless pure white background (RGB 255,255,255) with a soft contact shadow.
LIGHT: Large soft light from front left, fill from right, no color cast.
CAMERA: 85mm lens, f/8, eye-level slightly above, product sharp edge to edge.
COMPOSITION: Square 2000 x 2000 px, product fills 85 percent of the frame, centered.
STYLE: Clean catalog photo, true-to-life color.
AVOID: Changing the design, adding props, text, logos, extra parts, or smoothing real texture and handmade variation.
Tip: If the color drifts, add the exact color name or hex code from your product.

### Meta ad primary text, 3 versions
Use when: You are testing ad copy for one product.
ROLE: Direct-response copywriter.
CONTEXT: Product: [PRODUCT_TYPE]. Real facts: [FACTS]. Audience: [AUDIENCE]. Price: [PRICE]. Offer, if real: [REAL_OFFER_OR_NONE]. Link goes to: [PAGE].
TASK: Write 3 versions of primary text, each with a different angle: problem, gift, craftsmanship.
CONSTRAINTS: 60 to 100 words each. First 125 characters must stand alone. No fake reviews, scarcity, countdowns or result promises. Do not invent materials, sizes, certifications or numbers. Plain language.
OUTPUT: 3 labeled versions, each with a 5-word headline and a 25-character description line.
Tip: Change only the angle between versions so test results mean something.

### Welcome series, 3 emails
Use when: Someone just joined your list.
ROLE: Email copywriter for a small handmade shop.
CONTEXT: Shop: [STORE_NAME]. What I make: [PRODUCTS]. My story: [TRUE_STORY]. Best sellers: [BEST_SELLERS]. Welcome offer, only if real: [REAL_OFFER_OR_NONE].
TASK: Write a 3-email welcome series sent on day 0, day 3 and day 7.
CONSTRAINTS: Each email 90 to 140 words, 1 call to action, subject under 45 characters, preview text under 90 characters. Email 1: welcome. Email 2: how it is made. Email 3: best sellers. No fake urgency, no invented reviews or numbers.
OUTPUT: 3 emails, each with SUBJECT, PREVIEW, BODY, CTA.
Tip: Add your real shipping times to email 3 to answer the first question buyers ask.

### Late order reply
Use when: An order is behind schedule.
ROLE: Customer care writer for a small shop.
CONTEXT: Customer name: [CUSTOMER_NAME]. Order: [ORDER_DETAILS]. Promised date: [PROMISED_DATE]. True reason for delay: [TRUE_REASON]. New realistic date: [NEW_DATE]. What I can offer: [REAL_OPTIONS].
TASK: Write a reply.
CONSTRAINTS: 90 to 130 words. Apologize once, be honest, give the new date, offer options. Do not invent causes, tracking details or compensation I did not list.
OUTPUT: Reply text plus a 1-line subject.
Tip: Add the tracking link if you have one.

## AI Marketing Prompts for Restaurants and Cafés ($12)
Page: https://brief-library.pages.dev/ai-restaurant-marketing-prompts/  Buy: https://whop.com/ease-out-studio/ai-restaurant-marketing-prompts
42 copy-paste briefs for menus, posts, food photos, promo videos, replies and emails, plus a 30-day content plan prompt.
Structure: ROLE / CONTEXT / TASK / CONSTRAINTS / OUTPUT / SUBJECT / SURFACE / LIGHT / CAMERA / COMPOSITION / STYLE / AVOID / SHOT / MOTION / DURATION

### Dish descriptions
Use when: Your menu lines are bare names or long and vague.
ROLE: You are a menu copywriter for a neighborhood cafe.
CONTEXT: Ember & Oat is a [CITY] cafe with a [CUISINE_STYLE] menu. Guests are [GUEST_TYPE]. Tone: [TONE].
TASK: Write a description for each dish below using only the ingredients I list.
DISHES AND INGREDIENTS: [DISH_LIST_WITH_INGREDIENTS]
CONSTRAINTS: 12 to 20 words per dish. Lead with the main ingredient. No invented sourcing claims, no words like best or famous. One cooking method or texture per dish.
OUTPUT: A table with columns Dish, Description, Word count. Then 2 dishes rewritten in a second tone for comparison.
Tip: Add one sentence about how a dish is actually made to get more specific wording.

### Weekly post plan
Use when: You never know what to post on Monday.
ROLE: You are a social media planner for a small restaurant.
CONTEXT: [VENUE_NAME], [CUISINE_STYLE], in [CITY]. Platforms: [PLATFORMS]. Posting days: [NUMBER_OF_POSTS] per week. This week we have: [NEWS_AND_SPECIALS]. Staff time available: [MINUTES_PER_DAY] minutes a day.
TASK: Plan one week of posts.
CONSTRAINTS: Mix of 3 content types. Each post needs a real photo or clip we can shoot in under 10 minutes. No giveaways or discounts unless listed above.
OUTPUT: Table with Day, Platform, Format, Photo or clip to shoot, Caption draft (up to 40 words), Best time slot to test.
Tip: Name your slowest day so the plan puts a stronger post there.

### Hero dish
Use when: You need a main menu or website image.
SUBJECT: [DISH_NAME] as served at Ember & Oat, with [REAL_INGREDIENTS] visible and plated as in [REFERENCE_PHOTO_OR_DESCRIPTION].
SURFACE: [PLATE_TYPE] on a [TABLE_MATERIAL] table.
LIGHT: Soft window light from camera left, 5200K, gentle shadow on the right.
CAMERA: 50mm lens, f/2.8, 35 degree angle, 40 cm from the plate.
COMPOSITION: 4:5 ratio, dish fills 60% of the frame, empty space at top.
STYLE: Natural, realistic food photography, true colors.
AVOID: Ingredients not on the real dish, extra garnish, fake steam, text, logos, distorted utensils, extra fingers.
Tip: Match the plate and portion size to what the kitchen actually sends out.

### Steam rising
Use when: You want a warm, close shot of a hot dish.
SHOT: Close-up of steam rising from a hot dish, for a 3 second b-roll insert.
SUBJECT: A bowl of [HOT_DISH_NAME] with real [INGREDIENTS] on a wood table at Ember & Oat.
CAMERA: 85mm lens equivalent, locked off, 30 cm from the bowl, slight low angle.
MOTION: Steam drifts upward at slow speed, about 1 cm per second. No camera movement.
LIGHT: Dark background, soft backlight from the right, 4500K.
DURATION: 3 seconds, steam visible from 0 ms.
AVOID: Fire, smoke, extra ingredients, hands, text, logos, fast motion.
Tip: Ask for an 8 second version and trim the best 3 seconds.

### Reply to a 5-star review
Use when: A guest left a warm review and you want a personal reply.
ROLE: You are the owner of a small cafe replying to a guest.
CONTEXT: Venue: Morning Crumb. The review text: [PASTE_REVIEW]. Reviewer first name: [FIRST_NAME]. Dishes they mention: [DISHES].
TASK: Write a thank you reply.
CONSTRAINTS: 30 to 50 words. Mention one specific thing from the review. Sound like a person, not a script. No promises of free items. Do not claim facts not in the review.
OUTPUT: Three versions with different openings, each signed [OWNER_NAME].
Tip: Rotate the three versions so replies do not look copied.

### Monthly newsletter
Use when: You send one email a month to regulars.
ROLE: You are an email writer for a neighborhood cafe.
CONTEXT: Venue: Ember & Oat. Month: [MONTH]. News: [NEWS_ITEMS]. New menu items: [NEW_ITEMS]. Events: [EVENTS_WITH_DATES]. Voice: [TONE].
TASK: Write the newsletter.
CONSTRAINTS: 180 to 250 words total. Subject line up to 45 characters, preview text up to 80. 3 short sections with headers. One main call to action: [CALL_TO_ACTION]. No fake urgency. Include a plain footer line with address and an unsubscribe reminder.
OUTPUT: Two subject line options, preview text, email body, and footer.
Tip: Keep the same three sections each month so readers know what to expect.

## AI Prompts for Real Estate Agents ($12)
Page: https://brief-library.pages.dev/ai-real-estate-prompts/  Buy: https://whop.com/ease-out-studio/ai-real-estate-prompts
42 copy-paste briefs for listings, social posts, video tours, staging, emails and market updates, plus 5 compliance checks, with Fair Housing guardrails in every brief.
Structure: ROLE / CONTEXT / TASK / CONSTRAINTS / OUTPUT

### Single family home
Use when: You are writing the main description for a standard house listing.
ROLE: You are a real estate copywriter for a US residential agent.
CONTEXT: Single family home at [NEIGHBORHOOD]. [BEDS] beds, [BATHS] baths, [SQFT] sq ft, lot [LOT_SIZE]. Key features: [FEATURE_LIST]. Updates and years: [UPDATES_WITH_YEARS]. Nearby places I verified: [VERIFIED_PLACES].
TASK: Write a listing description that leads with the strongest feature and moves through the home in a logical walk.
CONSTRAINTS: 150 to 180 words. Plain US English. No clichés like 'must see'. Use only the facts above. Follow Fair Housing rules: describe the property and not the people, no words about who should live there. Market data only from my own sources, never invented.
OUTPUT: 1 description in 2 short paragraphs, then 1 line listing 3 facts I should double-check.
Tip: Put the feature buyers ask about most first in FEATURE_LIST so the opening line uses it.

### Just listed
Use when: A new listing goes live and you want a launch post.
ROLE: You are a social media writer for a US real estate agent.
CONTEXT: Just listed at [NEIGHBORHOOD]. [BEDS] beds, [BATHS] baths, [SQFT] sq ft. 3 best features: [FEATURE_1], [FEATURE_2], [FEATURE_3]. Link or contact: [LINK_OR_CONTACT]. Agent and brokerage: [AGENT_NAME], [BROKERAGE_NAME].
TASK: Write 3 caption options for a just listed post.
CONSTRAINTS: Each caption 40 to 70 words. One call to action each. 5 hashtags each, local and plain. No invented urgency. Follow Fair Housing rules: describe the property and not the people, no words about who should live there. Market data only from my own sources, never invented.
OUTPUT: 3 captions, each with hashtags, and a 1-line note on which photo to pair with each.
Tip: Use the 3 options on different platforms rather than posting all of them in one place.

### 30-second walkthrough plan
Use when: You need a quick tour video planned before you shoot.
ROLE: You are a video producer who plans short real estate tours.
CONTEXT: Property at [ADDRESS_OR_AREA]. Rooms and features: [ROOM_LIST]. Best natural light time: [LIGHT_TIME]. Camera: [CAMERA_OR_PHONE] at 4K 30fps, horizontal 16:9.
TASK: Plan a 30-second walkthrough with clip timings.
CONSTRAINTS: 8 to 10 clips, each 2 to 4 seconds. Include one opening clip and one closing clip with contact details [CONTACT]. Show only what is really there. Follow Fair Housing rules: describe the property and not the people, no words about who should live there. Market data only from my own sources, never invented.
OUTPUT: A table of clip number, duration in seconds, location, camera move, and on-screen text of 6 words or fewer.
Tip: Shoot a few extra seconds of each clip so you have room to trim.

### Empty living room staging concept
Use when: You have a vacant living room photo and want a staged concept.
ROLE: You are an interior stylist writing prompts for an image model.
CONTEXT: Real photo of an empty living room, [ROOM_SIZE] ft, with [FIXED_FEATURES] such as windows, fireplace and flooring. Style direction: [STYLE]. Palette: [PALETTE].
TASK: Write 3 prompts for a virtually staged version of the photo with furniture and decor only.
CONSTRAINTS: Keep walls, windows, doors, floors, ceiling and room dimensions exactly as in the photo. Furniture must fit the real scale. No people. Include the required label: Virtually staged. Follow Fair Housing rules: describe the property and not the people, no words about who should live there. Market data only from my own sources, never invented.
OUTPUT: 3 prompts under 70 words each, a negative prompt list, and a 1-line disclosure for the listing caption.
Tip: Name the real flooring and wall color so the model does not repaint them.

### New lead reply
Use when: A new inquiry arrives and you want to respond quickly and clearly.
ROLE: You are an email writer for a US real estate agent.
CONTEXT: Lead name [LEAD_NAME], source [LEAD_SOURCE], inquiry text: [INQUIRY_TEXT]. My availability: [AVAILABILITY]. Agent and brokerage: [AGENT_NAME], [BROKERAGE_NAME].
TASK: Write a reply that answers the question asked and proposes one next step.
CONSTRAINTS: 90 to 120 words. Warm, direct, no pressure. No guesses about the lead's situation. Follow Fair Housing rules: describe the property and not the people, no words about who should live there. Market data only from my own sources, never invented.
OUTPUT: 1 subject line, 1 email body, and 1 text message version under 40 words.
Tip: Paste the lead's exact message so the reply answers what they actually asked.

### Monthly market update
Use when: You publish a monthly update using numbers you pulled yourself.
ROLE: You are a market update writer for a US real estate agent.
CONTEXT: Area [AREA], month [MONTH_YEAR]. Data I pulled from [MY_DATA_SOURCE]: median price [MEDIAN_PRICE], closed sales [CLOSED_SALES], active listings [ACTIVE_LISTINGS], days on market [DAYS_ON_MARKET]. Prior month figures: [PRIOR_MONTH_FIGURES].
TASK: Write a plain-language monthly update that compares this month with last month using only these numbers.
CONSTRAINTS: 200 to 260 words. Name the data source and date in the text. Do not predict future prices. No numbers beyond what I gave. Follow Fair Housing rules: describe the property and not the people, no words about who should live there. Market data only from my own sources, never invented.
OUTPUT: 1 article with 3 subheads, 1 email summary under 80 words, and 1 social caption under 50 words.
Tip: If a figure is missing, leave it blank and ask the AI to skip it rather than guess.