Your Claude Can Now Make Visuals
Image and video generation lived in apps.
Claude could think about them. It couldn't make them.
That gap closed today.
Pushing-creation is the cinematic prompt methodology installed as a Claude Code skill. It teaches Claude to brief like a director of photography, not whisper at a model.
v0.3.0 adds a keychain bridge. Provider keys live in macOS Keychain.
Claude calls a CLI that reads them at runtime and passes them straight to the API. The key value never enters Claude's context.
The result: every Claude Code session, in any workspace, can author style packs and generate frames end to end.
The shift
The methodology and the executor are in the same loop.
Before: author a brief in Claude. Switch apps. Paste the brief. Generate. Switch back.
Now: author the brief in Claude. Generate from the same session.
The three steps
Brief.
`/frames-brainstorm` runs a DP interview. Claude reads your reference images and writes style.md live. STYLE_ blocks fight defaults. NEG_ blocks fight failure modes.
Image.
`/frames-gen --kind image --shot-n 1`. Claude reads the shot from your storyboard, calls Gemini or GPT-image. The PNG lands in `renders/`.
Video,
`/frames-gen --kind video --shot-n 1`. Same shot, video provider. Kling video lands in `renders/`.
One session. One workspace. No app-hopping.
The keychain mechanic. The OS holds the key. Claude holds the brief.
Add each key once: `security add-generic-password -U -s "pushing-creation:gemini" -a "$USER" -w "your-key"`
Claude calls `bin/frames-gen`. Inside that process, the key gets read into a Python variable, passed to the HTTP client, and never logged or printed. Claude's transcript stays clean.
The OS guarantee: encrypted at rest, scoped to your user, accessible only with your authorisation.
The unlock
Every Claude session inherits this.
Storyboard. Product shot. Social post. Personal portfolio.
Same Claude. Same methodology. Different keys, but the keys were already there.
Two repos clone once. From then on, every workspace is a generation studio.
The takeaway
The methodology is the install. The keychain is the boundary. Once both land, the gap is closed.
You author. Claude generates. The keys stay yours.
---
Full breakdown. The setup walkthrough, the project format, and the three-step pipeline end to end, all live here:
// A<3
16
21 comments
Ari Evergreen
6
Your Claude Can Now Make Visuals
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by