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-x-custom-appskind topicweek —date —campaign it-dev-pillarpillar it_devbeat —asset videoduration 89.5sground blackscenes 14

Checklist the per-video bar — engine/sim

97.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-x-custom-apps 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 14 scenes · 89.5s · comp_id + rendered still + tier + the script

#Layer (comp_id · still · tier)BeatTimecodeMotionLogoAudioVO / on-screen / caption
1s1
matches intent
shared field
signature-3d		open0–6.1sspatial-parallaxicon·ember-fill♪ —
There is a tool your business actually needs that nobody sells, because it is shaped exactly like you.
on-screen: The tool that doesn't exist
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
CodeWindow
template		legacy6.1–12.8scrossfade-8ficon·wireframe♪ —
The old way was a spreadsheet duct-taped with formulas only one person understands, one wrong click from chaos.
on-screen: The spreadsheet held together
expected on screen: black ground · a CodeWindow panel over a dimmed Signal Field · Faber leads · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CodeWindowshape boxground blacktreatment wireframemotion crossfade-8fpower morphinstrument decay→three-symboliccurate codeLines, windowTitle
3s3
matches intent
NumberedList
template		teach12.8–19.200000000000003skinetic-buildicon·wireframe♪ —
We define the single job the tool must do, because a custom app that tries to do everything does nothing well.
on-screen: Step 1: the one job
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		teach19.2–25.299999999999997skinetic-buildicon·wireframe♪ —
We design the data shapes first, so the app is built on a real structure, not a pile of loose fields.
on-screen: Step 2: model the data
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
NodeGraphCard
template		teach25.3–31.700000000000003skinetic-buildicon·wireframe♪ —
Claude Code scaffolds the app from that model, so we start with a running skeleton in minutes, not weeks.
on-screen: Step 3: agent scaffolds it
expected on screen: black ground · a NodeGraphCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id NodeGraphCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate hub, nodes
6s6
matches intent
StackTrace
template		teach31.7–38.8skinetic-buildicon·wireframe♪ —
Every button does a real thing, reads or writes your data, so it is a runnable tool, not a clickable mockup.
on-screen: Step 4: real buttons, real actions
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→three-flowcurate errMsg, errType, fix, frames, nodes
7s7
matches intent
TerminalRun
template		teach38.8–45.199999999999996skinetic-buildicon·wireframe♪ —
We validate what users type, so a bad entry gets a friendly error instead of silently breaking the data.
on-screen: Step 5: guard the inputs
expected on screen: black ground · a TerminalRun panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id TerminalRunvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate nodes
8s8
matches intent
SchematicCard
template		teach45.2–50.7skinetic-buildicon·wireframe♪ —
We set who can see and change what, so the intern cannot delete the thing the company runs on.
on-screen: Step 6: who can do what
expected on screen: black ground · a SchematicCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id SchematicCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes
9s9
matches intent
LegacyCard
template		teach50.7–56.800000000000004skinetic-buildicon·wireframe♪ —
It plugs into the apps you already use through their APIs, so it lives in your stack, not beside
on-screen: Step 7: connect your tools
expected on screen: black ground · a LegacyCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id LegacyCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes
10s10
matches intent
ProcessFlow
template		teach56.8–63.5skinetic-buildicon·wireframe♪ —
We click through the actual user flow before launch, because a tool that passes tests can still feel wrong.
on-screen: Step 8: test the real flow
expected on screen: black ground · a ProcessFlow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ProcessFlowvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, steps
11s11
matches intent
ListCard
template		teach63.5–70.1skinetic-buildicon·wireframe♪ —
We deploy it to a real URL, so the team opens a link instead of running a script from someone's laptop.
on-screen: Step 9: ship it where they work
expected on screen: black ground · a ListCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id ListCardvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate items, nodes
12s12
matches intent
StatScoreboard
template		proof70.1–77.1sreceipts-counticon·wireframe♪ —
That is software shaped to your exact job, with real actions, guarded inputs, and the right people in charge.
on-screen: A tool, not a mockup
expected on screen: black ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground blacktreatment wireframemotion receipts-countpower receiptsinstrument spotlight→html-in-canvas-receiptscurate pillar, stats, statsLabels
13s13
matches intent
shared field
signature-3d		futurist77.1–83.0sspatial-parallaxicon·wireframe♪ —
When the tool fits the work instead of the other way around, the whole team stops fighting their software.
on-screen: What this unlocks
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
14s14
matches intent
shared field
signature-3d		resolve83.0–89.5scoalescenceicon·ember-fill♪ swell
Tell us the tool that should exist for your business. We will build the runnable version. temerarii.xyz.
on-screen: Describe the tool
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)

