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

SOMEONE BUILT A CLAUDE CODE PLUGIN THAT REFUSES TO WORK UNTIL YOU DO PUSH-UPS OR SQUATS its called workout gate and it is exactly as cursed as it sounds when the hook fires, it blocks your prompt, opens your webcam, and makes you exercise to keep coding > it... counts your reps live through the webcam with mediapipe, no honor system rounding down > only releases your prompt once you actually finish the reps > quit halfway and the leftover reps get saved as debt for your next session > chill, demo and hardcore presets, plus prompt based, time based or random triggers > tracks stats, streaks and personal records right in the claude code statusline we automated the coding, now we're automating the part where we actually take care of ourselvesshow more

Om Patel

26,834 subscribers

670,125 görüntüleme • 1 ay önce •via X (Twitter)

Sağlık & İyilik 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

20 days ago, I connected Claude Code to my newly created instagram handle.. I gained 4.3M views and 6500+ followers in less than a month [ i post Ai generated animated stories ] Full workflow: i let claude study my account before i write another reel.. This is the cleanest content workflow i've built on claude. give it your IG first. 4 prompts handle the rest.. niche research, the reel script, the hook, and the daily automation.. the whole loop is basically, give claude your IG → find what's working → write retention-optimized scripts → engineer the hook → automate the daily output.. ▫️ Setup: give claude your instagram open claude code. claude code has a built-in web tool that browses any public URL. or install any agentic browser like Browser Harness or Firecrawl or Comet browser paste this with your handle filled in: "Browse and pull the last 30 reels and posts. Analyze my recurring topics, top-performing hooks, formats, and engagement patterns. Then map out my actual audience and what they consistently respond to." claude reads your profile, pulls every reel down, and now has the context to personalize every prompt below to YOUR account, not a generic niche. if you're on claude desktop, the same works with firecrawl MCP connected. ▫️ Prompt 1 find what actually goes viral in your niche: "Analyze the highest-performing Instagram Reels, TikToks, and Reddit posts in the [niche] niche from the last 30 days. Identify repeating hooks, visual styles, emotional triggers, and content formats that consistently generate high engagement. Then summarize the 5 strongest content angles optimized for AI-generated content and short-form videos." run this after the setup. you get 5 angles backed by what's already working in your niche, cross-checked against what's already working on YOUR account. ▫️ Prompt 2 write a high-retention reel script "Write a short-form Instagram Reel script about [topic] with an aggressive hook in the first 2 seconds. Create immediate curiosity, tension, or controversy to stop scrolling, then deliver a fast and satisfying payoff. Keep it under 30 seconds and optimize the structure for watch time, replays, comments, and shares. Finish with a subtle CTA." the line that matters: "optimize the structure for watch time, replays, comments, and shares." claude writes for the metrics, not just the word count. ▫️ Prompt 3 engineer better hooks "Study the top-performing Reels in [niche] and break down the hook structure, pacing, and emotional triggers used in the first 3 seconds. Then generate 5 new hook variations that are even more curiosity-driven, emotionally charged, and optimized to stop scrolling instantly. Focus on triggers like surprise, fear, ego, urgency, or desire." most reels die in the first 2 seconds. this prompt has claude reverse-engineer what already works, then give you 5 sharper versions to swap in. ▫️ Prompt 4 automate the whole workflow "Build a complete AI-powered content workflow for Instagram in the [niche] niche. The system should identify trending topics daily, generate high-retention scripts, create matching AI visuals, turn them into short-form videos, and generate optimized captions and hashtags. Structure everything as a repeatable workflow designed for consistent daily posting and growth." once the niche and script structure are validated, this turns it into a daily loop. one prompt that handles topic → script → visual → video → caption. these 4 prompts are the building blocks. the setup is what makes them yours. your real value is in the [niche] you plug in. content workflow built in one weekend, daily posting on autopilot from monday.

Axel Bitblaze 🪓

199,569 görüntüleme • 1 ay önce

