Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

Claude Code 2.1.139 has been released. 50 CLI changes, 1 system prompt change Highlights: • Added /goal command to run tasks across turns until a set completion condition, with live elapsed/turns/tokens • System prompt compaction is now silent (no trimming alert), which may obscure that prompts were trimmed •... show more

Claude Code Changelog

77,193 subscribers

230,161 görüntüleme • 2 ay önce •via X (Twitter)

Eğitim Bilim & Teknoloji

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

I got curious how compaction works as a PM, so I did some brain surgery on Claude Code: (Anthropic's been doing really interesting work on context editing - they showed Claude Opus playing Settlers of Catan for 75+ minutes in a single thread by constantly editing the context instead of starting fresh. When I saw that Claude Code has a compaction command with optional custom instructions, I wanted to understand what's actually happening.) Abhishek Katiyar and Aman Khan gave me the key tip: Claude Code stores all your conversation history as text files on your computer. Open a new directory and give Claude Code a task. Here's how to watch compaction happening: 1. Go to your user's root directory 2. Press Command+Shift+Period (Mac) to show hidden folders 3. Navigate to ~/.claude/projects/ 4. Find your project folder and use Cursor/VSCode to open it (there's a reason) 5. Install the JSONL Gazelle plugin (open source, thank you Gabor Cselle!) 6. Open the most recent JSONL file - each row is a message in your conversation 7. Run the compact command in Claude Code with custom instructions 8. Watch what happens in the file What I learned: When you compact, Claude Code doesn't just summarize and delete everything. It creates a "compact boundary" in the conversation file, writes a summary of what happened before, but keeps the full original conversation (!!!!) The new thread can still retrieve any details from before compaction if needed. That is so damn cool. Why this matters: What you're getting in Claude Code is similar to what Anthropic ships in their developer SDK - so inspecting your daily tools is how you build real product intuition. The best way to understand AI systems is to open them up and look inside. Everything is text files.

I got curious how compaction works as a PM, so I did some brain surgery on Claude Code: (Anthropic's been doing really interesting work on context editing - they showed Claude Opus playing Settlers of Catan for 75+ minutes in a single thread by constantly editing the context instead of starting fresh. When I saw that Claude Code has a compaction command with optional custom instructions, I wanted to understand what's actually happening.) Abhishek Katiyar and Aman Khan gave me the key tip: Claude Code stores all your conversation history as text files on your computer. Open a new directory and give Claude Code a task. Here's how to watch compaction happening: 1. Go to your user's root directory 2. Press Command+Shift+Period (Mac) to show hidden folders 3. Navigate to ~/.claude/projects/ 4. Find your project folder and use Cursor/VSCode to open it (there's a reason) 5. Install the JSONL Gazelle plugin (open source, thank you Gabor Cselle!) 6. Open the most recent JSONL file - each row is a message in your conversation 7. Run the compact command in Claude Code with custom instructions 8. Watch what happens in the file What I learned: When you compact, Claude Code doesn't just summarize and delete everything. It creates a "compact boundary" in the conversation file, writes a summary of what happened before, but keeps the full original conversation (!!!!) The new thread can still retrieve any details from before compaction if needed. That is so damn cool. Why this matters: What you're getting in Claude Code is similar to what Anthropic ships in their developer SDK - so inspecting your daily tools is how you build real product intuition. The best way to understand AI systems is to open them up and look inside. Everything is text files.

Tal Raviv

57,910 görüntüleme • 6 ay önce

Spent weeks perfecting AI system prompts. Here's what most people get wrong: They write instructions. I engineer architectures. The difference: ❌ "You are a helpful design assistant. Create landing pages when asked." ✓ "You are a conversion-focused UI architect. End goal: production-ready landing page that converts skeptical B2B buyers. Constraints: no gradients, max 3 colors, 8px radius. Style: swiss minimal, editorial whitespace. Output: section-by-section, not full page. Validate each section against the trust test before proceeding." The 5-step method: 1. Define the end goal first (what does success look like?) 2. Ask AI to draft a system prompt for that goal 3. Extract every important keyword and constraint 4. Rewrite with your domain expertise layered in 5. Run through Gemini Gem to structure it as clear instruction blocks Works on Claude design. Cursor code. Custom agents. Everything. Specificity isn't optional. It's the entire game. Like + reply "INSTRUCT" for my full prompt engineering method. (must be following for DM)

Spent weeks perfecting AI system prompts. Here's what most people get wrong: They write instructions. I engineer architectures. The difference: ❌ "You are a helpful design assistant. Create landing pages when asked." ✓ "You are a conversion-focused UI architect. End goal: production-ready landing page that converts skeptical B2B buyers. Constraints: no gradients, max 3 colors, 8px radius. Style: swiss minimal, editorial whitespace. Output: section-by-section, not full page. Validate each section against the trust test before proceeding." The 5-step method: 1. Define the end goal first (what does success look like?) 2. Ask AI to draft a system prompt for that goal 3. Extract every important keyword and constraint 4. Rewrite with your domain expertise layered in 5. Run through Gemini Gem to structure it as clear instruction blocks Works on Claude design. Cursor code. Custom agents. Everything. Specificity isn't optional. It's the entire game. Like + reply "INSTRUCT" for my full prompt engineering method. (must be following for DM)

MotionViz

21,544 görüntüleme • 7 ay önce

Pi was built when there were already agent harnesses around. Here’s why Mario Zechner(Mario Zechner), found them suboptimal and built Pi, a minimalist self-modifying agent: #1 - Mario initially was a believer in Claude Code: "I was a believer in Claude code because they were the first that packaged agentic search up in a really compelling package. And at the time that fit my workflow really well. Everything around the LLM was kind of nice and tidy and easy to understand. I was super happy. I was proselytising Claude code." #2 - Reverse engineering Claude Code highlighted the degradation that Mario felt as a user: "I personally like simple tools that are stable and that I can rely on. Even if they have non-deterministic parts, all the deterministic parts should be as stable as possible. That was just not the experience with Claude Code around summer 2025. They would take away your control of the context. They would inject stuff behind your back, which is bad. Then, your workflows stopped working because there's now a system reminder that you don't even see in the UI that would modify the behaviour of the model. They would also do this to the system prompt. I built a little service where I can track the progression or evolution of the system, prompt and tool definitions and, with every release, it was messing with stuff. That just messed with my workflows and I don't appreciate that." #3 - PI was built with an appreciation for simple and reliable tools: "If I commit to a development tool, I want it to be a stable, reliable thing like a hammer. I don't want my hammer to break a different spot every day. That's terrible. We need somebody who goes the full velocity kind of way. But I don't want to work with a tool like that."

Pi was built when there were already agent harnesses around. Here’s why Mario Zechner(Mario Zechner), found them suboptimal and built Pi, a minimalist self-modifying agent: #1 - Mario initially was a believer in Claude Code: "I was a believer in Claude code because they were the first that packaged agentic search up in a really compelling package. And at the time that fit my workflow really well. Everything around the LLM was kind of nice and tidy and easy to understand. I was super happy. I was proselytising Claude code." #2 - Reverse engineering Claude Code highlighted the degradation that Mario felt as a user: "I personally like simple tools that are stable and that I can rely on. Even if they have non-deterministic parts, all the deterministic parts should be as stable as possible. That was just not the experience with Claude Code around summer 2025. They would take away your control of the context. They would inject stuff behind your back, which is bad. Then, your workflows stopped working because there's now a system reminder that you don't even see in the UI that would modify the behaviour of the model. They would also do this to the system prompt. I built a little service where I can track the progression or evolution of the system, prompt and tool definitions and, with every release, it was messing with stuff. That just messed with my workflows and I don't appreciate that." #3 - PI was built with an appreciation for simple and reliable tools: "If I commit to a development tool, I want it to be a stable, reliable thing like a hammer. I don't want my hammer to break a different spot every day. That's terrible. We need somebody who goes the full velocity kind of way. But I don't want to work with a tool like that."

The Pragmatic Engineer

62,825 görüntüleme • 2 ay önce

$Hermes + Claude + Higgsfield MCP + ViralBuilder = 💰💰💰 Four tools. One prompt chain. Hook to finished video in 10 minutes. I built a Claude skill that writes shot-by-shot Higgsfield prompts from a single creative brief. ViralBuilder tells you what's winning. The skill turns it into a production-ready prompt. Higgsfield renders it. No creative director. No guessing. No separate tools. Here is the setup: Higgsfield MCP → Open Claude Code → Settings → Connectors → Enter: → Connect your account Hermes → The agent layer running underneath Claude Code → It holds your skills, crons, memory, and routing rules → When you prompt Claude, Hermes feeds it the context it needs ViralBuilder (like Gethookd) → The winning ecom video database → Scrapes top performing ecom videos across platforms → Claude reads the data and extracts what styles, hooks, and formats are actually scaling The skill: video-prompt-builder → Installed inside Claude via Hermes → Takes a creative brief and outputs a full shot-by-shot prompt → Covers camera work, effects, transitions, pacing, and energy arc → Every output is structured for Higgsfield to render without ambiguity No switching apps. No export steps. Everything runs from one place. ▸ FIND WINNING CREATIVE ANGLES ViralBuilder tells you what the market already validated. Claude reads it and extracts the pattern. Prompts to run: "Search ViralBuilder for the top performing ecom videos in [niche] over the last 21 days. Extract the 3 dominant hook styles and rank by view velocity." "Pull the winning video formats in [niche] from ViralBuilder. Which opening 3 seconds appears most across videos spending over $10k?" "Find what video style is scaling right now in [niche] for the US market. UGC, talking head, or product demo. Filter for videos with over 1M views." "Pull the last 30 days of viral ecom hooks in [niche] from ViralBuilder. Cluster by emotional trigger. Which cluster has the most longevity?" You are not guessing at angles. You are reading what the market already spent money validating. ▸ BUILD THE PROMPT WITH THE SKILL This is where the video-prompt-builder skill takes over. You give Claude the winning angle. The skill outputs a complete shot-by-shot prompt with effects, transitions, pacing, and energy arc ready to fire into Higgsfield. Prompts to run: "Use the video-prompt-builder skill. Brief: 15-second UGC ad for [product] in [niche]. Hook style: [style from ViralBuilder]. Tone: direct to camera, US English. Output the full shot-by-shot effects timeline, effects inventory, density map, and energy arc." "Use the video-prompt-builder skill. The dominant hook in [niche] this week is [hook]. Build a 10-second product video prompt that opens with a speed ramp into a close-up product reveal. Include a signature visual effect and a low-density CTA landing." "Use the video-prompt-builder skill. Brief: replicate the pacing and energy of a [style description] video for [product]. Target duration: 20 seconds. Output all four sections. Then generate the video with Higgsfield using the shot-by-shot prompt." The skill outputs four sections every time: → Shot-by-shot effects timeline with camera, movement, and transitions per shot → Master effects inventory showing every technique used and where → Effects density map showing high, medium, and low intensity across the timeline → Energy arc describing how the video opens, builds, and lands That output goes directly into Higgsfield. No rewriting. No translating. ▸ GENERATE THE CREATIVE Claude writes the brief via the skill. Higgsfield MCP builds the video. Both happen in the same session. Prompts to run: "Use the video-prompt-builder skill to write a 15-second UGC prompt for [product]. Hook in the first 3 seconds, speed ramp into product reveal, slow-motion CTA landing. Then generate with Higgsfield in 9:16 format." "Build 3 prompt variations on this winning angle: [angle]. Each variation opens with a different effect — speed ramp, digital zoom, whip pan. Use the video-prompt-builder skill for each. Then generate all three with Higgsfield." "Use the video-prompt-builder skill. Brief: problem-solution ad for [product], 20 seconds, US market. Problem shot at high density, product reveal at medium, result and CTA at low. Generate with Higgsfield in 9:16." No separate tool. No file transfer. The video comes back in the same thread. ▸ CHAIN THE WHOLE STACK One prompt. All four tools firing together. "You are my ad creative director. Hermes has loaded my brand context. Pull the top performing video style in [niche] from ViralBuilder this week. Use the video-prompt-builder skill to write a full shot-by-shot prompt for [product] that replicates that style — 20 seconds, 9:16, US market, hook in the first 3 seconds. Output the effects timeline, inventory, density map, and energy arc. Then generate the video with Higgsfield." That single prompt replaces a half-day of production. The math before this stack: Brief: 30 minutes Script: 1 hour Creative production: 2 to 3 hours Agency or freelancer cost: $500 to $2,000 per creative With this stack: Hook to finished creative: 10 minutes Cost per creative: tool subscription, a fraction of agency rate 5 product tests in the time it used to take to brief one Bad product tests are where US ad budget disappears. $600 to $1,500 per failed test, before you even know if the angle works. This stack shows you what the market already validated before you spend a dollar on production. Hermes = your context layer. Brand, goals, past performance. Claude is always informed. ViralBuilder = your winning video database. See exactly what styles, hooks, and formats are scaling before you produce anything. video-prompt-builder skill = the translation layer. Turns a creative brief into a structured, production-ready Higgsfield prompt every time. Claude = the brain. Reads the market, writes the brief, chains the tools. Higgsfield MCP = the output. Video generated directly from the prompt. No export step. Four tools. One session. 10 minutes. Comment + RT "STACK" and I'll DM you the full workflow + the video-prompt-builder skill file.$

Hermes + Claude + Higgsfield MCP + ViralBuilder = 💰💰💰 Four tools. One prompt chain. Hook to finished video in 10 minutes. I built a Claude skill that writes shot-by-shot Higgsfield prompts from a single creative brief. ViralBuilder tells you what's winning. The skill turns it into a production-ready prompt. Higgsfield renders it. No creative director. No guessing. No separate tools. Here is the setup: Higgsfield MCP → Open Claude Code → Settings → Connectors → Enter: → Connect your account Hermes → The agent layer running underneath Claude Code → It holds your skills, crons, memory, and routing rules → When you prompt Claude, Hermes feeds it the context it needs ViralBuilder (like Gethookd) → The winning ecom video database → Scrapes top performing ecom videos across platforms → Claude reads the data and extracts what styles, hooks, and formats are actually scaling The skill: video-prompt-builder → Installed inside Claude via Hermes → Takes a creative brief and outputs a full shot-by-shot prompt → Covers camera work, effects, transitions, pacing, and energy arc → Every output is structured for Higgsfield to render without ambiguity No switching apps. No export steps. Everything runs from one place. ▸ FIND WINNING CREATIVE ANGLES ViralBuilder tells you what the market already validated. Claude reads it and extracts the pattern. Prompts to run: "Search ViralBuilder for the top performing ecom videos in [niche] over the last 21 days. Extract the 3 dominant hook styles and rank by view velocity." "Pull the winning video formats in [niche] from ViralBuilder. Which opening 3 seconds appears most across videos spending over $10k?" "Find what video style is scaling right now in [niche] for the US market. UGC, talking head, or product demo. Filter for videos with over 1M views." "Pull the last 30 days of viral ecom hooks in [niche] from ViralBuilder. Cluster by emotional trigger. Which cluster has the most longevity?" You are not guessing at angles. You are reading what the market already spent money validating. ▸ BUILD THE PROMPT WITH THE SKILL This is where the video-prompt-builder skill takes over. You give Claude the winning angle. The skill outputs a complete shot-by-shot prompt with effects, transitions, pacing, and energy arc ready to fire into Higgsfield. Prompts to run: "Use the video-prompt-builder skill. Brief: 15-second UGC ad for [product] in [niche]. Hook style: [style from ViralBuilder]. Tone: direct to camera, US English. Output the full shot-by-shot effects timeline, effects inventory, density map, and energy arc." "Use the video-prompt-builder skill. The dominant hook in [niche] this week is [hook]. Build a 10-second product video prompt that opens with a speed ramp into a close-up product reveal. Include a signature visual effect and a low-density CTA landing." "Use the video-prompt-builder skill. Brief: replicate the pacing and energy of a [style description] video for [product]. Target duration: 20 seconds. Output all four sections. Then generate the video with Higgsfield using the shot-by-shot prompt." The skill outputs four sections every time: → Shot-by-shot effects timeline with camera, movement, and transitions per shot → Master effects inventory showing every technique used and where → Effects density map showing high, medium, and low intensity across the timeline → Energy arc describing how the video opens, builds, and lands That output goes directly into Higgsfield. No rewriting. No translating. ▸ GENERATE THE CREATIVE Claude writes the brief via the skill. Higgsfield MCP builds the video. Both happen in the same session. Prompts to run: "Use the video-prompt-builder skill to write a 15-second UGC prompt for [product]. Hook in the first 3 seconds, speed ramp into product reveal, slow-motion CTA landing. Then generate with Higgsfield in 9:16 format." "Build 3 prompt variations on this winning angle: [angle]. Each variation opens with a different effect — speed ramp, digital zoom, whip pan. Use the video-prompt-builder skill for each. Then generate all three with Higgsfield." "Use the video-prompt-builder skill. Brief: problem-solution ad for [product], 20 seconds, US market. Problem shot at high density, product reveal at medium, result and CTA at low. Generate with Higgsfield in 9:16." No separate tool. No file transfer. The video comes back in the same thread. ▸ CHAIN THE WHOLE STACK One prompt. All four tools firing together. "You are my ad creative director. Hermes has loaded my brand context. Pull the top performing video style in [niche] from ViralBuilder this week. Use the video-prompt-builder skill to write a full shot-by-shot prompt for [product] that replicates that style — 20 seconds, 9:16, US market, hook in the first 3 seconds. Output the effects timeline, inventory, density map, and energy arc. Then generate the video with Higgsfield." That single prompt replaces a half-day of production. The math before this stack: Brief: 30 minutes Script: 1 hour Creative production: 2 to 3 hours Agency or freelancer cost: $500 to $2,000 per creative With this stack: Hook to finished creative: 10 minutes Cost per creative: tool subscription, a fraction of agency rate 5 product tests in the time it used to take to brief one Bad product tests are where US ad budget disappears. $600 to $1,500 per failed test, before you even know if the angle works. This stack shows you what the market already validated before you spend a dollar on production. Hermes = your context layer. Brand, goals, past performance. Claude is always informed. ViralBuilder = your winning video database. See exactly what styles, hooks, and formats are scaling before you produce anything. video-prompt-builder skill = the translation layer. Turns a creative brief into a structured, production-ready Higgsfield prompt every time. Claude = the brain. Reads the market, writes the brief, chains the tools. Higgsfield MCP = the output. Video generated directly from the prompt. No export step. Four tools. One session. 10 minutes. Comment + RT "STACK" and I'll DM you the full workflow + the video-prompt-builder skill file.

Kid Pak

57,026 görüntüleme • 2 ay önce

Obsidian + Claude just killed the $35K/year ghostwriter Sounds exactly like you, every time Pulls every relevant note you ever captured Ships finished drafts in under 90 seconds Gets sharper every month, not flatter The 30-minute vault + the voice profile that makes the output indistinguishable from yours Set up the stack: Install Obsidian: → 5 folders (00 CAPTURE → 04 SYSTEM) CLAUDE.md in 04 SYSTEM → 10 of your best pieces + your no-go phrases Tag every note in 01 - ACTIVE with the content vertical it feeds Claude Desktop + Filesystem MCP → reads every note in the vault Output Generator prompt in 04 - SYSTEM/prompts/ → triggered on demand 03 - OUTPUT/ → every draft lands here, linked back to source notes First prompt to Claude: Read my voice profile in CLAUDE.md Read every note tagged with [topic] in 01 - ACTIVE Write a complete draft in my voice - sentence rhythm, idioms, no-go phrases respected Synthesize across notes, don't summarize each Surface 1 angle no individual note contains but the combination supports Save to 03 - OUTPUT/[date]-[topic].md After it works, tune: voice profile (sentence length, idioms, things you'd never say) topic tags (one cluster per vertical - AI, crypto, growth) the "what would my reader push back on?" prompt before publishing draft length per format (thread / essay / newsletter) the Connection Surface (find the angle nobody used yet) the kill list (phrases the ghostwriter is never allowed to write) The numbers: → 4,000 notes → 1 monthly publishable pipeline → 90 seconds from prompt to first draft → 1 voice profile = unlimited content in that voice → 10 source pieces are all you need to train it → Month 3: drafts indistinguishable from your own Full breakdown above 👇

ZEUS⚡️

16,167 görüntüleme • 1 ay önce

Billions of $$ raised to generate images, and none of them let you actually edit what you get. You type a prompt, get something close, try to fix one thing, and the whole image regenerates. Now 50% of what was working is gone. So you prompt again. And again. Stuck in prompt doom loops, burning tokens every single time. The output is always a flat PNG, limiting what you can do with it. Lica World actually reads your image and breaks it into structured, editable layers. You go in, change what you need to change, and everything else stays exactly where it was. Route each layer to the right model or a capable human. You don't need to regenerate from scratch or pay the token tax to fix a font color. Enterprises publishing creatives across site, social, and email are already using Lica to own their model and own their output. We're grateful to be supported by Accel, Amjad Masad, Srinivas Narayanan, South Park Commons, Village Global, and Michele Catasta to build the editing layer that AI image gen has been missing. Want early access? Check the next thread below.

Billions of $$ raised to generate images, and none of them let you actually edit what you get. You type a prompt, get something close, try to fix one thing, and the whole image regenerates. Now 50% of what was working is gone. So you prompt again. And again. Stuck in prompt doom loops, burning tokens every single time. The output is always a flat PNG, limiting what you can do with it. Lica World actually reads your image and breaks it into structured, editable layers. You go in, change what you need to change, and everything else stays exactly where it was. Route each layer to the right model or a capable human. You don't need to regenerate from scratch or pay the token tax to fix a font color. Enterprises publishing creatives across site, social, and email are already using Lica to own their model and own their output. We're grateful to be supported by Accel, Amjad Masad, Srinivas Narayanan, South Park Commons, Village Global, and Michele Catasta to build the editing layer that AI image gen has been missing. Want early access? Check the next thread below.

Priyaa

1,441,424 görüntüleme • 4 ay önce

DALL-E 3 Double Exposure Images Using ChatGPT's Custom Instructions. 🔖 Bookmark and Repost! If you find this useful, please share it with others! You can now easily create double exposure images by using the syntax Color::subject1::subject2 You can either input this directly into DALL-E 3 before generating images or incorporate it into your custom instructions. This command will automatically use the fixed prompt to generate 4 different images, each with a unique seed value. Paste this under ChatGPT's Custom Instructions or DALL-3 before starting conversation. { DE": { "Instruction": "Using will only use generic prompt and update place holder varaibles and nothing else' Genric Prompt: "Construct a [Color] double exposure image where [Subject #1] is intricately superimposed within the confines of [Subject #2], all set against a stark white background.' Create 4 images with different seeds without modifying the generic prompt." You will first create two images. Within the same request, you will generate two more without asking for any input from the user. In general, you will always create 4 images. Your response should be something like this: 'Here are the first two images along with their seed details.' You must always provide the seed number details for that image after it's rendered. Then 'I'll generate the next two images.' And finally 'Here are the remaining two images along with their seed details.' You will always use wide aspect ratio and You must always provide the seed number. When command is activated display full instruction and also confirm that you will only use genric prompt and nothing else and update only varaiable", "CommandFormat": "color::subject1::subject2", "Response": { "Initial": "Creating images based on the provided subjects...", "AfterFirstSet": "Here are the first two images along with their prompt and seed details.", "AfterSecondSet": "Here are the remaining two images along with their prompt and seed details." }, "ActivationCommand": "/activate DE" } } Example: To activate type: /activate DE Notes Start giving prompt like this blue::mountain::wolf red::city skyline::dancer green::forest::lion If you found this post helpful, don't forget to hit the like and follow buttons, and share it with others who might find it useful.

