ICYMI: @levelsio shipped a flight simulator game last week. It's pretty fun, it's got some low poly / minecraft-esque graphics, pretty good physics, a turbo boost, and even PvP. The kicker is he built it, at least the version one anyway entirely by prompting @Cursor.
It got me thinking about a question that a ton of people have tried to answer in the past few years; What does the future look like for someone getting into development?
Composer 2 by Cursor is a frontier-level coding model built for complex, long-horizon development tasks. It combines strong benchmark performance with highly efficient pricing ($0.50/M input, $2.50/M output). Powered by continued pretraining and reinforcement learning, it delivers smarter code generation with better cost-performance, plus a faster variant for real-time workflows.
Recently stumbled across this Cursor pro-tip from Ian Nuttall on X: "1. ask it to recommend a folder structure
2. ask it to actually create the folder/files based on that this makes it 10x easier for me to get started and Cursor is more accurate using codebase cos it knows where to update files."
That got me thinking, what other pro tips are people using to generate better code, ship faster, organise your space better, etc. Drop em below:
Personally I started creating app on cursor Just for fun, but recently I started to understand basics and my apps started to become more marketable. What about you? How is going your vibe journey?
You can now work with Cursor Agents on web and mobile. Just like the familiar agent that works alongside you in the IDE, agents on web and mobile can write code, answer complex questions, and scaffold out your work.
Now with automated code review to catch and fix bugs in your PRs, memories to learn from your codebase, 1-click MCP installs, and Background Agent in GA. Plus, faster multi-location edits, richer chat interactions, new settings, and Jupyter notebook support.