Marketers. I’m begging you. Stop prompting Claude 12+ times when it can be done in 1. Most marketers open Claude and start typing whatever comes to mind. Several rounds later, you’re editing mediocre output by hand. My team built a prompt auditing tool that reads your work, grades it, and gets you to 95% in minutes. It’s based on the RCTC framework, which answers the 4 questions Claude actually needs to be effective: Role - WHO is this for? Channel - WHERE is this going? Task - WHAT outcome is the output getting to? Constraints - WHAT bad output sounds like? Then automatically edits your work so you’re more effective in Claude, ChatGPT, or Gemini. Comment “GA” and I’ll send you the tool.

Marketers. I’m begging you. Stop prompting Claude 12+ times when it can be done in 1. Most marketers open Claude and start typing whatever comes to mind. Several rounds later, you’re editing mediocre output by hand. My team built a prompt auditing tool that reads your work, grades it, and gets you to 95% in minutes. It’s based on the RCTC framework, which answers the 4 questions Claude actually needs to be effective: Role - WHO is this for? Channel - WHERE is this going? Task - WHAT outcome is the output getting to? Constraints - WHAT bad output sounds like? Then automatically edits your work so you’re more effective in Claude, ChatGPT, or Gemini. Comment “GA” and I’ll send you the tool.

Jesse Pujji

10,758 görüntüleme • 2 ay önce

New Feature Live!🚨 Introducing Prompt Assist—a feature designed to streamline your prompt-writing experience with Alchemist AI. Prompt Assist integrates a speed-oriented AI model that analyzes your input as you write, offering contextually relevant suggestions in real-time. Here’s how it works: • Real-Time Suggestions: Prompt Assist dynamically processes your input, predicting next steps from your initial wording. Press Tab to accept suggestions and seamlessly complete your prompt. • Smart Context Analysis: The feature leverages natural language processing models to understand the structure and intent of your prompt, this ensures the suggestions remain precise and useful.

New Feature Live!🚨 Introducing Prompt Assist—a feature designed to streamline your prompt-writing experience with Alchemist AI. Prompt Assist integrates a speed-oriented AI model that analyzes your input as you write, offering contextually relevant suggestions in real-time. Here’s how it works: • Real-Time Suggestions: Prompt Assist dynamically processes your input, predicting next steps from your initial wording. Press Tab to accept suggestions and seamlessly complete your prompt. • Smart Context Analysis: The feature leverages natural language processing models to understand the structure and intent of your prompt, this ensures the suggestions remain precise and useful.

ALCHEMIST AI 🔮

37,880 görüntüleme • 1 yıl önce

Simplicity is at the heart of great software. This is one of the reasons why Claude Code has been sticky for me. As a builder, I love planning and brainstorming, and this is now a key focus of Claude Code. I use Shift + Tab a lot to cycle between brainstorming, planning, and execution. This functionality provides the appropriate interface for me to either be very involved or less involved as I please. This works particularly well when building out new and complex features or entire new projects. This saves a huge amount of time. It allows me to tune Claude Code to execute and build more effectively. It also builds a loop of trust, and I often (surprisingly) find Claude Code asking for clarifications when it's confused. Coding agents don't normally do that. I have shared before on the power of brainstorming with AI for longer times. Try it and you will not be disappointed. Vibe coding is fun, but pair it with intentional development cycles, and you watch how far you can take a project with coding agents today.

Simplicity is at the heart of great software. This is one of the reasons why Claude Code has been sticky for me. As a builder, I love planning and brainstorming, and this is now a key focus of Claude Code. I use Shift + Tab a lot to cycle between brainstorming, planning, and execution. This functionality provides the appropriate interface for me to either be very involved or less involved as I please. This works particularly well when building out new and complex features or entire new projects. This saves a huge amount of time. It allows me to tune Claude Code to execute and build more effectively. It also builds a loop of trust, and I often (surprisingly) find Claude Code asking for clarifications when it's confused. Coding agents don't normally do that. I have shared before on the power of brainstorming with AI for longer times. Try it and you will not be disappointed. Vibe coding is fun, but pair it with intentional development cycles, and you watch how far you can take a project with coding agents today.

elvis

81,765 görüntüleme • 9 ay önce

