Some steps should be optional. This one probably shouldn't be.
Stop sending Claude-slop to your boss.
It's putting you on the edge of getting fired.
I am sure you're (definitely) sending a report with:
> unnecessary wall of text.
> titles/headings that sound like poetry.
> 12 cluttered boxes, and no idea where to start.
> no clue what you yourself are looking at, and why.
I like how Shopify's CEO calls it "slop grenades."
I spent an entire day figuring out how to un-slop those reports, whether you are the one sending or receiving them.
Here's how:
Step 1. Copy the prompt from my guide: ruben.substack.com/p/grenade
It has my free GitHub repo link. No, it's not technical
→ If you're making a new report
Copy the "make a page" prompt from the guide.
→ If you are fixing an existing one
Copy the "fix a page" prompt from the same guide.
Step 2. Attach your AI slop report to Claude.
> Your meeting notes.
> Your spreadsheet.
> Your existing report.
> Or an overwhelmingly slopped page someone just sent you to do the job, they are supposed to.
Step 3. Tell Claude (specifically) WHO will read it.
Your prompt "For Dana, my colleague" is a NO-go
Be painfully specific like: "For Dana, my CFO".
Then tell it what Dana needs to do after reading.
Step 4. The report needs to only have ONE job.
→ Either to make a decision? Put the ask on top.
→ Or to catch up? Lead with 3 or 4 numbers.
→ Or to learn a process? One step per screen.
→ Or to approve a proposal? One idea per slide.
Step 5. Now, go back to Step 1 and paste the prompt from the guide.
Do not ignore that prompt, it is going to un-slop by Claude reading my rules, then building the page for your reader.
Don't worry. You install nothing.
The prompts, before-and-after examples, and 7 types of pages are here:
ruben.substack.com/p/grenade
Take the last report you sent. Fix that one first.
Mattol retweeted
After 5 years and 100+ releases, Wasp v1.0 is in the works!
ETA: ~6 months
What's coming:
→ Every core feature reworked: Auth, RPC, Jobs, API, Deployment, etc
→ Full Stack Modules: install Stripe like a package, backend included
→ Native Windows, no WSL
→ Production-ready
Details (incl. roadmap): wasp.sh/blog/2026/10/20/wasp…
Mattol retweeted
You don't have to read the code.
Seriously. If you want to get the thing live, feel the product, play with the UX, then go. It's incredible that you can.
Just know what you're trading away when you skip it.
Then decide for yourself 🧵
Design doc dilemma:
Share at 50% → people poke holes I knew about.
Polish to 95% → too much time on something the team might kill in 5 min.
Trying a middle step: an AI review panel first. 5 AI personas vote on every item, then argue.
1
10
Mattol retweeted
Understanding is king.
Reject non-understanding.
Slop grenades are not just code and PRs. We run a real risk that *reading* gets entirely discounted, because of the exhaustion of getting low-quality and unverified AI prose being thrown at you all the time.
There's a thread going viral about a 'perf improvement' attributed to a compiler change. The PR *description* itself has the AI telling this person it's *not* due to the compiler change, it's how the algorithms and data structures have changed. And the implication is that a similar win could have been attained otherwise.
I want AI in the service of understanding the universe and enhancing human cognition and creativity.
44 skills for Small Business by Anthropic
Feels a little like cheating.
Check it out: claude.ai/customize/skills/i…
13
Give yourself and your AI a better toolkit.
There are so many good ones available that it feels way better than fighting your way through every niche from scratch.
Thanks @infomiho for mentioning this skills repo 🙌
jakub.kr/skills
Caught myself treating real life like Claude today. Wife gives an amazing answer → my brain: “Great, let's reuse this skill.” 😄
1
17
Running an internal AI assistant for our team and one of the trickier parts isn't the answers, it's when it should speak at all. Right now a cheap model reads every message and says yes or no -> is this worth the bot's attention -> and only on yes does it go to the bigger model.
8
Wanted my bot to send me a weekly digest on a topic from X, but the API is expensive. So the plan is a hand-picked list of people instead and while looking for them I found out X search takes actual boolean queries. Probably old news, still useful.
13
Mattol retweeted
As a startup founder, organizing myself is not easy, and usually all my productivity setups fall apart fast.
But, my GTD-like one I configured in Emacs, has now been going strong for a year or so!
It got to a place that actually works in practice for me, and its great being able to rely on it. Also ties up awesomely with AI.
Mattol retweeted
Instead of trying to engineer the perfect AI harness for a specific project, I would rather find the perfect abstraction for implementing it, acting as a harness.
You won't have AI generate assembly and then write a bunch of rules on what assembly needs to look like. You will instead use a higher-level language.
We should chase the same logic for most of the projects where there is potential for this -> first raise the abstraction, then comes the harness as a neccessary evil.
GPT-image 2.5 is soooo good!
I built this flipbook generator app a while ago but other models weren't cutting it. With gpt-image 2.5 I get great sequences and trueness to my original drawing.
This app is open-source if y'all wanna play with it. Here's how it works:
> user draws the starting frame
> user enters animation prompt (works best if its a loop)
> gpt-image 2.5 sunburst generates a quick sprite sheet for sequence consistency.
> sends the sheet to a job that generates each frame based on the next sprite in the sequence.
github.com/vincanger/gpt-ima…
This makes WebMCP even more important to learn:
github.com/vincanger/webmcp-…
💌 Wasp now supports @resend for sending emails 🐝
Set emailSender: { provider: "Resend" }, add your API key, and you're sending. No SMTP credentials, no extra packages - the official SDK comes wired in.
✉️ Send from anywhere on the server with emailSender.send()
🔐 Auth flows covered: verification & password reset emails go through Resend, zero extra code
🔁 Switching providers is a one-line change
🧑🚀 Built by community contributor Jamie Davenport - thanks Jamie! 🙏
Live in Wasp 0.25 - full guide below 👇
