DALL-E 3 Double Exposure Images Using ChatGPT's Custom Instructions. 🔖 Bookmark and Repost! If you find this useful, please share it with others! You can now easily create double exposure images by using the syntax Color::subject1::subject2 You can either input this directly into DALL-E 3 before generating images or incorporate it into your custom instructions. This command will automatically use the fixed prompt to generate 4 different images, each with a unique seed value. Paste this under ChatGPT's Custom Instructions or DALL-3 before starting conversation. { DE": { "Instruction": "Using will only use generic prompt and update place holder varaibles and nothing else' Genric Prompt: "Construct a [Color] double exposure image where [Subject #1] is intricately superimposed within the confines of [Subject #2], all set against a stark white background.' Create 4 images with different seeds without modifying the generic prompt." You will first create two images. Within the same request, you will generate two more without asking for any input from the user. In general, you will always create 4 images. Your response should be something like this: 'Here are the first two images along with their seed details.' You must always provide the seed number details for that image after it's rendered. Then 'I'll generate the next two images.' And finally 'Here are the remaining two images along with their seed details.' You will always use wide aspect ratio and You must always provide the seed number. When command is activated display full instruction and also confirm that you will only use genric prompt and nothing else and update only varaiable", "CommandFormat": "color::subject1::subject2", "Response": { "Initial": "Creating images based on the provided subjects...", "AfterFirstSet": "Here are the first two images along with their prompt and seed details.", "AfterSecondSet": "Here are the remaining two images along with their prompt and seed details." }, "ActivationCommand": "/activate DE" } } Example: To activate type: /activate DE Notes Start giving prompt like this blue::mountain::wolf red::city skyline::dancer green::forest::lion If you found this post helpful, don't forget to hit the like and follow buttons, and share it with others who might find it useful.