Claude Design + Shopify is f*cking ridiculous 🤯 You can now publish pages from Claude Design → Claude Code → Shopify. Built 100% with Claude Design, Claude Code, and the Shopify CLI. Perfect for DTC brands and agencies who want to skip the design → dev handoff entirely. Here's how it works: → Design any landing page in Claude Design → Export as a zip and drop it into Claude Code → Install the Shopify + Shopify AI Toolkit plugins → Prompt Claude to convert the HTML into a Shopify page template + push to live theme → Claude uploads the images, deploys the files, and creates a published page No more handing designs off to a dev and waiting 2 weeks for a Shopify page. What you get: - A workflow that turns any Claude Design page into a real Shopify page template - Editable sections so your marketing team can swap copy, images, and CTAs without code - Images uploaded straight to Shopify Files automatically - A files-only deploy that only touches what's new in your live theme - A repeatable pipeline you can use every time you design a new landing page This is essentially the design-to-deploy pipeline brands have been waiting for. I put together a step-by-step playbook for going from Claude Design → published Shopify page. Every install, every plugin, every command, and the exact prompt that runs the whole thing. Want the playbook for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Claude Design + Shopify is f*cking ridiculous 🤯 You can now publish pages from Claude Design → Claude Code → Shopify. Built 100% with Claude Design, Claude Code, and the Shopify CLI. Perfect for DTC brands and agencies who want to skip the design → dev handoff entirely. Here's how it works: → Design any landing page in Claude Design → Export as a zip and drop it into Claude Code → Install the Shopify + Shopify AI Toolkit plugins → Prompt Claude to convert the HTML into a Shopify page template + push to live theme → Claude uploads the images, deploys the files, and creates a published page No more handing designs off to a dev and waiting 2 weeks for a Shopify page. What you get: - A workflow that turns any Claude Design page into a real Shopify page template - Editable sections so your marketing team can swap copy, images, and CTAs without code - Images uploaded straight to Shopify Files automatically - A files-only deploy that only touches what's new in your live theme - A repeatable pipeline you can use every time you design a new landing page This is essentially the design-to-deploy pipeline brands have been waiting for. I put together a step-by-step playbook for going from Claude Design → published Shopify page. Every install, every plugin, every command, and the exact prompt that runs the whole thing. Want the playbook for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Mike Futia

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

next, here is how to animate the video once you generated the base image of your ai model, attach the image of your model and the product image in your ai tool and prompt, "she is holding this product" now to animate this scene, use such a simple prompt; "the girl is speaking in her beautiful voice; "this is the most powerful drink in the world... drink it once, and your whole hair is gone" no background music, no sound effects." adding "no background music" is necessory part when you're prompting to VEO 3 or Kling 2.6 and for the drinking scene, i also gave it a very simple prompt; "the girl is drinking, handheld camera shaking. No background music," then i asked nb pro to remove her hair, and then turn it into the using that simple prompt method. note; simple prompts works better than complicated one when it comes to animating your video that's it, if you need any help setting up your ai influencer to promote your product/app or service just DM me here on 𝕏 or comment "want" i'll dm you myself if you know how to make viral content + setup such a beautiful ai model 2026 will be yours, cheers

next, here is how to animate the video once you generated the base image of your ai model, attach the image of your model and the product image in your ai tool and prompt, "she is holding this product" now to animate this scene, use such a simple prompt; "the girl is speaking in her beautiful voice; "this is the most powerful drink in the world... drink it once, and your whole hair is gone" no background music, no sound effects." adding "no background music" is necessory part when you're prompting to VEO 3 or Kling 2.6 and for the drinking scene, i also gave it a very simple prompt; "the girl is drinking, handheld camera shaking. No background music," then i asked nb pro to remove her hair, and then turn it into the using that simple prompt method. note; simple prompts works better than complicated one when it comes to animating your video that's it, if you need any help setting up your ai influencer to promote your product/app or service just DM me here on 𝕏 or comment "want" i'll dm you myself if you know how to make viral content + setup such a beautiful ai model 2026 will be yours, cheers

ViralOps

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

