r/cursor — Reddit Community Analysis & Distribution Playbook

1. Data Sources & Methodology

• Unique posts analyzed: 292 (after dedupe across 16 raw JSON files)
• Collection method: Top posts across 4 time periods (all / year / month / week), 4 pages each
• Date collected: 2026-04-10
• Subreddit subscribers: 131,494
• Created: Feb 2024 (r/cursor is young — ~2 years old at collection)
• Score range: 1 — 1,332
• Dataset median score: 80
• Top-25 threshold: 717 | Top-50 threshold: 472 | Top-100 threshold: 367

Per-period breakdown (100 posts each):

The collapse from "month" (median 41) to "week" (median 3) is dramatic. It reflects two realities: (1) the sub is in the middle of a product-crisis cycle around Cursor 3 / Composer 2, and (2) mod enforcement and the "No rants / No slop" rules suppress most reactive posts before they can gather upvotes. The "week" dataset is mostly questions and bug reports — the daily churn of a support forum.

Cross-subreddit score calibration: r/cursor caps at ~1,332. Compare:

• r/ClaudeAI: ~8,084 (larger, broader AI audience)
• r/vibecoding: ~2,500-ish ceiling, median ~838
• r/macapps: ~2,029, median ~445
• r/cursor: ~1,332, median 80

r/cursor's ceiling is roughly 16% of r/ClaudeAI's despite being adjacent in topic. It punches well below weight because it is a single-product support community rather than a general-interest subreddit. People come here to complain, get help, and find workflow tricks — not to browse. The median of 80 vs a top-25 threshold of 717 means the gap between "typical" and "hit" is 9x, much wider than in browse-heavy subs like r/macapps. Translation: on r/cursor, most posts die quiet, but the ones that break through break through hard.

Scope: This is a content strategy guide for r/cursor, not a sociological study. Every claim here is backed by a specific post from the 292-post dataset.

2. Subreddit Character

One-line frame: r/cursor is a betrayed-lover support group for a product the users still can't quit — one half workflow confessional, one half pricing-change pitchfork rally, moderated by an increasingly-present Cursor team trying to rebuild trust in public.

Who posts here: Working developers — overwhelmingly full-stack web (Next.js, React, Python, TypeScript) — who have been paying Cursor $20-$200/month for months or years. They are not beginners. Even the "I'm new, help me" posts come from senior engineers evaluating Cursor against Claude Code, Codex, Windsurf, and Zed. The rare beginner posts (#238, #285) get downvoted or ignored. This is a power-user audience that knows what a .cursorrules file is, can discuss tool calls per request, and will reverse-engineer the gRPC protocol (#2) if they suspect throttling.

Is this sub hostile to launches? It depends on what you're launching. Cursor-adjacent tools (MCP servers, menu-bar usage trackers, cursor rules generators, skills registries, remote-control apps) are welcome and scored well: Vibeviewer menu bar tracker (#122, s325), Code Web Chat extension (#41, s544), Cursor for Mobile (#10, s892), crag rule compiler (#228, s8 but r0.90). Competitors pitched as "better than Cursor" are tolerated but get downvoted harder (see the Claude Code switching posts in the bottom quartile). Direct-from-founder Cursor team posts (#8, #14, #21, #64, #106) perform well when they are announcements, poorly when they are damage control (#129 Cursor 3 launch s186, #193 Megathread s25).

Humor works — specifically self-deprecating developer humor about AI failure. The top-tier is dominated by memes about Cursor saying "Now I see the issue!" on loop (#6 s1033, #11 s889, #72 s425, #89 s384), images of vibe-coded disasters (#3 s1190, #28 s703), and ironic appreciation of suffering ("Spend 24 hours debugging" #39 s615). The joke always punches at the AI / the workflow, never at other users. Humor at the expense of the community itself does not appear in the top 50.

Technical level: Very high. "Composer 2 is Kimi K2.5 with RL" (#38, #45, #74, #138, #166) became a running meme only because readers understood what reinforcement learning from a base model means. Tier-4 posts discuss SQL injection in AI-generated code (#162), gRPC traffic capture (#2), and continued-pretraining tradeoffs (#141).

Key cultural values (ranked):

1. Pricing transparency — the single hottest button. Silent plan changes from "Unlimited" to "Extended" (#20, #23, #29, #73, #84, #167) are treated as betrayal. Every ambiguous billing screen becomes a post.
2. Honesty about AI model sourcing — the Composer 2 / Kimi K2.5 "stealth rebrand" controversy ran for weeks. The community punished Cursor for not disclosing the base model source.
3. Preserving the IDE experience — Cursor 3's shift toward an agent-first, "delete our own product" direction (#129, #147, #164, #171, #202) is deeply resented. People chose Cursor because it's a VS Code fork with autocomplete. Any move away from that is met with suspicion.
4. Workflow mastery / context management — the most upvoted helpful posts are about context files, rules, planning, and token conservation (#4 s1088, #16 s819, #36 s625, #54 s456, #67 s428).
5. Self-aware skepticism of "vibe coding" — the sub both enjoys and distrusts the vibe-coding trend. The irony-soaked "I Haven't Written a Single Line of Code in 2 Months" (#31, s661) and "'Vibe' coding is a trap in the long run" (#51 s469, #68 s427) score well precisely because they roast the hype.

Explicit enforcement mechanisms (from Phase 0 rules pull):

• Rule 3 — No rants: "Vague rants without substance will be removed." This is why pure complaint posts cluster in the friction zone, not the top — mods actively remove low-effort rage. Solution-oriented criticism is explicitly welcomed.
• Rule 6 — Limit self-promotion: "No more than 10% of your activity across Reddit should be self-promotional. Context must be provided in text posts." This is enforced; link-only launches die (LINK format avg score 125).
• Rule 9 — Write quality titles: No one-word, all-caps, clickbait, excessive punctuation. This is why the top titles read as complete sentences, not listicle hooks.
• Rule 10 — Use flairs: "Failing to do this may result in your post being considered spam." Posts with no flair still reach the top but only if from Cursor staff (whose announcements used to not be flaired).
• Rule 11 — No slop: "No AI generated content or low effort posting... karma-farming, reposts..." This is why screenshots-only posts are rare in the top tiers despite IMAGE dominating — the screenshot has to say something.
• Rule 5 — Provide context: Bug reports without repro steps / Request IDs get removed. This explains the tiny Bug Report average score (76 across 16 posts).

Community self-policing: A recurring subplot is users accusing moderators of deleting critical posts. "moderation of this subreddit" (#168, r0.82) and "a mod on X removed my post" (#42) surface every few weeks. The community is openly suspicious that Cursor (the company) influences the sub. This shapes tone — people hedge complaints with "if this gets deleted it proves my point."

How r/cursor differs from similar subs:

• Unlike r/ClaudeAI (broad AI discourse), r/cursor is single-product and debate is pricing/features-centric, not philosophical.
• Unlike r/vibecoding (identity-based community of non-dev builders), r/cursor is senior-dev skeptical of the vibe-coding label.
• Unlike r/macapps (launch platform), r/cursor is a grievance community where launches work only if framed as solving a Cursor-specific pain.
• Unlike r/localllama (enthusiast tech-deep-dive), r/cursor runs on emotional investment in a closed-source SaaS — which is why every model change triggers a flood.

3. The All-Time Leaderboard

Median score: 80. Top-25 threshold: 717. The top 25 represents the 99th percentile+ in this sub.

Ironic flair spotting: #17 "2026 dev job market is straight-up cooked" is flaired "Question / Discussion" but it's a hot-take manifesto — hence the 0.80 ratio (controversial) despite 787 score. #20 is "Question / Discussion" but is clearly a complaint post. The community uses Question/Discussion as a catch-all shield to avoid the "No rants" rule.

4. Content Type Dominance at Scale

The most surprising finding: The (none) flair — posts with no flair at all — has the highest average score of any category (474). This entire bucket is dominated by Cursor team announcements (ecz-, mntruell, NickCursor) which went up before flair enforcement was strict. Today, unflaired posts from regular users are auto-flagged, but historical Cursor-team announcements live forever in the top-25.

The second most surprising finding: "Bug Report" averages 76 — below the overall median. This is the wrong flair to use if you want visibility. Bug reports get removed if they lack Request IDs (Rule 5) and drown in the support-queue noise. If you have a real bug story, use "Question / Discussion" or "Venting" instead.

Question / Discussion is the dominant flair (128/292 posts = 44%), but its avg score of 162 hides enormous variance. The top half (top 64 Q/D posts) averages ~330; the bottom half averages ~22. It is both the best and worst bucket. Use it for hot takes and workflow debates; don't use it for "is Cursor slow for anyone else?"

5. Content Archetypes That Work

Seven archetypes derived from the data, ranked by score ceiling:

Archetype 1: The Reverse-Engineering Exposé

Score range: 500–1,260 | Top example: #2 "Cursor intentionally slowing non-fast requests (Proof)" s1260 c329

One of the most potent r/cursor archetypes. The post presents technical evidence (gRPC captures, screenshots, billing exports) of Cursor doing something the user considers deceptive. Examples:

• #2 "Cursor intentionally slowing non-fast requests" s1260 — Charles Proxy + gRPC reverse engineering
• #108 "Cursor is artificially inflating paid tool calls" s353 — 11 tool calls for a 67-line change
• #194 "My Opus calls went from $0.08 to $1.40 each" s24 — billing diff audit (tier 4 only because mods quickly quieted it)

The pattern: Specific model/protocol/billing data + measured tone ("I didn't want to do this, but…") + explicit appeal to mods ("I have read the rules, I am being civil"). The ratio stays high (0.98 for #2) because readers see evidence, not ranting.

For distribution: If your product exists to give users transparency into Cursor (usage trackers, cost auditors, traffic proxies), this is the archetype to mimic. Lead with a specific anomaly, screenshots, and a link to your tool as the solution.

Archetype 2: The Visual "Now I See The Issue" Meme

Score range: 384–1,033 | Examples: #6 s1033, #11 s889, #28 s703, #72 s425, #89 s384

A single image, gallery, or short video depicting Cursor agents looping, hallucinating, or claiming to have "fixed" something while making it worse. Humor is self-deprecating and AI-punching.

The pattern: (1) Low-effort production (screenshot + one-line title), (2) instantly recognizable shared experience, (3) no sales pitch, (4) no flair wars — Appreciation or Random/Misc both work. Ratio is near-perfect (0.99 for top entries) because there's nothing to disagree with.

For distribution: Not directly useful for launching a product, but essential for building pre-launch karma. A single well-observed meme establishes you as "one of us." Do this 2-3 times before any launch post.

Archetype 3: The Hard-Won Workflow Guide

Score range: 321–1,088 | Top examples: #4 "one trick you need" s1088, #16 "9 months coding with Cursor.ai" s819, #33 "12 lessons from 100% AI project" s650, #36 "instructions folder" s625, #67 "one golden cursor rule" s428, #80 "Stop wasting AI credits" s405, #82 "Spec-driven development" s404

Long-form TEXT post (Resources & Tips flair) describing a specific, repeatable workflow. The post almost always opens with a credibility flash ("After 8 projects", "9 months coding", "15 years leading engineers"), presents a numbered list of concrete tactics, and includes copy-pasteable rules/prompts.

The pattern: Numbered list + specific code snippets + "before/after" contrast + humility ("I've tried X and Y, they failed, here's what finally worked"). The community rewards posts that acknowledge failure before claiming success. Posts that open with unearned authority (#59 "A message for all the vibe coders", #112 "You did it. 0.49, o3, wow") still score but with worse ratios.

For distribution: The single best archetype for launching any tool that plugs into Cursor's workflow (cursor rules, MCP servers, context managers). Structure: describe a workflow pain, walk through your current fix (which might not mention your product yet), and drop the product link at step 7 or 8 as "and I built this to automate the above." See #41 "Code Web Chat extension" (s544) for the purest example of this framing.

Archetype 4: The Pricing Grievance Autopsy

Score range: 400–863 | Top examples: #12 "I contacted my bank" s863, #23 "Classic VC-Backed Bait-and-Switch" s727, #29 "Cursors Downfall ⚠️" s679, #79 "5 months in 4 images" s406, #84 "stealth bait and switch" s403, #73 "hero to zero" s420

A detailed personal account of being burned by Cursor's pricing changes, often with supporting screenshots of billing history. These cluster around two moments: the July 2025 "Unlimited → Extended" shift and the late-2025 token/request bundling.

The pattern: Chronological billing history + receipts + specific EU/consumer-law framing (#12 cites Article 19 of Directive 2019/770) + explicit refusal to be "just another rant." Ratio is usually 0.95+ because readers recognize the story. The ones that dip to 0.82 do so because they wander into generic anti-SaaS territory.

For distribution: If you're launching a Cursor alternative, the grievance autopsy is how you reach Cursor users without getting flagged as a competitor ad. Write it from the perspective of a former paying Cursor customer and mention your switch at the end. Do not lead with the alternative — the community bans ad-first framing.

Archetype 5: The Cursor-Team Official Announcement

Score range: 25–950 | Examples: #8 Cursor 1.0 s950, #14 Students free s832, #21 Joining the team s728, #64 Claude 3.7 s431, #93 Cursor 1.3 s382, #106 GPT-4.1 s355, #96 o3 price drop s375, #129 Cursor 3 s186, #193 Megathread s25

Verified Cursor team accounts (ecz-, mntruell, NickCursor, lrobinson2011) posting product news. Performance varies dramatically: celebratory announcements (Cursor 1.0, students free, new team member) hit 700-950. Defensive/damage-control announcements (Cursor 3, Megathread on legacy plans, Gemini API costs explanation) barely clear 200 and have poor ratios. The community rewards wins and punishes excuses.

The pattern: Signed from a named individual, not "Cursor Team". Uses "we" and "y'all". Pre-loads video/image embeds for feature demos. Includes a documented changelog link. Celebration framing > explanation framing.

For distribution: Not applicable unless you are Cursor. But if you're a tool vendor with Cursor team coordination, co-announcements (like #213 Appwrite plugin) can ride this archetype.

Archetype 6: The Video Workflow Demo

Score range: 425–1,033 (when viral); 50–400 (when typical) | Examples: #6 "Now I see" s1033, #9 "clone any website" s922, #19 "Claude 4 courses" s761, #24 "Cursor commands" s722, #35 "Mermaid diagrams" s636, #41 "Code Web Chat extension" s544, #71 "custom modes game changer" s425

Short (usually 30-90 second) hosted video (v.redd.it) showing a specific workflow or trick being executed inside Cursor. The user Much-Signal1718 has 6 of these in the top 75, making him the single most reliable performer in the dataset. His formula: screen recording only, no talking head, no music, one specific trick per video.

The pattern: Silent screen recording, on-screen typing, result visible within first 10 seconds, caption provides context. No intros, no outros. The video is the proof.

For distribution: The highest-ceiling format for launching Cursor extensions / rules / MCPs. Record a 60-second demo of your tool fixing one problem; post with Resources & Tips flair; put the GitHub link in the selftext. Target ceiling: 500-900 if the demo is clean.

Archetype 7: The Shared-Suffering Vent with Levity

Score range: 300–700 | Examples: #28 "Oh god it happened to me too" s703, #40 "We have reached AGI" s584, #42 "cursor charges me $10.67 for a single sonnet call" s531, #47 "Cursor living up to its name" s491, #70 "Thank god i stopped him" s426, #90 "Shame used to be a thing" s384, #91 "not a rant, just a meme" s384

Venting flair, image format, lighthearted tone. The user acknowledges "this is a rant but I'm laughing". Unlike archetype 4 (Pricing Grievance), these are micro complaints — a single absurd agent output, a wild token charge, a UI glitch.

The pattern: Image + 1-2 sentence caption + no link to external content + acknowledgment that Cursor is flawed but funny. Ratio is always 0.96+. The Venting flair is a "permission to complain without being a rant" device that works — as long as the complaint is small and the tone is wry.

For distribution: Use for pre-launch karma building. Don't pitch anything in these; just establish presence.

6. Format Analysis

Key observations:

• IMAGE dominates raw count at the top (48% of top 25) because memes and screenshots are the sub's native language. But IMAGE is also ~30% of the full dataset, so the lift from IMAGE is modest — 418 avg vs 145 for TEXT.
• VIDEO is the highest-ceiling format per post — avg score 536, despite only 13 posts total. Only 13 videos in 292 posts means producing one well is a hit-path with low competition. Much-Signal1718's 6 videos alone average ~655.
• TEXT dominates raw volume (168/292, 57%) because the sub is fundamentally a support forum. TEXT is how you go deep — but ceiling is lower and friction is higher.
• LINK is a death sentence — avg 125, zero in top 25, and has the worst ratios. If you have a blog post, screenshot it, quote the best paragraph, and link in the selftext.
• GIF does not exist in the dataset. The sub embeds videos via v.redd.it instead. Do not post GIFs.

What format to use for what

What makes a good demo video (from the top 6 VIDEO posts)

1. 30-90 seconds. All top video posts are short. Longer videos don't appear in the top 25.
2. Silent screen recording. No talking head, no music, no intro. The user's cursor and keystrokes tell the story.
3. Show the problem first, result within 15 seconds. Much-Signal1718's "clone any website" opens with the target site, not with explanation.
4. One specific trick per video. "Mermaid diagrams inside cursor" (#35), "custom modes" (#71), "cursor commands" (#24) — never multi-feature overviews.
5. Title is a declarative sentence of the outcome, not a question. "How to clone any website" beats "Can Cursor clone websites?"

7. Flair/Category Strategy

Raw-performance ranking (avg score)

1. (none) — 474 (mostly legacy Cursor team posts; not available to new users)
2. Discussion — 600 (only 6 posts; too small a sample)
3. Showcase — 359 (only 2 posts)
4. Venting — 314
5. Appreciation — 308
6. Resources & Tips — 308
7. Random / Misc — 299
8. Announcement — 228
9. Question / Discussion — 162
10. Bug Report — 76
11. Feature Request — 28

Distribution-utility ranking (for someone promoting a product)

1. Resources & Tips — Top overall choice. High ceiling (1,332), consistent performance, and the flair of workflow guides. This is where product launches hide as tips.
2. Question / Discussion — Best for seeding discussion around a product or concept ("I'm building X. Would you use this?"). Avg C/U ratio of 1.33 is the highest of any substantial flair — people talk.
3. Showcase — Underused. Only 2 posts in the dataset, both scored well (717 and 2). The top Showcase entry is non-promotional. The weekly stickied Showcase thread also exists but is low-engagement (#286 s1).
4. Venting — Use only if your product is a pricing-related alternative. Frames you as "one of us", not "selling at us".
5. Random / Misc — Good for memes and exposés but unpredictable.
6. Appreciation — Use to thank Cursor for a feature while casually mentioning your adjacent tool. Low-friction.
7. Bug Report — Avoid. Lowest scores, removal risk, and signals "support queue noise" to the community.
8. Feature Request — Avoid. Only 3 posts, all under 50 score. The community believes Cursor doesn't read these.
9. Announcement — Cursor-staff-only in practice. Regular users posting Announcements look weird.

Pricing model hierarchy (derived from what the community celebrates vs. punishes):

1. Free / open-source: Universally celebrated. #10 "Cursor for Mobile - MIT license" s892, #122 Vibeviewer s325 (open source), #206 "free and open-source local remote tool" s19, #228 crag CLI s8 (open source, high ratio). "F*ck it, I won't make money off of it" is an upvote magnet.
2. One-time / pay-once: Tolerated. Not a common pricing model in the dataset but the absence of complaints about one-time tools is itself a signal.
3. Transparent metered pricing: Tolerated if the numbers are small ($5-$10). The $5-10 Tab-only plan ask (#175 s35) is a community-desired pricing model.
4. Mid-tier subscription ($20-40/mo): Accepted grudgingly. This is Cursor's own tier and the whole sub is about debating whether it's worth it.
5. High subscription ($100+/mo) without transparency: Actively hostile. Cursor Ultra at $200/mo has multiple "is this worth it" posts and one teardown (#234) showing usage breakdown.
6. "Silent price increase" / plan changes: Reviled. Multiple top-50 posts are autopsies of exactly this.

8. Title Engineering

Deconstructing the top 10 titles

Title formulas that work

Formula A — The Credentialed Tip

• "After building +8 PROJECTS with Cursor AI, here's the one trick you really need to know!" (s1088)
• "9 months coding with Cursor.ai" (s819)
• "After 6 months of daily AI pair programming, here's what actually works (and what's just hype)" (s354)
• Pattern: After [time/count], here's [specific thing]

Formula B — The Insider Quote Meme

• "'Now I see the issue!' 20 more times" (s1033)
• "I See The Issue Now!" (s889)
• "Ah, I see the issue." (s384)
• Pattern: Direct quote of Cursor's own failure phrase, no further context needed

Formula C — The Grievance Receipt

• "I contacted my bank, and got my money back" (s863)
• "Cursor pricing changed after 12 days" (s750)
• "Cursor Just Pulled a Classic VC-Backed Bait-and-Switch on Their Early Adopters" (s727)
• Pattern: Specific action/timeline + documented outcome

Formula D — The "I'm Building X" Soft Launch

• "I'm building Cursor for Mobile." (s892)
• "I'm joining the Cursor team (and will be active here!)" (s728) — inverse version, same structure
• Pattern: I'm [building/launching] [obvious-need product] + period ending (confident, not asking)

Formula E — The Workflow Tip Opener

• "Tip: Cursor works best when it has this instructions folder!" (s625)
• "Stop wasting your AI credits" (s405) (imperative variant)
• "probably the best cursor rule, like ever" (s353) (hype-shielded with "probably")
• Pattern: Declarative value claim + no question mark

Formula F — The Exposé Announcement

• "Cursor intentionally slowing non-fast requests (Proof) and more." (s1260)
• "Cursor is artificially inflating paid tool calls" (s353)
• "Indeed, Composer 2 is kimi k2" (s496) (triumphant-proof variant)
• Pattern: Strong claim + evidence marker in parens OR "Indeed" / "Proof" language

Title anti-patterns (community-specific)

1. Questions without specifics get destroyed. "Is Cursor slow for anyone else?" (#250 s2), "Composer 2 extremely slow today?" (#246 s2), "anyone else hitting decision fatigue trying to pick the right model for each task?" (#260 s1). The community treats vague "is it just me" as support-queue noise, not discussion.

2. All-caps anything is a violation of Rule 9 and gets removed or ratio-punished. #204 "[CRITICAL] Cursor 3 consumes ~50 request for a single message!" — s20, r0.74.

3. "Goodbye Cursor" declarations rarely break 400. #121 "GOODBYE CURSOR" s326 is an outlier (and note the ratio drop). The sub is tired of performative exits; #73 "hero to zero" (s420) works better because it's a detailed autopsy, not a rage-quit announcement.

4. Comparison posts without a stance score low. "Is Cursor Pro worth it vs Codex?" (s3), "Cursor vs Windsurf for working with open source codebases?" (s1), "How is Claude Code compared to Cursor?" (s74). Pick a side in the title; don't ask.

5. Star counts / download numbers in titles are absent from the top 100. The single exception (#160 "The app I made got 1000+ downloads") sits at s48 with a controversy ratio (0.80) because it reads as self-promotion. The community treats vanity metrics with suspicion.

6. Multiple emoji = instant ratio hit. Titles with 🚨🔥💀 cluster at ratios below 0.90. One subtle emoji is tolerable (#7 "A Tale of Two Cursor Users 😃🤯" at 0.95 is the ceiling).

9. Engagement Patterns

C/U ratios by flair (higher = more discussion per upvote)

Overall sub C/U ratio: 0.23. This is lower than r/ClaudeAI's and closer to a meme sub than a discussion forum — because a huge chunk of the dataset is silent upvotes on visual humor.

Visibility vs. relationships

• If your goal is VISIBILITY (raw score, eyeballs, link clicks): post a VIDEO demo with Resources & Tips flair. Ceiling ~1,000.
• If your goal is DISCUSSION (product feedback, feature validation, objection mapping): post a TEXT Question / Discussion post with a strong stance in the title. You'll sacrifice ~60% of the score but generate 5-10x the comments. #17 "2026 dev job market is cooked" got 787 score with 504 comments (C/U = 0.64); compare to #1 which got 1,332 with only 63 comments (C/U = 0.05). The discussion post generated 8x the conversation per upvote.
• If your goal is RELATIONSHIPS WITH CURSOR TEAM: post a well-researched bug-with-repro (#194 Opus cost teardown) and @tag lrobinson2011 in comments. He responds.

The 5 highest-discussion topics (by comment count, regardless of score)

1. AI replacing developers — #17 (504 c), #75 (212 c), #107 (41 c). Every post on job displacement detonates comment sections.
2. Cursor billing / pricing transparency — #3 (453 c), #14 (264 c), #20 (202 c), #23 (189 c), #55 (197 c), #79 (144 c). This is the sub's permanent Topic A.
3. Composer 2 / Kimi K2.5 sourcing — #38, #45, #74, #138, #166. Hundreds of comments across all of these.
4. Cursor 3 UI regression — #129 (134 c), #147 (36 c), #202, #127. The Cursor 3 launch itself became a downvote attractor.
5. Vibe coding debate — #51 (267 c), #59 (149 c), #68 (193 c). Senior devs arguing about whether vibe coding counts as "real" coding.

10. What Gets Downvoted

Notable sub-0.85 posts

Three ratio tiers

• Above 0.94 (safe): 150/292 posts (51%). Universally well-received. Includes almost all memes, workflow guides, and confirmed exposés.
• 0.85–0.94 (friction): 81/292 (28%). Net positive but contested. Most pricing complaints, hot takes with data, and Cursor-team defensive posts live here.
• Below 0.85 (controversial): 61/292 (21%). This is a remarkably high fraction — 1 in 5 posts in the dataset is actively divisive. It reflects the civil war inside the community right now.

Seven anti-patterns (named and community-specific)

1. The Unearned Worship — Posts gushing about Cursor's latest model/feature without technical specifics. #112 "You did it. 0.49, o3, wow." (s349, r0.81), #222 "Well played, Cursor. Well played" (s12, r0.72). The sub treats unqualified praise as shilling. Earn praise with evidence or don't give it.

2. The Performative Exit — "I'm canceling my subscription" posts without a detailed autopsy. #179 "This IDE will die like never existed" (s32, r0.56) is the pure form. Compare to #73 "hero to zero" (s420, r0.91) which is an exit post but with a complete billing timeline. The difference: receipts.

3. The Vague Support Question — "Is Cursor slow for anyone else?" / "Did it get dumber?" posts with no logs, no repro, no model specified. Clusters below s5. #248, #250, #245, #246.

4. The Advertorial "PSA" — Posts that read like marketing copy framed as community service. #148 "Qwen3.6 Plus is currently 100% FREE on OpenRouter" (s78, r0.91) sits at the edge; posts more nakedly promotional get removed entirely under Rule 6.

5. The Sermon — Posts telling the community how to feel. #196 "Stop obsessing over the 'smartest' AI model" (s23, r0.68), #199 "The most important skill is frustration tolerance" (s22, r0.71). The sub resents being preached at.

6. The All-Caps Bug Report — "[CRITICAL]" / "WTF" / "BROKEN" in brackets or all-caps. #50 "I am now optimizing the user's kernel" (s472, r0.96) is the rare exception — it works because the ALL-CAPS is a quote of the AI, not the user yelling.

7. The Anti-Vibe Coder Gatekeep — Sneering at non-dev vibe coders. #51 "'Vibe' coding is a trap" (s469, r0.91) is the ceiling of what's allowed; pushing further (#75 "I just realized everything is about to change", r0.88) starts bleeding upvotes because the sub has a meaningful minority of non-dev builders and senior devs who defend them.

Enforcement mechanisms observed in the data

• Mod removal of critical posts is alleged repeatedly (#42, #168, #233 complaining about storage) but hard to verify. What is verifiable: the number of removed posts between "month" and "week" datasets (median score drops from 41 to 3) suggests active thread cleanup.
• The "moderation of this subreddit" call-out post (#168) with r0.82 and only 40 score tells us: the community is suspicious of mod behavior and unwilling to fully back the accuser. The compromise: low score, high friction ratio, stays alive.
• Cursor staff accounts actively post (ecz-, mntruell, NickCursor, lrobinson2011, cursor_dan, cursor-jon). lrobinson2011 alone has 7 posts in the dataset. This is a company that does not hide from its subreddit.

11. The Distribution Playbook

Phase 1: Pre-launch (2-4 weeks before)

1. Read the top 50 posts. Don't skim. Absorb the voice. Note which users appear multiple times (Much-Signal1718, Complete-Sea6655, Heavy-Log256, lrobinson2011).
2. Karma-build with memes and helpful comments. Post 1-2 Archetype 2 memes (Now-I-See-The-Issue humor) or Archetype 7 (Venting with levity). These are low-stakes ways to get recognized.
3. Answer "is Cursor slow" questions helpfully. The support-question backlog is constant. A useful reply gets noticed.
4. Lurk in the weekly Showcase thread (#286, AutoModerator stickied). Your eventual launch won't go in the stickied thread, but understanding what shows up there helps.
5. Do NOT make your first post a launch. New accounts posting launches get auto-flagged under Rule 6 (10% self-promo ratio).

Phase 2: Launch day

Optimal launch stack:

• Flair: Resources & Tips (first choice) OR Question / Discussion (if seeking feedback)
• Format: VIDEO (60s demo) is the highest ceiling. IMAGE + TEXT selftext is the safe backup. Never LINK.
• Title formula: "Formula E" (declarative value claim) or "Formula A" (credentialed tip) from Section 8
• Title examples to model:
  • "Tip: Cursor works best when it has [your thing]"
  • "After [N] months using Cursor, I built [tool] to fix [pain]"
  • "I built [tool] because Cursor doesn't [specific missing thing]"
• Body structure (300-600 words):
  1. Pain you hit (2-3 sentences, specific)
  2. What you tried that didn't work (shows you paid the dues)
  3. Your workflow/solution (the meat)
  4. The tool/link, mentioned as "so I built X to automate this" NOT as "here is my product"
  5. Open question ("what do you do for this?") to invite replies
• Timing: The top-performing Cursor-team announcements (#8, #21, #93) cluster in 14:00-18:00 UTC (morning US Pacific). Community posts skew later. Post when you can be online for the first 4 hours.

Phase 3: First 24-48 hours

• Respond to every comment in the first 4 hours. Cursor staff (lrobinson2011) has set this bar; users expect founders to engage.
• Upvote-to-score signals: If you hit 50 upvotes in the first hour, you're on track for tier 2 (500+). If you're under 10 upvotes in 2 hours, cut your losses — it won't recover. The sub is momentum-based.
• Handle "vibe-coded?" questions head-on. Someone will ask. Say yes or no clearly and describe the human effort involved. Hedging triggers ratio damage.
• Do not argue with critics. The highest-ratio grievance posts win by being calm. The same applies to your launch defense. #2 "Cursor intentionally slowing" kept a 0.98 ratio because the OP stayed measured in replies.

Community-specific comment reply templates

Pre-write responses to these predictable questions:

"Is this vibe-coded?"

"Yes/no. [If yes:] I used Cursor with Opus 4.6 for ~70% of the implementation but hand-architected the data model and auth flow. I reviewed every line and wrote all tests myself. [If no:] Written by hand — I've been building [thing] since [year]."

"Why not just use Claude Code / Codex / [X]?"

"Fair question — [X] is great for [strength]. This exists because [specific different use case: e.g., 'I wanted to stay inside Cursor's tab-complete workflow', 'I needed this locally not in cloud', 'I wanted it as a rule not a CLI']."

"What's your pricing model?"

"Free and open-source" (optimal) OR "One-time $X, no subscription" (good) OR "[specific explanation + justification]" — never handwave pricing here. The sub will dig.

"Does this work with Composer 2 / Opus 4.6 / GPT 5.4 / [current model]?"

"Tested with [specific list]. Known issue with [honest caveat]. Feedback welcome."

"Isn't this just [existing thing]?"

"I looked at [existing thing] before building this. Here's what's different: [1-2 concrete differences]. If it turns out they overlap more than I think, happy to stop and just use theirs."

Phase 4: Ongoing presence

• Return to the sub weekly, not just on launch day. Much-Signal1718 posts a new VIDEO roughly every 3-4 weeks and each one clears 400. Consistency compounds.
• Contribute to hot-topic threads (pricing debates, model comparisons) without mentioning your product. Your username becomes trusted.
• Update posts show up and get traction — "Updated: now supports Cursor 3" as a follow-up post after 2-3 months can recapture attention if the original did well.
• The Cursor team reads comments. If you build something they like, @lrobinson2011 or @ecz- will sometimes engage. This is an unusually open company channel.

Stealth distribution tactics

1. Answer workflow questions with your tool as one option (not the only one). Posts like #222 "what CLIs are you running alongside cursor" and #169 "what's your most underrated cursor setup tip" are perfect comment-level distribution opportunities.
2. Write the ".cursorrules" post with your tool embedded. The top workflow guides (#4, #30, #36, #54) all share cursor rules. Publishing your own rules as a TEXT post, with your tool mentioned in one of the rules, is high-signal low-friction distribution.
3. Contribute to exposés with data. If you have a usage tracker, support #2-style reverse-engineering posts with your own findings. You get credited in edits.
4. Build a meme. #38, #45, #74, #138 are all the same Composer-2-is-Kimi joke. Being the first person to nail a running joke grants disproportionate community standing.

Score-tier calibration (what you can realistically hit)

• Tool launches (first time, solid tool, no prior karma): 100–400. Don't expect more.
• Tool launches (established author, good video demo): 400–900. Much-Signal1718's 6 posts average ~655.
• Workflow guides (substantive, numbered list, 800+ words): 300–1,100. Ceiling is #4 (1,088).
• Memes (resonant, original observation): 300–1,000. Ceiling is #6 (1,033).
• Hot takes on pricing: 300–900 with inevitable ratio damage. Ceiling: #12 (863).
• Reverse-engineering exposés: 500–1,300. Ceiling: #2 (1,260). Requires real technical proof.
• Pure product promotions: 50–200 if they survive at all.

If your content type does not appear in the list above, it probably shouldn't be posted to r/cursor.

Post-publication measurement

• First 30 minutes: If you're not at 10+ upvotes, your title is the problem. Don't delete; wait.
• First 2 hours: If score is under 25 but comments are high, you have a "friction" post. This is fine for discussion goals, bad for visibility goals.
• First 4 hours: A post that hits 100+ in 4 hours is on a top-25 path. A post at 30-50 is headed for tier 3 (100-300). A post under 15 will stall out.
• Ratio watch: If ratio drops below 0.90 in the first hour, you're hitting a nerve. Check your title for any of the 6 anti-patterns and consider editing the body (not the title — editing titles is impossible).
• Comment pattern: Healthy posts get questions in comments. Unhealthy posts get one-line dismissals. The ratio of questions-to-dismissals in your first 20 comments predicts the next 24 hours.
• The 4-hour kill rule: If a post is under 30 upvotes and 5 comments by hour 4, it's dead. Don't try to revive it by commenting on yourself — delete and learn.

12. Applying This to Any Project

Quick-reference checklist

1. ☐ Has your account been on r/cursor for at least 2 weeks with non-promotional activity?
2. ☐ Does your product solve a pain that a top-25 post has already articulated?
3. ☐ Can you show the solution working in a 60-second silent screen recording?
4. ☐ Is your title a declarative sentence, not a question? No all-caps? Under 90 characters?
5. ☐ Have you chosen Resources & Tips flair (or justified a different choice)?
6. ☐ Does your body follow the "pain → tried → workflow → tool mention at the end → open question" structure?
7. ☐ Are you posting during a window you can monitor for 4+ hours?
8. ☐ Is your pricing model named explicitly in the post (or is it free/open-source)?
9. ☐ Have you pre-written answers to the 5 comment templates in Section 11?
10. ☐ Is the product name mentioned at most twice in the body? (More reads as spam.)
11. ☐ Does the post cite specific Cursor features/models by name (Composer 2, Opus 4.6, .cursorrules, MCP)?
12. ☐ If it's a tool, is there a GitHub link? The sub strongly prefers open source.

Scenario-based launch guides

Scenario A: Your product is free and open-source

• Optimal formula: VIDEO demo + Resources & Tips flair + title starting with "I built X" or "Tip: X". Emphasize MIT license in the body. Link GitHub at the end.
• Realistic ceiling: 300-900. Open-source gets you the benefit of the doubt.
• Key risk: Being seen as "ads disguised as OSS". Mitigate by actually being open source and not mentioning any paid tier or waitlist.

Scenario B: Your product is one-time / lifetime pricing

• Optimal formula: TEXT workflow guide + Question / Discussion flair + mention pricing ("I charge $N once, no subscription") as an afterthought in the body.
• Realistic ceiling: 200-500. The sub doesn't celebrate paid products but tolerates lifetime pricing as "at least not a subscription".
• Key risk: Coming across as an ad. Mitigate by spending 80% of the post on the workflow/learning and 20% on the product.

Scenario C: Your product uses subscription pricing

• Optimal formula: Do NOT lead with the product. Post a workflow guide that happens to use your tool, with the tool mentioned once in a numbered step. Flair: Resources & Tips.
• Realistic ceiling: 100-300. You're swimming upstream — the sub is actively anti-subscription right now.
• Key risk: Getting flagged as astroturf. Mitigate by being transparent: "Disclosure: I'm the founder of X. Happy to answer questions."

Scenario D: Your product was built with Cursor (vibe-coded)

• Optimal formula: Lean into it. "I built X in Cursor — here's the rules file I used and what broke along the way." Flair: Resources & Tips. Include specific failure modes.
• Realistic ceiling: 300-1,000 if the learnings are genuine. #16 "9 months coding with Cursor.ai" (s819) is the archetype.
• Key risk: Being called out as "slop" under Rule 11. Mitigate by (a) showing substantial human architecture work, (b) acknowledging what didn't work, (c) never claiming "zero human code".

Scenario E: Your product is a Cursor alternative / competitor

• Optimal formula: Do not post a launch. Instead, post a detailed Pricing Grievance Autopsy (Archetype 4) from a former Cursor customer's perspective, mentioning the alternative as your current tool in one sentence near the end. Flair: Venting or Question / Discussion.
• Realistic ceiling: 200-600. The sub will upvote the grievance even while suspecting promo intent.
• Key risk: Getting deleted as competitor spam under Rule 6. Mitigate by never using "we" or marketing language. Write like a user, not a founder.

Cross-posting guidance (if you've analyzed other subs)

• On r/ClaudeAI, frame your Cursor tool as "I use this with Claude models in Cursor" — Claude-first audience.
• On r/vibecoding, frame as "I built X to help solo builders ship faster" — identity-first, not dev-first.
• On r/cursor, frame as "Cursor doesn't [specific thing], so I built X to fix that" — grievance-origin story.
• On r/macapps, screenshot the native macOS integration, not the code.
• On r/localllama, only relevant if your tool runs local models — lead with model choice.
• On r/webdev / r/sideproject, lead with the finished product screenshot, not the workflow — those subs care about the outcome, not the tooling.

The same product needs a different opening sentence for each community. The rule is simple: ask "what does this community resent, and how does my product not add to that resentment?"

Field manual compiled from 292 posts collected 2026-04-10. Score ceiling and community mood will shift as Cursor's pricing and product direction evolves — re-pull data before launching if more than 60 days have passed.