AshutoshShrivastava

34,305 görüntüleme • 2 yıl önce

GT Protocol AI Digest No.86: Claude Just Leveled Up Here are five stories worth your attention 👇 🧠 Claude Opus Gets an Upgrade Anthropic released a new Opus model with stronger performance in coding and cybersecurity. The update, alongside its Mythos Preview, points toward more advanced and autonomous AI systems. 🎨 Canva Goes Full Prompt Mode Canva’s AI 2.0 update expands prompt-based editing across the entire design process. Users can now generate and modify layouts, images, and text through simple instructions. 💻 Gemini Moves to Desktop Google launched a native Gemini app for macOS, bringing AI directly into the operating system. Assistants are becoming persistent tools, not just browser features. 🧬 AI Gets Specialized in Biology OpenAI introduced a biology-focused model designed for scientific workflows. AI is moving beyond general use into domain-specific applications. ⚙️ Intel Repositions in the AI Race Intel is aligning with Google’s infrastructure strategy and exploring ties to Musk’s chip projects. The competition is shifting toward hardware and large-scale compute. Read the full digest on our Medium 👉

GT Protocol AI Digest No.86: Claude Just Leveled Up Here are five stories worth your attention 👇 🧠 Claude Opus Gets an Upgrade Anthropic released a new Opus model with stronger performance in coding and cybersecurity. The update, alongside its Mythos Preview, points toward more advanced and autonomous AI systems. 🎨 Canva Goes Full Prompt Mode Canva’s AI 2.0 update expands prompt-based editing across the entire design process. Users can now generate and modify layouts, images, and text through simple instructions. 💻 Gemini Moves to Desktop Google launched a native Gemini app for macOS, bringing AI directly into the operating system. Assistants are becoming persistent tools, not just browser features. 🧬 AI Gets Specialized in Biology OpenAI introduced a biology-focused model designed for scientific workflows. AI is moving beyond general use into domain-specific applications. ⚙️ Intel Repositions in the AI Race Intel is aligning with Google’s infrastructure strategy and exploring ties to Musk’s chip projects. The competition is shifting toward hardware and large-scale compute. Read the full digest on our Medium 👉