When you train in the 10-12 rep range, most of your reps have no direct effect on growth. When you train in the 4-6 range, virtually all of your reps are growth reps. Both ranges can build muscle. The mechanism doesn't care about the rep count. It cares about how close you get to true failure on the reps where the high-threshold motor units are recruited and every available fibre is firing. Those are the stimulating reps. Everything else is filler. The catch with 10-12 is twofold. First, only the last 4-5 reps in a 12-rep set are actually stimulating. The first seven are buffer. They generate fatigue, lactic acid, and joint wear that the muscle has to push through before any growth signal arrives. Effort, yes. Stimulus, no. Second, and this is where the high-rep crowd quietly come undone: the long set produces so much afferent feedback (burning, gasping, the legs giving a small philosophical speech) that almost nobody actually takes the set to true failure. They stop two, three, sometimes four reps short, mistake the discomfort for the limit, and call it a hard set. The stimulating reps they were chasing never showed up. A set of 6 doesn't allow that confusion. Failure is mechanical. The weight either moves or it doesn't. No interpretive dance required. You'll grow on 10-12. You'll grow more on 4-6, with less joint wear, less recovery debt, and considerably less guesswork. One range tolerates your mistakes. The other doesn't have room for them.

When you train in the 10-12 rep range, most of your reps have no direct effect on growth. When you train in the 4-6 range, virtually all of your reps are growth reps. Both ranges can build muscle. The mechanism doesn't care about the rep count. It cares about how close you get to true failure on the reps where the high-threshold motor units are recruited and every available fibre is firing. Those are the stimulating reps. Everything else is filler. The catch with 10-12 is twofold. First, only the last 4-5 reps in a 12-rep set are actually stimulating. The first seven are buffer. They generate fatigue, lactic acid, and joint wear that the muscle has to push through before any growth signal arrives. Effort, yes. Stimulus, no. Second, and this is where the high-rep crowd quietly come undone: the long set produces so much afferent feedback (burning, gasping, the legs giving a small philosophical speech) that almost nobody actually takes the set to true failure. They stop two, three, sometimes four reps short, mistake the discomfort for the limit, and call it a hard set. The stimulating reps they were chasing never showed up. A set of 6 doesn't allow that confusion. Failure is mechanical. The weight either moves or it doesn't. No interpretive dance required. You'll grow on 10-12. You'll grow more on 4-6, with less joint wear, less recovery debt, and considerably less guesswork. One range tolerates your mistakes. The other doesn't have room for them.

Sama Hoole

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

MOONSHOT JUST MADE A FREE REPLICA OF CLAUDE CODE. It’s called Kimi Code CLI. It’s open source, free to use, and built by the team behind Kimi K3. It comes with features you won’t find in Claude Code: → upload a screen recording as input → built-in coding, planning, and research agents that work in separate contexts → plan your changes before editing any files → set up MCP servers directly from the CLI with /mcp-config → works with VS Code, JetBrains, and Zed → lightweight - no Node.js setup, starts in seconds The CLI is completely free. The Kimi K3 model behind it starts at $3 per million input tokens. Grab it below 👇

MOONSHOT JUST MADE A FREE REPLICA OF CLAUDE CODE. It’s called Kimi Code CLI. It’s open source, free to use, and built by the team behind Kimi K3. It comes with features you won’t find in Claude Code: → upload a screen recording as input → built-in coding, planning, and research agents that work in separate contexts → plan your changes before editing any files → set up MCP servers directly from the CLI with /mcp-config → works with VS Code, JetBrains, and Zed → lightweight - no Node.js setup, starts in seconds The CLI is completely free. The Kimi K3 model behind it starts at $3 per million input tokens. Grab it below 👇

MIKE

45,132 görüntüleme • 19 gün önce

New feature in Claude Code 2.1.14 just dropped! You can now search and install plugins from the marketplaces installed in your current Claude Code session. This is huge if you’re building plugins on top of Claude Code’s marketplace layer (Skills, Agents, Hooks, etc). How it works: - Run /plugin - The official Claude marketplace is installed by default - Use the search bar to find the plugin you want - Select one or multiple plugins with space, then press i to install - Go to the Installed tab to browse and enable them With the exponential growth of Skills and Agent-based components running in the CLI, improving plugin discoverability is a big win. Pretty sure more marketplace-related features are coming

