AERIX®
Free pack · Prompts

Every prompt behind the page and the drone.

The starter prompt for a page like AERIX, the four Higgsfield prompts for the worlds with their settings and cost, and every message I sent GPT-6.2 Astra to build RILL in Blender.

01 · Start a page like this

Starter prompt

It lays out the whole structure. Give it your own model and change the sections to fit your product, then add effects one at a time from the vocabulary sheet.

Starter prompt
Build a scroll-driven product landing page in Three.js for my 3D drone (GLB attached, with the inside parts modeled).

Concept: the whole page is one takeoff. As the visitor scrolls down, the drone rises.

Sections, in order:
1. Loader: the drone sits on a launch platform in the dark, inside the hero. The lights come up, rim light first, then the key light, with a small counter to 100.
2. Hero: a 3D Rolodex title that flips through three words, then breaks into particles as the scroll starts.
3. Ascent: the drone lifts off. The rotors blur into spinning discs and the drone banks a little as it climbs. Three short cards that scan in from top to bottom.
4. Exploded view: the drone opens into its layers, and each part gets a numbered pin that matches its label.
5. Close studies: the battery, the flight computer and the camera, each with a wireframe scan sweeping through it.
6. Through the lens: the camera flies into the drone's lens and opens onto a city at night.
7. Flight worlds: views from the drone (mountains, forest, coast, city) dissolving into each other, each one a short video, and the scroll waits for each video to finish.
8. Landing: the platform comes back into view and the drone lands where it started, then a finish picker with five colours.

Style: a high-tech product. A wide, squared display font, a mono for small labels, deep navy with one cool blue accent. Labels decode letter by letter, never soft fades.

Keep one camera and one model the whole way, smooth scrolling, a progress rail on the right, and make it work on a phone.
02 · The worlds behind the drone

Four clips on Higgsfield

Each world is a 5 second text-to-video clip made with Seedance 2.5 on Higgsfield, then upscaled to 4K with Topaz on Higgsfield. Naming a real place made the shots far more believable. The four clips cost 140 credits, plus 70 for two Times Square retakes and 32 for the 4K upscales. The clips themselves stay with the video, so the page in this pack uses the September stills. Paste these into Higgsfield to make your own.

World 01 · Glacial heights

Moraine Lake, Banff, at sunrise

Seedance 2.5Text to video720p16:95 sAudio off35 credits
Topaz Video upscale2160p (4K)8 credits

What I asked for: more mountainous, like the original image, near Moraine Lake in Banff.

Higgsfield prompt
Real aerial drone footage, one continuous shot, no cuts. Story: sunrise in the Canadian Rockies over a small glacial lake of vivid turquoise water, ringed by a wall of jagged snow-capped limestone peaks, like Moraine Lake in Banff National Park. Camera: a cinema drone about 300 metres up glides slowly forward over the lake towards the wall of peaks, rising very gently so more and more summits appear behind each other, gimbal-smooth, no shake, no zoom, no rotation. Life in the scene: the first pink and gold alpenglow lights the summits while the lake and the dark spruce forest on its shores stay in cool blue shadow, thin mist lifts off the water, small patches of snow and scree slopes run down to the shore, glacier ice hangs between the peaks. Look: true documentary nature footage shot on a full-frame cinema camera at 24 frames per second, crisp mountain air, enormous real scale with atmospheric haze between the ranges, natural colour, no oversaturation, no CGI look. Locks: same sunrise light throughout, no text or logos, no people, no boats, no buildings, no drone, aircraft or birds in frame.
World 02 · Into the evergreen

A Canadian forest path in autumn

Seedance 2.5Text to video720p16:95 sAudio off35 credits
Topaz Video upscale2160p (4K)8 credits

What I asked for: a nice path between trees, autumn colours, somewhere in Canada.