GT Protocol

37,782 görüntüleme • 3 ay önce

Claude Code + Nano Banana 2 is f*cking cracked 🤯 I built a system inside Claude Code that researches any brand, writes 40 ad prompts from scratch, and fires them all to Nano Banana 2. One brand name + one URL = 40 production-ready static ads. All inside Claude Code. I took Alex Cooper's brilliant framework and automated the whole thing inside Claude Code. Perfect for DTC brands and agencies who need high-volume ad creative without briefing a designer or spending hours in Canva. If you're finding winning ad concepts on Meta and manually recreating them one at a time in Higgsfield — copying prompts, pasting product details, tweaking aspect ratios, downloading, organizing... This system eliminates the entire loop: → Give Claude a brand name and URL → It researches the brand's fonts, colors, packaging, and photography style → Builds a Brand DNA document from scratch → Fills in Alex's 40 proven ad templates (headline, us vs them, testimonial, UGC, review cards, stat callouts) with brand-specific details → Fires every prompt to Nano Banana 2 with your product photos as reference → Downloads finished ads into organized folders with an HTML gallery No Higgsfield. No manual prompt filling. No copy-pasting between tools. What you get: → 40 ad formats filled with your exact brand colors, fonts, and copy → 4 variations per format so you pick the best output → Product photos passed as reference so the model matches your real packaging → A reusable system — new brand, new folder, same pipeline Built 100% in Claude Code with Nano Banana 2. I put together a full playbook & Loom video showing the exact process to set this up yourself. Want access for free? > Like this post > Comment "NANO" And I'll send it over (must be following so I can DM)

Mike Futia

423,473 görüntüleme • 4 ay önce

One of my favorite upgrades to Claude Cowork right now: Projects Here's the problem it solves: By default, every new thread starts blank Claude has no memory of what you were working on, what other threads figured out, or what your instructions were So you'd re-explain yourself at the start of every session Or your agents would overlap, contradict each other, or miss context that another thread already had If you've been following my Cowork setup guides, you've already solved part of this — local files and a CLAUDE.md get you most of the way there Projects takes it the rest of the way Shared memory across every thread in the project Permanent instructions that apply everywhere — set once, always on Scheduled tasks that prep your work before you open the app One project HQ to launch every agent from The day-one prompt I paste into every new project: "I just created this project. Read every file in the folder. Then summarize what you know about this workspace — what's here, what I probably use it for, and what instructions you'll follow. If anything is unclear, ask me some questions." Run that once and Claude builds its own understanding of your project workspace from scratch Full video with my live build, including my 4 tips for getting Projects right, and where projects still lack. Send to someone whose ready to Do More with AI, or bookmark to implement this weekend!

One of my favorite upgrades to Claude Cowork right now: Projects Here's the problem it solves: By default, every new thread starts blank Claude has no memory of what you were working on, what other threads figured out, or what your instructions were So you'd re-explain yourself at the start of every session Or your agents would overlap, contradict each other, or miss context that another thread already had If you've been following my Cowork setup guides, you've already solved part of this — local files and a CLAUDE.md get you most of the way there Projects takes it the rest of the way Shared memory across every thread in the project Permanent instructions that apply everywhere — set once, always on Scheduled tasks that prep your work before you open the app One project HQ to launch every agent from The day-one prompt I paste into every new project: "I just created this project. Read every file in the folder. Then summarize what you know about this workspace — what's here, what I probably use it for, and what instructions you'll follow. If anything is unclear, ask me some questions." Run that once and Claude builds its own understanding of your project workspace from scratch Full video with my live build, including my 4 tips for getting Projects right, and where projects still lack. Send to someone whose ready to Do More with AI, or bookmark to implement this weekend!

JJ Englert

29,809 görüntüleme • 3 ay önce

Claymotion ads are crushing it on Meta right now. Built a free claude skill to make them 👇 If you've been scrolling Meta lately, you've seen them — stop-motion clay characters, tactile textures, weirdly satisfying to watch. CTRs are 2-3x the feed average. Almost nobody is running them. The problem: they look impossible to make unless you have a studio. They're not. You just need the right prompts. So I packaged the prompt system as a Claude Code skill. It's free. Here's what it does: Paste your product URL. Out comes a full claymotion ad plan: 1/ Shot-by-shot storyboard 5-7 shots with the narrative arc. Setup → product reveal → payoff → CTA. 2/ Image prompt per shot Exact prompt you paste into Midjourney, Nano Banana, or any image gen. Camera angle, lighting, clay texture specs, character details — dialed in for consistency across shots. 3/ Video prompt per shot The animation prompt you paste into Kling, Veo, Seedance, or Sora. Motion direction, pacing, transitions — so the shots actually flow. 4/ VO script per shot Voiceover copy written for rhythm. Timed to the shot length. Hook, body, CTA — all on brand. 5/ Music + sfx direction Tone notes for the track. Specific sfx cues per shot (squish, pop, whoosh) You take the outputs. Paste them into your image + video generators. Stitch the shots. Record the VO. A full claymotion ad in under an hour, at the cost of a few API credits. Instead of $3,000 and 3 weeks with an animation studio. Why claymotion works right now: → Pattern break — nothing else in the feed looks like it → Tactile feel — clay reads as "real" even when AI-generated → High dwell time — people watch the whole thing → Cheap to test — 5-10 variations per product is now feasible Comment "Clay" and I'll send you: → The Claude Code skill (free) → A starter prompt pack → 3 example storyboards so you can see the output (must be connected)

Ahad Shams

16,776 görüntüleme • 3 ay önce

I just cracked the code on AI animation ads 🤯 every one of these cost me 12 cents and under 20 seconds to make Gemini Omni + Claude Code is f*cking wild. i built a system that turns any product into an end-to-end AI animated ad in ANY style you want.. claymation, pixar-style 3D, anime, paper cutout, lego, you name it you drop in your product photo and a one line pitch and it handles everything end to end. images, video, voiceover, music, captions, all generated with AI inside Claude.. AI animation ads are crushing on Meta right now and everyone still assumes you need an expensive editor with a 3-week turnaround time to make one. you don't. you just need the right workflow. Im making full end to end high quality AI animation ads in under 3 minutes with this system and they work just as hard organically on TikTok, reels and shorts so i packaged the whole thing up… here's what you're getting: > every prompt i used across all 8 steps > the exact tool stack + the order to run it in > style recipes for claymation, pixar, anime, wes anderson, retro cartoon + CGI > one system that works for paid Meta AND organic built across Claude Code and Gemini Omni RT + reply 'STYLES' and i'll send it over (must be following so i can dm)

I just cracked the code on AI animation ads 🤯 every one of these cost me 12 cents and under 20 seconds to make Gemini Omni + Claude Code is f*cking wild. i built a system that turns any product into an end-to-end AI animated ad in ANY style you want.. claymation, pixar-style 3D, anime, paper cutout, lego, you name it you drop in your product photo and a one line pitch and it handles everything end to end. images, video, voiceover, music, captions, all generated with AI inside Claude.. AI animation ads are crushing on Meta right now and everyone still assumes you need an expensive editor with a 3-week turnaround time to make one. you don't. you just need the right workflow. Im making full end to end high quality AI animation ads in under 3 minutes with this system and they work just as hard organically on TikTok, reels and shorts so i packaged the whole thing up… here's what you're getting: > every prompt i used across all 8 steps > the exact tool stack + the order to run it in > style recipes for claymation, pixar, anime, wes anderson, retro cartoon + CGI > one system that works for paid Meta AND organic built across Claude Code and Gemini Omni RT + reply 'STYLES' and i'll send it over (must be following so i can dm)

Miko

111,329 görüntüleme • 27 gün önce

GPT-5 is live in Cline. We've been working with OpenAI to get this model ready, and here's our take: it's disciplined, persistent, & highly competent. It's collaborative in planning & and a diligent operator while acting. It plans thoroughly, asks optioned follow-ups when needed, & then gets out of the way and ships code. On long tasks it keeps going before pausing to check in. It follows instructions to the letter. And most importantly -- it writes good code. GPT-5 is like "The Wolf" from Pulp Fiction. Comes in, assesses the situation, then executes. Here's what you can expect from GPT-5 in Cline: > verbose while planning; terse while executing > asks a lot of good clarification questions, & frequently provides options when appropriate > strong context retention and persistence over long horizons (256k context window) > good at diff-style edits and multi-file changes (we'll monitor as more usage data comes in) > quiet in Act mode -- writes code without yapping Metaprompting is another strength. We tested early with OpenAI and used GPT-5 to tune our own prompt for GPT-5. Here's a pattern we like: “Answer from your own perspective: what changes or additions would help you better follow this prompt? Here is the prompt (or snippet): [snippet]. Users have complained about X and Y. What minimal edits would you make while keeping the rest intact?” Do you need to change any of your existing patterns in Cline? No -- it's good out of the box. Give a clear goal and constraints, let it plan, then let it cook. Expect more clarifying questions than most models. Pricing: $1.25/M input tokens (+90% cache), $10/M output. Roughly half of Sonnet 4 ($3/$15). Want to try GPT-5? Use it in Cline today for pure, unfiltered inference via the OpenAI, Cline, or OpenRouter providers. (fyi -- GPT-5 one-shotted this browser DAW below on the prompt "build something impressive to show me what you're capable of")

