Launched this week
Yansu
AI that learns how you work and turns it into software
813 followers
AI that learns how you work and turns it into software
813 followers
Yanshu learns from the work you already do. It spots repeated tasks across files, messages, and workflows, then turns the best patterns into apps and automations. No process mapping or blank canvas—just the routines worth systemizing. Use it to automate recurring work, build lightweight internal tools, and speed up daily ops without writing code.
DeckSpeed
Really like the positioning of Yansu as “serious coding” rather than just another AI code generation tool. In real-world software projects, the hard part is rarely just producing more code — it’s aligning intent, specs, edge cases, team knowledge, and long-term maintainability. The idea of combining spec-driven development, scenario simulation, human QA, and traceable code feels very relevant for teams building complex products. Excited to see more AI coding platforms move from vibe coding to reliable engineering outcomes. Congrats on the launch!
@hanzhizhang0405 Thank you — really appreciate this.
From a design perspective, that’s exactly what feels important to us: moving beyond “generate more code” toward clearer intent, better alignment, and a product experience teams can actually trust in real workflows.
DeckSpeed
@miltonheyan Thanks! 🙏 If you give it a spin, I'd love to know what the first crystal Yansu suggests for you turns out to be — sometimes the surprises are the best part.
Wow. this looks promising! i'm always wondering how i can automate tasks, but i have to do an audit manually and then write on clickup to create an automation. it would be great if there is a process that automatically spots tasks to automate!
I like that this starts from observing real workflows instead of asking users to manually design automations from scratch. Turning repeated work patterns into lightweight internal tools feels much more natural for teams that want automation without spending weeks setting up complex systems.
Upvoted only because of a fun video :-)
How do you think about pricing for something that builds unique software per user—subscription, usage-based, or outcome-based?
What’s the most surprising entity relationship Yansu has discovered about a beta user that the user themselves hadn’t explicitly realized?