Hey everyone 
I built a local-first Cursor extension called **Buckram Studio** to solve the “context window decay” problem when editing long-form prose and fiction using the usual suspects tools and browser chats.
### The Problem
When working on novel chapters or long articles in Cursor, keeping 200-message chat threads causes context rot. The scrollbar shrinks, costs spike, and the model starts repeating itself or generating soft, generic prose.
### The Solution
Instead of living inside giant chat threads, Buckram Studio enforces a zero-context, file-driven workflow directly in Cursor:
- **Local Specs & Lore:** Keeps world-building, character sheets, and chapter outlines in small, targeted local Markdown files.
- **Fresh Context per Edit:** Feeds minimal, explicit context (@ mentions of only what’s required) to the Cursor agent for each revision.
- **Targeted File DIFFs:** Returns clean 3-line inline DIFFs on disk rather than re-generating entire chapters in chat.
- **Built-in AI Critics:** Includes automated *AI Slop* and *Story Critics* that audit your drafts and launch targeted fix-chats to resolve plot holes or weak prose.
- **Git State Protection:** Automatically commits state before agent modifications so you can roll back anytime.
### Links & Feedback
• Open VSX / Marketplace: https://open-vsx.org/extension/buckram/buckram-studio
It’s completely local-first and works with your existing Cursor setup. Would love to hear thoughts, feedback, or critiques from anyone using Cursor for non-code long-form projects!