👀 It’s funny how this same old circus keeps rolling around again and again: during shakeouts, fools panic-sell everything in hopes of striking gold with scam tokens, while smart investors seize the opportunity to buy undervalued and top-tier projects at a discount. In the end, the fools are left empty-handed 🤦♂️, while the smart investors grow their 💎 wealth. It’s a pattern as predictable as the sunrise.
У Кейна вышло видео про «Пять уроков» — созвучно моему представлению о том как жить жизнь, поэтому распишу тоже.
1. Имей цель.
Она не обязана быть конкретной; например, «выучить C++» или «сделать маленькую игру от начала до конца». В нестабильные времена план нужен больше всего.
I ran a Tinder Experiment as a 28 Sugar Daddy Alexandr Wang who runs his own startup
used some bad pics just to prove that money matters
Within hours, my DM's were being flooded by prime college aged baddies in need of funds. Most of them agreed to go on a date for $200-300 ppm but remember folks money doesn't matter
Every girl was legitimately a 10/10 and these were not even the best looking ones
Ran this shit for a day, results are shocking imo. Money beats out Looks when it comes to dating in 2026
My skills repo has 160K stars, 7.5m downloads...
...and no tutorial.
So, here it is. Watch me walk through the essential skills:
- /grill-with-docs
- /to-spec
- /to-tickets
- /implement
- /code-review
It's the whole flow, end-to-end. Enjoy:
THE ANATOMY OF A LOOP RUNNING WHILE YOU SLEEP
an anthropic engineer runs autonomous code cycles on a closed laptop using a five-file folder
this loop architecture opens pull requests and runs tests without a single chat prompt:
> contract.md - defines the shift rules and operational boundaries
> schedule.yml - triggers the cron events to launch the next cycle
> rubrics/ - stores the graders to evaluate output quality before staging
> state/ - logs active checkpoints to recover from system crashes
the window to run Fable 5 reasoning loops under the $20 subscription closes on July 12th
build your autonomous pipelines now before it shifts to expensive API billing
grab the full folder blueprint below 👇
New in Claude Code: /checkup
Run /checkup to:
1. Clean up unused skills/MCPs/plugins and save context
2. Dedup your local CLAUDE.md against the checked in CLAUDE.md
3. Break up root CLAUDE.md into nested CLAUDE.md's + skills
4. Turn off slow hooks
5. Update your Claude Code to the latest version
6. Enable auto mode by default
7. Pre-approve frequently denied read-only commands
.. And a few other goodies.
/checkup confirms with you before making any changes. Enjoy!
GPT 5.6 SOL IS HERE!
How to run your personal + business life with GPT 5.6 Sol + Codex (full 49 min masterclass)
We tested it for 30 days and the video it's the CLEAREST look at the FUTURE of work:
Here's what's possible once you set it up:
1. Your inbox becomes cards every morning, each with a summary and a reply drafted in your own voice. Y
2. Your Slack, meeting notes, and company updates can turn into one daily feed with a clear next action. It learns what you care about over time and rewrites its own prompts to get sharper.
3. You can give your agent its own email address, so your other tools and even your team's Slack bot email it directly and it just handles things.
4. You can have it watch you do a task once and turn it into a skill it repeats forever.
5. You can set a long goal and walk away. You can have it run for 20 hours straight, and fine-tune your own models, something that was out of reach for non-engineers 12 months ago.
How to start: Open Codex, give it access to your computer, and ask it to suggest things it could do for you based on how you already work.
Full episode on @startupideaspod (thanks @danshipper for sharing your entire workflow and review of GPT 5.6)
Start with one boring task, get it working, and build from there.
You'll learn exactly how to make something similar.
GPT 5.6 Sol is impressive.
Sol (according to openAI benchmarks) is the best coding model out right now. It set a new state of the art on Terminal-Bench 2.1 at 88.8%, and its "ultra mode" hits 91.9%, beating Claude Opus 4.8, Fable 5, and even Mythos 5
this masterclass is 100% free, like always. For more @startupideaspod
Watch
He runs Obsidian, the notes app for engineers.
instead of keeping his Obsidian skills for Claude private, he open-sourced them.
Steph Ango. That Obsidian: CEO, author of the 'File over app' manifesto.
'obsidian-skills' - a skill-pack that lets Claude Code actually work with your notes.
40,240 stars. MIT.
→ https://t.co/kVspFl8WgI
bookmark it. This is how your Claude setup goes pro.
La biología en PDF acaba de morir otra vez.
Un tío hizo una app donde rotas células, aíslas orgánulos y comparas estructuras 3D como un videojuego.
UI: GPT Images 2. Código: Gemini 3.1 Pro.
Los libros de texto ya no mandan.
Por aca te dejo 6 repos de AI Agents que están creciendo rápido en github
1. agency-agents
Agencia de IA completa con 232 sub-agentes especializados en 16 áreas (frontend, Reddit, copywriting, etc.). Se instala con un solo script en Claude Code y otras herramientas.
https://t.co/ShBpArRMNt
2. codebase-memory-mcp
Convierte todo tu codebase en un knowledge graph ultra rápido. Soporta 158 lenguajes, reduce tokens más del 99% y responde en milisegundos.
https://t.co/RWnCvNRGVL
3. OpenMontage
Convierte tu agente de coding en un estudio completo de producción de videos. Planificación, guion, assets, edición y renderizado con solo prompts en lenguaje natural.
https://t.co/DMbUQbjd5j
4. Agent-Reach
Dale “ojos” a tu agente para navegar internet. Lee y busca en X, Reddit, YouTube, GitHub y más. Todo gratis combinando herramientas públicas (sin pagar APIs).
https://t.co/uXVIElF7Mk
5. orca
Gestiona y ejecuta múltiples agentes de coding en paralelo. Disponible en desktop y móvil, usando tu propia suscripción. Ideal para trabajar con flotas de agentes.
https://t.co/xUsr4Q1YuX
6. OmniRoute
Gateway gratuito que une 237 proveedores de IA (90+ gratis) en un solo endpoint. Reduce el consumo de tokens hasta un 95%. Perfecto para Claude Code, Codex, Cursor, etc.
https://t.co/WAkQa7Cx5F
kinda insane that Karpathy talked about this a year ago but no one paid attention...
he described a model writing a book for itself on how to solve problems... but that concept is real now
and today is the last day to have the smartest model write yours: Fable 5 leaves every Claude subscription tonight
here's how you run the extraction with 5 workflows:
1. plant its standards
open each project and have fable rewrite your claude[.]md as the operating manual a weaker model would need: your conventions, the mistakes to prevent with the rule that stops each one, the quality bar as checkable criteria
then have it write your 3 highest-leverage skills in full
2. the consultant audit
give it your projects and numbers with one prompt: "act as the consultant i can't afford, audit everything, deliver a roadmap a less capable model can execute step by step
the reasoning gets written down while the model that produced it is still flat-rate"
3. the second brain run
fire deep research runs on your niche, your competitors, your customers' problems
mine every run into an Obsidian vault, one insight per note... a hundred linked notes get reused, one long report gets buried
4. /goals + dynamic workflows
describe what done looks like, demand the proof pasted in the finish line, cap every run with a turn or time limit... the model builds unattended for hours while the tokens still cost nothing extra
5. the recorder skill
one skill that fires after every hard problem: the approach, the judgment calls, the reusable rule, saved as a note in your repo
wire it into your claude rules and fable documents its own thinking all day, automatically
check out the full guide:
asked an anthropic engineer how his loops run on a closed laptop.
he didn't answer. he sent me one folder.
CONTRACT.md → schedule.yml → rubrics/ → state/checkpoint.json → receipts/2026-07-05/
five files. one shift. 5,382 shifts archived.
zero keystrokes since 20:41 yesterday. fourteen PRs opened, three rollbacks, six digests, all before he woke up.
no chat window. no "please can you". no follow-up.
the folder wakes. the contract is the boundary. the rubric is the judge. the checkpoint is the memory. the receipt is the proof.
that's the anatomy.
save the file tree below before he realizes i posted it.
İspanyalı 22 yaşında bir kız ChatGPT’ye $12’lik domain buldurdu. 17 gün sonra Silicon Valley’li bir founder o domaini ondan $11,000’a aldı.
Prompt basitti:
“Bana kimsenin daha bilmediği ama 30 güne patlayacak bir tech terimi bul. .com boş mu bak. Basit tut.”
ChatGPT 9 dakikada ona mini bir scraper yazdı. Kız botu telefonundan çalıştırdı. O kadar.
1.gün. Bot bir terim yakaladı: “synthetic memory”. Niş bir podcast’te 23 kez geçmiş. Twitter’da sıfır. Kız öğle molasında .com’u $14’ye aldı.
2.gün. Terim Hacker News ana sayfasına çıktı. Telefon DM yağmuruna tutuldu.
3.gün. Menlo Park’tan bir founder $13,000 masaya koydu. Kız pazarlığı bitirmedi. $13,000 + adamın 80K’lık hesabından teşekkür tweet’i istedi. Aldı da.
Aynı gün 10 saniyelik bir video çekti. Sadece gülümsüyor. Elinde telefon, ekranda satış onayı. Üstünde tek yazı:
$14 → $13,000. 16 gün. Ben sadece Chate bir soru sordum.
Video 4.9M izlendi. 13,000 kişi yorumlara tek kelime yazdı: SIGNAL.
Kızın tek cümlesi şu:
“Hızlı olmak, zengin olmaktan iyidir. Onu kanıtlamak istedim.”
Everyone's arguing about which AI model is smartest
Meanwhile, the top 1% of Claude Code users quietly figured out something else:
The model isn't your bottleneck. Your repo is
Same model. Same prompts. One dev gets a chatbot, the other gets an autonomous engineer
The difference is a folder structure.
I call it the Final Boss Setup
━━━━━━━━━━━━━━━
1️⃣ The Context Ladder (this changes everything)
Stop thinking "what goes in CLAUDE.md."
Start thinking "what loads WHEN."
There are 4 rungs:
• Every session → CLAUDE.md (tiny, always in context)
• Path-gated → rules/*.md (loads ONLY when Claude touches those files)
• On invoke → skills/* (loads when a task matches)
• Isolated → agents & workflows (own context entirely)
Most people dump everything on rung 1.
Then wonder why Claude gets dumber as the project grows
You're not writing docs. You're designing a memory hierarchy
━━━━━━━━━━━━━━━
2️⃣ ASKED vs FORCED (the line that separates amateurs from pros)
CLAUDE.md and rules = ASKED.
Instructions Claude reads and *usually* follows
Hooks and settings = FORCED.
permissions.deny blocks rm -rf whether Claude agrees or not
Here's the test:
"Please run the formatter" → asked. Works 90% of the time.
PostToolUse hook that formats every edit → forced. Works 100% of the time.
Anything where 90% isn't good enough — secrets, migrations, prod — should never live in a markdown file.
Guidance for style. Enforcement for survival.
━━━━━━━━━━━━━━━
3️⃣ The Routing Rule (tattoo this somewhere)
Every recurring thing you do fits exactly one slot:
• Research → subagent (own context, reports back clean)
• Procedure → skill (the playbook, loaded on demand)
• Guarantee → hook (happens every time, no discretion)
Repeating a workflow in prompts? That's a skill you haven't written.
Reminding Claude to run tests? That's a hook you haven't wired.
Letting exploration pollute your main context? That's a subagent you haven't spawned.
━━━━━━━━━━━━━━━
4️⃣ Rules That Load Themselves
The underrated file: .claude/rules/ with path-gating.
frontend/react.md only enters context when Claude touches frontend code.
api-design.md only when it's in the API.
Your conventions follow Claude around the codebase like a senior engineer looking over the right shoulder at the right moment
Zero tokens wasted on rules that don't apply
━━━━━━━━━━━━━━━
5️⃣ Agents With Their Own Memory
The 2026 upgrade nobody's using yet:
agent-memory/ — Claude writes what it learned, you commit it
Your debugger agent remembers last month's gnarly race condition.
Next session, it starts smarter than it ended
Claude writes. You commit. The team inherits
Your AI's experience becomes version-controlled infrastructure
━━━━━━━━━━━━━━━
6️⃣ CLAUDE.md in the Danger Zones
Global context can't know that your auth module has landmines
So drop local files where the bodies are buried:
src/api/CLAUDE.md
src/payments/CLAUDE.md
Claude reads them exactly when it enters those directories
Warnings appear at the moment of danger — not 4,000 tokens earlier where they get ignored
━━━━━━━━━━━━━━━
7️⃣ The Golden Rules (from the trenches)
• CLAUDE.md under ~200 lines. When it grows, split into rules/. Bloat = missed signals.
• List REAL commands (npm test, build, lint) — so Claude can verify its own work.
• Secrets stay in ${ENV_VAR} references. Never in .mcp.json. Literally never.
• Commit .claude/, gitignore *.local.* — your setup is team infrastructure, not personal preference
━━━━━━━━━━━━━━━
Here's the shift most people miss:
A prompt improves one conversation
Structure improves every conversation, for every teammate, forever
Prompting is renting intelligence
Structure is owning it
Build the repo once and Claude stops visiting your codebase and starts living in it
this is f*cking gold
Andrej Karpathy came over to Anthropic just five weeks back.
Someone on his team pulled up the actual Claude.md they run day to day and showed it to me.
I plugged it straight into my workflow. Claude’s next reply wasn’t just improved.
It felt like a different model.
The canned, one-size-fits-all stuff vanished, and it started reasoning in my voice.
Save this before it disappears down your timeline.
Read it first then hit the article below.
Este proyecto Open Source es BRUTAL: Meetily.
Transcribe y resume tus reuniones con IA.
¡Pero lo hace todo en local! Sin subir tu audio a ningún servidor, totalmente gratis, 100% privado, en segundos.
→ https://t.co/RjZ08yP5y1