tiktokThere is a tool your business needs that nobody sells, because it is shaped exactly like you. (AI-assisted) Stop duct-taping a spreadsheet only one person understands. Define the single job the tool must do. Design the data shapes first, so it is built on real structure. Claude Code scaffolds the app from that model, a running skeleton in minutes. Every button does a real thing, reads or writes your data. Validate the inputs. Set who can change what, so the intern can't delete the thing the company runs on. Then deploy it to a real URL, so the team opens a link, not a script on someone's laptop.
instagramThere's a tool your business needs that nobody sells. Because it's shaped exactly like you. Define the one job Model the data first Claude Code scaffolds the app Real buttons, guarded inputs Deploy to a real URL Software shaped to your job, not a mockup. #CustomSoftware #ClaudeCode #BuildInPublic #AItools #Temerarii
linkedinThere is a tool your business actually needs that nobody sells, because it is shaped exactly like you. Here is how to build the runnable version, given away. The old way was a spreadsheet duct-taped with formulas only one person understands, one wrong click from chaos. The method: 1. Define the single job the tool must do, because a custom app that tries to do everything does nothing well. 2. Design the data shapes first, so the app is built on a real structure, not loose fields. 3. Claude Code scaffolds the app from that model, so we start with a running skeleton in minutes. 4. Every button does a real thing, reads or writes your data, so it is a runnable tool, not a clickable mockup. 5. Validate what users type, so a bad entry gets a friendly error instead of silently breaking the data. 6. Set who can see and change what, so the intern cannot delete the thing the company runs on. 7. Test the actual user flow, then deploy to a real URL. That is software shaped to your exact job, with real actions and the right people in charge. Tell us the tool that should exist for your business. We will build the runnable version. temerarii.xyz
xThere's a tool your business needs that nobody sells, because it's shaped like you. Define the one job Model the data first Claude Code scaffolds it Real buttons, guarded inputs Deploy to a real URL A tool, not a mockup. temerarii.xyz
facebookThere is a tool your business actually needs that nobody sells, because it is shaped exactly like you. Stop duct-taping a spreadsheet only one person understands. Define the single job the tool must do. Design the data shapes first. Claude Code scaffolds the app from that model in minutes. Every button does a real thing. Validate the inputs. Set who can change what. Then deploy to a real URL so the team opens a link, not a script on someone's laptop. Tell us the tool that should exist. temerarii.xyz
threadsThere's a tool your business needs that nobody sells, because it's shaped exactly like you. Define the one job. Model the data first. Claude Code scaffolds the app in minutes. Real buttons, guarded inputs, the right people in charge. Deploy it to a real URL. Software shaped to your job, not a clickable mockup.
pinterestHow to build the custom tool nobody sells you: define the single job, model the data first, let Claude Code scaffold the app, wire real buttons that read and write your data, guard the inputs, and deploy to a real URL. A plain method for runnable custom software, not a mockup.
blueskyThere's a tool your business needs that nobody sells, because it's shaped like you. Define the one job. Model the data first. Claude Code scaffolds it in minutes. Real buttons, guarded inputs, the right people in charge. Deploy to a real URL. A tool, not a mockup. temerarii.xyz
youtubeBuild the Custom Tool Nobody Sells You (Runnable, Not a Mockup) There is a tool your business actually needs that nobody sells, because it is shaped exactly like you. This walks the full method and gives it away. The old way was a spreadsheet duct-taped with formulas only one person understands, one wrong click from chaos. The method: 1. Define the single job the tool must do, because a custom app that tries to do everything does nothing well. 2. Design the data shapes first, so the app is built on a real structure, not a pile of loose fields. 3. Claude Code scaffolds the app from that model, so we start with a running skeleton in minutes, not weeks. 4. Every button does a real thing, reads or writes your data, so it is a runnable tool, not a clickable mockup. 5. Validate what users type, so a bad entry gets a friendly error instead of silently breaking the data. 6. Set who can see and change what, so the intern cannot delete the thing the company runs on. 7. Connect it to the apps you already use through their APIs. 8. Test the actual user flow, then deploy to a real URL. That is software shaped to your exact job, with real actions, guarded inputs, and the right people in charge. Tell us the tool that should exist for your business. We will build the runnable version. 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