Higgsfield prompt
Real aerial drone footage, one continuous shot, no cuts. Story: a peak autumn morning in a Canadian forest. A narrow dirt path winds through a dense mix of dark green spruce and pine and blazing autumn trees, golden aspens and birches, orange and deep red maples. Camera: a cinema drone about 40 metres above the treetops glides slowly forward following the winding path as it curves away into the forest, gimbal-smooth, no shake, no zoom, no rotation. Life in the scene: soft low morning sun from the side rakes across the canopy and makes the yellow and red leaves glow, a few leaves drift down onto the path, thin morning mist sits in the hollows, the forest rolls on over gentle hills to the horizon. Look: true documentary nature footage shot on a full-frame cinema camera at 24 frames per second, rich but natural autumn colour, fine detail in every tree, real haze in the distance, no oversaturation, no CGI look. Locks: same morning light throughout, no text or logos, no people, no cars, no drone, aircraft or birds in frame.
World 03 · Somewhere beyond

A lagoon resort at sunset, Bora Bora style

Seedance 2.5Text to video720p16:95 sAudio off35 credits
Topaz Video upscale2160p (4K)8 credits

What I asked for: a tropical resort beach like Bora Bora or the Maldives, clear water, palm trees, a sunset. The prompt also names what was wrong last time: no dark patches in the water.

Higgsfield prompt
Real aerial drone footage, one continuous shot, no cuts. Story: a luxury island resort in a tropical lagoon at golden hour just before sunset, inspired by Bora Bora and the Maldives. Camera: a cinema drone about 80 metres up glides slowly forward along a curving white sand beach lined with leaning coconut palms, over crystal-clear shallow water towards a row of thatched overwater villas on stilts and a green volcanic peak on the horizon, gimbal-smooth, no shake, no zoom, no rotation. Life in the scene: the water is glass-clear, pale turquoise over white sand in the shallows deepening to sapphire blue further out, no rocks, seaweed or dark patches, gentle small waves fold onto the sand, the palms sway slightly in a warm breeze, the low sun turns the sky peach and gold and lays a warm glitter path on the lagoon. Look: true documentary travel footage shot on a full-frame cinema camera at 24 frames per second, warm vacation light, clean natural colour, real haze over the horizon, no oversaturation, no CGI look. Locks: same golden-hour light throughout, no text, signs or logos, no people close up, no boats moving fast, no drone, aircraft or birds in frame.
World 04 · Above the everyday

Manhattan at night, above Times Square

Seedance 2.5Text to video720p16:95 sAudio off35 credits
Topaz Video upscale2160p (4K)8 credits

What I asked for: New York at night, Times Square. The first take had a real-looking rooftop sign and phone ads, so this retake goes higher and locks out every letter and logo.

Higgsfield prompt
Real aerial drone footage, one continuous shot, no cuts. Story: New York City at night seen from high above Midtown Manhattan, the glowing canyon of Times Square below. Camera: a cinema drone about 300 metres up, well above the rooftops, glides slowly forward high over the avenue, looking down the long bright street towards the dense lit skyline and the dark rivers beyond, gimbal-smooth, no shake, no zoom, no rotation. Life in the scene: the street far below glows with a river of coloured light from the building-sized screens, rivers of tiny yellow taxis and red tail lights flow along the avenues, thousands of office windows glow warm and cool, thin steam drifts between towers, the deep blue night sky holds a soft city glow at the horizon. Look: true documentary city footage shot on a full-frame cinema camera at 24 frames per second, rich night contrast, real light bloom and depth, natural colour, no oversaturation, no CGI look. Locks: every screen and sign shows only soft abstract colour gradients and light, absolutely no letters, words, logos, faces, products or brand names anywhere in the frame, rooftop signs are blank, same night light throughout, no people close up, no drone, aircraft or birds in frame.
03 · The drone · GPT-6.2 Astra in Codex

Building RILL, every message

The project brief first, then every message I sent while it built the outside of the drone, version by version, from the grey blockout to V14c. The model and the Blender scripts it wrote are in the model folder. The real drone it was measured from isn't named here, the same as in the video.

