Speed up feature delivery by moving a team to Cursor
- Source date:
- Last verified:
- Method:
- How we verify
Evidence: Article or interviewA newsletter, journalist or interview account of what happened.
Outcome
Security startup Jit moved its engineers from JetBrains to Cursor and, according to the article, delivered features 1.8–3x faster.
Reported by LeadDev:1.8x–3x productivity gains
This is the source's own number. We haven't measured it.
Agent
Prompt Recreated prompt
The source did not publish its exact prompt. This one is our reconstruction from what the source describes.
Not sure how to start? Tell me what you're trying to get done and I'll help you turn it into a clear request. Goal: Build this feature from start to finish, front end and back end, following my team's coding rules, and open a pull request for review. Quick check first: what should the finished feature do? Tell me the one or two things that matter most, so we agree on what "done" means. What I need from you: - The ticket or a short description of the feature - Your team's coding rules in Cursor (the language, frameworks, style guidelines and folder structure you use) - Access to the code repository, and permission to commit and open a pull request Rules: - Follow the team's coding rules everywhere, so the code looks like a teammate wrote it and not generic code. - Only change what this feature needs. - If the ticket or the rules don't answer something, ask me instead of guessing. - When the work is done, commit it, open a pull request, and update the ticket. If reviewers leave comments, address them. - Don't merge. Stop once the pull request is open and hand it back to me. Output: the pull request link, a short plain-language summary of what changed, and any open questions. If any of this is unclear, tell me what you have and I'll help fill the gaps. You'll know it worked when: the feature behaves the way the ticket describes and the pull request is ready for a teammate to review. You can also ask me to: address review comments on an existing pull request, or update or create the ticket for this work. Works best when: your team's coding rules are already written down in Cursor.
Source
https://leaddev.com/technical-direction/how-jit-overcame-developer-resistance-shift-cursor
By Chantal Kapani (LeadDev) · Published May 15, 2025 · Added Oct 15, 2026 · Last verified Oct 15, 2026
Related cases
- Automate defect remediation across C/C++ codebases with Codex CLIRecreated promptEvidence: Company case study
According to OpenAI's case study, Cisco's Codex CLI defect-repair workflow raised defect resolution throughput 10–15x, and Codex build optimization saved more than 1,500 engineering hours a month.
According to OpenAI:10–15x defect resolution throughput
OpenAI Codex CLI · Coding · Source date:
- Write and ship a complete Datasette plugin with Claude CodeEvidence: Screenshots or logs
Claude Code (Sonnet 4.5) wrote every line of code and every test for the datasette-os-info plugin with minimal prompting, and the author shipped it.
Claude Code · Coding · Source date:
- Migrate two websites from WordPress to Wagtail with Claude CodeRecreated promptEvidence: Described by poster
Over a weekend Claude Code migrated two sites from WordPress to Wagtail (PHP to Python), including server setup, data transfer, testing and fixes, and redesigned a homepage; the poster reports nothing broke and traffic and tools stayed in place.
Claude Code · Coding · Source date: