todai
Thursday, 21 May
5 min read · 834 words

REDDIT SIGNAL

  • Workflow — "11 Claude things I wish someone had told me 12 months ago" — 11 high-signal tips from 18 months of daily Claude use: CLAUDE.md over prompts, Skills over custom instructions, subagents for parallel test runs, Haiku for batch jobs, and Artifacts calling the API ("Claudeception") — 1,664 upvotes, 126 comments | r/ClaudeAI | https://www.reddit.com/r/ClaudeAI/comments/1tgqnsl/
  • Security — "Your Agent Is Mine" paper resurfacing: 9 of 28 paid + 400+ free LLM API routers actively inject malicious code into tool calls, 17 touched researcher AWS keys, 2 only attack after 50 calls or in YOLO mode — 68 upvotes, 44 comments | r/LLMDevs | https://www.reddit.com/r/LLMDevs/comments/1te9s3a/
  • rohitg00/ai-engineering-from-scratch — 762★ today (9,330★ total) — 428-lesson open curriculum (Python, TypeScript, Rust, Julia) from linear algebra to autonomous agent swarms — every lesson ships a reusable prompt, skill, or MCP server | https://github.com/rohitg00/ai-engineering-from-scratch

TODAY'S ITEMS

1. Claude Code v2.1.145 — <code>claude agents --json</code>, Plugin Previews, Security Fix

  • New today: claude agents --json lists live Claude Code sessions as JSON for scripting into tmux, status bars, or session pickers; /plugin Discover and Browse screens now show a plugin's commands, agents, skills, hooks, and MCP servers before you install; terminal tab titles show awaiting-input count when agents need attention.
  • Security patch: a permission bypass where bare variable assignments to non-allowlisted env vars were auto-approved — update now if you use bash hooks or permissive env var workflows.
  • Source: Claude Code Releases
  • Why it matters: If you run Claude Code with bash hooks or custom env var configurations, update now — the auto-approved permission bypass is a real exposure.
  • Verified

2. The Anthropic Stack: 4-Step Change Request → Clean PR Workflow

  • Today's Anthropic Stack newsletter lays out a concrete pattern: natural language change request → file/code path map → targeted patch plan → test proposals — cutting a 3–6 hour SME task to under an hour.
  • Key discipline: state rule ordering explicitly before any code edit, or the agent rewrites logic silently (VAT/discount sequence example in the piece).
  • Source: The Anthropic Stack
  • Why it matters: Adding a file map step before any code edit is the single change that makes Claude Code genuinely reliable for messy real-world change requests.
  • Verified

3. Google I/O 2026: Gemini Spark + Antigravity 2.0 Are Live

  • Google announced Gemini Spark (a direct OpenClaw competitor — personal AI agent with native Gmail, Calendar, Drive, Docs, Sheets, YouTube integration) and Antigravity (Claude Code equivalent: CLI agent in Go, VS Code fork IDE, Python SDK).
  • Gemini 3.5 Flash is shipping now; most other I/O announcements are "coming soon" — Simon Willison's coverage is the sharpest breakdown available.
  • Source: Simon Willison
  • Why it matters: Antigravity is now an installable CLI with an open Python SDK — worth understanding before clients ask how it compares to Claude Code.
  • Verified

NEW TOOL / PRODUCT SPOTLIGHT

  • alirezarezvani/claude-skills — 15,651★ — 313+ Claude Code skills and agent plugins (engineering, marketing, product, compliance, research, finance, C-level advisory) — works with Claude Code, Codex, Gemini CLI, and Cursor. git clone https://github.com/alirezarezvani/claude-skills | https://github.com/alirezarezvani/claude-skills

PROMPT OF THE DAY

You are a skilled PR author. For the change request below, do the
following steps in order — do not skip or combine any step:

Step 1 — File map: List every file (with path) that contains the logic
the change request affects. For each file, one sentence on what it does
and why it's relevant.

Step 2 — Rule ordering: Write a short paragraph (3–5 sentences) on the
sequence of operations as they currently exist, and how this change will
alter that sequence. Be explicit: "X happens before Y. After this change,
Y will happen before X."

Step 3 — Patch plan: List the specific edits to make, file by file,
before writing any code. Stop here and wait for my approval.

Step 4 (after approval) — Write the PR description: what changed, why,
what was not changed, and what the reviewer should test manually.

Change request: Move regional discounts to apply before VAT in the
pricing module.

Four-step structured workflow for handing off any change request to Claude Code — forces the file-map-first discipline from today's Anthropic Stack. Community source: https://theanthropicstack.substack.com/p/from-messy-change-requests-to-clean

LANDSCAPE NOTES