GPT-5 is live in Cline. We've been working with OpenAI to get this model ready, and here's our take: it's disciplined, persistent, & highly competent. It's collaborative in planning & and a diligent operator while acting. It plans thoroughly, asks optioned follow-ups when needed, & then gets out of the way and ships code. On long tasks it keeps going before pausing to check in. It follows instructions to the letter. And most importantly -- it writes good code. GPT-5 is like "The Wolf" from Pulp Fiction. Comes in, assesses the situation, then executes. Here's what you can expect from GPT-5 in Cline: > verbose while planning; terse while executing > asks a lot of good clarification questions, & frequently provides options when appropriate > strong context retention and persistence over long horizons (256k context window) > good at diff-style edits and multi-file changes (we'll monitor as more usage data comes in) > quiet in Act mode -- writes code without yapping Metaprompting is another strength. We tested early with OpenAI and used GPT-5 to tune our own prompt for GPT-5. Here's a pattern we like: “Answer from your own perspective: what changes or additions would help you better follow this prompt? Here is the prompt (or snippet): [snippet]. Users have complained about X and Y. What minimal edits would you make while keeping the rest intact?” Do you need to change any of your existing patterns in Cline? No -- it's good out of the box. Give a clear goal and constraints, let it plan, then let it cook. Expect more clarifying questions than most models. Pricing: $1.25/M input tokens (+90% cache), $10/M output. Roughly half of Sonnet 4 ($3/$15). Want to try GPT-5? Use it in Cline today for pure, unfiltered inference via the OpenAI, Cline, or OpenRouter providers. (fyi -- GPT-5 one-shotted this browser DAW below on the prompt "build something impressive to show me what you're capable of")

Cline

63,496 görüntüleme • 11 ay önce

This is next-level smart: An open-source platform that evaluates your prompts and automatically refines them based on the results. Of course, it feels obvious after you see it: • You write a prompt • The system evaluates it across different scenarios • Based on the results, it refines it to improve results I recorded a quick video to show you how it works. It's pretty cool stuff! Here are some of the problems and best practices for teams building AI applications: 1. Testing your prompts manually doesn't scale 2. Prompts should not be spread throughout the codebase 3. Non-technical people need easy access to your prompts 4. Prompts can always use a version history to track changes 5. Monitoring the performance of prompts overtime is critical Evaluating the prompts is what keeps me up at night from this list. Of all the conversations I've had with companies and people building AI applications, this is the area that's causing the most pain. Testing a prompt is difficult. Think about how you'd test the response of a model subjectively. What do you account for, "tone," "objectivity," "completeness," "creativity," "readability," etc.? Last week, I met the developers behind Latitude, an open-source prompt engineering platform trying to solve all of these issues. You can try the platform in two ways: • You can self-host the platform. Free and open-source. • If you want to try their online product, their free tier is huge. Here is the link: Thanks to the Latitude team for collaborating with me on this post, and congratulations on going live with their product!

This is next-level smart: An open-source platform that evaluates your prompts and automatically refines them based on the results. Of course, it feels obvious after you see it: • You write a prompt • The system evaluates it across different scenarios • Based on the results, it refines it to improve results I recorded a quick video to show you how it works. It's pretty cool stuff! Here are some of the problems and best practices for teams building AI applications: 1. Testing your prompts manually doesn't scale 2. Prompts should not be spread throughout the codebase 3. Non-technical people need easy access to your prompts 4. Prompts can always use a version history to track changes 5. Monitoring the performance of prompts overtime is critical Evaluating the prompts is what keeps me up at night from this list. Of all the conversations I've had with companies and people building AI applications, this is the area that's causing the most pain. Testing a prompt is difficult. Think about how you'd test the response of a model subjectively. What do you account for, "tone," "objectivity," "completeness," "creativity," "readability," etc.? Last week, I met the developers behind Latitude, an open-source prompt engineering platform trying to solve all of these issues. You can try the platform in two ways: • You can self-host the platform. Free and open-source. • If you want to try their online product, their free tier is huge. Here is the link: Thanks to the Latitude team for collaborating with me on this post, and congratulations on going live with their product!

Santiago

64,157 görüntüleme • 1 yıl önce

There is a strategy for Claude Max users that will 3-5X productivity and vibe coding learning curve. Which most vibe coders don't utilize! Most people using Claude Code just sit and watch the terminal while their prompt cooks. That’s dead time. If you’re on Claude Max, you’re paying for parallel capacity you’re probably not using fully. And tokens get wasted. Here’s a methodology to fix that and boost the way you use Claude forever: The Setup & Workflow 1. Add the repos you’re actively working on to your workspace from your IDE 2. Click “new terminal” and open 3-4 terminal instances, each pointed at a different project 3. Toggle between them on the right side of your terminal panel 4. When one terminal is cooking a prompt, look at the others 5. Use the time Claude is working to prompt the next project 6. Continuously rotate and ship across 3-4 projects like this 7. Use your tokens effectively, build more, learn faster The Result You ship 3-4 projects simultaneously. You burn through your token allocation on actual output instead of letting it sit unused. You learn faster because you’re getting more reps in the same amount of time, too. As long as you work on different projects at the same time like this, it will only be a boost in productivity, with no chance for code to get spaghetti. In the video, you can see where to find add workspace, run new terminal, and change between terminals:

There is a strategy for Claude Max users that will 3-5X productivity and vibe coding learning curve. Which most vibe coders don't utilize! Most people using Claude Code just sit and watch the terminal while their prompt cooks. That’s dead time. If you’re on Claude Max, you’re paying for parallel capacity you’re probably not using fully. And tokens get wasted. Here’s a methodology to fix that and boost the way you use Claude forever: The Setup & Workflow 1. Add the repos you’re actively working on to your workspace from your IDE 2. Click “new terminal” and open 3-4 terminal instances, each pointed at a different project 3. Toggle between them on the right side of your terminal panel 4. When one terminal is cooking a prompt, look at the others 5. Use the time Claude is working to prompt the next project 6. Continuously rotate and ship across 3-4 projects like this 7. Use your tokens effectively, build more, learn faster The Result You ship 3-4 projects simultaneously. You burn through your token allocation on actual output instead of letting it sit unused. You learn faster because you’re getting more reps in the same amount of time, too. As long as you work on different projects at the same time like this, it will only be a boost in productivity, with no chance for code to get spaghetti. In the video, you can see where to find add workspace, run new terminal, and change between terminals:

Meta Alchemist

82,000 görüntüleme • 6 ay önce