New feature in Claude Code 2.1.14 just dropped! You can now search and install plugins from the marketplaces installed in your current Claude Code session. This is huge if you’re building plugins on top of Claude Code’s marketplace layer (Skills, Agents, Hooks, etc). How it works: - Run /plugin - The official Claude marketplace is installed by default - Use the search bar to find the plugin you want - Select one or multiple plugins with space, then press i to install - Go to the Installed tab to browse and enable them With the exponential growth of Skills and Agent-based components running in the CLI, improving plugin discoverability is a big win. Pretty sure more marketplace-related features are coming

Daniel San

40,994 görüntüleme • 6 ay önce

You don't understand... Higgsfield MCP + Claude just automated AI film making. Every single step you used to grind through to make an AI movie, you can now do 10x faster. Drop the script into Claude Opus 4.8 and say: "Here's my script. Break it into a full shotlist. Shot number, scene, shot type, camera move and the action in each frame." Now the whole film is mapped, shot by shot. - Pull your assets. Ask Claude: "From this shotlist, list every character, every location and every prop across the whole film." That's your build list. The stuff you would need to generate and give as references in next steps. - Build the character sheets. Higgsfield MCP is connected, so Claude has hands now to do stuff directly. It generates the images itself. Have the full body, back view and close up in the character sheet. One per character. Each sheet becomes the locked reference for that face. Same move for locations, generate the empty plate for each one before anyone steps into it. - Generate the frames. Feed Claude the references plus the shot and have it write and fire the Seedance 2.0 prompt. "Using the lead's character sheet and the alley plate, generate shot 4 in Seedance 2.0. Low angle, slow push-in, rain." Claude builds the prompt, calls Seedance 2.0 and the frame lands back in chat. Use a Seedance 2.0 skill to teach Claude how to prompt it properly. Now, there are 3 ways to make the shots. Pick one per scene. - Pure prompting. Fastest one. You describe the action in words and let Seedance interpret it. For consistency across a sequence, feed it a frame from the previous shot so the look carries. - Storyboarding. You hand it a panel and it matches that composition exactly. Way more control over how the shot is framed. The tradeoff is that it can introduce more cuts than you actually want. - Path Control System This is the latest technique Seedance 2.0 technique. Generate a still base plate of the scene. Draw a red line across it to mark the exact path of the movement, then describe what's happening. Seedance follows that line for the action. Also ask Claude to remove the red line when animating. This is the one for anything where motion has to land precisely. The output reads like real live action. - Lastly, generate every clip you need, then cut them together. Get it to Capcut for editing and audio design. And that's it. The pipeline that used to need a full crew and a studio can now run from one Claude chat. 2026 is gonna be wild

You don't understand... Higgsfield MCP + Claude just automated AI film making. Every single step you used to grind through to make an AI movie, you can now do 10x faster. Drop the script into Claude Opus 4.8 and say: "Here's my script. Break it into a full shotlist. Shot number, scene, shot type, camera move and the action in each frame." Now the whole film is mapped, shot by shot. - Pull your assets. Ask Claude: "From this shotlist, list every character, every location and every prop across the whole film." That's your build list. The stuff you would need to generate and give as references in next steps. - Build the character sheets. Higgsfield MCP is connected, so Claude has hands now to do stuff directly. It generates the images itself. Have the full body, back view and close up in the character sheet. One per character. Each sheet becomes the locked reference for that face. Same move for locations, generate the empty plate for each one before anyone steps into it. - Generate the frames. Feed Claude the references plus the shot and have it write and fire the Seedance 2.0 prompt. "Using the lead's character sheet and the alley plate, generate shot 4 in Seedance 2.0. Low angle, slow push-in, rain." Claude builds the prompt, calls Seedance 2.0 and the frame lands back in chat. Use a Seedance 2.0 skill to teach Claude how to prompt it properly. Now, there are 3 ways to make the shots. Pick one per scene. - Pure prompting. Fastest one. You describe the action in words and let Seedance interpret it. For consistency across a sequence, feed it a frame from the previous shot so the look carries. - Storyboarding. You hand it a panel and it matches that composition exactly. Way more control over how the shot is framed. The tradeoff is that it can introduce more cuts than you actually want. - Path Control System This is the latest technique Seedance 2.0 technique. Generate a still base plate of the scene. Draw a red line across it to mark the exact path of the movement, then describe what's happening. Seedance follows that line for the action. Also ask Claude to remove the red line when animating. This is the one for anything where motion has to land precisely. The output reads like real live action. - Lastly, generate every clip you need, then cut them together. Get it to Capcut for editing and audio design. And that's it. The pipeline that used to need a full crew and a studio can now run from one Claude chat. 2026 is gonna be wild

