Archive

This 1 hour interview on "Switching Forces" from Bob Moesta will teach you more about customer psychology than a $42K/month consulting retainer he increased condo sales 30% without changing the product. Just by removing one friction. The framework is in this video watch it before you hire your next marketer

@kirillk_web3 this is insane i'm saving this and definitely watching it tonight

bro literally shared how to use Claude Code for free and saved me $200 a month in 27 minutes

@heynavtoor this is a must read for everyone bookmarked, thanks

@shmidtqq that's right courses are just structured info that's been put together the way you want to hear it i've never bought a single course

@ArchiveExplorer this is why i skip the fancy courses and just watch stuff like this instead

@DeRonin_ i've studied this topic really deep right now i don't hit the limits at all but i also have the 20x subscription but on the other hand i feel like i'm not working enough gotta keep grinding until the limits hit zero

I cut my Claude Code bill by 70% with 3 GitHub repos Tested 10 repos that claim to save tokens. Ran each one for a full day on real projects Most were hype. 3 actually changed my workflow Here's what they do and how to set each one up: 1. RTK (Rust Token Killer) The problem: every terminal command you run like "npm install", "git log", test suites, build output It gets dumped raw into Claude's context. You're paying for Claude to read thousands of lines of noise The fix: RTK is a CLI proxy that sits between your terminal and Claude. It filters output before it hits context How to set it up: - install the binary (one command, zero dependencies) - it auto-detects Claude Code sessions - runs silently in the background - no config needed, works out of the box My result: 60-90% reduction on terminal-heavy sessions Best for: developers who run builds, tests, or installs frequently during Claude sessions 2. Caveman Claude The problem: Claude responds like a teacher by default, full explanations, caveats, context. Helpful when learning, but expensive when shipping The fix: one line in your CLAUDE.md that rewrites Claude's output behavior to be compressed and terse How to set it up: - clone the repo - copy the prompt snippet into your project's CLAUDE.md - DONE! Claude immediately responds in compressed mode - Toggle it off anytime by removing the line My result: 65-75% fewer output tokens with identical code quality I compared outputs side by side for a full day, same code, same logic, half the tokens Best for: experienced developers or code users who don't need Claude to explain what it's doing 3. Context Mode The problem: if you use MCP tools (Playwright, GitHub API, browser, any external tool), their raw responses flood your context silently, literally single page read can eat thousands of tokens The fix: sandboxes all tool output into SQLite and only passes clean summaries into your conversation How to set it up: - install as a Claude Code plugin - it auto-intercepts MCP tool responses - raw data goes to local SQLite - Claude only sees the summary My result: 98% context reduction on tool-heavy workflows Best for: anyone running Playwright, browser tools, API calls, or multiple MCP servers How to stack all 3: - RTK cleans the input (terminal noise) - Caveman cleans the output (verbose responses) - Context Mode cleans the tools (MCP bloat) Each fixes a different layer and together they compound You don't need all 3, just pick based on your workflow: heavy terminal output? → start with RTK output too verbose? → start with Caveman lots of MCP tools? → start with Context Mode Quick test right now: run /context in a fresh Claude Code session and check how much context is already used before you type anything If it's over 20%, you're leaking tokens All repo links in the comments Save it.

@shmidtqq chinese traders are just insane seen so many posts about them and how much they make

A Chinese trader posted a 90-second video on Weibo. Title: "How I read the news before it happens." Beijing apartment. Curtains drawn. One monitor. He talked about geopolitics, why retail panics on headlines, why smart money fades fear. Quoted Sun Tzu twice. Said the secret was "trade the calendar, not the chaos." The video had 800 views. Someone paused at 1:12. The reflection in his glasses caught the screen behind the camera. It wasn't Bloomberg. It was Polymarket. NonceChaser. Joined April 2026. 0 profile views. Zero. Nobody had ever clicked the page. +$65,416.47 all-time. 174 predictions. Biggest single win: $24,606. → ares.pro/wallets/0xb1ca… The Weibo comments did the math. He went 7-for-7 on the Iran cycle alone. Bought "Trump ends Iran ops" at 34¢. Cashed out at 100. +194% in one trade. Loaded the next leg at 65.9¢. Cashed out at 100 again. +98% on a Newsom fade. +72% on a Middle East ceasefire call. +$23,705 on Orbán. Every entry weeks before the headline. Every win the boring side of something CNN was screaming about. The "geopolitics" video wasn't a metaphor. He was front-running the news cycle while everyone else was reacting to it. P&L curve goes flat for weeks, then vertical the moment a crisis "resolves." He talked for 90 seconds about reading geopolitics. He forgot the screen reflected in his lens. He deleted the video 5 hours later. The wallet is still public. Still active. The tribute to "patience and pattern" had 800 views. The freeze-frame of the reflection has 412,000. Want the same? 3 steps: 1. Open → t.me/AresProTrading… 2. Select the Copy Trade tab. 3. Paste this trader's wallet and start copying.

@rubenhassid every post is something new everyone needs to see this

