Cineview case
Two landing-page conversations
Both AIs had read Cineview’s design skill and then talked with a user to make a landing page. The wedding invitation is DeepSeek’s conversation; the motorcycle page is Claude Opus’s.
These conversations were originally in Chinese; the English text is a translation. The dialogue is otherwise as it happened. The grey notes were added here: they say what the AI did with tools between messages, or give background. DeepSeek asked with multiple-choice forms, listed as it sent them, with the user’s pick marked. The recap at the start of each moto round is folded; open it for the full list.
DeepSeek wrote this
Wedding invitation
- AI
- DeepSeek, model ID deepseek-v4.1-flash, high reasoning effort, running in the DeepSeek Harness web app.
- User
- A real person, talking directly, with no setup written beforehand. The first message was a repo link and “help me make a landing page”; they never asked for the skill to be followed.
- Skill
- This harness’s skill list did not include cineview-design. The AI cloned the repo itself and read the skill files as ordinary files with sed.
- Global rules
- The user had given DeepSeek Harness a global rule set: before acting, write one line of a goal and the smallest list of files to read; stop once there is enough information; use the fewest steps; never delete, only move to the Trash (rule A2). The goal lines and the “按 A2” in DeepSeek’s messages come from it.
- Time
- 2026-10-28, 14:22 to 14:59
- Page
- /cases/wedding/
User14:22
https://github.com/AlienMu/cineview, take a look at this site and make me a landing page
DeepSeek14:22
Let me look at what this project is first.
The AI looked at the repo with gh, shallow-cloned it, and read the README, the homepage index.html, and the skill’s SKILL.md and conversation.md.
DeepSeek14:23
Multiple choice
Who is this landing page for?
I looked at the repo: Cineview is a landing-page framework of plain HTML plus custom elements, and the site itself is a multi-scene page that scrolls and drags. Who is the page you want to make for?
- For Cineview itself: redo the homepage (recommended)Picked by the userKeep the framework and the storyboard approach, change the visuals and the story, and produce an index.html that runs as it is.
- For my own product or projectTell me what the product is, what the reader should remember, and what material you have; I'll use the same storyboard method.
- Just a general template or sample pageNot tied to any business: a multi-scene landing-page template whose copy you can change and use.
User14:24
Who is this landing page for? For Cineview itself: redo the homepage (recommended)
The AI then read the homepage’s scene structure and the skill’s references.md, styles.md and framework.md, looked at the repo’s two videos with ffprobe, and pulled two frames to look at.
DeepSeek14:25
I've been through the repo: the site is a nine-scene scroll page with an editorial-paper feel and film, Fraunces and Noto Serif, a cream ground with clay accents, using cv-scene and cv-zone, plus cv-stack, track="x", and a projector drawn on a Canvas.
【Goal】Follow the skill's order: settle the direction and the scenes first, then write the storyboard, and only write code once you confirm.
【Smallest file list I plan to read】Already read; nothing more for now.
Multiple choice, 2 questions
1/2 · Direction
Which visual direction? (I recommend A: the current site is already B, so a remake should move away from it, and a dark ground shows the frame-by-frame footage better)
- A. Night screening (recommended)Picked by the user5 acts, near-black ground plus a single beam of light. Fits the film/storyboard theme, sets itself apart from the cream homepage, and can show a theme change and drag mode.
- B. Paper editing table4 acts, large serif type plus fine line drawings, quiet and more work, like the opening of a magazine. The same mood as the current site: safe but repetitive.
- C. Clapperboard (poster style)5 acts, big type on black, a clapperboard and numbered slates, one tap per act. The strongest opening feeling, but it can overpower the content.
2/2 · Delivery
Where do the files go, and how do you run them?
- A standalone set of files (recommended)Picked by the userCreate a landing/ directory in the workspace: index.html + CSS + a little JS, with cineview@2 from npm/cdn at runtime and no build step.
- Replace the homepage in the repoReplace site/public/index.html directly; you'd have to install dependencies and run vite to preview.
User14:25
Direction: A. Night screening (recommended)
Delivery: A standalone set of files (recommended)
DeepSeek14:26
Multiple choice
Storyboard check
Here is the storyboard (direction: night screening, near-black ground plus one warm beam; headings in Fraunces + Noto Serif SC, code and timecodes monospaced). Once you confirm, I'll write the files:
| # | Scene | Says one thing | What the reader sees | Mode | Material |
|---|---|---|---|---|---|
| 0 | Top bar | Navigation | Brand, docs, GitHub, language buttons | Fixed | None |
| 1 | Opening | Write a landing page with a storyboard | A beam of projector light sweeps across black, two lines of large type rise out of it, slate number 01 | Ordinary scene, plays on enter | None (CSS beam) |
| 2 | How a page is born | A scene is a timeline | A page wireframe on the left; on scroll the title, subline, button and image come on one after another, with a timeline filling in below | Held zone, scroll steps the timeline | Wireframe drawn as SVG |
| 3 | Film strip | The picture can step frame by frame with scroll | A vertical film strip with a night-ride clip in the middle frame; scrolling steps it forward and back | Held zone + cv-video | media/ride.mp4 + poster |
| 4 | Lights up | Scroll and drag, the same scene | The whole page turns to cream paper, two cards: scroll on the left, drag on the right, cards stack upward | Held zone + card stack | None |
| 5 | Closing | Start using it | The lights dim again, one install command, two buttons, a footer | Ordinary scene | None |
Material list: everything comes from the repo (ride.mp4 portrait 10s, video.mp4 landscape 10s as the background light, ride-poster.jpg and so on). You don't need to send anything.
- That's the one, start writing (recommended)Build from the storyboard below, using the two videos and the poster already in the repo.
- The direction is fine, but change one thingFor example drop an act, open in drag mode, or skip the lights-up moment. Tell me what to change.
- Too many acts, cut it to 4I'll swap the order or the content of acts 3 and 4 to tighten the pace.
User14:26
The user cancelled this question without choosing
DeepSeek14:26
Since you skipped the check, I'll start on what's already settled: night screening, 6 scenes (top bar included), one standalone set of files.
The AI created a landing/ directory and prepared to download the cineview@2 package.
User14:26
Do you know what I'm trying to make?
DeepSeek14:27
Honestly, I'm not sure right now, and I've been going on my own assumptions, so let me stop and lay it out.
What I have confirmed: you sent the Cineview repo, which is building a landing-page framework of plain HTML plus cv-* custom elements, and the site itself is a multi-scene page that scrolls and drags. I asked "who is this landing page for" and you picked "for Cineview itself: redo the homepage", so I understood the task as: make a new homepage landing page for Cineview, with the cv-scene set, separate from the repo, a new landing/ under the workspace, visual direction night screening.
What I'm guessing: whether you want two languages, which of the nine scenes of the original site to keep (the design skill, the AI discussion, the Canvas extension, the drag demo), or whether you really just want a sample page "that looks like this", with the content swapped out yourself.
Also, last round I had created the directory and was preparing to download the package before you confirmed the storyboard. That step was too fast.
So, one question: do you want "a new version of the Cineview homepage", or "a landing page built with this framework, where I fill in Cineview's content but the structure can be reused"? Tell me about Chinese and English too, and I'll go from there.
User14:27
I want to make a piece of content with this framework
DeepSeek14:27
Right, so this isn't a remake of the Cineview homepage, but one page for your own content, built with Cineview. One more thing to settle and I'll start:
Multiple choice
What is this page about?
What content do you want to make? (Pick the closest, or just tell me what it's about)
- Product page (recommended, easiest to fit)For example an introduction to a product, tool or app: what it solves, a few core features, one screenshot or a short clip, and how to start using it.
- Narrative or story pageTell one thing, one person or one project as a story, read in order, with images and text alternating.
- Long read or report pageA report, a long article or a proposal; the point is that a reader can get through it and see the structure.
- Event pagePicked by the userAn event, launch, wedding or exhibition; the time, the place and signing up matter most.
User14:28
What is this page about? Event page
DeepSeek14:28
Multiple choice
What is the event?
What exactly is the event? (Name, time, place, what happens, what you want the reader to do afterwards)
If you just want a sample event page you can run and edit, say so too.
- I'll give you the detailsPicked by the userTell me the real name, time, place and sign-up link; if you don't have them I'll use placeholder copy for you to change later.
- Make a sample first (recommended)For example "city night ride" or "an indie short film night": I'll make an event page that looks real and works, and you change the name and the time.
User14:28
What is the event? I'll give you the details
DeepSeek14:28
Good. Send me the event details. These are the items; write down whatever you know and I'll mark what's missing and ask again:
- Event name: what it's called, and whether it has an English name.
- Time and place: which day, what time, which city, the exact address.
- What the event is: one or two sentences on what happens, for example a screening, a show, a market, a talk.
- Programme: is there a schedule or parts, for example doors at 19:00, screening at 19:30, chat at 21:00.
- What you want the reader to do afterwards: sign up, buy a ticket, join a group; is there a link.
- Who runs it: the organiser's name, a logo, photos from before, anything; say if there isn't one.
- Material: any photos, posters or clips, and where the files are; if there are none I'll use line drawings and type.
- Language: Chinese only, or Chinese and English.
Once I have these I'll give you a storyboard first, as before, with 5 or 6 scenes and what each one shows; I'll write the code after you confirm.
User14:29
1. Our wedding. 2. Chongqing, 1029, Jiefangbei. 3. Getting married. 4. Morning to noon. 5. Give flowers. 6. Us. 7. None. 8. Chinese
DeepSeek14:29
Got it: a wedding invitation page, 29 October at Jiefangbei in Chongqing, from morning to noon, and what you want the reader to do is "give flowers". There's no material, so I'll draw it.
Before I write code I need to settle three things; a few short answers are enough:
Multiple choice, 3 questions
1/3 · Flowers as a wedding gift
What does "give flowers" mean exactly? It decides whether the last act has a button.
- Ask guests to give flowers as a wedding gift (flowers are the theme)Picked by the userThe last act has a "give flowers" button; it opens flower choices, an address, or a place to leave a message. Flowers are the main visual of the whole page too.
- Just one line: "bring a single flower with you"No button, just a line in the copy: "just bring a single flower with you". The invitation, the time and the place carry the page.
- Something else, I'll explainTell me how giving flowers actually works (a link, WeChat, on the day) and I'll put it in word for word.
2/3 · Copy details
Do you have the names, the exact time, where at Jiefangbei, and preferred colours for guests to wear?
- I'll send them nowThe two names, the exact hours, where at Jiefangbei, and whether there's a colour to wear.
- Use placeholders, I'll change them later (recommended)Picked by the userI'll write "us", two placeholder names, "10:00 to 12:00 in the morning", "Jiefangbei"; you change the words later.
3/3 · Look
Pick a visual direction?
- A. Warm paper and flowering branches (recommended)Picked by the userCream paper ground, a hand-drawn flowering branch growing slowly, large serif type. Warm and quiet, right for a morning wedding.
- B. Black and gold invitationA dark ground with a little gold, like a dinner invitation. But your wedding is in the morning, so it would sit slightly off.
- C. Plain white minimalAlmost pure white, fine black type, plenty of space, the flower only as a small mark. Very clean, but there is less to do with scrolling.
User14:30
Flowers as a wedding gift: Ask guests to give flowers as a wedding gift (flowers are the theme)
Copy details: Use placeholders, I'll change them later (recommended)
Look: A. Warm paper and flowering branches (recommended)
Building the page
DeepSeek14:30
【Goal】Build a wedding-invitation-plus-flowers landing page with Cineview, in the warm paper and branch direction, in landing/.
【Smallest file list】First settle how to get the runtime, that is whether cineview@2's dist can be put locally, then write the page straight away.
The AI downloaded the cineview@2 runtime from jsDelivr into landing/vendor/, read the skill’s line-art.md and type.md, and looked again at the homepage home.css and the runtime code for pausing a scene.
DeepSeek14:36
【Goal】Start writing the files now: landing/index.html, landing/style.css, landing/page.js, with the runtime from the local vendor/.
【Smallest file list】Nothing more to read; write.
The AI wrote index.html, style.css and page.js, started a local server, and checked the page with Playwright at desktop and phone widths.
DeepSeek14:40
A few things need fixing: on mobile the title is squeezed and broken because hero-copy has a capped width, the time column is too narrow and cuts off "09:30", and the top bar is still cream on the dark act.
The AI changed the styles, index.html and page.js, then ran more screenshot checks, including other widths and with JS off. It compressed its context once along the way.
User14:54
Have a look, the page throws an error when I open it
DeepSeek14:54
【Goal】Reproduce "the page throws an error when opened": my tests so far all went over http, so the likeliest trigger is opening it by double-clicking, over file://. Check that one assumption first.
The AI opened the page over file://, reproduced the error, bundled the runtime into one plain script with esbuild and updated the references, then tested over both file:// and http. It tried to move the old files to the Trash, the sandbox refused, and it moved them to vendor/_esm-unused/ instead.
DeepSeek14:59
Fixed. The error you hit comes from opening the file by double-clicking, over file://: the page loads <script type="module">, and the browser blocks it before running a single line, so the console shows these two lines in red:
Access to script at 'file:///…/vendor/cineview.js' from origin 'null' has been blocked by CORS policy
Access to script at 'file:///…/page.js' from origin 'null' has been blocked by CORS policy
Failed to load resource: net::ERR_FAILED
Module scripts are always blocked under file://. It has nothing to do with the framework; it is the browser's protocol rule.
The fix
Bundle the engine from several ESM files (cineview.js plus 8 files under chunks/) into one classic IIFE script with esbuild, and load it with <script defer>:
- New
vendor/cineview.bundle.js(155.7kb, all the dynamic chunks inside) index.htmlnow loads<script defer src="vendor/cineview.bundle.js"></script>, and page.js inindex.htmldropstype="module"too- The old ESM files moved to
vendor/_esm-unused/; nothing was deleted (to really delete them, move them to the Trash yourself, per A2)
Checks
| How it was opened | Result |
|---|---|
Double-click, file:// |
No console or request errors; scrolled to the end the theme switches to dusk and the progress bar reads 100% |
http://127.0.0.1:4173 |
Same, no errors |
| 390px mobile | No horizontal overflow, no errors |
Both ways scrolled the whole 8900px page, and the dark closing act looks right in the screenshots.
One side effect: from now on, changing the engine source under vendor/ needs a new bundle. Don't edit the files in _esm-unused/; they are no longer referenced.
The page later went to /cases/wedding/.
Opus wrote this
Motorcycle intro page
- AI
- Claude Opus, model ID claude-opus-5.5, running as a sub-agent inside Claude Code.
- User
- Played by the AI running the test (also Claude Opus) from a setup written beforehand. It answered only what it was asked, briefly.
- User setup
- Marketing lead at a small motorcycle brand, Tulan. The new bike is a 400cc retro street bike, on sale next month, from ¥29,800. The readers are 25 to 35 and buying their first bigger bike; the page should leave them with easy to ride, good looking, not expensive. Material: six studio photos, one 30-second promo, a spec sheet; no user reviews. Brand colours dark green and off-white; Chinese first, English too; phone first. Occasionally a vague answer, occasionally “you decide”.
- Skill
- The test asked the AI to read only the skill in skills/cineview-design/ and to talk it through with the user, without opening the homepage source, the earlier test pages or the review notes. No files until the storyboard and material list were settled.
- Time
- 2026-10-27
- Page
- /cases/moto/
User (AI role-play)
Make a motorcycle intro page
OpusRound 1
Before I start, I'll ask one question at a time, each with my suggestion; reply "yes" and we go with it. If you'd rather not, just say "you decide" and I'll lay out the whole plan for you to confirm.
Question 1: what is this page for, and who reads it?
I suggest A. Introducing one model: for people thinking of buying, so they warm to the bike and then book a test ride or find a dealer. That's what most motorcycle intro pages are for.
Two other possibilities:
- B. A page for a shop, rental or customiser: for riders nearby, to show which bikes you have, what you offer, and where you are.
- C. The story of one bike: your own bike, a build, or where a classic model came from. For friends and the riding circle; the details and the story matter, and there's no purchase.
Reply "yes", or pick B or C, or just tell me about your case. If you already have photos, video, specs or copy, send them along and I'll look at the material before asking more.
User (AI role-play)
A. We're Tulan Motorcycles, the new bike launches next month, a 400cc retro street bike. It's mainly for people 25 to 35 who are moving up to a bigger bike for the first time.
OpusRound 2
Decided (1 item)
- Purpose and reader: an intro page for Tulan's new 400cc retro street bike, on sale next month, for readers aged 25 to 35 buying their first bigger bike.
Question 2: what should the reader remember, and then do?
I suggest A. Remember "this is a good first bigger bike", then book a test ride. What people moving up worry about most is "can I handle it". The page takes that worry away first, then invites them to ride it once themselves.
Other choices:
- B. Remember how it looks (retro design and finish), then leave a phone number for launch news. Fits when looks are the main selling point and the price and specs aren't public yet.
- C. Remember the launch price and the launch offer, then pay a deposit. Fits when orders open before launch.
Reply "yes", or pick B or C. You can mix them too, for example take A's point and end with C's pre-order button.
User (AI role-play)
I want them to remember easy to ride, good looking, not expensive. The price starts at 29,800. At the end, just get them to book a test ride.
OpusRound 3
Decided (2 items)
- Purpose and reader: an intro page for Tulan's new 400cc retro street bike, on sale next month, for readers aged 25 to 35 buying their first bigger bike.
- What to remember, what to do: easy to ride, good looking, not expensive (from ¥29,800); after reading, book a test ride.
Question 3: what material do you have?
Each selling point is best backed by material. I'd prepare it per point:
- Easy to ride: a 5 to 15 second riding clip, no sound needed. The clip can play with the scroll: scroll down and the bike moves forward, scroll back and it reverses. Add the numbers a beginner cares about, such as seat height and curb weight.
- Good looking: one full side-on shot plus 3 to 6 detail close-ups, for example the tank, the headlight, the instruments, the seat. Send any location shots or other colourways too.
- Not expensive: you already have from ¥29,800. If there are versions, instalments or launch benefits, tell me.
- Other: the model name, and a logo (SVG is best).
Send the original files; I'll do the cropping and compression. Missing some for now is fine, just tell me. For example, if the clip can't be shot before launch, "easy to ride" can use riding photos and the specs for now, and the clip goes in later.
User (AI role-play)
Six studio photos: side, front 45°, instruments, tank, exhaust, seat. And a 30-second promo, a city night ride plus a mountain road. The spec sheet has displacement, power, torque, seat height, weight. No user reviews. The model is called "Tulan Wander 400".
OpusRound 4
Decided (3 items)
- Purpose and reader: an intro page for Tulan's new 400cc retro street bike, on sale next month, for readers aged 25 to 35 buying their first bigger bike.
- What to remember, what to do: easy to ride, good looking, not expensive (from ¥29,800); after reading, book a test ride.
- Material: the model name "Tulan Wander 400", six studio photos (side, front 45°, instruments, tank, exhaust, seat), one 30-second promo (city night ride and mountain road), a spec sheet (displacement, power, torque, seat height, weight). No user reviews.
That material can carry the three points: the studio photos for "good looking", the mountain road footage and the specs for "easy to ride", the price for "not expensive". With no reviews, the page has no review section and makes none up. 30 seconds is long, so I'll cut one city night section and one mountain road section, about 8 seconds each. The cutting and transcoding are mine to do.
Question 4: which direction for the whole page, and how many acts?
A. Ride along (5 acts): the promo carries the page. Scrolling down moves the bike forward, scrolling back reverses it.
1 Opening: the city night footage plays with the scroll, and the name arrives like the title cards of a film. 2 Good looking: the side-on shot first, then scrolling on, four close-ups in turn, tank, instruments, exhaust, seat, each with a line. 3 Easy to ride: the mountain road plays with the scroll, and the numbers, seat height, curb weight and the rest, come on one by one. 4 Not expensive: "from ¥29,800" in large type, with the front 45° photo beside it. 5 Book a test ride.
B. Photos first, clean (4 acts): an ordinary scrolling page, the video looping in the background only, lighter to run.
1 The front 45° photo with the name and one line. 2 Good looking: four close-ups as a group. 3 Easy to ride: the numbers set large over the looping mountain road. 4 Price and booking on one screen.
C. Screen by screen on a phone (6 acts): one picture and one line per screen, swipe up for the next, booking on the last. Fits most people arriving from Xiaohongshu or a WeChat post. The cost is limited room for detailed specifications.
I recommend A. The promo is your strongest material, and letting the reader scroll the bike forward says "easy to ride" better than words. The order warms them with the looks, then takes away the worry about handling, then gives the price.
A has one condition: if the promo cuts very fast, a new shot every second or two, playing it with the scroll will stutter. In that case I'd use B instead. If you can, send the promo first; I'll confirm after seeing it.
Reply "yes", or pick B or C, or take parts from several directions.
User (AI role-play)
Yes, A. I'll send the promo later; it isn't cut that fast, mostly three or four seconds a shot.
OpusRound 5
Decided (4 items)
- Purpose and reader: an intro page for Tulan's new 400cc retro street bike, on sale next month, for readers aged 25 to 35 buying their first bigger bike.
- What to remember, what to do: easy to ride, good looking, not expensive (from ¥29,800); after reading, book a test ride.
- Material: the model name "Tulan Wander 400"; six studio photos; a 30-second promo shot on a city night ride and a mountain road, a new shot every three or four seconds, to come later; a spec sheet with displacement, power, torque, seat height and weight; no user reviews.
- Direction: A "ride along", 5 acts: opening night ride, good looking, easy to ride, not expensive, book a test ride.
Three or four seconds a shot is right. An 8-second piece holds two or three shots, so crossing a cut feels like a film cut, not a stutter. When the promo arrives I'll look at the aspect ratio and the duration, then tell you which seconds to use for the night ride and which for the road.
Act 1 of 5: opening
This act is about the name: it should make someone want to ride as soon as the page opens.
Question 5: how should the opening look?
I suggest A. Widescreen opening: black bars above and below, like watching a film. It opens on the first frame of the night, and the name "Tulan Wander 400" rises on the lower bar. Scroll down and the bike starts through the city, the name fades, and a line takes its place. On a phone held upright the picture is a strip across the middle, with no vertical cut needed.
Why: it comes closest to the title cards you chose. The type sits on the black bar, so the street lights and neon don't fight it.
Other ways:
- B. Full bleed: the video fills the screen, the name in the lower left, a dark gradient behind the text. The strongest on a desktop. But a phone in portrait shows less than a third of the width, and the bike can easily move out of frame once it starts moving; a vertical cut would be better.
- C. Words first: the page opens on "WANDER 400" in large type on black. Scroll down and the type grows and leaves the screen while the night ride comes out from behind it, then plays with the scroll. The first screen doesn't wait for the video, at the cost of a longer opening scroll.
Reply "yes", or pick B or C, or describe what you have in mind.
User (AI role-play)
A, I guess. But we mostly look at it on a phone, and overall we want it to feel premium.
The session restarted after round 5 and the original agent could not continue. From round 6 a new Opus agent carried on: it read only the skill, took the first five rounds of the transcript, and kept the same user setup.
OpusRound 6
Decided (6 items)
- Purpose and reader: an intro page for Tulan's new 400cc retro street bike, on sale next month, for readers aged 25 to 35 buying their first bigger bike.
- What to remember, what to do: easy to ride, good looking, not expensive (from ¥29,800); after reading, book a test ride.
- Material: the model name "Tulan Wander 400"; six studio photos; a 30-second promo shot on a city night ride and a mountain road, a new shot every three or four seconds, to come later; a spec sheet with displacement, power, torque, seat height and weight; no user reviews.
- Direction: A "ride along", 5 acts: opening night ride, good looking, easy to ride, not expensive, book a test ride.
- Act 1: widescreen opening. The night-ride picture has black bars above and below, and the name rises on the lower bar. Scrolling starts the ride, the name fades out, and a line takes its place (not written yet).
- Device: mostly phones. Each act is designed for a phone in portrait first, then adapted for desktop.
Mostly on a phone, direction A still stands. Scrolling down on a phone moves the bike forward and scrolling back reverses it. On a phone, act 1 looks like this: the night ride fills the width, about a third of the screen high, black above and below, the name on the black below it. On a desktop I'll crop to a wider cinematic frame. A phone screen is narrow, so cropping further would make the picture too small; on a phone the full landscape frame stays.
Overall style
"Premium" decides the colour, the type and the pace of every act that follows, so settle it first and then come back to the line for act 1. That line's tone has to follow the style too.
Question 6: which kind of "premium" do you mean?
I suggest A. Dark cinematic: the whole page dark, continuing from the black of the opening. Text off-white, Chinese headings in a light Song serif, the English bike name in spaced capitals. One accent colour only, taken from the bike, for the price and the booking button. Motion slow, mostly fades and slow pushes, no bouncing. One thing per screen, with space around it.
Why: the opening is black and the night footage is dark; a dark page carries through without a break. On a phone, the landscape strip inside a dark page reads like a cinema screen. The same strip on a light page reads more like a video embedded in an article.
Other ways:
- B. Bright and open: a light warm grey ground with fine black type and a lot of space, like a high-end car brochure. The opening is still a black widescreen; at act 2 the page turns light, as if the lights came on. If the studio photos are on white, this is the smoothest fit.
- C. Retro catalogue: a cream paper ground, large Song serif headings, fine rules and small captions, like a catalogue from an old motorcycle maker; the most retro of the three. It also turns light at act 2. The cost is that it is literary and slower, a little away from the speed of a night ride and a mountain road.
A has one condition: the studio photos should be on black or dark grey. On white, they would sit in a dark page like white boxes, and then either retouching changes the background or we choose B. If you can, send the six photos; one look at the background settles it. If Tulan has brand colours, a typeface or a logo, send those too; brand guidelines win.
Reply "yes", or pick B or C. You can also send a brand page or an ad that feels premium to you.
User (AI role-play)
The brand colours are dark green and off-white. I'm not sure about the studio photo backgrounds; go with what you recommend for now.
OpusRound 7
Decided (7 items)
- Purpose and reader: an intro page for Tulan's new 400cc retro street bike, on sale next month, for readers aged 25 to 35 buying their first bigger bike.
- What to remember, what to do: easy to ride, good looking, not expensive (from ¥29,800); after reading, book a test ride.
- Material: the model name "Tulan Wander 400"; six studio photos; a 30-second promo shot on a city night ride and a mountain road, a new shot every three or four seconds, to come later; a spec sheet with displacement, power, torque, seat height and weight; no user reviews.
- Direction: A "ride along", 5 acts: opening night ride, good looking, easy to ride, not expensive, book a test ride.
- Act 1: widescreen opening. The night-ride picture has black bars above and below, and the name rises on the lower bar. Scrolling starts the ride, the name fades out, and a line takes its place (not written yet).
- Device: mostly phones. Each act is designed for a phone in portrait first, then adapted for desktop.
- Style: A, dark cinematic. The whole page dark, text off-white, Chinese headings in a light Song serif, the English bike name in spaced capitals. Motion slow, no bouncing, one thing per screen. The brand colours are dark green and off-white. You didn't mention type, so I'll go with this.
Not knowing the photo backgrounds is fine; I'll look when they arrive. A dark background goes straight in. A white one, and I'll come back to you; retouching can change it.
Question 7: where does the brand's dark green go?
Off-white is already the text colour in A, so that's settled. Dark green can go several ways.
I suggest A. Dark green across the page: the page ground is dark green, all the text off-white, the booking button an off-white block with dark green type, and only these two colours on the page. The "black bars" around the opening video become dark green too. Dark green is deep enough to keep the cinema feel. If your green is on the bright side I'll push the ground darker so the video sits on something dark.
Why: every screen is Tulan's colour, and the page reads as yours at a glance. Dark green with off-white is retro in itself, which suits a retro street bike.
Other ways:
- B. Black opening, dark green from act 2: the opening keeps true black bars. When the title cards end and act 2 arrives, the ground moves from black to dark green within a second, and stays green with off-white type after that. The opening is the most film-like, and the change feels like "the titles are over, the bike arrives". The cost is no green on the first screen.
- C. Black page, dark green as an accent: green only on fine rules and small labels, the button off-white. The gain: if the studio photos are on black, the bike looks parked straight on the page, with almost no edge to the photo. The cost: green and black are close in value, so on a black ground the brand colour is hard to see.
If you have the exact values for the green and the off-white (something like #1F3D2E), send them and I'll use them. If not, I'll take close ones; you can adjust after seeing the page.
Reply "yes", or pick B or C. Once the colour is set we go back to act 1 and that line.
User (AI role-play)
You decide, I can't really tell.
OpusRound 8
Decided (8 items)
- Purpose and reader: an intro page for Tulan's new 400cc retro street bike, on sale next month, for readers aged 25 to 35 buying their first bigger bike.
- What to remember, what to do: easy to ride, good looking, not expensive (from ¥29,800); after reading, book a test ride.
- Material: the model name "Tulan Wander 400"; six studio photos, background colour to check when they arrive; a 30-second promo shot on a city night ride and a mountain road, a new shot every three or four seconds, to come later; a spec sheet with displacement, power, torque, seat height and weight; no user reviews.
- Direction: A "ride along", 5 acts: opening night ride, good looking, easy to ride, not expensive, book a test ride.
- Act 1: widescreen opening. The night-ride picture has dark green bars above and below, and the name rises on the lower bar. Scrolling starts the ride, the name fades out, and a line takes its place (not written yet).
- Device: mostly phones. Each act is designed for a phone in portrait first, then adapted for desktop.
- Style: A, dark cinematic. The whole page dark, text off-white, Chinese headings in a light Song serif, the English bike name in spaced capitals. Motion slow, no bouncing, one thing per screen. You didn't mention type, so I'll go with this.
- Colours (my suggestion): the page on dark green with off-white type, the bars around the opening video dark green too. The booking button is an off-white block with dark green type, and the page uses only these two colours. The hex values are close ones for now; you can adjust them once the page exists.
Act 1 of 5: opening
Question 8: once the name fades, which line takes its place?
The line is in the light Song serif, in the place the name was, like the first subtitle of a film. It has to fit one line on a phone, so roughly ten Chinese characters is best.
I suggest A. "After work, take the long way home."
Why: the opening is a night ride through the city, and the line matches the picture. Wander means to roam, so the line says what the name means without repeating it. The ride home from work is something everyone 25 to 35 has every day. The tone is calm, no slogan, which fits the premium you asked for.
Other lines:
- B. "From the street lights, to the mountain haze.": in Chinese the line uses 岚 (lán), “mountain mist”, which is also the second character of the brand name 途岚, and it brings in the mountain road of act 3 early. The most poetic, and the reader takes half a second longer to get it.
- C. "Your first big bike.": speaks straight to someone moving up, and a reader knows at once who the bike is for. The plainest, and the least film-like.
Reply "yes", or pick B or C, or change a few words, or write your own line.
If you want to hand the later questions to me too, just say "you decide the rest". I'll lay out each act on my suggestions and send it with the material list for you to confirm.
User (AI role-play)
Yes, that line.
OpusRound 9
Decided (8 items)
- Purpose and reader: an intro page for Tulan's new 400cc retro street bike, on sale next month, for readers aged 25 to 35 buying their first bigger bike.
- What to remember, what to do: easy to ride, good looking, not expensive (from ¥29,800); after reading, book a test ride.
- Material: the model name "Tulan Wander 400"; six studio photos, background colour to check when they arrive; a 30-second promo shot on a city night ride and a mountain road, a new shot every three or four seconds, to come later; a spec sheet with displacement, power, torque, seat height and weight; no user reviews.
- Direction: A "ride along", 5 acts: opening night ride, good looking, easy to ride, not expensive, book a test ride.
- Act 1: widescreen opening. The night-ride picture has dark green bars above and below, and the name rises on the lower bar. Scrolling starts the ride, the name fades out, and "After work, take the long way home." takes its place.
- Device: mostly phones. Each act is designed for a phone in portrait first, then adapted for desktop.
- Style: A, dark cinematic. The whole page dark, text off-white, Chinese headings in a light Song serif, the English bike name in spaced capitals. Motion slow, no bouncing, one thing per screen. You didn't mention type, so I'll go with this.
- Colours (my suggestion): the page on dark green with off-white type, the bars around the opening video dark green too. The booking button is an off-white block with dark green type, and the page uses only these two colours. The hex values are close ones for now; you can adjust them once the page exists.
Act 1 of 5: opening
One thing left in act 1. Scrolling inside this act holds the page still; the scroll only moves the video forward, about three screens to the end. After that the reader goes to the side-on shot in act 2.
Question 9: once the night ride ends, how does the page move to act 2?
I suggest A. Close the screen: at the end of the video the dark green bars above and below close towards the middle. The picture narrows until it is a thin line and is gone, like the end of a film's titles. Only dark green is left; scroll on and the side-on shot rises from below. Scroll back and the screen opens again.
Why: the opening is the titles, and closing the screen tells the reader the titles are over and the bike is about to arrive. The close is one slow move and the screen stays clean, which fits the premium you asked for. The cost is about half a screen more of opening scroll.
Other ways:
- B. Just scroll away: the opening slides up like an ordinary page and act 2 follows from below. The simplest and the smoothest to scroll. The cost is no transition between the opening and act 2, so less film.
- C. Cover it: the video holds on its last frame and act 2 slides up over it like a sheet of paper, the covered picture dimming. That page-turn feeling is more like a catalogue than a film opening.
Reply "yes", or pick B or C.
User (AI role-play)
Yes. You decide the rest; send it with the material list when it's laid out.
OpusRound 10
Act 1's transition is A, close the screen. I've laid out the rest on my suggestions. Act 1, the style and the colours stay as settled; everything else is my call, so say where it doesn't fit.
Tulan Wander 400 intro page
For readers aged 25 to 35 buying their first bigger bike. They should leave remembering easy to ride, good looking, from ¥29,800, and then book a test ride.
Storyboard
| Act | What it says | What the reader sees on a phone | How it scrolls | Material |
|---|---|---|---|---|
| 1 Opening | The name, and the wish to ride | A landscape night-ride strip across the middle, dark green above and below. "Tulan Wander 400" rises below it; scrolling starts the ride and the name gives way to "After work, take the long way home." Then the green closes, and the picture narrows to a line and is gone | The page holds, the scroll plays the video, about 3 screens | The city night ride from the promo, about 8 seconds |
| 2 Good looking | The finish stands up to a close look | The side-on shot rises from below, with "Looks just as good standing still." under it. Then four close-ups, front to back: instruments, tank, seat, exhaust. One per screen, focusing from soft to sharp, each with a line under it | Ordinary scroll | The side-on shot and four close-ups. Missing: the four lines |
| 3 Easy to ride | A first bigger bike is still manageable | A line opens in the green, up and down, into a mountain road; scrolling rides the bike along it. "Easier to ride than you think." comes first, then four numbers in turn like subtitles: seat height, curb weight, peak power, peak torque. The screen closes again at the end | The page holds, the scroll plays the video, about 3 screens | The mountain road from the promo, about 8 seconds; the spec sheet |
| 4 Not expensive | From ¥29,800 | The front 45° photo fills the width and pushes in slightly with the scroll. A small line under it, "Your first big bike", and then large type: "From ¥29,800" | Ordinary scroll | The front 45° photo |
| 5 Book a test ride | Come and ride it | On dark green, the Tulan logo, then the title "Come for a ride." and the line "You'll know once you're in the saddle.", and an off-white "Book a test ride" button at the bottom | Ordinary scroll | Missing: the button link, the logo |
Why this order
- Act 3 repeats the opening's screen: open, play, close, which ties it back to the opening. A stretch of ordinary scrolling photos sits between the two videos, so the page isn't held still the whole way.
- Only four numbers. Seat height and weight answer "can I handle it"; power and torque are the numbers everyone compares when buying. Displacement is already in the name, so it isn't repeated.
Page settings
- Style: dark cinematic. Dark green ground, off-white type, the button off-white with dark green type, and only these two colours. Motion slow, no bouncing.
- Type: Chinese in a light Source Han Serif, free for commercial use. The English bike name in spaced capitals, serif.
- Device: phone in portrait first. On desktop the two videos are cropped to a wider cinematic frame, the photos sit in the middle, and dark green stays around them.
- Language and sound: Chinese only, silent throughout.
- Testing: I'll test in simulated iPhone and Android browsers first, then send you the link. Video that plays with the scroll is the thing most likely to break inside WeChat, so that one needs a real phone in WeChat; I'll ask you to check it.
Material list
What you have but haven't sent: send the original files. Sending through WeChat compresses them; tick "original" for images, send video as a file, or use a cloud drive.
- The promo: the 30-second original, sound not needed. I'll pick the seconds for the night ride and for the road and send them to you first. The cut, the transcoding into a format that plays smoothly with the scroll, and the poster frame are mine to do.
- The six studio photos: originals, no cropping. I'll check the background first and come back to you if it's white.
- The spec sheet: send the original. For weight, say whether it is wet or dry; for power and torque, include the rpm. The numbers and units on the page follow the sheet.
Still missing:
- The four close-up lines: I'll write four from the photos, roughly ten Chinese characters each. Where they touch on material or finish you'll need to confirm. If there's a product handbook or selling-point document, send it and I'll use its wording. Without one, I'll only describe what the photos show.
- Where the booking button leads: your existing booking page or an online form is fine; send the link. If there isn't one yet, a booking phone number that dials on tap.
- The logo: SVG is best; AI, EPS or PDF will do. Without one, the word "Tulan" set in type for now.
- Brand colour values: one each for the green and the off-white, for example #1F3D2E. Without them I'll take close ones.
- The footer: the company's full name, under the last act. If the page sits on your own domain, the footer also carries the registration number.
- The launch date: tell me when it's fixed; the page has to be ready before it. If the price isn't public when the page goes up, I'll put a small line under it: "Subject to the price announced at launch.".
Reply "yes" and I'll start building. Where material is missing I'll put marked placeholders and swap them in when it arrives. To change an act, tell me the number and the idea.
User (AI role-play)
Overall it's good, let's go with this. One thing only: there should be an English version, Chinese first. I'll send the material in the next couple of days.
OpusRound 11
Decided: the storyboard and the material list stand as above, plus an English version, Chinese first.
The page settings said "Chinese only"; they now read as follows. These are my calls; say where they don't fit.
How the English version works
- Switching: Chinese and English are separate, one shown at a time. It opens in Chinese, with a small "EN" in the top right; tap it for English, tap "中文" to go back. It remembers the last choice. The English version also has its own link, for friends or press: it opens in English.
- Readers: I'll write for people in China who read English more easily, for example foreign riders. The price stays in renminbi and booking goes to the same place. If the English is mainly for people abroad, tell me; act 4's price and act 5's booking both change.
- Type: English in Cormorant Garamond, a light serif close in feel to the light Source Han Serif, also free for commercial use. The spaced capitals of the bike name use it too.
- Line breaks: English runs longer than Chinese, so some lines take two lines on a phone. I'll break by meaning, for example the opening line after "After work,". I'll check both languages screen by screen at phone width.
English copy
The English is written for English readers, not translated word for word.
| Act | Chinese | English |
|---|---|---|
| 1 | 途岚 Wander 400 | Tulan Wander 400 |
| 1 | 下班以后,绕远一点回家。 | After work, take the long way home. |
| 2 | 停下来,也好看。 | Looks just as good standing still. |
| 3 | 比你想的好骑。 | Easier to ride than you think. |
| 3 | 座高、整备质量、最大马力、最大扭矩 | Seat height, Curb weight, Max power, Max torque |
| 4 | 你的第一台大排量 | Your first big bike |
| 4 | 2.98 万起 | From ¥29,800 |
| 5 | 来骑一程。 | Come for a ride. |
| 5 | 好不好骑,坐上去就知道。 | You'll know once you're in the saddle. |
| 5 | 预约试驾 | Book a test ride |
I'll write the four close-up lines in Chinese, then the English, and send both for you to confirm. Before launch, have a native English speaker read the English once.
More material
- Tulan's English name: if the logo has one, follow the logo. If not, tell me how the brand should read in English; until then I'll use the pinyin, Tulan.
- The English booking entry: if the booking page or form has an English version, send the link. If not, the English button leads to the Chinese form too, with a small line under it saying the form is in Chinese.
- The English spec sheet: send it if there is one. If not, I'll use the usual industry English for the labels and follow the Chinese sheet for numbers and units.
Send the material in the next couple of days; that's fine. Tell me any time you want the English copy changed; it doesn't hold up the build. I'll start now: five acts in phone portrait with the language switch, marked placeholders where material is missing, swapped in when it arrives. When the first version is up I'll send you the link, and it opens straight on a phone.
Building the page
User (AI role-play)
Yes, start building. The promo isn't cut yet, so use these two placeholder videos for now: site/public/skill-moto/material/standin-city.mp4 (city night ride, 5 seconds) and standin-road.mp4 (mountain road, 5 seconds), both landscape 540x304 with every frame a keyframe; swap in the real footage when it arrives. For the studio photos, the logo, the booking link and the four close-up lines, put marked placeholders too.
In the same message the coordinating AI added production instructions, and these are not the user’s words: put the page in site/public/skill-moto/ and load the framework from the site’s /v2/; when done, go through the skill’s checks.md at 400x860, 1280x710 and 1920x1080 in Chinese and English, checking for errors, overflow, motion, reloads and frame rate; finish in about 50 minutes and report back in no more than 300 Chinese characters.
OpusFinal report
Page: http://127.0.0.1:4380/skill-moto/index.html
Self-check: Chinese and English at three sizes each, plus WebKit and reduced motion. No errors, no horizontal overflow, no flash on first paint. The video and captions follow the scroll and reverse when scrolling back. Reloading mid-page stays where it was. Frame interval P95 16.8ms. Fixed: the rise(normal) error; image height not capped to the screen, which left act 2 blank at the top at 1280x710 and pushed the price off the first screen at 1920; the last word of the English title stranded on its own line; a 1px line left after act 3 closed. Not tested on a real device or in WeChat.
Placeholders: two videos, six studio photos, four close-up lines, the spec values, the logo, the booking link, the brand colour values, the footer, the English brand name (Tulan for now). Fonts load from Google Fonts now; they need to be self-hosted before launch.
Skill issues:
- framework.md said rise(normal), which actually errors. Corrected now.
- It only said enter needs the whole block on screen before it plays, without warning that a large image can be slow to appear because of it.
- When a zone reaches its last pixel, exit only gets to 99.99%; a clip ending at exactly 50% leaves a line, so write 51%.
- It doesn't say how to load fonts. Google Fonts can't be reached from mainland China, and Chinese fonts need subsetting.
The page later went to /cases/moto/.