Glean 拾遗
Daily · timeline

A few picks a day.

Tue, Jun 23, 2026 3picks
← 06-22
Calendar ▾
2026 · 06
MoTuWeThFrSaSu 123456789101112131415161718192021222324252627282930
has picks today
06:00

The Debug Loop: How Claude Code Finds the Bug in 6 Steps Instead of 60

调试循环:6步而非60步,用Claude Code定位根因

Most developers debug with Claude Code by pasting errors and accepting speculative fixes, leading to a 40-60 message death spiral. This post proposes a six-step loop: first establish a reliable repro (failing test), isolate the search area in plan mode, dispatch read-only subagents to trace root causes from multiple angles, fix only the root cause (not symptoms), verify with an automatic hook (e.g., PostToolUse running the test), and keep the repro as a permanent regression test. The key insight is that Claude Code was always capable; the failure mode is skipping straight to 'fix' before understanding the bug.

06:00

How to Build an AI Second Brain With Claude and Obsidian That Gets Smarter Every Day (Full Guide)

用 Claude 和 Obsidian 搭建每日进化的 AI 第二大脑完整指南

A step-by-step guide to building a persistent 'second brain' using Claude and Obsidian, based on Andrej Karpathy's LLM Wiki pattern. Obsidian stores all notes as local plain text files, while Claude (via MCP protocol) reads, organizes, and links the entire vault. Key steps: install Claude Desktop (paid plan), install Obsidian with Local REST API plugin, connect via MCP, create a CLAUDE.md profile via interview, structure projects with Inputs/Process/Outputs/Feedback folders, build reusable skills, wire in live data (calendar, email), and set up autopilot scheduling. The author stresses ownership (plain text, vendor-independent) and security ('keys, not prompts'). Aimed at engineers and knowledge workers tired of context loss.

x.com · 11 min · Ai-Memory · Claude Code · Context Engineering · Mcp · Open Source
06:00

Vercel's AI Design Spec: A Textbook Example

Vercel 的 AI 设计规范:一份教科书级的参考

This article deeply analyzes Vercel's DESIGN.md, showcasing how to write an efficient and executable design specification for AI. It breaks down Vercel's approach across color, spacing, typography, motion, copy, and accessibility, revealing the thinking behind it. The color system uses a 100-1000 scale where each number corresponds to a fixed UI state (default, hover, click), eliminating AI guesswork. Spacing is limited to 9 values based on 4px increments, enforcing rhythmic consistency. Typography adopts role-based thinking (heading/label/copy/button) instead of pixel-based thinking. Motion design advocates 'no animation is often best' and gives precise durations per scenario. This piece is valuable for product managers, front-end engineers, and AI tool developers aiming to improve AI-generated UI consistency or build their own design specs.

x.com · 4 min · Ai Tooling · Design System · Developer Tools · Vercel