Back Office · office.temerarii.xyz
One asset, all the way in — composition, the wireframe + storyboard, the output format stack, and the template, all read from the SAME content-index record. The expected output matches what /media surfaces for this post.
post topic-it-webdesignkind topicweek —date —campaign it-dev-pillarpillar it_devbeat —asset videoduration 61.6sground blackscenes 9

Checklist the per-video bar — engine/sim

98.0/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-it-webdesign good|bad)
⚠ 1 flag(s) — not yet ship-ready: too_complex · see docs/strategy/VIDEO-CHECKLIST.md

Composition comp · template family · expected output

composition SceneReelfamily / template SceneReel
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
▶ open rendered mp4
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.

Composition layer × scene 9 scenes · 61.6s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–5.0sspatial-parallaxicon·ember-fill♪ —
You don't need a template farm or a six-week agency timeline.
on-screen: A real site, built by AI
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment ember-fillmotion spatial-parallaxpower summoninstrument summon→three-mark
2s2
matches intent
BuildLog
template		legacy5.0–12.4scrossfade-8ficon·wireframe♪ —
The old way was buying a theme, fighting its limits, then filing tickets every time you wanted something it didn't do.
on-screen: Old way: themes and tickets
expected on screen: black ground · a BuildLog panel over a dimmed Signal Field · Faber leads · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BuildLogshape boxground blacktreatment wireframemotion crossfade-8fpower morphinstrument decay→three-symboliccurate lines
3s3
matches intent
NumberedList
template		teach12.4–18.3skinetic-buildicon·wireframe♪ —
We start with a plain brief: what the page must do, who it's for, and the one action it should drive.
on-screen: Step 1: write the brief
expected on screen: black ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NumberedListvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
4s4
matches intent
ChecklistCard
template		teach18.3–26.3skinetic-buildicon·wireframe♪ —
Then we diagram the structure, pages, sections, and the flow between them, so we're building architecture, not decorating.
on-screen: Sitemap before pixels
expected on screen: black ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate items, nodes
5s5
matches intent
StackTrace
template		teach26.3–35.1skinetic-buildicon·wireframe♪ —
We hand the brief to Claude Code and it writes real HTML, CSS, and components, hand-editable, no proprietary lock-in.
on-screen: Claude Code writes the markup
expected on screen: black ground · a StackTrace panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StackTracevisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate errMsg, errType, fix, frames, nodes
6s6
matches intent
FlowSchematic
template		teach35.1–42.9skinetic-buildicon·wireframe♪ —
It flows fast: build, open a live preview, fix what looks off in the same loop, then deploy to a real URL.
on-screen: Build -> preview -> fix -> deploy
expected on screen: black ground · a FlowSchematic panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id FlowSchematicvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, stages
7s7
matches intent
RankList
template		proof42.9–49.3sreceipts-counticon·wireframe♪ —
A custom landing page that was a multi-week project now lands in hours, and you own every line of
on-screen: Hours, not weeks
expected on screen: black ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id RankListvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate rows, statsLabels
8s8
matches intent
shared field
signature-3d		futurist49.3–55.699999999999996sspatial-parallaxicon·wireframe♪ —
Soon a site isn't a static deliverable, it's something you can restyle or re-section by just asking.
on-screen: Sites that rebuild on command
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldshape boxground blacktreatment wireframemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→three-forward
9s9
matches intent
shared field
signature-3d		resolve55.7–61.6scoalescenceicon·ember-fill♪ swell
Need a site that's actually yours? We'll brief it and ship it. Start at temerarii.xyz.
on-screen: Ship your site
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→three-coalescence

Format stack 3 aspects · same scenes[], re-cropped

9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video

Channels 12 destinations

LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBlueskyEmailSMSBlog

Social captions supplemental published copy · per channel (comp_id level)

tiktokYou do not need a template farm or a six-week agency timeline to get a real site. Here is the build: write a plain brief covering what the page must do, who it is for, and the one action it should drive. Diagram the sitemap before any pixels. Hand the brief to Claude Code and it writes real HTML, CSS, and components you can hand-edit, no lock-in. Then build, open a live preview, fix what looks off in the same loop, and deploy to a real URL. AI-assisted.
instagramA real site, built by AI. No template farm. No six-week timeline. The build: - Write the plain brief - Sitemap before pixels - Claude Code writes real HTML/CSS - Build, preview, fix, deploy You own every line. temerarii.xyz #webdesign #claudecode #temerarii #buildinpublic #nocodelockin
linkedinYou do not need a template farm or a six-week agency timeline to get a real website. The old way was buying a theme, fighting its limits, then filing tickets every time you wanted something it did not do. Here is the build we run instead: 1. Write the brief. What the page must do, who it is for, and the one action it should drive. 2. Sitemap before pixels. Diagram pages, sections, and the flow between them, so you are building architecture, not decorating. 3. Claude Code writes the markup. Real HTML, CSS, and components, hand-editable, no proprietary lock-in. 4. Build, preview, fix, deploy. Open a live preview, fix what looks off in the same loop, then deploy to a real URL. The takeaway: a custom landing page that was a multi-week project now lands in hours, and you own every line of it. Need a site that is actually yours? temerarii.xyz
xYou do not need a template farm or a six-week timeline for a real site. Write the brief. Sitemap before pixels. Claude Code writes real HTML and CSS, no lock-in. Build, preview, fix, deploy. You own every line. temerarii.xyz
facebookYou do not need a template farm or a six-week agency timeline to get a real website. The old way was buying a theme, fighting its limits, then filing tickets for anything it could not do. Here is the build: write a plain brief covering what the page must do and the one action it should drive, diagram the sitemap before any pixels, hand it to Claude Code which writes real HTML and CSS you can hand-edit, then build, preview, fix, and deploy to a real URL. Need a site that is actually yours? temerarii.xyz
threadsYou do not need a template farm or a six-week agency timeline for a real site. Write the brief: what the page does, who it is for, the one action it drives. Sitemap before pixels. Claude Code writes real HTML and CSS, hand-editable, no lock-in. Then build, preview, fix, and deploy to a real URL. You own every line. temerarii.xyz
pinterestWeb design method: how to build a real custom site without a template farm or a six-week agency timeline. Write a plain brief covering what the page must do and the one action it drives. Diagram the sitemap before any pixels. Hand the brief to Claude Code, which writes real HTML, CSS, and components you can hand-edit with no lock-in. Then build, open a live preview, fix what looks off, and deploy to a real URL in hours, not weeks. temerarii.xyz
blueskyYou do not need a template farm or a six-week timeline for a real site. Write the brief. Sitemap before pixels. Claude Code writes real HTML and CSS, no lock-in. Build, preview, fix, deploy to a real URL. You own every line. temerarii.xyz
youtubeA Real Site, Built by AI: Brief to Sitemap to Deployed URL in Hours You do not need a template farm or a six-week agency timeline to get a real website. The old way was buying a theme, fighting its limits, then filing tickets every time you wanted something it did not do. The build: - Write the brief. What the page must do, who it is for, and the one action it should drive - Sitemap before pixels. Diagram pages, sections, and the flow between them, so you are building architecture, not decorating - Claude Code writes the markup. Real HTML, CSS, and components, hand-editable, no proprietary lock-in - Build, preview, fix, deploy. Open a live preview, fix what looks off in the same loop, then deploy to a real URL A custom landing page that was a multi-week project now lands in hours, and you own every line of it. Need a site that is actually yours? We will brief it and ship it. temerarii.xyz

Cross-links every lens is a view on this one record

→ Wireframe · scenes→ Calendar week→ Media (audience preview)→ Storyboard hub→ Day view→ Channel view