Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More
3 contributions to AI Automation Society
5 Claude Skills I Can't Live Without
Last week I wrote in detail about my favorite Claude skill here: https://www.skool.com/ai-automation-society/how-i-5xd-my-builds-with-my-favorite-planning-skill?p=591ec641. I wanted to expand on that and talk about the others that make my life easier. 1. Superpowers (my #1, see link above) - What it does: a full build system. Instead of letting the agent jump straight into code, it makes it stop and pull a real spec out of you first, then write a step-by-step plan, then build it one task at a time with a review check between each task. - Why it's needed: AI likes to fix things without thinking about what the fix might break. This makes it figure out a detailed plan and consider consequences before it's allowed to start building. You can install it today as an official plugin. It also works in Cursor, Codex, Gemini CLI, and others. 2. Compact (public, built into Claude Code) - What it does: it compresses your current conversation into a tight summary and keeps going, freeing up room so a long session doesn't hit the context limit or lose the thread. You're mid-project, the window is filling up, you run it, and the work continues from a condensed version of everything so far. - Why it's needed: I'm sure most of you know this, but the more context in a session, the more your token usage goes up and the dumber Claude gets. I'm aggressive about compacting to save my weekly token cap and to keep Claude running lean and smart. 3. Wrap - What it does: an end-of-session checkpoint. Before I shut down or the context fills up, it sweeps everything the session produced into permanent places: memory files, docs, my todo list, git, and a short handoff note for next time. - Why it's needed: Compact does it's best to summarize the important things that happened in the session, but it's judgment based and it doesn't always get it right. /wrap summarizes every important detail, saves it to my memory and claude markdowns, and writes a detailed handoff file for the session to pick up after I compact. - I built this one wired into my own project tooling, so it's not a plug-and-play download. The idea is simple to copy, though, and worth copying.
2 likes • Aug 18
bro the transcripts one is an absolute gamechanger lol. Saves so much time vs copying it manually.
#AIS day 2 Scraper for leads
Daily Wins I scraped a marketing role from WeWork Remotely and also a sitemap for Blue Tokai Coffee.
#AIS day 2 Scraper for leads
1 like • Aug 18
Let's go. How many can you scrape per day though? Is there a limit?
Day 3 Building a Real Claude Code Skill
Today combined the Day 3 theory (skill anatomy, progressive loading) with a full hands-on build: a real, working Claude Code skill for a client project, built from an empty folder to a tested, functioning tool. What was built: agency-infographic Brand system (reference.md, sourced from the real platanusdesign-brand skill): PlatanusDesign's actual colors (#F47D20 orange accent, #341390 indigo, etc.), Poppins/Open Sans typography, real logo usage rules, and a "card grid" layout pattern refined through iteration — solid black background, large topic-specific icons in orange, orange card headings, white body text. Outcome: A fully working, tested skill: confirmed to research, draft, gate on user confirmation, render on-brand output, and generalize correctly across unrelated topics/industries — built and debugged hands-on rather than handed over per-made.
Day 3 Building a Real Claude Code Skill
2 likes • Aug 18
solid work man, which part did you find most difficult?
1-3 of 3
@behnam-piltan-9117
On a mission

Active 2d ago
Joined May 21, 2026
Powered by