01Project brief
Prompt to GPT-6.2 Astra in Codex
I want to build a new 3D drone in Blender with you, structure first.

Two months ago I built a drone in Blender with GPT-6 Astra, starting from a GPT Image reference. It looked good, but the image wasn't a real product, so the arms, hinges and legs never quite fit, and a lot of versions went into fixing that. This time I want to try it the other way round. We start from the real dimensions of an existing drone, build a grey blockout that actually works, and only then design the look on top of it. I'm recording this for a YouTube video about GPT-6.2 Astra, so every step has to be visible and saved.

## Rules
- Work only in this folder. Don't open or reuse any of my older drone projects. This one starts fresh.
- Blender 5.2.0 LTS is at /Applications/Blender.app. Drive it in the background with Python scripts. Keep every script in `scripts/` so the model can be rebuilt.
- Every version is a new file (`blender/drone-v01.blend`, `v02`, ...). Never overwrite a version. Render the same angles with the same lighting every time, so before and after line up.
- At each ⏸ review point, stop and wait for me. Give me a short summary and tell me what to look at.
- The final drone must not look like the real product. Use only its dimensions, proportions and the way it folds. No brand, no logo, no copied design details. Give it its own one-word name, used only as a small logo on the shell.
- Photos of the real product stay in `references/real/` for your own use. They won't be shown in the video.

## Stage 1: find the real structure
- Find 2 or 3 real foldable camera drones with a 3-axis gimbal and official published dimensions: folded and unfolded size (L × W × H), diagonal wheelbase, propeller diameter and weight. Use the manufacturers' spec pages, and a teardown if one exists, so we know the inside layout too.
- Save `references/spec-sheet.md` with a table and the source links, plus a few photos per product (top, side, front, folded).
- Recommend one and tell me why (clear dimensions, a good folding mechanism, enough views to model from).

⏸ Review 1: I pick the base product.

## Stage 2: grey blockout (V01)
- Build it at real scale, in meters, from the chosen product's numbers. Grey clay only, no design detail yet.
- Separate named objects with correct pivots: body, four arms, four motors, propellers (two blades each), gimbal and camera, landing legs, battery bay.
- Folding must really work. Make an unfolded and a folded pose with the hinges where the real ones are, and get the folded size close to the real folded size. Check that no parts pass through each other when folded.
- Render front, side, top, back and three-quarter at 1920 × 1080 (orthographic for front, side and top), unfolded and folded, in a neutral studio.
- Make a table of your measured dimensions against the real spec, with the difference in %.
- Export a GLB and build a simple local Three.js viewer (orbit, zoom, version selector, fold and unfold) on a free port, so I can inspect it and send you screenshots.

⏸ Review 2: I check the proportions and the folding before any styling.

## Stage 3: design on top of the blockout
- Render the blockout's three-quarter view in a clean studio.
- Use image generation to restyle that render into three different design directions, image to image. Each one keeps the exact silhouette, camera angle, arm and hinge positions, propeller size and gimbal position. Only the surfaces change: the shell's shape language, materials, colours and details. Realistic premium product photography, the whole drone in frame and not cropped, and no text except the small one-word logo.
- Save them in `concepts/` with the exact prompts you used.

⏸ Review 3: I pick one direction.

- Then restyle the front, side, top and back blockout renders the same way for the chosen direction, one view at a time, so every view is locked to the same geometry and the views agree with each other. These become the modelling references.

## Stage 4: the detailed model
- Model the chosen design on top of the blockout, version by version (V02, V03, ...). Keep V01's proportions and folding.
- Work in this order: shell surfaces and seams, arms and hinges, motors and propellers, gimbal and lens (real depth in the glass), legs, then materials and small details (bevels, screws, vents, sensor windows).
- Compare every version with the concept views from the same angle, side by side, and fix the biggest difference first.
- Render the same five angles for every version, plus a close-up of what changed.

