Curiosity Rooms

Index - Cursor MVP Implementation Guide

2 min read

Index - Cursor MVP Implementation Guide

Source: /Users/nitishchauhan/Downloads/Cursor_MVP_Implementation_Guide.pdf Type: product-spec Status: indexed

1. Recurring keywords / key ideas

  • Zero-Friction Knowledge Capture Chrome extension
  • Manifest V3, background worker, content scripts
  • Turndown.js HTML to Markdown
  • chrome.downloads local Inbox pathing
  • Capture modes: page, selection, link
  • AI chatbot DOM heuristics (ChatGPT, Claude, Readability fallback)
  • Duplicate detection hash queue
  • Strict Markdown metadata template
  • Friction Counter micro-modal / CSV log
  • Capture First, Organize Later / offline-first MVP matrix

2. Core / novel / atypical ideas

  • Cursor instruction: build a perfect screwdriver, not a Swiss Army knife; Phase 1 only
  • Core rule: never ask questions during capture; headless, silent, background
  • Constraint check: if removing a feature does not make the product worse, it is not MVP
  • Local Inbox via chrome.downloads with saveAs: false to bypass folder dialogs (Memory/Inbox/YYYY/MM/DD/title.md)
  • Specialized scrapers for nested AI chat DOMs plus Readability.js generic fallback
  • URL+content hash duplicate interception with “Already captured” notice
  • Non-negotiable forever-readable Markdown export layout with source, date, URL, capture mode metadata
  • Friction Counter as hidden gem: log friction notes to Memory/Friction/log.csv
  • Explicit exclusion matrix: no OCR, voice, AI summaries, cloud sync, Notion, tagging prompts, semantic search in Phase 1

3. Context and flow

This technical implementation document tells Cursor exactly how to build a Chrome MV3 knowledge-capture extension in one shot. It covers architecture, mind-map data flow from highlight to Markdown download, MVP details (inbox pathing, menus, scrapers, dedupe), the mandatory export template, future-proofing add-ons like the Friction Counter, and an executive matrix separating Phase 1 from postponed work. Philosophy throughout: offline-first, zero questions at capture time, organize later.

4. Publishing angles

  • Mode: Authority article
  • Why: Concrete engineering spec with explicit MVP constraints and capture philosophy suitable for explanatory build writing.
  • Angles:
    • Zero-question capture: why chrome.downloads unlocks local Inbox without friction
    • Screwdriver vs Swiss Army knife: writing Cursor-ready MVP constraints
    • Scraping AI chat DOMs without losing conversational turns
    • Friction Counter as product instrumentation before adding features

Graph View

Backlinks