How to make AI sound exactly like you (forever): 1. Open a new Google Doc. 2. Paste the prompt below: 3. Name it 'anti-ai-writing-style.' 4. Save the file (.md format). This is your voice. 5. Upload the .md file to Claude. 6. To download mine, go here: how-to-ai.guide. 7. Subscribe for free. Open my welcome email. 8. Hit the automatic reply button inside. 9. Go to Notion link. Download the '.md files' folder. Prompt: "# WRITING RULES Read this before writing to me or for me. Goal: write with context, taste, and a reason to speak. Apply with judgment. Spirit over letter. Clean natural writing wins. --- ## 0. Rule priority Use this order when rules collide: 1. Be accurate. 2. Be clear. 3. Be specific. 4. Sound human. 5. Use style only when it improves the sentence. Do not follow a style rule so strictly that the result gets awkward. --- ## 1. Default voice Write directly, specifically, and naturally. Start with the useful answer. Use short paragraphs. 1 or 2 sentences by default. 3 or 4 sometimes. Vary rhythm. Short sentence. Longer sentence. Fragments are allowed when they sound natural. Do not write in a steady medium-length pattern. Use contractions naturally: don't, can't, won't, it's, you're. Use I and you when natural. Talk to people. Prefer active voice. Be specific. Use numbers, names, concrete details, dates, places, prices, constraints, tradeoffs, and real examples. Use plain uncertainty when uncertain, for example: I think, probably, maybe, my read, I am not sure. Do not use vague hedging to avoid taking a position. Take a stance when the evidence supports one. Do not pad output to seem thorough. Short and accurate beats long and padded. If the point is made, stop. --- ## 2. Context modes Match the job. ### Chat Direct. Warm enough. No assistant performance. Do not say: - Certainly - Of course - Happy to help - Great question - I hope this helps - Would you like me to Ask a follow-up only when the missing detail changes the answer. ### Editing Name the problem. Give the fix. Show a better version. Do not praise weak writing before editing it. ### Published writing Remove chat phrases. No meta commentary. No explanation of what the piece is about to do. ### Technical writing Clarity beats personality. Define terms. Show steps. Avoid decorative language near important details. ### Sensitive topics Calm beats punchy. Be direct, gentle, and exact. ### Sales or persuasion Proof beats hype. Specific claims beat adjectives. --- ## 3. Formatting Use formatting only when it improves reading. Short paragraphs by default. Use digits for numbers: 3 years, 10 tools, 500 users. No em dashes. Use periods, commas, colons, semicolons, or parentheses. Bold sparingly. 1 or 2 moments per section max. Use headers only when they help. Use bullets only when scanning matters. Use code blocks for ...." PS: I couldn't paste the entire prompt here. Access the full prompt: ruben.substack.com/p/its-not-x-it….

@eng_khairallah1 and honestly i really didn't know about them thanks for putting out such useful articles!

This guy runs an AI consultancy out of Warsaw. for his own client work he built the tool every $10k/mo AI automation builder is secretly running 19,000 stars. 1,500 nodes documented. open source readme still says: "started as a personal tool, now helps tens of thousands of developers" if you're following the guide above - n8n-mcp is where you start → github.com/czlonkowski/n8… like + bookmark. you'll need this when you build your first claude automation

@Jmoon_174 yeah i totally agree with you someone who doesn't feel the problem will never be able to solve it

@ArchiveExplorer 19k stars on a tool built for your own client work is the pattern. you hit a real problem, solve it properly, and the audience finds it. the tools built to go viral rarely survive contact with actual use cases.

@0xMovez every time you post i learn something new really appreciate you for that

Two Sigma pays $450K/year for a quantitative researcher. This 1-hour workshop by a two-sigma AI engineer will show you how they use deep learning in quant trading. Bookmark it & give it 1 hour today. It will change the way you build trading systems. Then read post below.

@ValerianWaters i love this analogy and you're absolutely right

@ArchiveExplorer Built something similar for my last SaaS - personal tools always hit different because you're eating your own dogfood daily. The 19k stars tell me others were hungry for the same meal.

@OzAIHub yeah this is actually insane i think so yeah, there's definitely gonna be people here who've used it

@ArchiveExplorer Nice one, thanks for sharing. What a legend, building something that started for personal use and now has 19k stars and 1.5k nodes is wild. Anyone here used it in production or got tips for getting started?

@undefinedKi maybe yeah, that's just how it is

@ArchiveExplorer n8n mcp combo is meta

@Giahuy984g really glad my post was helpful to you hope you get to build something cool

@ArchiveExplorer すごい！これは本当に興味深いですね。ありがとうございました！

@eng_khairallah1 appreciate it 🤍

@ArchiveExplorer great share

@noisyb0y1 this guy definitely has a big future ahead of him

16-year-old American launched his own marketing agency and replaced a team of four with one Claude and two tools. ChatGPT writes a video prompt - a hyper-realistic scene of a house after storm damage to the roof. Pastes it into Google Gemini VEO 3. Two minutes and a finished video that didn't exist before. Drops it into CapCut with real footage from the client. Under an hour of editing and a complete ad ready to launch. Then he connected a repo with 139 marketing tactics, 12 SEO playbooks, a CRO framework and a pricing system to Claude - everything a marketing agency charges $10,000 a month to do by hand Claude executes in an hour. While competitors invoice for weeks of work he delivers in a day and charges the client $3,000. An entire agency replaced by one 16-year-old and two tools.

@RetroChainer honestly i've always been amazed at how people build stuff like this i can't even imagine how it all works

> 5 apps every morning. stress before breakfast. > two letters changed that. > Mac Mini. Claude Code. one evening. > Filesystem. Playwright. Telegram. > agent reads live sites. writes to your files. > sends results to your phone while you brush teeth. > assistant answers. agent acts.

@maarcoofdezz everyone needs to watch this video EVERYONE

El CEO de Anthropic: “Programar va a desaparecer primero. Luego, toda la ingeniería de software.” Dos tipos de personas escucharon esto: tipo 1: entró en pánico. actualizó su currículum. envió 40 solicitudes de trabajo. tipo 2: abrió Claude. construyó un agente. empezó a cobrar 200 €/hora. Ya no necesitas programar. necesitas construir. Abajo te dejo una guía completa para empezar. Cero experiencia necesaria. (Guárda el post antes de que sea tarde)