Most AI image work fails at the brief, not the model. Three lines in. Generic out. People blame the tool. I shipped a fix. Pushing-creation installs into Claude. Drop reference images into refs/. Run /frames-brainstorm. Claude reads your refs, runs a DP-style interview, and writes the style pack live as you answer. /frames-shotlist drafts the full storyboard. /frames-shot polishes individual frames. Output is markdown. Drop it into PUSHING FRAMES, Midjourney, Sora, or any tool. → github.com/PUSHINGSQUARES/pushing-creation To install, paste this into Claude: "Set me up with pushing-creation from github.com/PUSHINGSQUARES/pushing-creation. Read INSTALL_WITH_CLAUDE.md and walk me through it." You don't get better output by prompting harder. You get better briefs by treating the model like a director of photography. Specificity transfers craft. Stop prompting. Start defining outcomes. Read the deep-dive: https://aris-space.com/documents/workspaces/pushing-creation

"Hi. My name is..." Most of you thought *Slim Shady*. You didn't choose to. Your brain finished the line for me. That's not a memory. That's a file. Eminem put a .mp3 on enough devices that 27 years later the phrase auto-completes in your head before you've decided whether to. The .mp3 isn't the song. The .mp3 is the install. And the install is what survives everything else. Not the tour. Not the chart position. The file on the device. So I stopped thinking about reach as eyes-on-content and started thinking about it as files-on-devices. The yardstick Distribution is not marketing. Distribution is legacy. The PDF won. Not because it was the most elegant document format. It won because it ended up on more devices than anything else. The MP3 did the same. So did the JPEG. The format that earned a life was the format on the most machines. Not the most correct. Not the most beautiful. The most installed. The work that lasts is the work that travelled. What an install actually looks like Three signs you've installed, not just been seen. 1. Re-entry without prompting. Someone opens your thing before they decide to open it. The switching cost has disappeared. 2. Installed before adopted. It became part of a workflow before anyone consciously chose it. 3. Outlives the moment. Years later, the file is still on the device. Not because you maintained the relationship. Because the format earned its keep. The files I've shipped that travelled were not the files I pushed hardest. They were the files good enough to keep, in a format easy enough to spread. In a ICM workspace the output folder is the product I spent a long time charging for the hours. The client doesn't experience the hours. They experience the file. The deliverable. The thing they put in a folder and reference six months later when the person who commissioned it has moved on. So I started pricing the folder, not the working. The hours are overhead. The output is the product. The output is what survives the invoice.

Bottom line: Two hours. Jake's frameworks went from a folder to live tools running in my workspace. Most community content has a 48-hour half-life. You read it, save it, and it ends up somewhere it influences nothing. The content is fine. The structure is the problem. Here's what I did: --Organized the vault: Cleaned up 30+ scattered files, classified by type, split into five sections. A file you can't find in 15 seconds doesn't exist. --Built an auto-ingestion pipeline: Scheduled task runs nightly. Drop anything new into _Inbox, it classifies and routes itself. New content stays in its lane. --Converted three frameworks into live skills: - Council of 5 — runs on command. Five advisor perspectives on any decision, simultaneously. - 60/30/10 Triage Rule — installed into workspace operating rules. Applies to every task without prompting. - Discovery Call SOP — no longer a document you read mid-call. Phases through pre-call, live support, and debrief automatically. --Audited workspace documentation: Cut 30-40% from routing and context files. Tighter files, faster responses. Before: Jake's frameworks lived in a folder. After: three of them are running. The best part is that it compared it against what my current business needs are and filtered out resources that weren't relevant to me (yet). For example @Curtis Hays full agency or @Roc Lee and his awesome conference talk engine. If you want to replicate it, I've attached a step-by-step guide with the exact prompts I used across all five sessions. Thank you ALL for your inspiration and to @Jake Van Clief for building this incredible community.