Fulcrum — Prompt Engine Suite

Operating System

What are you working
on today?

Select an engine below, or let the orchestrator figure out what you need.

Not sure what you need?

Tell me what you're working on and I'll route you to the right engine

Session Planner

Generate a Claude Code session prompt with full project context

For Claude Code

This generates a session opener prompt you paste at the start of a Claude Code session. It loads project context, sets the mode, and establishes guardrails — so Claude Code starts every session with full awareness.

Project

Project name

Repo URL

One-sentence description

Tech stack

Session mode

Build a feature

Audit the codebase

Fix bugs / cleanup

Write tests

Update CLAUDE.md

Review a PR

Security review

Refactor

Session details

What specifically are we doing?

What must NOT break (the 3 sacred things)

Paste your current CLAUDE.md (or key rules from it)

Context from last session (what changed, what's in progress)

Session Planner

Build a New Engine

3 steps — then download an updated suite with your engine baked in

Identity

Engine name

Dashboard description

What problem does this engine solve?

What does success look like after using it?

AI Persona

Role title

Key expertise

Behavioral instructions

Tools to use

Web search

ClickUp

Notion

Google Drive

n8n

No tools needed

Step 1 of 3 — Identity

Input fields

Add the questions this engine needs to ask. Every field should earn its place.

Add a field

Field label

Type

Placeholder hint

Output definition

What should the AI deliver?

Output format

Structured document

Conversational

Action plan

Framework with rules

Decision tree

When info is missing

Ask clarifying questions

Assume and flag

Search the web

Offer two scenarios

What this engine must never do

Frameworks or methodologies to reference

Web Design & UI/UX

World-class frontend design brief for Claude Code

Brand

Brand / project name

Industry

Primary audience

Five personality words

Current live site URL (if exists)

What does success look like for the visitor?

Tone

Emotional tone

Calm & trustworthy

Bold & ambitious

Warm & pastoral

Clinical & precise

Premium & refined

Urgent & mission-driven

Minimal & modern

Narrative & editorial

Formal / Casual

FormalCasual5

Minimal / Expressive

MinimalExpressive5

Dark / Light

DarkLight7

Atmosphere notes

References

Layout patterns

Full-width hero

Split screen

Editorial long-scroll

Card grids

Asymmetric / broken grid

Bento / mosaic

Centered narrow column

UI details you admire

Avoid

Aesthetics to avoid

Generic purple gradients

Corporate stock photos

Cluttered / too busy

Cheap / templated

Over-animated

Missionary church website

Generic SaaS landing page

Additional anti-patterns

Colors & type

Existing palette

Typography character

Classic serif

Modern geometric sans

Humanist / warm sans

Editorial / magazine

Big bold display

Fonts you admire

Deliverable

What are we building?

Full homepage

Landing page

Marketing site

Component / section

Dashboard / app UI

Brand style guide

Tech stack

Mobile

Mobile-first

Desktop primary

Both

Final notes

Accessibility requirements

Existing design system or component library

Web Design & UI/UX

Brand & Identity

Voice, color psychology, logo direction, positioning

Basics

Brand name

Stage

New brand

Rebrand

Extension

Org type

Industry

Primary audience

Secondary audience

Current website URL

Personality

Five personality words

The one feeling to leave people with

This brand is like a person who...

If a publication, it would be

Competitive landscape

Direct competitors

Competitor URLs (for AI to analyze visually and strategically)

Category default (what they all look/sound like)

What we want to do differently

Constraints

Budget

Bootstrap

Mid-range

Full investment

Timeline

Existing assets to preserve

Non-negotiables

Brand & Identity

Product Vision & Architecture

PRD + tech architecture + market pressure-testing

Product context

Product name

One-sentence description

The problem it solves

ICP

How they solve it today

Why now

Vision & goals

Wild success in 3 years

MVP definition

North Star metric

Revenue model

Technical context

Stack so far

Required integrations

Compliance

Team

Timeline

Infra budget/mo

Existing codebase

Have you already started building this?

Yes, there's code

No, starting fresh

Product Architecture

Claude Code Guardrails

Generates CLAUDE.md + dev protocol

Project

Project name

Repo URL

Description

Phase

Greenfield

Active development

Refactor

Maintenance

Languages

Frameworks

Database

Deployment

Rules

Most important rule

Known landmines

Locked dependencies

Env variable names

Additional rules

Patterns (the more specific, the better the CLAUDE.md)

Folder structure (paste actual)

Naming conventions

Data fetching pattern (the ONE way)

Component architecture

Error handling pattern

Multi-tenant rules

Git workflow

Performance budgets

Pre-feature checklist

Example 'golden' files (the right way to do things)

What has Claude Code gotten wrong on this project?

Codebase snapshot

Quick paste: Run this in your project root and paste below:

echo '=== FILE TREE ===' && find ./src -type f -not -path '*/node_modules/*' | head -80 && echo '=== PACKAGE.JSON ===' && cat package.json && echo '=== ENV ===' && cat .env.example 2>/dev/null || echo 'no .env.example'

Codebase snapshot

Claude Code Guardrails

Curriculum & Learning Design

Backwards design from outcomes to lesson plan

Course context

Course name

Organization

Format

Async self-paced

Cohort-based

Live workshop

Hybrid

Platform

Duration

Target learner

Transformation

At the end, learners will be able to... (3-5 outcomes)

What they'll do differently

Single most important insight

False beliefs to dismantle

Core topics

Constraints

Tone

Academic

Conversational

Coaching

Peer-learning

Devotional

Production budget

Text / slides only

Basic video

Professional production

Competitor courses to review

Existing content assets to build on

Assessment model

Completion-based

Competency-based

Portfolio / project

Peer review

AI-evaluated

Accessibility / accommodations

Curriculum & Learning Design

Financial Advisor

Portfolio analysis, allocation, fund research

Context

Total investable assets ($)

Monthly contribution ($)

Accounts (types & balances)

Time horizon

Under 5yr

5-10yr

10-20yr

20+yr

Risk tolerance

ConservativeAggressive7

Primary goal

Faith-based / ESG preferences

Tax bracket / filing status

Significant debt

Current portfolio — what I'm invested in today

Paste or type your current holdings. Include fund name, ticker, current value, and which account it's in. You can paste from a spreadsheet, brokerage export, or just list them out.

Current holdings

Total portfolio value today ($)

Anything you're unsure about in your current holdings

Options I'm considering

Paste funds or investments you're looking at. These could be funds your plan offers, ETFs you've been researching, or options your advisor recommended. The AI will evaluate each one against your goals, values, and existing portfolio.

Available fund options (from employer plan, brokerage, or research)

Where are these options from?

Employer 403b/401k plan

Roth IRA (open market)

Taxable brokerage

Advisor recommended

My own research

What specifically do you want evaluated about these options?

Mindset

Biggest financial fear

What I've been putting off

Financial Advisor

Chief Strategy Officer

Pinnacle/EOS coaching, GTM, competitor research, ICP clarity

Organization

Org name

Stage

Pre-revenue

Early traction

Growth

Mature

One-sentence description

Revenue / budget

Team size

Strategic reality

Core problem right now

What's failed

What's working - don't break this

Decision I keep avoiding

Market & GTM

ICP

Top competitors

Differentiator

GTM motion not working

Pinnacle / EOS

Core Values

Current Rocks

Biggest issue

The real reason we're stuck

Data & links

Your website URL

Competitor URLs (paste so AI can analyze)

Revenue breakdown by product/service

Customer acquisition cost (even rough estimate)

Cash runway / financial pressure

Chief Strategy Officer

Chief of Staff

ClickUp sync + priority clarity + weekly operating plan

Session

Goal

Weekly planning

Monthly review

Quarterly reset

Brand focus

Decision clarity

Open

Time available

Energy (1-10)

EmptyFull6

What's on your mind

What's weighing on you most

Current challenge

Focus brand

Brand 1

Brand 2

Brand 3

All / unclear

ClickUp focus areas

Personal

How you're feeling about work

Energized and clear

Productive but scattered

Overwhelmed

Stuck / unclear

Burned out

Personal context (optional)

Decisions & delegation

Decisions that need to be made this session

What can be delegated right now

ClickUp workspace URL

Strategic context (links to living docs)

Strategic plan / roadmap (ClickUp, Notion, Google Doc)

Financial dashboard / P&L

Pipeline / CRM view

Paste current strategic priorities or OKRs

Other reference docs (paste links)

Chief of Staff

QA & Codebase Audit

Vision-to-code gap, security audit, pre-launch readiness score

Product vision

Product name

One-sentence description

Who uses it and what they need

Core promise

Phase

Early prototype

Active dev

Pre-launch

Live

Next milestone

Original vision (what you wanted built)

Vision vs. reality audit

Describe what this product was supposed to be in full detail. The more specific you are, the more precisely the audit can identify where the codebase drifted from your intent. Paste PRDs, specs, or just describe it in your own words.

Full capability description (everything this product should do)

User flows as you designed them (the happy paths)

Data model as you intended it

What it must feel like to use

What this product must never be

Non-negotiable principles

Paste your PRD, spec, or original planning doc (if you have one)

Tech stack

Frontend

Backend

Database

Auth

Infra

Testing

Third-party services

Audit focus

Areas of highest concern

Security & auth

Missing features

Architecture

Performance

Stack compliance

Data model

API design

Multi-tenancy

Fragile / incomplete features

Part you trust least

Recently changed (regression risk)

Known issues on radar

Access & constraints

Repo URL

Branch

Key files / dirs

Codebase description

Team

Milestone requirements

Timeline pressure

Critical - days

Tight - weeks

Moderate

No pressure

Anything else to know

Code samples (paste real code for specific findings)

2-3 representative API routes

Auth middleware

RBAC / permission model

Critical user flows (3-5 most important)

How code gets to production

Locked decisions (do NOT recommend changing)

QA & Codebase Audit

Vision Integrity Audit

Mission drift detection, value alignment, stakeholder trust score

Organization

Org name

Founded / years active

Original mission statement

Current mission statement (if changed)

Core values

Founding story / origin

Current reality

What you actually spend most time on

Revenue streams

What feels misaligned

What stakeholders are saying

Decisions made in the last year that felt off

Drift indicators

Areas of concern

Mission creep

Revenue vs. values tension

Team alignment

Brand confusion

Stakeholder trust

Program relevance

Leadership fatigue

Strategy scatter

If you could only do ONE thing, what would it be?

What would your founder-self say about today?

Evidence

Your website URL

What have you said no to in the last year?

What are you saying yes to that you shouldn't be?

How do you measure success today?

Board / advisor dynamics

If money wasn't a constraint, what would you do?

Vision Integrity Audit

GTM Playbook

Channel strategy, messaging, launch sequencing, ICP activation

Product / Offering

Product name

One-sentence description

Product / website URL

What it replaces / competes with

Price point / model

Stage

Pre-launch

Beta / pilot

Early traction

Growth

Expansion

ICP & Market

Ideal customer profile

Buying process

Key objections you hear

Top competitors

Competitor URLs (for AI to analyze)

Your unfair advantage

Current GTM

What you've tried

What's working

What's not working

Existing content assets (blog posts, case studies, demos)

Current pipeline (prospects at each stage)

Sales cycle length

Monthly marketing budget

Team available for GTM

Timeline / urgency

Constraints

Channels you want to explore

Content / SEO

Paid search

Paid social

Email / nurture

Cold outbound

Events / conferences

Partnerships

Community / PLG

Referral program

Non-negotiables

GTM Playbook

Content & Copy System

Voice-locked copy, SEO content, email sequences, social calendars

Brand voice

Brand name

Industry

Voice description

Words we use / Words we never use

Tone spectrum

Authoritative

Conversational

Inspirational

Educational

Pastoral

Data-driven

Story-led

Provocative

Sample content you love (URL or paste)

Audience & goals

Primary audience

Content goal

Awareness / SEO

Lead generation

Nurture / retention

Thought leadership

Sales enablement

Community building

Primary CTA

SEO keywords (if relevant)

Content request

What do you need?

Website copy

Blog post

Email sequence

Social calendar

Landing page

Newsletter

Case study

Ad copy

Full content system

Topic / subject

Key messages to include

Constraints

Distribution channels

Competitor content URLs to beat

Your best-performing content (links or describe)

Content & Copy System

Data Model Designer

Schema design, entity relationships, multi-tenancy, migration planning

Product context

Product name

Domain description

Core entities

Relationships

Multi-tenancy model

Not multi-tenant

Row-level isolation (RLS)

Schema per tenant

Subdomain routing

Technical context

Database

ORM

Existing schema (paste if modifying)

Compliance

Auth system

User roles

Scale expectations

Data Model Designer

Architecture Decision Review

Audit existing decisions or pressure-test new ones with research and alternatives

Two modes

Mode 1: Give it an existing project and it will analyze every architectural decision that was made, research whether they're still the right calls, and flag what should change. Mode 2: You're weighing a specific decision and want it pressure-tested before you commit.

What mode?

Review existing project decisions

Pressure-test a new decision

Architecture Decision Review

SOW & Contractor Handoff

Scope, acceptance criteria, architecture constraints for dev handoff

Engagement

Project name

Contractor / team

What needs to be built

Existing codebase (repo URL)

Architecture constraints

Requirements

Stack

Do NOT touch

Testing requirements

Timeline

Budget

Communication cadence

Definition of done

Existing CLAUDE.md or architecture doc (paste)

Example of 'right way' code for contractor to follow

SOW & Contractor Handoff

Security Audit

OWASP Top 10, auth flows, data exposure, compliance, secrets management

Product & stack

Product name

Description

Frontend

Backend

Database

Auth system

Third-party services

Data & compliance

Data types handled

PII

Financial

Health

Education records

Minor / child data

Compliance requirements

FERPA

COPPA

HIPAA

SOC2

GDPR

User roles

Code context

Repo URL

Branch

Auth middleware (paste)

RLS policies (paste)

Env var names

Known security concerns

Security Audit

Logo Concept Generator

Strategic logo concepts with symbolic meaning, scalability analysis, and creative direction

Brand foundation

Brand name

Industry

Brand personality (5 words)

Target audience

What does this brand stand for? (the deeper meaning)

Brand story or origin (if relevant to the mark)

Tagline or descriptor (if the logo needs to work with one)

Brand architecture

Standalone brand

Part of a brand family

Endorsed by parent brand

Sub-brand

How long should this logo last?

3-5 years (startup, expect evolution)

5-10 years (established, stable)

10+ years (institutional, timeless)

Positioning statement

Visual direction

Brands whose visual identity you admire (names + URLs)

Brands whose visual identity you dislike (names + why)

Design style

Minimal

Bold

Geometric

Organic

Abstract

Retro

Futuristic

Handcrafted

Typographic

Logo type preference

Wordmark

Lettermark

Brandmark / symbol

Combination mark

Emblem

Open to anything

Colors already decided (or leave blank)

Existing logo (if rebranding — describe or paste URL)

Context & constraints

Primary use cases (where will this logo live most?)

Website / digital

Mobile app icon

Business cards

Signage / physical

Merchandise

Social media avatar

Print materials

Must the logo work without color (single color / grayscale)?

Yes, must work in single color

Color only is fine

Competitor logos to differentiate from

Anything the logo must never look like or evoke

Where will this logo appear MOST? (force-rank top 3)

Does the logo need to work on dark AND light backgrounds?

Yes, both

Primarily light backgrounds

Primarily dark backgrounds

Trademark search needed?

Yes

No

Already trademarked

Logo Concept Generator

Brand Color Palette

Psychology-driven color system with accessibility, dark mode, and design tokens

Brand context

Brand name

Industry

Brand personality (5 words)

Target audience

Primary emotion the brand should trigger

Brand positioning (premium, accessible, playful, serious, etc.)

Market context

Top competitors and their brand colors

Colors you love (and why)

Colors you dislike (and why)

Existing brand colors to preserve (if any)

Competitor URLs (for visual color analysis)

Extended requirements

Do you need a data visualization palette?

Yes

No

Do you need a gradient system?

Yes

No

Do you need photography / illustration color guidelines?

Yes

No

Multiple product lines or tiers that need color coding?

Technical requirements

Where will this palette be used?

Website / web app

Mobile app

Print materials

Product packaging

Social media

Physical signage

Accessibility requirements

Need dark mode variant?

Yes

No

Output format

CSS custom properties

Tailwind config

Design tokens (JSON)

Figma-ready

Print (CMYK + Pantone)

Brand Color Palette

Brand Typography System

Font selection, type scale, pairing rules, and responsive typography system

Brand context

Brand name

Industry

Brand personality (5 words)

Target audience

Desired emotional tone of the typography

Typography preferences

Typography styles you admire (brand names or font names)

Typography character

Classic serif

Modern geometric sans

Humanist / warm sans

Editorial / magazine

Big bold display

Monospace / technical

Handwritten / script

Slab serif

Existing fonts to keep (if any)

Budget

Free fonts only (Google Fonts)

Open to paid fonts

Custom / commissioned

Technical context

Primary medium

Website / web app

Mobile app

Print / editorial

Presentations

Product UI

Tech stack (for web font loading)

Performance sensitivity

Performance critical (minimize font files)

Balanced

Visual quality over speed

Content types this typography system must handle

Long-form articles

Data dashboards

Marketing pages

Product UI

Email templates

Slide presentations

Multi-language support needed?

Who will implement this? (affects system complexity)

Design team with full control

Developers

Non-designers in a CMS

Brand Typography System

Website Design Brief

Conversion-focused site architecture, page-by-page specs, and design system

Brand & business

Brand / company name

Industry

What does this business do? (one sentence)

Primary goal of the website

Generate leads

Sell product / SaaS

Build authority / thought leadership

Inform / educate

Drive donations

Recruit / hire

Target audience (who visits this site?)

What should a visitor DO on this site? (primary CTA)

Secondary CTAs

Current state

Current website URL (if exists)

What works on the current site

What doesn't work / what frustrates you

Current analytics data (if available)

Competitor websites to analyze (URLs)

Websites you admire (any industry)

Design direction

Visual tone

Clean / minimal

Bold / high-impact

Warm / approachable

Premium / luxury

Technical / precise

Editorial / storytelling

Playful / creative

Pages needed

Homepage

About

Services / features

Pricing

Blog / resources

Contact

Case studies

Team

FAQ

Landing pages

Dashboard / app

Existing brand assets (logo, colors, fonts — or link to brand guide)

Content ready or needs to be written?

Content exists, needs design

Need content + design

Will write content based on design brief

Social proof available

Client testimonials

Logo bar

Case studies

Stats / metrics

Awards / press

None yet

Integrations needed

CRM

Email marketing

Analytics

Chat / support

Payment

Booking / calendar

SEO priority keywords (if known)

Photography / imagery direction

Technical

Tech stack / platform

Budget range

Mobile priority

Mobile-first

Desktop-first

Equal priority

Accessibility

Timeline

Website Design Brief

AI Video Production

Precision prompt for Claude Code to build Remotion scenes, motion graphics, and product demos in one pass

Video context

Video title / name

Brand / product

What is this video for? (one sentence)

Video category

Product video

Service video

Video type

Product feature demo

Explainer / how-it-works

Marketing / hero video

Onboarding walkthrough

Social media clip

Investor / pitch deck video

Educational / tutorial

Brand story / narrative

Testimonial / case study

Service overview / capabilities

Process walkthrough

Before/after transformation

Target audience

Where will this video live?

Website hero

Feature page embed

YouTube

Twitter/X

Instagram Reels

TikTok

Sales deck embed

Email campaign

Visual references — Loom walkthroughs & screenshots

Show, don't just tell. Loom videos give Claude the full walkthrough context (transcript + visual). Screenshots show exactly what to recreate. The more visual context you provide, the closer the first render lands.

Loom instruction videos

Screenshot file paths or URLs

How should Claude use these references?

Recreate UI exactly as shown

Match the layout / structure

Use as inspiration (not exact)

Extract color palette from screenshots

Follow the walkthrough step-by-step

Recreate the data shown

Additional notes about the references

Technical specs

Framework / tool

Remotion

Motion Canvas

Revideo

FFmpeg pipeline

HTML/CSS animation capture

Resolution

1920x1080

1080x1920 (vertical)

1080x1080 (square)

3840x2160 (4K)

FPS

30

60

24

Target duration (seconds)

Existing project path (if any)

Existing components / infrastructure to reuse

Audio & voiceover

Audio source

Pre-recorded voiceover file

TTS (generate from script)

Music only / no voice

Silent (captions only)

Audio file path (if pre-recorded)

Transcript / narration script

Whisper transcript JSON path (if available)

Captions

Burned-in captions

No captions

Subtitle file (.srt)

Scene-by-scene plan

Define every scene. Each scene = one visual moment synced to narration. The more specific you are here, the closer Claude Code gets to a perfect first build. Include: what the viewer sees, what text appears, what animates, and when.

Scene breakdown

Total scene count

Visual design

Visual style

Product UI recreation

Motion graphics / abstract

Kinetic typography

Screen recording style

Illustrated / icon-driven

Photo/video with overlays

Data visualization

Split screen / comparison

Device mockup showcase

Color palette

Typography

Icon system

Heroicon outline SVGs

Lucide icons

Custom SVGs provided

No icons

Device mockups needed

iPhone frame

MacBook frame

Browser window

iPad frame

No devices

Product UI to recreate (if applicable)

Graphics, diagrams & data visualization

Graphics-first video design. Define every diagram, flowchart, data visualization, and graphic element. These are built as React/SVG components and animated frame-by-frame.

Graphic types used in this video

Flowcharts / process diagrams

Org charts / hierarchy

Timeline / roadmap

Data charts (bar, line, pie)

Comparison tables

Icon grids / feature cards

Network / connection diagrams

Funnel / pipeline

Before/after split

Step-by-step numbered sequence

Metric callouts / KPI cards

Architecture diagrams

Mind map / radial

Ecosystem / stakeholder map

Diagram-by-diagram breakdown

Data visualization specs

Diagram visual style

Clean / corporate (sharp lines, solid fills, sans-serif labels)

Dark tech (dark bg, neon/cyan accents, glow effects)

Soft / editorial (rounded corners, pastel fills, warm tones)

Blueprint / technical (grid bg, monospace text, precise measurements)

Flat / minimalist (no shadows, solid colors, geometric shapes)

Glassmorphism (frosted glass cards, blur, semi-transparent)

Isometric / 3D-ish (angled perspective, depth, layered planes)

Hand-drawn / organic (sketch strokes, imperfect lines, whiteboard feel)

Diagram layout rules

Diagram animation style

Progressive reveal (nodes appear one by one)

Draw-on (lines/shapes animate drawing)

Fade + scale in

Fly in from edges

Typewriter for labels

Highlight / glow active element

Connection lines animate between nodes

Graphic rendering approach

SVG components (sharp at any scale)

Canvas-based (complex particle effects)

CSS/HTML div-based (simple layouts)

Annotation / callout style

Floating labels with leader lines

Tooltip popups

Badge / pill callouts

Arrow + text overlay

Highlight box / spotlight

Number badges with legend

Animation & motion

Animation philosophy

Smooth and professional

Snappy and energetic

Cinematic and dramatic

Minimal and subtle

Playful with bounce

Data-driven / precise

Easing preference

spring() (natural feel)

cubic-bezier (precise)

linear (mechanical)

Mix per scene

Transition style between scenes

Cross-dissolve / fade

Slide / push

Zoom in/out

Morph / transform

Cut (no transition)

Wipe

Varies per scene

Specific animation behaviors

Emotional pacing

Personas & narrative

Who is the protagonist?

Persona definitions (if multi-perspective)

Narrative arc

Problem → Solution → Result

Day in the life (before/after)

Feature walkthrough

Cascade / ripple effect

Comparison (old vs. new)

Story → Reveal

The "aha moment" — what should the viewer feel?

Opening & closing

Opening

Logo intro

Problem statement text

Jump straight into content

Statistics / data hook

Question to viewer

Closing

Logo + tagline

CTA (book demo, sign up)

URL + QR code

Fade to black

Custom closing card

CTA text (if applicable)

Logo file path

Reference & anti-patterns

Anti-patterns — what to never do

Emoji as icons

Generic stock footage feel

Too much text on screen

Cheap template transitions

Robotic / no personality

Over-animated / distracting

Fake data / lorem ipsum

Mismatched aspect ratios

Additional rules / constraints

Build instructions for Claude Code

File structure preference

One file per scene

Single composition file

Scene + shared components

Render command

What does "done" look like?

AI Video Production

Voiceover Script Generator

Brand-locked voiceover scripts powered by humanizer voice configs. Instructions in, on-brand script out.

Brand voice source

The script will be written in this brand's exact voice. Select a brand from the humanizer repo or upload a JSON config. The full voice rules — banned words, required patterns, emotional register, ICP — are injected into the prompt so Claude writes as that brand, not as a generic AI.

Select brand

Fulcrum Collective

Hunhu

Pulse

FindCoach

Find Spiritual Director

Fulcrum International

Or upload brand voice JSON

Brand voice preview (loaded config)

Script brief

Script title / working name

Script purpose

Product demo voiceover

Explainer video narration

Marketing / hero video

Social media clip

Pitch / investor video

Onboarding walkthrough

Case study / testimonial

Educational / tutorial

Service overview

Brand story

Target audience

Target duration

Placement

Topic / subject matter

Key messages (what MUST be communicated)

Your instructions & context

Tell the script what to say, not how to say it. The brand config handles voice. Your job is the content direction — what points to hit, what story to tell, what the viewer should feel. Loom walkthroughs are the best way to give rich context fast.

Loom instruction videos

Written instructions / creative direction

Reference material (URLs, docs, notes)

Existing copy to draw from

Script structure & tone

Narrative arc

Problem → Solution → Result

Day in the life (before/after)

Feature walkthrough

Ripple effect / cascade

Story → Reveal

Question → Answer

Testimonial-driven

Emotional progression

Pacing notes

Slow build, fast payoff

Conversational throughout

Punchy and fast

Cinematic / dramatic pauses

Match to scene cuts

Speaker perspective

Brand voice (we/our)

Narrator (third person)

Character/persona (first person)

Direct address (you/your)

Output format

Script format

Scene-by-scene with timestamps

Continuous narration (no scene breaks)

Two-column (audio | visual)

Include visual direction notes

Include on-screen text callouts

CTA / closing line

Additional constraints

Voiceover Script Generator