Claude Code + Shopify AI is f*cking cracked 🤯 Shopify just dropped an official AI Toolkit that connects Claude Code directly to your store. One prompt → Claude reads your products, rewrites your descriptions for AI shopping, and pushes the updates live. All from the terminal. All inside Claude Code. Perfect for DTC brands on Shopify who are still manually editing product pages, writing descriptions in Google Docs, and copy-pasting into the Shopify admin one product at a time. Claude Code + the Shopify AI Toolkit fixes the entire workflow: → Install the official Shopify plugin in Claude Code → Authenticate to your store → Claude reads your entire product catalog → Rewrites every description to be optimized for AI shopping → Pushes the updates directly to your store automatically → Validates every API call against Shopify's official docs before executing No Shopify admin tab-switching. No copy-pasting from a Google Doc. No hiring a copywriter to rewrite 50 product pages. What you get: → Claude Code connected directly to your live Shopify store → Product descriptions optimized for how ChatGPT, Gemini, and Perplexity recommend products → Bulk updates across your entire catalog from a single prompt → Full access to Shopify's GraphQL API — products, themes, inventory, orders, everything Claude can read and write → An official plugin built by Shopify that auto-updates as new features ship I put together a full playbook with the plugin install, the store authentication walkthrough, 5 DTC workflows to run on day one, and the exact prompts I used. Want it for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Claude Code + Shopify AI is f*cking cracked 🤯 Shopify just dropped an official AI Toolkit that connects Claude Code directly to your store. One prompt → Claude reads your products, rewrites your descriptions for AI shopping, and pushes the updates live. All from the terminal. All inside Claude Code. Perfect for DTC brands on Shopify who are still manually editing product pages, writing descriptions in Google Docs, and copy-pasting into the Shopify admin one product at a time. Claude Code + the Shopify AI Toolkit fixes the entire workflow: → Install the official Shopify plugin in Claude Code → Authenticate to your store → Claude reads your entire product catalog → Rewrites every description to be optimized for AI shopping → Pushes the updates directly to your store automatically → Validates every API call against Shopify's official docs before executing No Shopify admin tab-switching. No copy-pasting from a Google Doc. No hiring a copywriter to rewrite 50 product pages. What you get: → Claude Code connected directly to your live Shopify store → Product descriptions optimized for how ChatGPT, Gemini, and Perplexity recommend products → Bulk updates across your entire catalog from a single prompt → Full access to Shopify's GraphQL API — products, themes, inventory, orders, everything Claude can read and write → An official plugin built by Shopify that auto-updates as new features ship I put together a full playbook with the plugin install, the store authentication walkthrough, 5 DTC workflows to run on day one, and the exact prompts I used. Want it for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Mike Futia

113,232 görüntüleme • 3 ay önce

“We’ve got /loop, /goal, and workflows. They all get the agent to run for long periods of time.” Here’s my new episode with Thariq from the Claude Code team, where he shared how he plans, builds, and runs loops with Claude Code: → How /loop, /goal, and workflows work differently → Live demo: Editing launch videos with Claude → Using HTML artifacts to plan and learn Some quotes from Thariq: “We cut Claude Code’s system prompt by 80%. As models have gotten smarter, they need less direction, fewer constraints, and fewer examples.” “Planning is an iterative process of exploring, investigating, and finding out what you don’t know.” “One failure mode I see is that people glaze over AI’s plans. You want to make sure it’s something you read.” I've been wanting to interview Thariq for a long time and I learned so much from this epsiode. 📌 Watch now: Thanks to our sponsors: Riverside: All-in-one AI studio for podcasts and video Wispr Flow: 4x faster than typing with your voice

“We’ve got /loop, /goal, and workflows. They all get the agent to run for long periods of time.” Here’s my new episode with Thariq from the Claude Code team, where he shared how he plans, builds, and runs loops with Claude Code: → How /loop, /goal, and workflows work differently → Live demo: Editing launch videos with Claude → Using HTML artifacts to plan and learn Some quotes from Thariq: “We cut Claude Code’s system prompt by 80%. As models have gotten smarter, they need less direction, fewer constraints, and fewer examples.” “Planning is an iterative process of exploring, investigating, and finding out what you don’t know.” “One failure mode I see is that people glaze over AI’s plans. You want to make sure it’s something you read.” I've been wanting to interview Thariq for a long time and I learned so much from this epsiode. 📌 Watch now: Thanks to our sponsors: Riverside: All-in-one AI studio for podcasts and video Wispr Flow: 4x faster than typing with your voice

Peter Yang

184,489 görüntüleme • 6 gün önce

Your competitor spent 8 months and $50K building an AI voice agent SaaS. You typed one prompt on naïve and shipped the same thing today. That is not an exaggeration. That is exactly what just happened. 🔗 I opened Naive, typed one sentence, and watched a full team of AI employees spin up and start building my AI voice agent SaaS platform from scratch. No dev agency. No co-founder. No seed round. No 8-month runway burn. Here's what my team built, and is running right now: 🔧 Engineer: architected the entire platform, wrote production code, shipped without a single review from me. 📞 Sales rep: started booking demos with potential customers before the platform was even fully live. 🎧 Support agent: set up the entire ticket system and started handling user queries from day one. 💰 Finance manager: set up revenue tracking, reconciled accounts, and started generating reports automatically. Each one has their own email inbox, bank account, phone number, and workspace. They share context. They delegate tasks to each other. They get sharper with every user onboarded and every bug resolved. My entire prompt: "Build me an AI voice agent SaaS platform." That's all I typed. Then I walked away. No technical background. No dev experience. No agency retainer required. What founders on this platform are seeing right now: → Real ARR with zero human employees → +32% revenue growth week over week → +42% tasks completed week over week You have a SaaS idea sitting in your head right now. One prompt on naïve and it's already shipping. Your competitor burned 8 months to get where you'll be in 10 minutes. 👉 #NaïveAI2B9YHR

Your competitor spent 8 months and $50K building an AI voice agent SaaS. You typed one prompt on naïve and shipped the same thing today. That is not an exaggeration. That is exactly what just happened. 🔗 I opened Naive, typed one sentence, and watched a full team of AI employees spin up and start building my AI voice agent SaaS platform from scratch. No dev agency. No co-founder. No seed round. No 8-month runway burn. Here's what my team built, and is running right now: 🔧 Engineer: architected the entire platform, wrote production code, shipped without a single review from me. 📞 Sales rep: started booking demos with potential customers before the platform was even fully live. 🎧 Support agent: set up the entire ticket system and started handling user queries from day one. 💰 Finance manager: set up revenue tracking, reconciled accounts, and started generating reports automatically. Each one has their own email inbox, bank account, phone number, and workspace. They share context. They delegate tasks to each other. They get sharper with every user onboarded and every bug resolved. My entire prompt: "Build me an AI voice agent SaaS platform." That's all I typed. Then I walked away. No technical background. No dev experience. No agency retainer required. What founders on this platform are seeing right now: → Real ARR with zero human employees → +32% revenue growth week over week → +42% tasks completed week over week You have a SaaS idea sitting in your head right now. One prompt on naïve and it's already shipping. Your competitor burned 8 months to get where you'll be in 10 minutes. 👉 #NaïveAI2B9YHR

Gina Acosta

15,888 görüntüleme • 2 ay önce

This Chinese developer runs 9 agents on Claude Code under a GPT-5.5 orchestrator and they close 500 client tasks a month without a single assistant. His client work is closed without him, on a single laptop and only three subscriptions. The entire system lives on one MacBook Pro M4 with 128 GB of memory and subscriptions to Claude Code and GPT-5.5 cost him approximately $300 a month. There is no CRM, no team, no office only a terminal window with 9 parallel streams. The orchestrator works with a simple system prompt: «You are the orchestrator of a client inbox. Classify every incoming email into 4 categories: code, content, analysis, communication. Delegate to the corresponding worker agent. When the result is ready, check it for completeness, send it to the client on my behalf, and mark the task as closed. Do not ask clarifying questions.» And the orchestrator checks the inbox every 30 seconds, classifies fresh emails, and distributes them to 9 worker agents on Claude Code, each of whom is responsible for their own class of tasks. Here is an example of how one of them closes a request to refactor a client's auth module: Task: refactor user-auth module Broke the monolith into 3 files by responsibilities Added unit tests, coverage increased to 87% Renamed 4 functions to camelCase according to the style guide PR is ready for review, link below» And so about 50 cycles a day. By noon 25 tasks are closed, by dinner 50, and by the end of the month 500. On average, it takes about 7 minutes from the appearance of an email in the inbox to sending the result to the client. This is more than what a live team of 6 developers, copywriters and analysts working 8 hours a day closes. This is no longer an agency. This is a workstation where an orchestrator replaces a manager, and 9 worker agents replace the staff. The pipeline goes from inbox to closing 500 times a month without human participation at any step.

