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-softwarekind topicweek —date —campaign it-dev-pillarpillar it_devbeat —asset videoduration 85.1sground blackscenes 14

Checklist the per-video bar — engine/sim

98.6/100
plain languagevo coverageno dead airuniquenesscaption fitcompletenesscleanliness
quantitative quality · weights learn from your reviews (engine.sim.memory review topic-it-software 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 · 85.1s · 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.2sspatial-parallaxicon·wireframe♪ —
Everyone has the app idea. The gap is turning it into something that actually runs.
on-screen: Your idea. Working software.
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground blacktreatment wireframemotion spatial-parallaxpower summoninstrument summon→three-mark
2s2
matches intent
DiffCard
template		legacy5.2–11.7scrossfade-8ficon·wireframe♪ —
The old way: a six-month spec, a contractor in another timezone, and a demo that broke on day one.
on-screen: How it used to go
expected on screen: black ground · a DiffCard panel over a dimmed Signal Field · Faber leads · crossfade-8f · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id DiffCardshape boxground blacktreatment wireframemotion crossfade-8fpower morphinstrument decay→three-symboliccurate lines
3s3
matches intent
NumberedList
template		teach11.7–17.6skinetic-buildicon·wireframe♪ —
We start by writing the whole feature as a plain-English spec, the same brief a junior dev would get.
on-screen: Step 1: spec in plain English
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		teach17.6–24.5skinetic-buildicon·wireframe♪ —
Then Claude Code reads the actual repository, so it edits your real files instead of inventing new ones.
on-screen: Step 2: Claude Code reads the repo
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
CheatSheet
template		teach24.5–30.7skinetic-buildicon·wireframe♪ —
We have it write the failing test before the feature, so the definition of done is provable, not a feeling.
on-screen: Step 3: tests first
expected on screen: black ground · a CheatSheet panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id CheatSheetvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, points, uses
6s6
matches intent
SchematicCard
template		teach30.7–37.6skinetic-buildicon·wireframe♪ —
Every change lands as one small commit on a branch, so a bad idea is one revert away, never a rewrite.
on-screen: Step 4: small commits
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-flowcurate nodes
7s7
matches intent
AnnotatedDiagram
template		teach37.6–43.5skinetic-buildicon·wireframe♪ —
We lock the data shapes with types, so the editor catches the bug before the user ever does.
on-screen: Step 5: typed contracts
expected on screen: black ground · a AnnotatedDiagram panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id AnnotatedDiagramvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-panelcurate callouts, nodes
8s8
matches intent
WireframeMock
template		teach43.5–49.8skinetic-buildicon·wireframe♪ —
Then we actually launch the app and click through it, because a passing test is not the same as it feeling right.
on-screen: Step 6: run it, watch it
expected on screen: black ground · a WireframeMock panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id WireframeMockvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-diagramcurate nodes
9s9
matches intent
StepFlow
template		teach49.8–55.699999999999996skinetic-buildicon·wireframe♪ —
A second pass reviews the diff against the main branch for the bugs the first pass talked itself out
on-screen: Step 7: review the diff
expected on screen: black ground · a StepFlow panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id StepFlowvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→html-in-canvas-codecurate nodes, steps
10s10
matches intent
BlueprintGrid
template		teach55.7–61.300000000000004skinetic-buildicon·wireframe♪ —
It goes out as a pull request with the tests green, so the merge is a decision, not a
on-screen: Step 8: ship on a PR
expected on screen: black ground · a BlueprintGrid panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id BlueprintGridvisual node-graphshape boxground blacktreatment wireframemotion kinetic-buildpower morphinstrument morph+laser→three-flowcurate nodes, rows
11s11
matches intent
ProcessFlow
template		teach61.3–67.1skinetic-buildicon·wireframe♪ —
After deploy we open the live URL and confirm the thing we built is the thing that loaded.
on-screen: Step 9: verify in prod
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→html-in-canvas-panelcurate nodes, steps
12s12
matches intent
StatScoreboard
template		proof67.1–73.19999999999999sreceipts-counticon·wireframe♪ —
That loop, spec to test to commit to ship, is how a feature goes from sentence to live software.
on-screen: Spec to running app
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		futurist73.2–79.0sspatial-parallaxicon·wireframe♪ —
When the loop is this tight, the bottleneck stops being engineering and becomes deciding what to build.
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		resolve79.0–85.1scoalescenceicon·wireframe♪ swell
Bring the idea. We will show you the spec-to-ship loop running on it. Start at temerarii.xyz.
on-screen: Bring the idea
expected on screen: black ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·wireframe logo · caption bottom-left
spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground blacktreatment wireframemotion 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)

