This resonates. We've been moving toward this with AI coding assistants, the ticket description IS the prompt. The better you write the ticket, the better the output. The missing piece is giving the AI agent enough context about your codebase conventions. Things like MCP servers that expose project-specific tools and rules help bridge that gap.
Love this approach of compiling a readable language to a platform-specific format. Same pattern works well for i18n. Write in one language, compile/translate to the target formats automatically.
The developer experience of writing real code instead of clicking through a GUI (Shortcuts app in this case) is always the right bet for power users
This is interesting for MCP server deployment. Right now most MCP servers run as local stdio processes. Containerizing them would solve the security and isolation concerns that come up every time someone installs a thirdparty MCP server.
Would love to see this support stdio-to-HTTP bridging so local MCP servers can be exposed as remote ones without rewriting them.