Rez Karim

10,951 görüntüleme • 2 ay önce

I just built a Claude Code skill that scores whether your landing page actually keeps your Meta ad's promise 🤯 Drop in your ad and the page it points to. It reads both, scores the "ad scent" from click to page, and finds the exact line where the page breaks the promise that won the click. All inside Claude Code. Perfect for DTC brands and media buyers who pour everything into the ad and the CPA but never grade the seam in between. If you're scaling spend on a winning ad, the click is landing on a page that opens with something slightly different, the ad promised 50% off and the page shows full price, the ad hooked "for oily skin" and the page is a generic homepage, and nothing looks broken, but the visitor feels it and bounces... That gap has a name in conversion work: message match. And you already paid for the click you're losing. Here's what it does: → Drop in your ad (headline, copy, offer, CTA) and the landing-page URL → It fetches the live page and reads what's actually above the fold → Grades 7 continuity dimensions: promise, offer, angle, CTA, audience, proof, visual → Shows your ad's words next to your page's words, so every gap is right there → Rewrites your hero headline so the page keeps the ad's promise → Renders a dashboard with a Match Score out of 100 No guessing why the click bounced. No blaming the creative for a page problem. No buying more traffic to fix a copy problem. What you get: → A Match Score on every ad-to-page pair before you scale → The ad-side vs page-side quotes, side by side, for every leak → A hero rewrite you can paste straight onto the page → A dashboard you can hand to your team or client I'm giving away the full skill completely for free. Built 100% in Claude Code. No API keys. Want the skill? > Like this post > Comment "MATCH" And I'll send it over (must be following so I can DM)

I just built a Claude Code skill that scores whether your landing page actually keeps your Meta ad's promise 🤯 Drop in your ad and the page it points to. It reads both, scores the "ad scent" from click to page, and finds the exact line where the page breaks the promise that won the click. All inside Claude Code. Perfect for DTC brands and media buyers who pour everything into the ad and the CPA but never grade the seam in between. If you're scaling spend on a winning ad, the click is landing on a page that opens with something slightly different, the ad promised 50% off and the page shows full price, the ad hooked "for oily skin" and the page is a generic homepage, and nothing looks broken, but the visitor feels it and bounces... That gap has a name in conversion work: message match. And you already paid for the click you're losing. Here's what it does: → Drop in your ad (headline, copy, offer, CTA) and the landing-page URL → It fetches the live page and reads what's actually above the fold → Grades 7 continuity dimensions: promise, offer, angle, CTA, audience, proof, visual → Shows your ad's words next to your page's words, so every gap is right there → Rewrites your hero headline so the page keeps the ad's promise → Renders a dashboard with a Match Score out of 100 No guessing why the click bounced. No blaming the creative for a page problem. No buying more traffic to fix a copy problem. What you get: → A Match Score on every ad-to-page pair before you scale → The ad-side vs page-side quotes, side by side, for every leak → A hero rewrite you can paste straight onto the page → A dashboard you can hand to your team or client I'm giving away the full skill completely for free. Built 100% in Claude Code. No API keys. Want the skill? > Like this post > Comment "MATCH" And I'll send it over (must be following so I can DM)

Mike Futia

10,548 görüntüleme • 22 gün önce

For Anthropic’s Claude Design, your opening prompt sets the ceiling of the project. If your prompt is a comprehensive brief, it will land somewhere near production-ready Seems obvious, but here is something interesting we observed: one designer wrote: >16 prompts >climbed in specificity over the session >and still finished worse than they started A single "reconsider" prompt at iteration 2 tanked output quality by -0.7 and the session never recovered. 2/3 of every prompt typed across all 5 sessions was refinement or correction. TLDR: Your first move is the whole game. and prompting is an art. What a time to be alive.