⏸ Review 4 after each version. I'll give feedback with screenshots.

## The teach folder (important)
This build is going into a YouTube video and a course, so record everything in `teach/` as it happens, not at the end:
- `teach/session-log.md`: every message I send, word for word, with the time. Under it, a short summary of what you did, what came back and how long it took. Put the model you're running on at the top (set in Codex as GPT-6.2 Astra).
- `teach/journal.md`: the moments worth teaching. Why this product, the techniques (how the folding pivots were set up, how image to image kept the geometry), problems and how they were fixed, and turning points.
- `teach/decisions.md`: a table of every decision, who suggested it (me or you) and who decided.
- `teach/timeline.md`: start and end time of each stage and each version.
- `teach/shots/`: before and after images for every version, same angles, named by version.
- `teach/prompts/`: every image generation prompt, with its input image and the result.

Start with Stage 1.
02Review 1 decision and Stage 2 brief
Prompt to GPT-6.2 Astra in Codex
Let’s go with the reference drone. Start Stage 2, build the V01 grey blockout, and stop at Review 2 so I can check the proportions and folding in the viewer.
03Review 2 reference question
Prompt to GPT-6.2 Astra in Codex
Okay, do you have the image reference of the actual model that you get inspired from?
04Review 2 feedback
Prompt to GPT-6.2 Astra in Codex
Okay, what are the next step? It looks good, the gray version looks good
05Review 3 choice
Prompt to GPT-6.2 Astra in Codex
Let’s go with Basalt. Use the V01 renders to make the front, side, top and back references, one view at a time. Keep the proportions and folding geometry the same.
06V02 request
Prompt to GPT-6.2 Astra in Codex
Looks good. Start V02 with the Basalt shell surfaces and seams. Keep V01’s proportions and folding, compare the renders side by side with the references, and stop at Review 4 so I can check it in the viewer.
07V03 request
Prompt to GPT-6.2 Astra in Codex
V02 looks good. Start V03 with the Basalt arms and hinges. Keep the V01 pivot positions and folding clearances, compare the renders side by side with the references, and stop at Review 4 so I can check it in the viewer.
08V04 request
Prompt to GPT-6.2 Astra in Codex
Okay, so far so good. The drone looks good, similar to the image reference, but make sure that there's no part floating. I know it's still in the early phase, but just a reminder and make sure the body resemble the reference because when I look from the top view, it feels thin and fragile. So just double check that and. But I know it's still not the final phase. So maybe it will get fixed later on. But just make sure so you know. So if those feedback are for later, you can go ahead with V04
09V05 request
Prompt to GPT-6.2 Astra in Codex
V04 looks good. Go ahead with V05 on the Basalt gimbal and camera lens. Give the glass real depth, keep the gimbal connected and clear through the fold, compare it with the references, and stop at Review 4 so I can check it in the viewer.
10V05 proportion question
Prompt to GPT-6.2 Astra in Codex
Okay, I just want to know right now how accurate do you think the 3D model compares to the original image reference? When I look from the top, I feel the arm and the forearm feels like super fragile. I'm not sure if it's was designed like that. So yeah, just confirm that
11V06 request
Prompt to GPT-6.2 Astra in Codex
Okay, let’s make the front and rear arms a little fuller in V06 so they look closer to the Basalt reference. Keep the pivots and folding clearances, compare the top and three-quarter views side by side, and stop at Review 4.
12V06 comparison with the reference drone
Prompt to GPT-6.2 Astra in Codex
So if you compare to the actual model, the reference drone, how does the arm compare from the original product compared to your modeling?
13V07 request
Prompt to GPT-6.2 Astra in Codex
Okay, let’s make the V07 arms closer to the reference drone, around 9 mm at midspan, with fuller rear shoulders and a little flare into the motors. Keep the Basalt look, pivots and folding clearances. Compare the top view and stop at Review 4.
14V07 viewer contrast and overhead photo
Prompt to GPT-6.2 Astra in Codex
Okay, do you have a, some shot of the actual the reference drone? I just want to see from up top how it compare. And also can you for the viewer, can you make it the background a little bit darker? Because right now the blades is almost blending into the background. So it's hard to visualize.
15V08 reference drone remodel
Prompt to GPT-6.2 Astra in Codex
Yeah, so there's something I don't really like about our drone. I, okay, so I think you use actual dimension but okay, I think the dimensions are good, but here's, I thought you were gonna try to replicate the actual model. Because when I look at the image, it feels like a real drone. It's small, it's mini but it's compact. The body, I never thought our body was like that compared to the original one. Right now our V7 version looks like a remote control, the body. And I think what I like about the reference drone because it feels small, compact, but the arm is proportional to its body. So it feels like robust. But ours feels skinny, long arm, long legs. So I think we're, we're getting on the wrong path . So what I want from here is to you to remodel, try to reproduce the actual the reference model. But we're gonna just change the brand. And it's for conceptual. Try to reproduce the same blades, the same arm, same body, same curve. So we need a remodeling because I think at the end even if you put the texture, I don't think it looks like a real drone. It feels too skinny. So work on it for V08. And try to replicate that closely Because right now I don't like the shape of our body. It looks like a, I don't know. It feels weird. It looks like a remote control
16V08 Review 4 feedback
Prompt to GPT-6.2 Astra in Codex
Okay, this is much better. Love it. Feels like a real drone now. So what is the next step?
17V09 landing gear
Prompt to GPT-6.2 Astra in Codex
ok proceed
18V10 · Camera centering and final finish direction
Prompt to GPT-6.2 Astra in Codex
Okay, this is good. I like how it feel compact, solid even for a mini. So I think the only thing I seen so far is this not properly centered. But okay, so what is the next step? Make sure that at the end result we have something that looks, it feels like a real product. When we look at it, you hesitate not knowing if it's a true product or just a model. So the texture, the lighting, the polishing should be super premium
19V11 · Materials
Prompt to GPT-6.2 Astra in Codex
Okay, proceed with version 11, the material path
20Between V11 and V12 · Timing of final polish
Prompt to GPT-6.2 Astra in Codex
Okay, how many stages is there left for before we reach the final polish?
21V12 · Side vents and battery hatch
Prompt to GPT-6.2 Astra in Codex
ok proceed with v12
22V13 · Camera side covers and front arm roots
Prompt to GPT-6.2 Astra in Codex
Okay, here look at the main camera. There's an overlapping of the two round, or circle on each side. And it feels the material doesn't look the same on each side. So fix that overlapping and the material texture. And on the second screenshot, for the front arm, just check the connection. It feels a little bit weird. Try to make one small piece So fix them on the, on front of left and right
23Between V13 and V14 · Lighting review
Prompt to GPT-6.2 Astra in Codex
Okay, what is the next step?
24V14 · Studio lighting
Prompt to GPT-6.2 Astra in Codex
Okay, perfect, proceed with the version 14 for the studio lighting
25V14a · Front edge polish
Prompt to GPT-6.2 Astra in Codex
Okay, still in version 14, I think it looks super nice. Everything is clean. Try just to make sure there's no rough edges in the front end because this part is important. So you can see, just try to make everything sharper. And I just want to know the line on the left, you can see it feels a little bit like blocky. I don't know if it's because of the reference from the original model, but maybe try to make it less blocky like that straight edges. Maybe a slight polishing on the each edge. But that looks natural and professional. Because when you look at it now from screenshot 2 and 3, it feels a little bit too straight line and hard edges
26V14b · Sidewall finish
Prompt to GPT-6.2 Astra in Codex
The each side feels a little bit unfinished. Can you do a final pass, try to make it a little bit more smoother so we don't like see those, I don't know how it's called, but it feels unfinished and unpolished
27V14c · Both rear hatch corners
Prompt to GPT-6.2 Astra in Codex
Make sure to do that on this, on both sides