ASCII characters are not pixels: a deep dive into ASCII rendering

jQuery 4

Iconify: Library of Open Source Icons

Predicting OpenAI's ad strategy

Erdos 281 solved with ChatGPT 5.2 Pro

Command-line Tools can be 235x Faster than your Hadoop Cluster (2014)

ThinkNext Design

Profession by Isaac Asimov (1957)

How London cracked mobile phone coverage on the Underground

What is Plan 9?

Gaussian Splatting – A$AP Rocky Helicopter Music Video

Milk-V Titan: A $329 8-Core 64-bit RISC-V mini-ITX board with PCIe Gen4x16

A free and open-source rootkit for Linux

Starting from scratch: Training a 30M Topological Transformer

A Social Filesystem

I&#x27;m Dan, and I built a CLI that lets AI agents design in Figma.What it does: 100 commands to create shapes, text, frames, components, modify styles, export assets. JSX importing that&#x27;s ~100x faster than any plugin API import. Works with any LLM coding assistant.Why I built it: The official Figma MCP server can only read files. I wanted AI to actually design — create buttons, build layouts, generate entire component systems. Existing solutions were either read-only or required verbose JSON schemas that burn through tokens.Demo (45 sec): <a href="https:&#x2F;&#x2F;youtu.be&#x2F;9eSYVZRle7o" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;9eSYVZRle7o</a>Tech stack: Bun + Citty for CLI, Elysia WebSocket proxy, Figma plugin. The render command connects to Figma&#x27;s internal multiplayer protocol via Chrome DevTools for extra performance when dealing with large groups of objects.Try it: bun install -g @dannote&#x2F;figma-useLooking for feedback on CLI ergonomics, missing commands, and whether the JSX syntax feels natural.

HN