惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Blog — PlanetScale
Blog — PlanetScale
J
Java Code Geeks
月光博客
月光博客
Engineering at Meta
Engineering at Meta
WordPress大学
WordPress大学
Jina AI
Jina AI
小众软件
小众软件
U
Unit 42
云风的 BLOG
云风的 BLOG
Stack Overflow Blog
Stack Overflow Blog
雷峰网
雷峰网
博客园 - Franky
Microsoft Security Blog
Microsoft Security Blog
罗磊的独立博客
宝玉的分享
宝玉的分享
B
Blog
C
Check Point Blog
爱范儿
爱范儿
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
量子位
阮一峰的网络日志
阮一峰的网络日志
Vercel News
Vercel News
酷 壳 – CoolShell
酷 壳 – CoolShell

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Communicate Ideas Visually: Let AI Run the Feedback Loop
Ooi Yee Fei · 2026-05-26 · via DEV Community
Cover image for Communicate Ideas Visually: Let AI Run the Feedback Loop

Ooi Yee Fei

Share a rich HTML doc, gather everyone's comments on it, let AI converge and facilitate continuously

I shared htmldrop earlier — a Claude Code skill + CLI that turns any HTML file into a one-command shareable link. But sharing is only half the problem. The other half is discussion — and today that goes to die in buried chat threads, or worse, in competing V1/V2/V3 documents that never actually respond to each other. Someone sends a spec; you reply with your own AI-polished counter-spec; now there are two confident docs talking past each other.

This is the other half — making the shared document the place the conversation actually happens, and then making it easy to act on that conversation.

A link and a password is all it takes to get in — and the page lands as a place to talk, not just read. From there, anyone you've shared it with reacts right on the document: highlight a sentence to comment, select a passage, or drag a box around a diagram — every note pinned to the exact part it's about, no account needed.

Then the part I care about most. Getting comments is easy; knowing what to do with them isn't — some are clean fixes, some are real forks in the road. So you bring the whole thread back to your coding agent: it folds in the clear wins (a vague metric becomes a concrete target) and, on the genuine disagreements, lays out both sides and leaves the call to you. Re-publish and the same link shows the next version, comments intact — the document evolves from the conversation instead of forking into V1/V2/V3 copies that never answer each other.

Example of how it looks like after convergence:

It's open source, works with whatever coding agent you already use (Claude Code, Codex, Gemini CLI, Antigravity…), and your-own-data — self-host the comment backend, or just keep every comment in your repo as the record.

If you want to try it yourself, here's the detailed walkthrough:

Read the full writeup on Build Signals