valdis iljuconoks 🤘

Game: #DaysGone Developer: @BendStudio #PhotoMode #VirtualPhotography

I'll be doing a livestream with Figma on March 31st on how to use Claude Code with the Figma MCP to collaborate between engineers and designers. Hope to see you there, you can sign up below!

Today we're launching local scheduled tasks in Claude Code desktop. Create a schedule for tasks that you want to run regularly. They'll run as long as your computer is awake.

@trq212 hey, is it a known bug? Claude code desktop@win. you select cloud env, repo, specific branch. perform exercise and ask to create PR. Claude branches of from default branch (not the selected one). all PRs are throwaway and we need to instruct to cherry pick then.. thx!

We've rolled out a new auto-memory feature. Claude now remembers what it learns across sessions — your project context, debugging patterns, preferred approaches — and recalls it later without you having to write anything down.

Someone really built this. A VS Code extension that turns your AI agents into pixel art characters working inside a virtual office.

this guy literally built a VS Code extension that turns Claude code agents into pixel characters in a virtual office, showing what each agent is doing with animations.

Another fantastic guide from Anthropic👇 🌟The Complete Guide to Building Claude Skills🌟 • How to structure your skill folder correctly • What makes a skill trigger reliably (and what breaks it) • How to write clear, effective SKILL.md instructions • How to test, iterate, and ship production-ready skills resources.anthropic.com/hubfs/The-Comp…

@nicopreme unfortunately my diagrams are all broken. not sure what causes this..

Created an agent skill called “Visual Explainer” + set of complementary slash commands aimed to reduce my cognitive debt so the agent can explain complex things as rich HTML pages. The skill includes reference templates and a CSS pattern library so output stays consistently well-designed. Much easier for me to digest than squinting at walls of terminal text. github.com/nicobailon/vis…

Introducing: built-in git worktree support for Claude Code Now, agents can run in parallel without interfering with one other. Each agent gets its own worktree and can work independently. The Claude Code Desktop app has had built-in support for worktrees for a while, and now we're bringing it to CLI too. Learn more about worktrees: git-scm.com/docs/git-workt…

someone built a tool that REMOVES LLM CENSORSHIP in 45 minutes with a SINGLE command its called HERETIC here is how it works and why everyone is talking about it

try it

@julesagent hey, we have some issues with environment setup scripts. seems like env is not snapshotted, but script executes fine and validates ok. any ideas how to debug & diagnose? thx

Almost 40K downloads across just 3 Claude Code agents Trying them out is simple: - Go to aitmpl.com - Select Agents and browse the list - Click on one, then copy or run the command in your project - Ask Claude Code to use that agent for a task You’ll see Claude call the agent and run it in isolation, meaning the subagent works in its own context, executes the task independently, and only returns the result. keeping your main project clean and focused.

Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table. Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication. Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.” Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it. The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks. Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.

We’ve shipped three new updates for Claude Agent SDK to make it easier to build custom agents: - Support for 1M context windows - Sandboxing - V2 of our TypeScript interface

@tomcrawshaw01 GEMINI

I just spent 12 hours stress-testing Gemini Pro 3.0. The results were startling. The barrier between "technical" and "non-technical" is gone. I didn't write code. I didn't hire a dev. I didn't open n8n. I just used plain English. So let's look at what happened... The Clean Up: I pasted a description of a broken lead-routing process. Gemini spotted the bottleneck. It redesigned the logic flow. It wrote the SOPs for my team. The Analysis: I uploaded raw, messy sales transcripts. I asked for patterns. It found a pricing objection I had missed for months. That one insight is worth five figures. The Build: I requested a client portal architecture. It gave me the database schema. It mapped the user journey. It defined the error handling. Most people use this tech to write emails. That is a waste of horsepower. It’s not a chatbot, it’s a 24/7 operator. But it only works if you know how to speak to it. I documented everything I did in those 12 hours. I call it the Gemini Prompting Playbook. Inside: - 40+ Operator-grade prompts - My exact SOP frameworks - Templates to turn data into decisions I’m giving it away for free. Reply "GEMINI" below. I’ll DM you the link. (Must be following so I can message you)

@alex_prompter Claude

Fuck it. I’m giving away my full Claude Mastery Guide for free. Inside: → Claude prompt engineering mini course → 30 key principles → 10+ mega prompts → Strategic Claude use cases Comment "Claude" and I’ll DM you the file. (Follow to receive)