Viliam Elischer @vireliam

Something I have been thinking about: in the past, the best engineers I knew spent a lot of time automating their work in various ways. Better vim/emacs automations, writing lint rules to catch repeat code issues, building up a suite of e2e tests so they don't need to smoke test the app manually. These kinds of things were the highest leverage activities an engineer could do, because it multiplied their own output, which in turn meant they could build more things. I think many of these automations have become even more important now. This is true for a number of reasons. First, infra and DevX automation speeds you up. And if you are running an army of agents, each of those agents will be sped up also. More automation == more output per unit of time. Second, moving things to code improves efficiency. Your agent could fix an issue every time it sees that issue happen, but that uses tokens and might miss cases. If Claude instead writes a lint rule, CI step, or routine, that class of issue can be fully automated forever. This is really what people are talking about when they talk about loops -- it's about automating entire types of busywork rather than solving them one off. This isn't a new idea at all. Engineers have been doing this for a long time! Third and most importantly, automation makes it possible for others to contribute to the codebase more easily. Increasingly what I am seeing is engineers are contributing to codebases on day one because Claude can navigate the codebase for them, and that non-engineers are able to contribute to a codebase as effectively as engineers can. What gets in the way of both of these is domain knowledge that lives in peoples' heads rather than in automation -- the stuff you used to have to learn when ramping up. What has changed thanks to agents is the domain knowledge that can be encoded as infrastructure is no longer limited to what is expressible in lint rules and types and tests; it can now capture nearly all domain knowledge, encoded as code comments and skills and CLAUDE.md rules and memories. If I put up a PR for an iOS codebase I don't know and a code reviewer rejects it because it doesn't use the right framework, or if a designer builds a new feature and it gets rejected because it doesn't follow the right architectural patterns, these are failures of automation. Every team should be writing the CLAUDE.md's, REVIEW.md's, skills, and docs that enable agents to productively work in their codebase with zero additional context from the prompter. This sounds crazy, and at the same time is a natural extension of the stuff engineers have always done: automate, and encode domain knowledge as infrastructure. As the model gets smarter and as the harness matures, this task becomes easier. In the meantime, it is on every team to look for ways to convert their domain knowledge to infra so that Claude can write code better, so that code review catches issues automatically, and so the next person working on your codebase can contribute more easily.

@ChrisArtmann But then also Bash is all your agent needs 🤖 at least according to Brex (there's some truth) brex.com/journal/long-r…

Great read

George Sivulka @gsivulka

6 days ago

x.com/i/article/2075…

136 360 2K 2.1M 4K

Today we're shipping screen-aware dictation. First, we built a speedy speech-to-text (very fast, ~450ms). But, many products do this! So we went further. Now dictate using your screen as context. In Claude Code, it writes the prompt. In G-Mail, it replies in your voice. Demo:

AGENTS.md/CLAUDE.md is largely an anti-pattern

introducing screenpipe: it records and learns how you work and turns it into a searchable memory, SOPs, and AI agents open source, local-first, 20K+ GitHub stars, 1,900+ forks, and 130+ contributors

Coding with AI showed you could give models powerful tools and dramatically improve their usefulness. We're seeing the same thing happen now for all knowledge work. The agent can use the computer as you would and gain context from all the apps you use. The future is exciting!

Our Excalidraw+ MCP is getting stronger by the day! Diagrams and arrow connections now improved.

This makes artifacts much more expressive and can be combined in creative ways. One of my favorites is to create a dashboard for a project in Claude Tag that can be edited by others or by my local Claude Code sessions.

ClaudeDevs @ClaudeDevs

7 days ago

Artifacts now support public sharing and multiplayer editing in Claude Code, and can be created with Claude Tag.

193 209 4K 625K 950

Introducing Blume 🪷 A world-class docs framework for everything you ship. Drop Markdown into a folder and ship a full docs site with no app boilerplate. → zero-config setup → automatic SEO and AEO → 30+ components → powered by astro + vite → open source, free forever

1. Delete the docs you create to explain your code 2. Take the tokens you save on updating those docs 3. Spend them on making your code self-explanatory

You can now write Native SDK apps in TypeScript For agents: half the turns, half the cost, half the LOC → Compiles to native → No JS engine, no GC → 83ns update dispatch → Real TS: Classes, generics, try/catch → No Zig required / eject to Zig anytime

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!

mattpocock/skills v1.1 is out! - /wayfinder helps you plan more ambitious work than ever - /to-spec and /to-tickets replace /to-prd and /to-issues - /implement + /code-review complete the whole lifecycle - /research and /prototype help support wayfinder, or can be used independently - Crucial fixes to /grill-me Run npx skills@latest add mattpocock/skills to update!

Here's a step-by-step process to kill all the bloat from your Claude Code system prompt: 1. Run a proxy so you can see exactly what gets sent to Claude Code (included in the article) 2. "Fuck, there is so much cruft in there" 3. Use my settings.json to kill all the bloat Down to a clean 13K tokens to start each session with. Nice. Full process here: aihero.dev/how-to-kill-th…

Claude Cowork is coming to mobile and web. Hand Claude a task at your desk and pick up the finished work from your phone. Close the laptop and Claude keeps going. Beta is rolling out over the next several weeks starting with the Max plan, with more plans to follow.

In the next version of codex.bar - see exactly when you resets expire so you can up your ̶t̶o̶k̶e̶n̶m̶a̶x̶x̶i̶n̶g̶ valuemaxxing game!

Mám takovou libůstku: sleduju na Githubu nové zajímavé repozitáře. Udělal jsem vám z toho web stránku. Mrkněte se, jestli by vám vyhovovala takto nebo jinak a jestli vám přijde užitečná: vibecoding.cz/radar

PostgreSQL 19 keeps eating the stack. AI apps need more than vectors. They need relationships: users → documents users → topics users → creators Relational + JSON + vectors + graph queries. The industry keeps adding more databases. Postgres keeps removing reasons to need them. x.com/alxshp/status/…

alex shapalov @alxshp

3 weeks ago

PostgreSQL 19 will bring graph-style querying to SQL. You can describe relationship paths like: user → likes → topic ← likes ← peer → follows → creator That is useful for recommendations, permissions, social graphs, fraud paths, and AI memory. x.com/alxshp/status/…

6 34 333 62K 148

claude fable 5 can scrape thousands of sold homes and finds the patios with zero shade in 100°+ heat. then it mails the owner a postcard with the fix rendered into their own backyard here's the system you can sell to contractors: - scrapes every home sold in the metro in the last 12 months (recent buyers spend the most) - vision-reads the listing photos, skips the 64% with cover already - measures the sun on each patio, hour by hour, off google's satellite data - renders a louvered pergola into the owner's actual backyard photo - prints the diagnosis on the postcard: "your patio takes 11 hours of direct sun a day. saturday it hits 97°." - QR opens a heat report for their exact address with a booking link every install is $6.5k to $18k, one close covers months of retainers and homes sell every single day. reply "SYSTEM" + RT and i'll send you a free guide so you can build this too (must be following so i can DM you)