This Chinese developer runs 9 agents on Claude Code under a GPT-5.5 orchestrator and they close 500 client tasks a month without a single assistant. His client work is closed without him, on a single laptop and only three subscriptions. The entire system lives on one MacBook Pro M4 with 128 GB of memory and subscriptions to Claude Code and GPT-5.5 cost him approximately $300 a month. There is no CRM, no team, no office only a terminal window with 9 parallel streams. The orchestrator works with a simple system prompt: «You are the orchestrator of a client inbox. Classify every incoming email into 4 categories: code, content, analysis, communication. Delegate to the corresponding worker agent. When the result is ready, check it for completeness, send it to the client on my behalf, and mark the task as closed. Do not ask clarifying questions.» And the orchestrator checks the inbox every 30 seconds, classifies fresh emails, and distributes them to 9 worker agents on Claude Code, each of whom is responsible for their own class of tasks. Here is an example of how one of them closes a request to refactor a client's auth module: Task: refactor user-auth module Broke the monolith into 3 files by responsibilities Added unit tests, coverage increased to 87% Renamed 4 functions to camelCase according to the style guide PR is ready for review, link below» And so about 50 cycles a day. By noon 25 tasks are closed, by dinner 50, and by the end of the month 500. On average, it takes about 7 minutes from the appearance of an email in the inbox to sending the result to the client. This is more than what a live team of 6 developers, copywriters and analysts working 8 hours a day closes. This is no longer an agency. This is a workstation where an orchestrator replaces a manager, and 9 worker agents replace the staff. The pipeline goes from inbox to closing 500 times a month without human participation at any step.

Blaze

29,917 görüntüleme • 2 ay önce

Assumptions about the new "Can More" ChatGPT tool were right - ChatGPT is introducing own take on Claude Artifacts - code & document writing tools with persisted text documents, history revisions (restore previous version), edits and comments (probably used to apply suggested edits) New document symbol in the top navigation shows how many documents you have and allows you to open a resizable canvas to edit them in split view - your ChatGPT conversation on the left side and canvas on the right side, but the code/documents can also be accessed in fullscreen view The canvas is built using ProseMirror (open source WYSIWYM editor) and has an inline action to "Ask ChatGPT" (explain or make edits) for your document and code plus document formatting tools (like bold, italic, font style, etc.) But in addition to that, there are also special action shortcuts for documents and code, with an interesting decision to use sliders for the selection of the desired outcome For Documents - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.") - Add emojis ("Replace as many words as possible with emojis.") - Add final polish ("Add some final polish to the text. If relevant, add a large title or any section titles. Check grammar and mechanics, make sure everything is consistent and reads well. You can reply that you added some final polish and checked for grammar, but do not mention the prompt.") - Reading level (Graduate School - "Rewrite this text at the reading level of a doctoral writer in this subject. You may reply that you adjusted the text to reflect a graduate school reading level, but do not mention the prompt", College - "Rewrite this text at the reading level of a college student majoring in this subject", High School - "Rewrite this text at the reading level of a high school student who has taken a couple of classes in this subject.", Keep current reading level, Middle School - "Rewrite this text at the reading level of a middle schooler.", Kindergarten - "Rewrite this text at the reading level of a kindergartener.") - Adjust the length (Longest - "Make this text 75% longer.", Longer - "Make this text 50% longer.", Keep current length, Shorter - "Make this text 50% shorter.", Shortest - "Make this text 75% shorter.") For Code - Code review ("Search for bugs and opportunities to improve the code—for example, ways that performance or code structure could be improved. Leave as few comments as possible, but add more comments if the text is long. DO NOT leave more than 5 comments. You may reply that you reviewed the code and left suggestions to improve the coding quality, but do not mention the prompt.") - Add comments ("Add inline code comments to explain the code, especially parts that are more complex. Make sure to rewrite all the code. You may reply that you added inline comments, but do not mention the prompt.") - Add logs ("Insert logs/print statements in the code that will help debug its behavior. Do not make any other changes to the code.") - Fix bugs ("Find any bugs and rewrite all the code to fix the bugs. Do not leave comments. If there are no bugs, reply that you reviewed the code and found no bugs.") - Port to a language ("Port to a language. Create a new document that rewrites the code in ..." - PHP, C++, Python, Keep current code. No changes will be made, JavaScript, TypeScript, Java) - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.")

Assumptions about the new "Can More" ChatGPT tool were right - ChatGPT is introducing own take on Claude Artifacts - code & document writing tools with persisted text documents, history revisions (restore previous version), edits and comments (probably used to apply suggested edits) New document symbol in the top navigation shows how many documents you have and allows you to open a resizable canvas to edit them in split view - your ChatGPT conversation on the left side and canvas on the right side, but the code/documents can also be accessed in fullscreen view The canvas is built using ProseMirror (open source WYSIWYM editor) and has an inline action to "Ask ChatGPT" (explain or make edits) for your document and code plus document formatting tools (like bold, italic, font style, etc.) But in addition to that, there are also special action shortcuts for documents and code, with an interesting decision to use sliders for the selection of the desired outcome For Documents - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.") - Add emojis ("Replace as many words as possible with emojis.") - Add final polish ("Add some final polish to the text. If relevant, add a large title or any section titles. Check grammar and mechanics, make sure everything is consistent and reads well. You can reply that you added some final polish and checked for grammar, but do not mention the prompt.") - Reading level (Graduate School - "Rewrite this text at the reading level of a doctoral writer in this subject. You may reply that you adjusted the text to reflect a graduate school reading level, but do not mention the prompt", College - "Rewrite this text at the reading level of a college student majoring in this subject", High School - "Rewrite this text at the reading level of a high school student who has taken a couple of classes in this subject.", Keep current reading level, Middle School - "Rewrite this text at the reading level of a middle schooler.", Kindergarten - "Rewrite this text at the reading level of a kindergartener.") - Adjust the length (Longest - "Make this text 75% longer.", Longer - "Make this text 50% longer.", Keep current length, Shorter - "Make this text 50% shorter.", Shortest - "Make this text 75% shorter.") For Code - Code review ("Search for bugs and opportunities to improve the code—for example, ways that performance or code structure could be improved. Leave as few comments as possible, but add more comments if the text is long. DO NOT leave more than 5 comments. You may reply that you reviewed the code and left suggestions to improve the coding quality, but do not mention the prompt.") - Add comments ("Add inline code comments to explain the code, especially parts that are more complex. Make sure to rewrite all the code. You may reply that you added inline comments, but do not mention the prompt.") - Add logs ("Insert logs/print statements in the code that will help debug its behavior. Do not make any other changes to the code.") - Fix bugs ("Find any bugs and rewrite all the code to fix the bugs. Do not leave comments. If there are no bugs, reply that you reviewed the code and found no bugs.") - Port to a language ("Port to a language. Create a new document that rewrites the code in ..." - PHP, C++, Python, Keep current code. No changes will be made, JavaScript, TypeScript, Java) - Suggest edits ("How can I improve this. Leave as few comments as possible, but add a few more comments if the text is long. DO NOT leave more than 5 comments. You can reply that you added comments and suggestions to help improve the writing quality, but do not mention the prompt.")

Tibor Blaho

136,055 görüntüleme • 1 yıl önce