@lushptr · X

I feel really guilty for vibe coding this but it looks cool even tho it is really inefficient and broken you can use it too now I'll desloppify it after exams I swear

@rotaercz · X

Built it for my son. 0 MRR but priceless to make a child happy.

@maxchu2021 · X

160 Three.js examples built with Claude through vibe coding. AI didn’t replace coding—it accelerated experimentation and iteration. Next step: turning these demos into production-ready products. Link: #ThreeJS #WebGL #AI #Claude #VibeCoding

@Sparsh209 · X

Hi isha! Check it out here at: Would love to hear your feedbacks

@MengTo · X

These will instantly make your vibe-coded projects look less generic. Free, open-source libraries from the same creator: • • •

@zdkiel_labs · X

Started with a single image. Ended with an interactive Three.js scene. Still amazed that experiences like this run entirely in the browser. Built with img2threejs + Claude Code. Demo ↓ @threejs

@songfeitong · X

Introducing Pretty Lattice, a modern-looking crystal visualization tool for creating beautiful figures. Built with Codex since 5.5, and now with 5.6 sol. A huge leap from 5.5, much better at frond end. Github: Demo:

@OprosOlamiflex · X

Check out what I just built with Lovable!

@vkuoo · X

Added more demos showcasing graph-math relationships, built with Codex.

ahmedxuhri · HN

Postroom – HN thread 2D Visualizer as auditorium AI-powered summaries

chenglong-hn · HN

Data visualizations are the bridge between user and data. But building AI agents that can generate visualizations reliably can be very tricky: - simple chart specs can be reliable, but generated charts are often of low quality due to reliance on system defaults; - complex chart specs with explicit details can produce good-looking charts, but they are verbose and agents can struggle with reliability We figured out it is a limitation on the language issue (not just AI capability thing) -- current visualization languages are a bit too low-level for AI agents, requiring them to explicitly make visual decisions that are supposed to be handled by a good compiler. Flint is a visualization intermediate language to address this issue, allow AI agents to solve this last-mile human-agent interaction problem. It provides a simple semantic-type based specification, and contains a layout optimization engine that can produce good-looking charts (filled with derived low-level details) from simple

@ashkans_dev · X

An ETL tool: