Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

this is f**king insane i cancelled my $20/mo claude subscription for this. a dev found a way around OpenAI's usage limits and got unlimited GPT-5.6 Luna on Codex for FREE ($0)😳 He built a three step local workflow on a single machine. This involved no servers, shared accounts, or...

98,056 görüntüleme • 19 gün önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Making OpenCode as lean as Pi agent? Just trimmed 25k out of OpenCode's system prompt (from 30k to 4-5k tokens) How? Just disable skills and get rid of massive skill definition bloat. Who needs skills anyway? Just kidding, this is the not the way. It makes the agent lame and defeats the point of using one. But it sets a precedent: Find a way to use skills without their definitions pre-loaded into the system prompt every single turn. Another interesting stuff: Upon testing this temporary "no skill setup" with two of hottest OpenCode Zen free models, Mimo V2.5 vs DeepSeek V4 Flash: One thinks more and talks less One thinks less and talks more Check the video to see which is which If you made it here, I'm finding a way to leanest OpenCode setup that I can get I simply don't believe that OpenCode can't be as lean as Pi Upon tinkering, I made a plugin that temporarily extracts the system prompt while I test, and noticed the hundreds of definitions in it from my .agents/skills directory which is shared across all my coding agents (Cursor, Antigravity, Claude, etc.) Of course disabling skills is not the answer, but it just proved that there is a way to strip the system prompt of these massive skill defs Aside from the system prompt hierarchy that injects confusion imo if you have a conflicting and redundant AGENTS.md which I discovered upon digging into OpenCode's source code Apparently it has prompt.ts/system.ts/instruction.ts/llm.ts and loads base .txt prompts based on model family (claude/gpt-o/gpt-5/codex/gemini/others) that all work together to make OpenCode aware of who it was and how it should use tools and become a "coding agent" Gotta find the most minimal mix that fits right into my workflow Make OpenCode as lean as Pi? We'll see. All in

raymel 👋

37,478 görüntüleme • 2 ay önce

Beauty ads just changed forever. Free Claude Opus 4.8 + GPT Image 2 + Seedance 2.0 workflow to spin up 100s of video ads. No studio, no model, no macro lens, no shoot day. Here's what nobody in beauty marketing wants to say out loud. That glossy lip shot. The droplet hitting the surface in slow motion. The whip-pan into the next scene. The crystalline product splash. All the stuff that used to need a real set, a real camera op, and a full shoot day. You can generate every frame of it from a text prompt now, and stitch it into a finished ad before your coffee goes cold. The workflow is almost stupidly simple: → Tell Claude Opus 4.8 the beauty shot you want (dewy skin macro, gloss-on-lips contact, ripple transition, the works) → Claude turns it into a shot-by-shot storyboard plus a prompt for every frame → GPT Image 2 generates the photoreal stills, frame by frame → Seedance 2.0 animates each one into a clip with that buttery slow-mo glide → You drop the clips into HeyOz and assemble the full ad in one place The real unlock is volume. This isn't one hero video. Once the workflow is dialed, you spin up hundreds of variations. Different shades, different models, different hooks, different transitions. The exact creative volume Meta rewards, minus the production cost that used to make it impossible. Old way: one shoot, one look, $10k+, weeks of waiting. New way: a hundred angles, any look, a few dollars each, same afternoon. I wrote up the entire workflow. The Claude storyboard prompt, the GPT Image 2 frame prompts, the Seedance motion settings, the full assembly flow. Completely free, no email gate. Want it? Comment "GLOSS" and I'll send it straight over. (make sure you're following so it can actually reach you)

Ahad Shams

11,126 görüntüleme • 2 ay önce

THIS GUY JUST REBUILT A $35,000 ANIMATED SITE FOR $12. IF YOU RUN A WEB STUDIO, YOU SHOULD PROBABLY KEEP SCROLLING. Every agency billing $100-149/hr is selling you five departments wearing one invoice. Here’s each one - collapsed into a single agentic session. LAYER 1 - THE CONCEPT ROOM (Claude) Reads the brief, pulls references, and scripts the scroll: what the visitor feels at second 3, second 15, second 40. → Used to be a strategist and a wall of mood boards. Now it’s a conversation. LAYER 2 - THE MOTION STUDIO (Higgsfield) Cinematic clips from 30+ generative models - hero shots, transitions, ambient loops - all matched to the story from Layer 1. → Used to be a motion artist on retainer. Now it’s a prompt. LAYER 3 - THE DEV TEAM (Claude Code) Scaffolds the site, writes the GSAP ScrollTrigger timelines and Lenis smooth-scroll, extracts frames, optimizes every asset. → A full scroll-driven build with zero hand-coded keyframes. LAYER 4 - THE DESIGN DEPT (baked-in cinematic layer) Six effects, zero config: film grain, particles, vignette, glass cards, color tints, scroll pacing. → The polish that justified the invoice - now it ships by default. LAYER 5 - THE QA PASS (Claude) Checks load speed, mobile breakpoints, and whether the scroll actually lands - then rewrites whatever doesn’t. → Used to be a client call and a revision cycle. Now it’s one more turn in the same session. Five departments. One operator. One pass. A strategist, a motion artist, a developer, a designer, and a QA lead - weeks of handoffs - now run in a single session. For a Claude subscription and a few dollars of Higgsfield credits. The studio was never selling talent. It was selling overhead. And the overhead just became five layers. Follow me, reply “website” to this post and I will send you the step-by-step Playbook 👇

ZEUS⚡️

141,226 görüntüleme • 1 ay önce

How a 22-year-old developer built a full 3D Jet Ski racing game in just 40 minutes with zero manual coding He used Claude Opus 5 to generate physics, WebGL 3D graphics, HUD, and audio in a single prompt and turned single-prompt gamedev into a high-margin income stream. Costs: $423 He launched a single-prompt generation workflow that built the entire HTML5 project from scratch: Top layer: A Three.js and WebGL rendering pipeline dynamically creates 3D water physics, real-time wave dynamics, dynamic lighting, and jet ski fluid mechanics, all written autonomously inside one output file without external frameworks. Bottom layer: The Claude Opus 5 engine processed a massive 690-million-token context window to generate the complete gameplay logic, collision handling, dynamic sound generation, controls, and UI layout directly from a detailed initial system prompt. The trend of single-prompt 3D game creation is rapidly exploding across media and indie development. The author monetizes this tech stack through three main channels: 1. Viral Content & Media Systems: Short-form breakdown videos driving massive reach, monetized via promo placements, prompt-pack access, and private developer communities. 2. Rapid Hypercasual Prototyping: Testing 10+ WebGL mechanics per day, flipping fully functional browser games on itch io or CodeCanyon, and licensing prototypes directly to casual game portals. 3. Interactive WebGL Client Solutions: Delivering custom 3D promotional browser games and interactive brand experiences for clients in 48 hours instead of weeks. First month results: > WebGL games generated: 24 > Viral impressions generated: 3.8M+ > Total revenue across licensing & content: $21,400 The AI completely automated the core development lifecycle: Claude Opus 5 built the physics engine, rendered 3D graphics in WebGL, hooked up audio controllers, and generated interactive browser logic with zero manual line-by-line coding. Bookmark it and check article 👇

Ridark

11,592 görüntüleme • 13 gün önce

EVERYONE'S TRYING TO SOLVE AI TEAM MEMORY WITH SERVERS, VECTOR DATABASES, AND ORCHESTRATION PLATFORMS. THIS OPEN SOURCE TOOL DOES IT WITH ONE FOLDER IN YOUR REPO. Every dev on your team runs Claude Code. When one agent screws something up, the rest have no idea. They just repeat the mistake next week. It's called teamlore. When your agent gets corrected or breaks something, it writes a small lore file into a .lore/ folder. That file ships with your PR, gets reviewed like normal code, and after merge every teammate's agent automatically recalls it when they touch that part of the repo. No server. No datab No accounts. No SaaS bill. Just a folder in git. Which means code review catches bad lessons before they poison the team, git blame tells you when a rule was added and why, and the whole thing works offline. One command to install: npx teamlore init Companion command: npx teamlore scarmap. Turns your team's history of mistakes into a visual heat map of the codebase. Every red zone is a place your team has been burned before. Which means every red zone is a place your agents should slow down. Here's the wildest part. The teamlore repo's own .lore/ folder contains every mistake Claude made while building teamlore itself. Dogfooded end-to-end. You can literally open the folder and read the receipts. The author's public invitation: "Would love for someone to try and break it." Available on npm. Repo just launched. 100% open source. (link in the comments)

Harman

34,614 görüntüleme • 21 gün önce