aditgupta

Jim nailed the core problem. I've been building exactly this "missing layer" for past few months. The challenge isn't just connecting product decisions to code. It's that product context lives in a format that's optimized for human communication, not machine consumption. When engineers feed this to LLMs, they spend massive effort "re-contextualizing" what stakeholders already decided. I built TypMo (https://typmo.com) around two structured formats that serve as this context layer: PTL (Product Thinking Language)- Structures product decisions (personas, objectives, constraints, requirements) in a format both humans can read/edit and LLMs can parse precisely. Think YAML for product thinking. and Interface Structure Language (ISL) - Defines wireframes and component hierarchies in structured syntax that compiles into visual mockups and production-ready prompts. LLMs don't need more context, they need structured context. The workflow Jim describes (stakeholder meeting → manager aggregates → engineer re-contextualizes for LLM) becomes: stakeholder meeting → PTL compilation → IA generation → production prompts.

LEt's see where it goes!

I wanted a minimal tool to easily track, organize, and reflect on my reading—so I built one: https://bookstates.app. I'm familiar with StoryGraph, but aimed for something even simpler. (and with a sprinkle of AI)

I made a simple iOS app for designers called as UX Assist. It has been around for 6 years now. I’m just happy that it’s out there and helping some folks now and then. [UX Assist](https://apps.apple.com/in/app/ux-assist/id1491649877)