stop telling Claude Code/Codex "read this file".
stop telling Claude Code/Codex "now read that one too".
stop telling Claude Code/Codex "grep the whole repo".
install codebase-memory. it indexes the Linux kernel, 28M lines, in 𝟯 𝗺𝗶𝗻𝘂𝘁𝗲𝘀. your repo takes seconds.
index once and the whole repo becomes 𝗼𝗻𝗲 𝗴𝗿𝗮𝗽𝗵 of every function, file and dependency. one query replaces dozens of grep and read cycles.
benchmarked across 31 real repos:
→ 10x fewer tokens on structural queries
→ 83% answer quality on complex tasks
→ 2.1x fewer tool calls
two prompts. send them straight to your agent 👇
Today we're launching Goose Ads in Claude.
This is a skill /goose-ads that lets anyone make high-performing ad creatives directly in Claude, Claude Code, Cowork, or Codex.
Here's how it works:
1. Install the skill: npx gooseworks install --all
2. Run this prompt:
/goose-ads create ads for my brand <brand-website>
3. (Optional) Pick templates you like on the platform
The skill finds top-performing ads that companies are already spending $ on and generates creatives for your brand.
It also ensures that generated creatives are accurate to your brand's messaging, logo, assets, etc.
It's that easy.
But this is just the start.
We have created a library with 100+ open-source skills for growth that some of the fastest growing startups in the world are using every day to run ads, content, competitor research, gtm, seo and more.
Comment Goose and I'll DM you the full open-source skill library.
So @loaibassam asked me my stack recently, I replied:
FREE:
Nginx web server on Ubuntu (free)
Auto upgrade with unattended-upgrade (free)
Scheduled workers with Cron (free)
Vanilla PHP for site backend (free)
Vanilla CSS (free)
Vanilla JS for code (free)
Game servers I do in vanilla Node JS (free)
SQLite for DB (free)
Python for tool scripts (free)
Cloudflare with Cloudflare tunnel for DNS/SSL (free)
Tailscale for security (free)
OpenFreeMap for maps (free)
CHEAP:
xAI for AI API (cheap)
Stripe for payments (cheap)
Cloudflare R2 for image storage (cheap)
Hetzner VPS ($4/mo)
Cloudflare domain reg (~$10/year)
So about ~$5/mo total costs with about ~5M unique visitors per month per site (these are site averages)
a quick opus 4.5 vibecoding tip
ask claude to make state machine diagrams of existing components
this causes it to map out all paths (which, it will default to being lazy otherwise) but also helps you verify if it's doing things correctly at a systems level
🚨 Just dropped: The Affiliate Discovery Agent.
Let AI find affiliates for you.
No more manual research.
No more guessing.
Start a search, pick your channels, get real leads.
I used to do this manually for big brands, now it’s fully automated. And in your hands!
Try the Affiliate Finder now with @useAffonso 🫶
Happy prospecting!
Your app is slow.
Your users are waiting 3, 4, maybe 5 seconds for a page to load. You check your logs. The problem isn't your code. It's your database.
It's on fire. It's spending all its time running the same complex 'SELECT' queries with 'JOINs' and 'ORDER BY' clauses, over and over, just to fetch a user's profile and their 10 most recent posts from a slow, spinning disk.
You've heard of Redis. You think 'cache'.
You also think, 'it's in-memory, so if my server reboots, all my data is gone'. You think it's just a temporary, volatile speed boost, a fragile layer you can't really depend on for anything important.
That's not the full story. I was digging into it, I was expecting a simple cache. What I got was a Swiss Army Knife for my data.
Here was my journey from slow app to superpower.
Step 1: The 'Hello World' (The Obvious Cache)
This is what everyone does, and it's brilliant.
- My Problem: That slow 3-second SQL query.
- My New Workflow: I fetch the data 'once', 'SET' it in Redis (which lives in blazing-fast RAM), and set an expiration of 5 minutes.
- For the next 5 minutes, 10,000 requests for that profile are served in 'sub-milliseconds'.
- My database load just dropped 99%. My app is fast.
But the real magic begins when you stop treating it like a dumb string store.
Step 2: The Click Moment (Data Structures)
The real power is that Redis is a high-speed data 'structure' server.
- My Problem: I need a real-time leaderboard. My 'ORDER BY score' query is killing my 10-million-row 'users' table.
- My New Workflow: I use a Redis 'Sorted Set'. When a user's score changes, I 'ZADD leaderboard-main 19850 'user:123''. Redis handles the sorting 'instantly' on insertion. Fetching the top 10 is near-instant.
Step 3: The 'Wait, what?' Features
- My Problem: I need a list of recent notifications. 'SELECT ... LIMIT 20' is still a waste.
- My New Workflow: I use a Redis 'List'. When a new notification comes in, I 'LPUSH' it. Then I 'LTRIM' the list to keep it at 20 items. It's a perfect, high-speed stack.
- My Problem: I need a background job queue to send welcome emails.
- My New Workflow: I don't install RabbitMQ. I just 'LPUSH' a job to a 'List', and my worker 'BRPOP's (blocking pop) to wait for the next job. It's simple and reliable.
- My Problem: I need a real-time chat app.
- My New Workflow: I don't build a complex WebSocket server. I just use 'Pub/Sub'. It's a high-speed, lightweight message broker built-in.
Step 4: The "Pro Escape Hatch" (Debunking the Myth)
This is what sold me.
- My Fear: 'But if it reboots, my data is gone!'
- The Reality: Redis has 'persistence'. It's not on by default (for speed), but it's there.
- It can take 'snapshots' (RDB) of your dataset. Or, it can keep an 'Append-Only File' (AOF) log of every single write command.
- It's not a replacement for Postgres as your 'source of truth', but it's far from a 'throwaway' cache.
It's your cache, your message queue, your session store, your leaderboard, and your real-time engine, all in one.
I thought Redis was a 'nice-to-have' performance boost. It's not.
It's the high-speed multi-tool for your entire application.
Releasing #2 of 100 Midjourney styles designed for branding.
This one’s called Origin. Free to copy, remix, and experiment with.
Style code and 50 prompts below.
tldr trump-crash
> be me
> check charts, kompletter markt nuked
btc freefall, eth implodiert, funding -200%
> ape rein, weil angst = opportunity
> seh „trump–china trade war“ als headline, timeline voll panik
> merk sofort, narrative ist cope
> mir egal, was der trigger war, ich kauf die liquidations
> ein paar stunden später: turns out, kein makro, kein trump
> ein giga brainhat ~90m usde auf binance geflushed
> oracle bugged, preissystem kollabiert, collateral evaporiert
> liquidation engine triggert 19b$ notional, domino-effekt
> während er synchron auf anderen venues 190m short profitet
> mfw ich das absolute abyss-level gekauft hab, weil binance mathematisch implodiert ist
thx for playing, ready for the next dance 🕺
OMG… you can now fine-tune your own AI model and run it entirely on your device.
No servers.
No API keys.
No data leaks.
Gemma 3 270M just made local LLMs real and it only takes about an hour to build your own.
Here’s how: