[WIP DEMO] feat(case-study): Anysphere Cursor success story [FABLE 5 MAX]#152
[WIP DEMO] feat(case-study): Anysphere Cursor success story [FABLE 5 MAX]#152oycyc wants to merge 3 commits into
Conversation
New /case-studies/cursor/ page on the immersive layout, copy taken verbatim from the marketing Notion draft. Ships three new immersive building blocks: - csi-phases / csi-phase — vertical engagement-journey rail (date chip + gradient dot per phase, full block-markdown bodies, nested ledgers) - csi-scale — type-specimen magnitude wall for the "what the platform manages" enumeration - csi-compare gains an optional delta: improvement pill per row Plus two CSS-drawn figures (cursor/terralith monolith, cursor/agent-rules editor window), branded chart exports from the Notion draft (one per duplicate pair; the spare doubles as preview/OG image), the official Cursor brand-kit lockup, in-card prose subhead styles, a fix for the light cs-pullquote two-line attribution name (was white-on-cream), and print checklist entries for all new cards. Cursor takes weight 1, so it leads the case-studies list. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
✅ Deploy Preview for masterpoint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
Next review available in: 13 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughAdds a complete Cursor immersive case study with new Hugo shortcodes, accessible CSS-drawn figures, phase and scale components, comparison deltas, responsive and print styling, and updated authoring documentation. ChangesCursor immersive case study
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Per content-owner feedback that the page had too many sections: 16 bands become 8 (TLDR, Key Value Delivered, The Problem, What Masterpoint Did, The Results, What Changed for the Team, testimonial, CTA), strictly alternating light/pine, with all copy unchanged. - new csi-figure shortcode embeds CSS-drawn figures inline in prose (the terralith monolith now sits inside the Problem card; the agent-rules window inside the rail's Feb-May phase, where the Notion draft has it) - charts move from csi-split media columns into the prose flow (.csi-prose img: rounded, shadowed, hairline edge on pine, break-inside: avoid in print) - prose h3 subheads sized up to carry the internal chapters, and heading render-hook anchors keep heading colour instead of prose link colour (mint headings on pine bug) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/case-studies/cursor.md`:
- Line 176: Correct the grammar in the sentence following the migration
description by changing “continued to improved” to “continued to improve.”
In `@docs/case-studies.md`:
- Around line 498-500: Replace the ambiguous `.csi-fig-terralith__mono/__stack`
entry in the selector list with two explicit comma-separated selectors,
`.csi-fig-terralith__mono` and `.csi-fig-terralith__mono__stack`, preserving the
surrounding selectors and prose.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: c8b091aa-5a4c-489a-8d75-d5900dc7f816
⛔ Files ignored due to path filters (6)
static/img/case-studies/cursor/cursor-dial-gauge.pngis excluded by!**/*.pngstatic/img/case-studies/cursor/cursor-frequency-stat.pngis excluded by!**/*.pngstatic/img/case-studies/cursor/cursor-lockup-white.svgis excluded by!**/*.svgstatic/img/case-studies/cursor/dependency-graph.pngis excluded by!**/*.pngstatic/img/case-studies/cursor/plan-time-column-compare.pngis excluded by!**/*.pngstatic/img/case-studies/cursor/tf-workspaces-growth.pngis excluded by!**/*.png
📒 Files selected for processing (10)
assets/css/case-studies.scsscontent/case-studies/cursor.mddocs/case-studies.mdlayouts/partials/case-studies/figures/cursor/agent-rules.htmllayouts/partials/case-studies/figures/cursor/terralith.htmllayouts/shortcodes/csi-compare.htmllayouts/shortcodes/csi-figure.htmllayouts/shortcodes/csi-phase.htmllayouts/shortcodes/csi-phases.htmllayouts/shortcodes/csi-scale.html
| As part of the final migration work, the production workspace was reduced by splitting out various provider-aliased resources into dedicated stacks, continuing the decomposition work that had started with IAM deduplication in November. | ||
| {{< /csi-phase >}} | ||
| {{< csi-phase date="February to May 2026" title="AI Agent Guardrails And Additional Improvements" >}} | ||
| After the migration was completed, Masterpoint continued to improved system usability and speed by: |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Fix grammar error: "continued to improved" → "continued to improve".
This is a clear typo in the published case study copy. The infinitive form requires "improve," not the past tense "improved."
✏️ Proposed fix
-After the migration was completed, Masterpoint continued to improved system usability and speed by:
+After the migration was completed, Masterpoint continued to improve system usability and speed by:📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| After the migration was completed, Masterpoint continued to improved system usability and speed by: | |
| After the migration was completed, Masterpoint continued to improve system usability and speed by: |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/case-studies/cursor.md` at line 176, Correct the grammar in the
sentence following the migration description by changing “continued to improved”
to “continued to improve.”
| `.csi-fig-terralith__mono/__stack`, `.csi-timeline`, `.csi-question`, | ||
| `.csi-phase__head`, `.csi-scale__row`, `.csi-fig-cmono__frame`, | ||
| `.csi-fig-rules__window`) pushes a whole |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Spell out both selectors explicitly.
.csi-fig-terralith__mono/__stack is ambiguous shorthand and is not a valid selector list readers can copy directly. Use two comma-separated selectors instead.
Proposed documentation fix
- `.csi-fig-terralith__mono/__stack`, `.csi-timeline`, `.csi-question`,
+ `.csi-fig-terralith__mono`, `.csi-fig-terralith__stack`, `.csi-timeline`, `.csi-question`,📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| `.csi-fig-terralith__mono/__stack`, `.csi-timeline`, `.csi-question`, | |
| `.csi-phase__head`, `.csi-scale__row`, `.csi-fig-cmono__frame`, | |
| `.csi-fig-rules__window`) pushes a whole | |
| `.csi-fig-terralith__mono`, `.csi-fig-terralith__stack`, `.csi-timeline`, `.csi-question`, | |
| `.csi-phase__head`, `.csi-scale__row`, `.csi-fig-cmono__frame`, | |
| `.csi-fig-rules__window`) pushes a whole |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/case-studies.md` around lines 498 - 500, Replace the ambiguous
`.csi-fig-terralith__mono/__stack` entry in the selector list with two explicit
comma-separated selectors, `.csi-fig-terralith__mono` and
`.csi-fig-terralith__mono__stack`, preserving the surrounding selectors and
prose.
…lumns The consolidated one-card sections used the default left alignment, which left a 760px prose column hugging the left edge of the wide band. Default (--left) csi-sections now render head + prose as a centred 880px article column with text left-aligned. MarketSpark and Power Digital pass align="center" on every section, so only Cursor is affected. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 participant
What this is
A new immersive case study for Anysphere / Cursor at
/case-studies/cursor/, built from the Cursor Case Study Draft in Notion. All case-study copy is the Notion draft verbatim — only placement/sectioning was designed; no wording was changed.Page structure — one card per chapter
Hero (Cursor brand-kit lockup × Masterpoint) → 4-up stat strip → TLDR band → Key Value Delivered impact grid → The Problem (one pine card: CSS-drawn terralith monolith figure inline, both Travis quotes, trust-erosion + TFC friction) → What Masterpoint Did (one light card: dated 4-phase rail — Nov audit with before/after ledgers, Dec Spacelift groundwork, Jan–Feb bulk migration, Feb–May AI guardrails with the editor-window rules figure + Ravi quote inside the phase) → The Results (one pine card: magnitude wall, Numbers That Matter ledger, plan-time dial, deployment-frequency chart, cohort ledger, democratization chart under
###chapter subheads) → What Changed for the Team (one light card: blast-radius chart + Ravi quote + the three closing reads) → Travis testimonial on the cosmic band → Terraform-ceilings CTA. Faces alternate light↔pine strictly.New immersive building blocks (documented in
docs/case-studies.md)csi-phases/csi-phase— vertical engagement-journey rail (gradient rail + dot, date chip, full markdown bodies, nested ledgers)csi-scale— type-specimen magnitude wallcsi-figure— embed CSS-drawn figures inline in prose (for consolidated single-card sections)csi-comparenow supports an optionaldelta:improvement pill per rowcursor/terralith(monolith-only) andcursor/agent-rules(editor window).csi-prose img), in-card###chapter subheads, and fixes: lightcs-pullquotetwo-line attribution name was white-on-cream; heading render-hook anchors were painted with the prose link colourGraphics
All four branded charts from the Notion draft are used — one per duplicate pair, matched to card faces (dark charts on pine bands, white charts on light bands). The spare white deploy-time column chart serves as
preview_image/og_img. Cursor logo is the official brand-kit horizontal lockup (off-white SVG).QA done
hugobuild clean;trunk fmtrun on changed filesweight: 1and leads the/case-studies/listFlagged for review (kept verbatim per instructions)
🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Enhancements
Documentation