For Anthropic’s Claude Design, your opening prompt sets the ceiling of the project. If your prompt is a comprehensive brief, it will land somewhere near production-ready Seems obvious, but here is something interesting we observed: one designer wrote: >16 prompts >climbed in specificity over the session >and still finished worse than they started A single "reconsider" prompt at iteration 2 tanked output quality by -0.7 and the session never recovered. 2/3 of every prompt typed across all 5 sessions was refinement or correction. TLDR: Your first move is the whole game. and prompting is an art. What a time to be alive.

ben

229,081 görüntüleme • 2 ay önce

we finished our app in 7 days it blocks your phone until you walk. But now, we are stuck.. WATING for the screen time apis to get approved by apple so In the mean time I decided to design some achievement badges for gamification and when i say desing, i mean we just sent a prompt to Rork app builder using gemini 3 and it generated them + added them to the project in 1 prompt. Meanwhile Mau Baron was setting up the MMP to start running ads hopefully we get approved later today Or tommorow And we can finally submit Step Lock And scale this to $30k/mo

we finished our app in 7 days it blocks your phone until you walk. But now, we are stuck.. WATING for the screen time apis to get approved by apple so In the mean time I decided to design some achievement badges for gamification and when i say desing, i mean we just sent a prompt to Rork app builder using gemini 3 and it generated them + added them to the project in 1 prompt. Meanwhile Mau Baron was setting up the MMP to start running ads hopefully we get approved later today Or tommorow And we can finally submit Step Lock And scale this to $30k/mo

Ernesto Lopez

17,498 görüntüleme • 6 ay önce

Stop editing timelines. Start writing prompts. Replit Animation lets you create animated videos inside Replit using code. Replit ⠕ #replitanimation It generates TypeScript behind the scenes with modern animation libraries, turning your ideas into fully rendered mp4 videos. Plug in your existing design systems, typography, tokens, and production components to create videos that match your product perfectly. Video as code changes the workflow. Your components become reusable animation blocks. Update the code, regenerate the video, ship again. From automated changelog videos to polished feature releases, video creation becomes a scalable pipeline. Here is an example of a video I generated with Replit Animation. Export in your preferred resolution and frame rate or host it online with a shareable URL. Mention video in your first prompt or choose Animation under App mode to activate it. Start creating:

Stop editing timelines. Start writing prompts. Replit Animation lets you create animated videos inside Replit using code. Replit ⠕ #replitanimation It generates TypeScript behind the scenes with modern animation libraries, turning your ideas into fully rendered mp4 videos. Plug in your existing design systems, typography, tokens, and production components to create videos that match your product perfectly. Video as code changes the workflow. Your components become reusable animation blocks. Update the code, regenerate the video, ship again. From automated changelog videos to polished feature releases, video creation becomes a scalable pipeline. Here is an example of a video I generated with Replit Animation. Export in your preferred resolution and frame rate or host it online with a shareable URL. Mention video in your first prompt or choose Animation under App mode to activate it. Start creating:

MAPUNDA

143,053 görüntüleme • 5 ay önce

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

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

Claude Code Desktop now opens a new window for each session This makes it much easier to visualize multiple Claude Code agents running in parallel My current stack depends on the task: - Ghostty: when starting a project. Bash commands, git, env variables, provider connections. All manual through the terminal with a Claude panel running alongside. - Claude Code Desktop: once everything is configured. GitHub connected, CLAUDE.md, Skills, subagents and Hooks ready. Claude Code runs on its own, no more terminal setup, just panels running and outputs to review. - VSCode: when I need to review code by hand. I use it less and less, but there are moments where I have to confirm Claude got it right. I usually open the Claude extension inside VSCode, but it lacks most of the CLI features so it's limited Solid update. Worth trying once your workflows are already set up 👇

Claude Code Desktop now opens a new window for each session This makes it much easier to visualize multiple Claude Code agents running in parallel My current stack depends on the task: - Ghostty: when starting a project. Bash commands, git, env variables, provider connections. All manual through the terminal with a Claude panel running alongside. - Claude Code Desktop: once everything is configured. GitHub connected, CLAUDE.md, Skills, subagents and Hooks ready. Claude Code runs on its own, no more terminal setup, just panels running and outputs to review. - VSCode: when I need to review code by hand. I use it less and less, but there are moments where I have to confirm Claude got it right. I usually open the Claude extension inside VSCode, but it lacks most of the CLI features so it's limited Solid update. Worth trying once your workflows are already set up 👇