tiktokEveryone has the app idea. The gap is turning it into something that runs. Here is the loop: write the feature as a plain-English spec, then let Claude Code read your real repository so it edits your files instead of inventing new ones. Write the failing test first. Land each change as one small commit. Lock the data shapes with types. Run the app and click through it. Review the diff, ship a pull request, then confirm it in prod. AI-assisted.
instagramEveryone has the app idea. The gap is making it run. The loop: - Spec it in plain English - Claude Code reads the real repo - Failing test first - Small commits on a branch - Typed contracts - Run it, then ship a PR Bring the idea. temerarii.xyz #claudecode #buildinpublic #temerarii #shipit #softwaredev
linkedinEveryone has the app idea. The gap is turning it into something that actually runs. The old way was a six-month spec, a contractor in another timezone, and a demo that broke on day one. Here is the loop we run instead: 1. Spec the feature in plain English, the same brief a junior dev would get. 2. Claude Code reads the actual repository, so it edits your real files instead of inventing new ones. 3. Write the failing test before the feature, so done is provable, not a feeling. 4. Land every change as one small commit on a branch, so a bad idea is one revert away. 5. Lock the data shapes with types, so the editor catches the bug before the user does. 6. Run the app and click through it, because a passing test is not the same as it feeling right. 7. Review the diff against main for the bugs the first pass talked itself out of. 8. Ship as a pull request with tests green, then verify on the live URL. The takeaway: when the loop is this tight, the bottleneck stops being engineering and becomes deciding what to build. Bring the idea. temerarii.xyz
xEveryone has the app idea. The gap is making it run. Spec in plain English. Claude Code reads the real repo. Failing test first. Small commits. Typed contracts. Run it. Review the diff. Ship a PR. Verify in prod. Bring the idea. temerarii.xyz
facebookEveryone has the app idea. The gap is turning it into something that actually runs. No more six-month spec and a demo that breaks on day one. Here is the loop: write the feature as a plain-English spec, let Claude Code read your real repo so it edits your files, write the failing test first, land small commits on a branch, lock the data shapes with types, run the app and click through it, review the diff, then ship a pull request and verify it in prod. Bring the idea and we will show you the loop running on it at temerarii.xyz
threadsEveryone has the app idea. The gap is making it run. Spec in plain English. Claude Code reads the real repo so it edits your files, not invented ones. Failing test first. Small commits on a branch. Typed contracts. Run it and click through. Review the diff. Ship a PR. Verify in prod. Bring the idea. temerarii.xyz
pinterestSpec-to-ship software loop: how an app idea becomes running software. Write the feature as a plain-English spec, let Claude Code read your real repository, write the failing test first, land small commits on a branch, lock data shapes with types, run the app and click through it, review the diff against main, ship a pull request with tests green, then verify on the live URL. A tight, repeatable build loop for turning a sentence into live software. temerarii.xyz
blueskyEveryone has the app idea. The gap is making it run. Spec in plain English. Claude Code reads the real repo. Failing test first. Small commits. Typed contracts. Run it. Review the diff. Ship a PR. Verify in prod. Bring the idea. temerarii.xyz
youtubeSpec to Running App: The Build Loop That Turns an Idea Into Live Software Everyone has the app idea. The gap is turning it into something that actually runs. The old way was a six-month spec, a contractor in another timezone, and a demo that broke on day one. The loop: - Spec the feature in plain English, the same brief a junior dev would get - Claude Code reads the actual repository, so it edits your real files instead of inventing new ones - Write the failing test before the feature, so done is provable - Land every change as one small commit on a branch, so a bad idea is one revert away - Lock the data shapes with types, so the editor catches the bug first - Run the app and click through it, because a passing test is not the same as it feeling right - Review the diff against main for the bugs the first pass talked itself out of - Ship as a pull request with tests green, then verify on the live URL When the loop is this tight, the bottleneck stops being engineering and becomes deciding what to build. Bring the idea. We will show you the loop running on 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