Daniel San

38,726 görüntüleme • 2 ay önce

"Where will AI get its compute?" We generated this video - character, voice, acting - with a single prompt on LTX-2.3. The model runs on consumer-grade GPUs. The same ones sitting in your PC right now. That's the whole point of DePIN. Your hardware powers AI that didn't exist two years ago. And you get paid for it.

"Where will AI get its compute?" We generated this video - character, voice, acting - with a single prompt on LTX-2.3. The model runs on consumer-grade GPUs. The same ones sitting in your PC right now. That's the whole point of DePIN. Your hardware powers AI that didn't exist two years ago. And you get paid for it.

GamerHash AI

430,760 görüntüleme • 3 ay önce

ANTHROPIC JUST TURNED AI AGENTS INTO GIT REPOS Anthropic shipped "ant" - a CLI that runs every Claude API endpoint straight from your terminal. The headline isn't the terminal access. It's that you can now version-control an AI agent as YAML in Git and have CI sync it to the Claude Platform, the same way you ship code. - Every API resource is a subcommand: messages, models, files, agents, sessions - Define an agent in a YAML file, check it into your repo, and keep it in sync with one update command - Spin up a session, send it an event, then pull every event and tool call back from the same CLI - Claude Code knows how to drive ant out of the box - it shells out and reads the results with no glue code Agents just stopped being prompts you babysit and became infrastructure you deploy.

ANTHROPIC JUST TURNED AI AGENTS INTO GIT REPOS Anthropic shipped "ant" - a CLI that runs every Claude API endpoint straight from your terminal. The headline isn't the terminal access. It's that you can now version-control an AI agent as YAML in Git and have CI sync it to the Claude Platform, the same way you ship code. - Every API resource is a subcommand: messages, models, files, agents, sessions - Define an agent in a YAML file, check it into your repo, and keep it in sync with one update command - Spin up a session, send it an event, then pull every event and tool call back from the same CLI - Claude Code knows how to drive ant out of the box - it shells out and reads the results with no glue code Agents just stopped being prompts you babysit and became infrastructure you deploy.

BuBBliK

200,319 görüntüleme • 2 ay önce

Verro is upgrading today Verro is going through a system upgrade today. During this time, some features may be temporarily unavailable while we make the changes. Your assets and your account information are safe and unchanged. Nothing is lost, nothing is moved. Everything stays exactly as it was when the upgrade started, and it will all be there when Verro comes back. This upgrade is part of preparing Verro for what's next. We're keeping the window as short as we can, and the system will be back soon. Thank you for your patience. We'll post an update here the moment everything is back online.

Verro is upgrading today Verro is going through a system upgrade today. During this time, some features may be temporarily unavailable while we make the changes. Your assets and your account information are safe and unchanged. Nothing is lost, nothing is moved. Everything stays exactly as it was when the upgrade started, and it will all be there when Verro comes back. This upgrade is part of preparing Verro for what's next. We're keeping the window as short as we can, and the system will be back soon. Thank you for your patience. We'll post an update here the moment everything is back online.

VERRO

10,813 görüntüleme • 1 ay önce

Alright, now that we know *what* an agent is, how does it actually work? When you ask for help on a task, the agent plans a series of steps and executes them directly in the application on your behalf, using the tools it has access to. Say you are booking a local service or trying to organize your inbox (which typically takes multiple steps): the AI model first plans how to achieve the task using its existing knowledge and then interacts with your inbox to execute the task. The agent will continue until it is confident the task has been successfully completed.

Alright, now that we know what an agent is, how does it actually work? When you ask for help on a task, the agent plans a series of steps and executes them directly in the application on your behalf, using the tools it has access to. Say you are booking a local service or trying to organize your inbox (which typically takes multiple steps): the AI model first plans how to achieve the task using its existing knowledge and then interacts with your inbox to execute the task. The agent will continue until it is confident the task has been successfully completed.

Google AI

22,487 görüntüleme • 8 ay önce