v8 Release Todos

＃ memory.wiki — release audit + asset production brief

One-shot reference for the late-May / early-June 2026 release cycle. Lists what shipped on every channel, what still needs human action, and the exact image + copy briefs to commission new marketing assets from a designer (or to produce yourself).

Status as of 2026-06-05. Document owner: Hyunsang. Update in place as each item ships; archive when the entire checklist clears.

TL;DR — what landed in the last two weeks

Nine channels touched (web, desktop DMG, chrome ext, vscode, cli, mcp, iOS, Android, Mac App Store). Two channels are fully live; the rest are blocked on either store submission, manual upload, or fresh screenshots.

Headline features of the cycle, in order of "users will notice":

1. Per-user AI usage tracking — every callAI / streamText writes a row to ai_usage with action, provider, model, tokens, cost. Admin Usage tab at /admin → Usage shows totals, daily trend, top users, per-feature breakdown, per-provider breakdown, plus the full action catalog. Pro pricing finally has billing data.
2. Per-site Intent Capture suggestions in the Chrome extension. Twenty-four sites covered; site chips carry a small AI sparkle icon and are dismissible.
3. QuickLook actually registers with macOS now (v2.7.2). Root cause turned out to be electron-builder's deep-sign overwriting the .appex's sandbox entitlement. Fixed with an afterSign hook that re-signs the .appex with the right entitlements then refreshes the parent sign chain.
4. Threads body capture fixed. Long posts no longer ship as [Image #N] — falls back to og:description on permalinks when the React DOM only yields a fragment.
5. X quote-tweet body leak fixed. Clicking Add on a quote-tweet captures the focal tweet, not the quoted one.
6. Sidebar drag-out UX overhaul in the web editor. Drop anywhere on the tree background to move to root. Post-drop bounce killed; replaced with a brief background-fill flash + auto-scroll-into-view.
7. Sidebar context menu fit-to-viewport — right-clicking the bottom-most row no longer clips the menu.

Smaller polish: admin Usage tab silent auto-refresh, AI provider config admin-tunable, chrome-ext chip rail chevrons wrap at the ends, chip dedupe.

Per-channel release notes

memory.wiki (web app)

Live. No version bump. Recent commits:

• 7d7c3fb0 AI usage tracking — ai_usage table + logUsage helper across 22 call sites + admin Usage tab
• 876b2cd1 admin Usage tab action catalog + sidebar drag-out UX + context menu fit-to-viewport
• 494c6050 sidebar post-drop flash + scroll-into-view
• ea5cbf06 kill the post-drop bounce
• ca89fc7e drop accent left bar on the flash (background fill only)
• 7b0b931e admin page periodic flicker fix
• f56eaecd Start tab Starred + Recent show 5 by default with See More
• d730ffd7 realtime audit pass — fix sidebar miss + leaks + a11y
• 695293ce kill the false "updated elsewhere" toast + show external updates as a fresh-pulse
• 95b9848b Auto-Format runs on lite model + input-sized output cap
• 7cc88318 sidebar Refresh button does a full server resync
• 3b3d905b b972db44 AI provider cascade unification

Migration 062_ai_usage.sql applied.

Desktop (Mac, DMG — v2.7.2)

DMG ready, GitHub Release published. Notarized + stapled. Signed with Developer ID Application (Team W7NL89YGSD).

Download: https://github.com/raymindai/memory-wiki/releases/tag/desktop-v2.7.2

v2.7.1 was broken (Active badge said on, Space-in-Finder did nothing). v2.7.2 fixes the real cause:

• electron-builder's deep-sign was overwriting the QL .appex's com.apple.security.app-sandbox entitlement with the host's hardened-runtime entitlements (no sandbox). macOS pkd then silently rejected the extension with "plug-ins must be sandboxed".
• Fix: new scripts/afterSign.js hook re-signs the .appex with the QL entitlements file (sandbox + network.client), then refreshes the QL host bundle's signature, then refreshes the outer host's signature (shallow so it doesn't re-trigger the deep-sign). Verifies app-sandbox is present after re-sign; aborts the build if not.
• installQuickLook() in main.js now strips quarantine xattr + unregisters stale paths from previous installs (Xcode derived-data dev builds, old install locations) before lsregister'ing the current bundle. The Repair CTA on the Home banner is still there for emergencies.

Desktop (Mac App Store — task #165 pending)

Not submitted. Same code base as DMG, different build target. apps/desktop/scripts/build-mas.sh is wired and produces a signed .pkg, but App Store Connect submission has never been done.

Differences from DMG:

• appId flips to wiki.memory.desktop (already configured)
• .appex is embedded inside the host's Contents/PlugIns/ (not Resources/), with bundle id rewritten to wiki.memory.desktop.qlextension per Apple's "extension must be a child of host" rule
• Signed with Apple Distribution + provisioning profile (file already at apps/desktop/build/embedded.provisionprofile)
• Wrapped as .pkg via productbuild

What's blocked on submission:

1. App Store Connect record — never created. Need a new app entry: bundle id wiki.memory.desktop, primary category Productivity, secondary Developer Tools.
2. Screenshots — App Store requires at least one screenshot per supported size (1280×800 and 1440×900 are the common Mac sizes). See "Image production brief / Mac App Store" below.
3. Privacy nutrition label — App Store Connect form. Data collected: account info (email), user content (markdown docs uploaded to memory.wiki cloud), diagnostics (none). Data NOT collected: location, contacts, browsing history, ads.
4. Export compliance — uses HTTPS + standard TLS. Encryption Yes / Exempt (1.2.3).
5. Demo account — demo@memory.wiki with a couple of test docs already exists. Add credentials to the App Review notes.

Chrome extension (v2.7.0)

Zip ready, GitHub Release published, Web Store upload pending.

Zip: apps/chrome-extension/memory-wiki-clipper-2.7.0.zip (515 KB, 36 files) GitHub Release: https://github.com/raymindai/memory-wiki/releases/tag/chrome-ext-v2.7.0

New (user-visible): Per-site Intent Capture suggestions (24+ sites). Chip rail chevrons wrap around.

Fixed: X quote-tweet body leak, Threads body extraction (og:description fallback), Add button covering icons (dynamic svg-based positioning with !important inline), chip dedupe.

VS Code extension (v1.7.0)

Already published on Marketplace (June 2). No new commits since v1.7.0. Skipping.

Optional: refresh the Marketplace gallery screenshots — current ones are from v1.4.x, before the v3.0 TipTap web-parity migration.

CLI / MCP

Both up to date on npm. No code changes this cycle.

iOS (v0.1.0 — not yet shipped)

Native SwiftUI app at apps/ios-native/. v8 W9 deliverable.

What's built

• Main app: timeline of your memory.wiki docs, browse + open
• Share Extension (wiki.memory.MemoryWiki.Share) — capture from Safari, X, Threads, Notes, anywhere with iOS Share Sheet
• Widget (wiki.memory.MemoryWiki.Widget) — Home / Lock screen, recent docs
• Spotlight indexing of saved docs
• Offline-first sync (local SQLite mirror, sync on launch + on background-fetch)
• WebView hybrid renderer (v3.0 Phase E) — same markdown-it / KaTeX / Mermaid pipeline as the web

Bundle ids: wiki.memory.MemoryWiki (host), .Share (extension), .Widget (widget)

Project structure: generated from project.yml via XcodeGen — repo never has to merge a hand-edited .pbxproj. Existing screenshots in apps/ios-native/screenshots/ at v011, v012, v013, v014.

What's needed for first App Store submission

1. App Store Connect record — new app: bundle id wiki.memory.MemoryWiki, primary category Productivity, secondary Reference. Pricing free.
2. Screenshots — required sizes: 6.9" (iPhone 17 Pro Max), 6.5" (iPhone 14 Plus), and at least one iPad size if marking iPad compatible. See "Image production brief / iOS" below.
3. App icon — 1024×1024 master already in the Assets catalog from project.yml.
4. App review notes — demo account demo@memory.wiki / [password], sample doc URL like memory.wiki/abc123, explanation of Share Extension flow ("After install, open Safari → tap Share → select memory.wiki to save the page as markdown").
5. Privacy nutrition label — same as Mac App Store entry above.
6. TestFlight beta (recommended) — 1 internal test cycle before public submission. Easy to do once App Store Connect record exists.

Android (v0.1.0 — not yet shipped)

Native Kotlin/Compose app at apps/android-native/. v8 W9/W10 deliverable.

What's built

• Main app: timeline + browse + open
• Share intent receiver — capture from any app via Android Share Sheet
• Widget (Home screen, configurable size)
• WebView hybrid renderer (v3.0 Phase F) — same pipeline as iOS
• Offline-first via Room + sync on launch
• Material 3 + design-token-driven theme (v8 Pure design language)

Application id: wiki.memory.MemoryWiki

Release scaffolding is done — apps/android-native/RELEASE.md documents the upload-keystore.jks layout, gradle signing config, AAB build target, and Play Console submission flow. Both files (release-keystore.properties + upload-keystore.jks) are gitignored; founder back up only.

What's needed for first Play Store submission

1. Play Console app entry — package wiki.memory.MemoryWiki, category Productivity. Pricing free.
2. Signed AAB build — ./gradlew :app:bundleRelease (signing config already wired) → produces apps/android-native/app/build/outputs/bundle/release/app-release.aab
3. Screenshots — at least 2 phone screenshots (recommended 8) at 1080×1920 or higher. See "Image production brief / Android" below.
4. Feature graphic — 1024×500 PNG, the Play Store hero image
5. Privacy policy URL — Play Store requires a public URL. Use https://memory.wiki/privacy.
6. Data Safety form — analog to Apple's nutrition label. Collected: email (for account), user-uploaded markdown content. Not collected: location, contacts, advertising IDs.
7. Internal testing track (recommended) — ship to internal testers first, then closed beta, then production.

Image production brief

Every visual asset the release needs. Each subsection lists, per channel, every image to produce with exact dimensions, content, copy overlay, source-page-to-capture, design tokens, and where the asset will be uploaded.

Global design tokens (memory.wiki Pure design language)

Typography

• Headline: Cal Sans (bundled), tracking -0.01em
• Body: system-ui / -apple-system
• Mono: JetBrains Mono (bundled)

Brand voice for image copy

Plain. Specific. Verbs over adjectives. No "transform your workflow", no "supercharge". Avoid em-dash and middle-dot as separators inside image copy; use spacing or a forward slash. Mention "memory.wiki" lowercase. Reference features by their actual UI name. Numbers ("24+ sites", "2.7.2", "3 seconds") are good.

Chrome Web Store (priority 1)

Five images. Specs unchanged from earlier draft below.

chrome / 01-hero.png

chrome / 02-site-suggestions.png

| Dimensions | 1280 × 800 | | Background | Light (#fafafa) | | Capture | 3 mock browser frames stacked: YouTube, arXiv, GitHub. Each shows its popup with matching site chips. Sparkle icon visible | | Headline | "It knows where you are." | | Sub | "On YouTube: 'Summarize from transcript'. On arXiv: 'Abstract + contributions'. On GitHub: 'README in 5 bullets'." |

chrome / 03-social-capture.png

| Dimensions | 1280 × 800 | | Background | Dark (#09090b) | | Capture | Split: left = X / Threads post with Add button NOT covering pencil/more, right = resulting memory.wiki URL preview with clean markdown | | Headline | "Save a post, get a URL." | | Sub | "Author + body + media. No screenshot. Any AI can read it." | | Use a real Korean Threads post (the one that motivated the bug fix) so the screenshot is its own QA evidence |

chrome / 04-ai-transform.png

| Dimensions | 1280 × 800 | | Background | Light (#fafafa) | | Capture | Popup with Intent textarea filled ("Action items as checklist") + result preview below | | Headline | "Type what you want. Get it." | | Sub | "Polish, summarize, extract code, action items as checklist — your prompt, your call." |

chrome / 05-promo-tile.png (small promo, 440×280)

Morph blob left + "memory.wiki Clipper" wordmark right, "Capture, with intent." sub, mono "v2.7.0" corner pill. Dark.

chrome / 06-marquee-1400x560.png (optional, for featured-tile placement)

Wide horizontal. Blob + 3 bullet features: per-site / cross-AI / X-Threads-pages.

memory.wiki landing (priority 2)

site / hero-2026-06.png

| Dimensions | 2400 × 1200 @2x, displayed at 1200 × 600 | | Layout | Headline left, card collage right (doc URL chip, chrome popup with site chips, desktop Recent list) | | Headline | "From thought to shared URL, faster than your AI typed it." | | Sub | "Capture anywhere — web pages, X, Threads, AI chats, files — to a memory.wiki URL that Claude, ChatGPT, Cursor, and Gemini can all read." |

site / feature-admin-usage.png

| Dimensions | 1600 × 1000 | | Capture | Real /admin → Usage screenshot: totals header, daily cost trend chart, ≥1 row of Top users, ≥3 rows of per-feature breakdown | | Headline | "Pro pricing, on real data." | | Use real (anonymized) admin view — Pro pricing legitimacy shot |

site / feature-cross-ai.png

| Dimensions | 1600 × 1000 | | Layout | Center: memory.wiki/abc123 URL chip. 4 arrows radiating to Claude / ChatGPT / Cursor / Gemini marks | | Headline | "One URL. Every AI reads it the same way." |

site / feature-quicklook.gif

| Dimensions | 1200 × 750, 8s loop, ≤ 4 MB | | Capture | Finder window, .md file, Space → preview opens with our QL renderer (heading + code + mermaid). Close, repeat once | | Caption | "QuickLook for .md files. Press Space. That's the install." |

Mac Desktop DMG hero / docs (priority 3)

desktop / 01-hero-2.7.2.png

| Dimensions | 1920 × 1200 | | Capture | Full app window on macOS Sonoma dark mode. Sidebar with Synced / Local / Cloud expanded, open .md doc showing TipTap WYSIWYG (heading + list + code + math + mermaid), ambient morph blob low-opacity background | | Caption | "memory.wiki Desktop 2.7.2 — local files + cloud sync, in one editor." |

desktop / 02-quicklook-repair.png

| Dimensions | 1600 × 900 | | Capture | Home tab's QuickLook banner. Side-by-side: "ACTIVE" state (after repair) and "Repair" state (icon dimmed). Arrow between captioned "One click registers with macOS" |

desktop / 03-sidebar-drag.png

| Dimensions | 1600 × 900 | | Capture | Mid-drag screenshot: tab being dragged out of folder, tree showing the subtle background tint, destination row about to flash | | Caption | "Drag anywhere out of a folder. It scrolls into view and flashes — so you see where it went." |

Mac App Store (NEW — priority 3.5, blocking MAS submission)

App Store requires its OWN screenshots (not the DMG marketing shots). Required sizes:

mas / 01-1280x800.png (primary)

| Dimensions | 1280 × 800 | | Capture | Split view: 사이드바(좁게) + 에디터 + preview pane. 가운데 doc은 H1 + 코드(highlight) + KaTeX 수식 + Mermaid 다이어그램 + 표가 한 화면에 다 들어가게. Reader 품질 + WYSIWYG 동시 노출 | | Caption (entered in App Store Connect) | "The best Markdown reader and editor on Mac." |

mas / 02-1280x800.png

| Capture | Editor view — WYSIWYG content with mermaid diagram + KaTeX math + syntax-highlighted code block, all rendered | | Caption | "Same renderer as memory.wiki. What you see is what visitors see." |

mas / 03-1280x800.png

| Capture | Home tab with the QuickLook banner showing ACTIVE state | | Caption | "QuickLook for .md files. Press Space on any markdown file in Finder." |

mas / 04-1280x800.png

| Capture | Cloud tab with bundles + hub view, showing the AI sidebar open for one selected doc | | Caption | "Sync with the cloud. Chat with your docs. Cross-AI by default." |

mas / 05-1440x900.png (large display)

| Dimensions | 1440 × 900 | | Capture | Same as mas/01 but at 1440×900 — App Store also accepts this as a primary size |

Marketing text fields (App Store Connect)

• App name: memory.wiki
• Subtitle (30 char max): Markdown to a shareable URL
• Promotional text (170 char, can be edited without re-review): Per-user AI usage tracking, QuickLook for .md files, full TipTap WYSIWYG. Same cloud as memory.wiki on web.
• Description: see Copy library below
• Keywords (100 char): markdown,memory,wiki,notes,publish,wysiwyg,quicklook,obsidian,bear,ulysses
• Support URL: https://memory.wiki/support
• Marketing URL (optional): https://memory.wiki

iOS App Store (NEW — priority 4)

Required screenshot sizes (Apple requires AT LEAST the 6.9" iPhone size; 6.5" recommended for older devices):

ios / 6.9-01.png (iPhone 17 Pro Max — primary)

| Dimensions | 1320 × 2868 (portrait) | | Capture | Timeline view: recent docs as cards with title + first line + tiny visibility chip (Public / Private / Shared) | | Caption | "Every memory.wiki doc, in your pocket." |

ios / 6.9-02.png

| Capture | Share Extension flow: Safari article + Share Sheet open with "memory.wiki" highlighted | | Caption | "Save anything from Safari, X, Threads — to a URL Claude / ChatGPT can read." |

ios / 6.9-03.png

| Capture | Open doc with rendered TipTap content (heading + list + code block + KaTeX math) | | Caption | "Renders Markdown the same way the web does." |

ios / 6.9-04.png

| Capture | Widget on a Home screen — recent docs as a tappable list | | Caption | "Widget on Home or Lock screen. Tap to open." |

ios / 6.9-05.png

| Capture | Spotlight search for a doc title — result appears with memory.wiki icon | | Caption | "Spotlight finds your docs by title or body." |

Repeat same set at 6.5" (1284 × 2778) if marking compatible with older devices. Existing apps/ios-native/screenshots/v014/ may already have prior screenshots — start from those.

App Preview video (optional, 15-30s) — record a Share Extension capture + open in app + scroll timeline. Mute audio.

Marketing text

• App name: memory.wiki
• Subtitle: Capture to a shareable URL
• Promotional text: Capture anywhere with the Share Extension. Widget on Home + Lock screen. Spotlight indexing. Offline-first.
• Keywords: markdown,notes,share,bookmark,obsidian,bear,scrapbook,wiki,memory,publish
• Description: see Copy library

Android Play Store (NEW — priority 4)

android / 01-phone-1080x1920.png

| Capture | Timeline of recent docs (same as iOS 6.9-01) | | Caption | "Every memory.wiki doc, in your pocket." |

android / 02-phone-1080x1920.png

| Capture | Share intent flow: Android Share Sheet showing memory.wiki as a target | | Caption | "Share to memory.wiki from any app." |

android / 03-phone-1080x1920.png

| Capture | Open doc with rendered Markdown | | Caption | "Same renderer as memory.wiki on web." |

android / 04-phone-1080x1920.png

| Capture | Home screen widget showing recent docs | | Caption | "Widget for one-tap access." |

android / 05-tablet-1920x1200.png (optional but recommended)

| Capture | Tablet view: 2-pane (timeline left, doc right) | | Caption | "Big-screen layout on tablets and foldables." |

android / feature-graphic-1024x500.png (REQUIRED)

| Dimensions | 1024 × 500 | | Layout | Wide horizontal hero. Phone mockup on the right showing the app + headline left | | Headline | "memory.wiki for Android" | | Sub | "Capture, sync, share." |

Existing prior screenshots: apps/android-native/screenshots/v014/ — start there.

Marketing text

• App name: memory.wiki
• Short description (80 char): Capture to a shareable URL. Share Sheet integration. Widget. Offline-first.
• Full description: see Copy library
• Category: Productivity

VS Code Marketplace (priority 5)

vscode / banner-1376x768.png

| Capture | VS Code with memory.wiki sidebar open, open .md, WYSIWYG preview right with mermaid | | Caption | "memory.wiki for VS Code / Sidebar / WYSIWYG preview / one-click publish" |

vscode / 02-sidebar.png

| Capture | Sidebar close-up: Starred top, Cloud docs grouped by state (Public, Shared, Private, View only), Local-only bottom | | Caption | "Every cloud doc, grouped by who can see it." |

vscode / 03-preview.png

| Capture | Editor split: markdown source left, full TipTap preview right (code + KaTeX + mermaid) | | Caption | "Same renderer as memory.wiki. What you see is what visitors see." |

Social launch set (priority 6)

social / twitter-1200x675.png

| Headline | "Capture from anywhere on the web. Tell it what you want. Get a URL Claude / ChatGPT / Cursor can all read." | | Footer | "memory.wiki Clipper 2.7.0 — out now for Chrome." |

social / linkedin-1200x627.png

Same headline + screenshot. Caption (post body, not on image):

Spent the week shipping the boring-but-load-bearing parts: per-user AI usage tracking across every surface, QuickLook on macOS that actually registers with the system, and a chrome popup that knows whether you're on YouTube vs. arXiv. Small features individually, but together they're the difference between "I tried this once" and "I use this every day."

social / threads-1080x1350.png

| Layout | Stacked: screenshot top, headline middle, 3-feature list bottom | | Headline | "It guesses what you want to do, before you type it." |

Copy library

Chrome Web Store

Name: memory.wiki Clipper

Short description (132 char max)

Save anything on the web to a memory.wiki URL any AI can read. Per-site Intent Capture. AI transforms on the fly.

Full description

memory.wiki Clipper turns any web page, AI chat, social post, image, or selection into a clean memory.wiki URL — the same URL Claude, ChatGPT, Cursor, and Gemini all read identically.

What's new in 2.7.0

Per-site Intent Capture. The popup looks at the current tab and surfaces the 3 most likely intents for that kind of page. On YouTube: summarize from transcript. On arXiv: abstract + contributions. On Stack Overflow: accepted answer + code. Click a chip, capture, done.

X / Threads / page capture, fixed properly. Quote-tweets, long Threads posts (the kind that used to come through as just an image), URL-only tweets with link cards — all now capture cleanly. The Add button positions itself dynamically so it never covers the pencil or more-menu.

Chip rail wraps at the ends. No more dead clicks.

Core

Capture anywhere: full pages, selections, images, AI chats (Claude / ChatGPT / Gemini / Perplexity), X / Threads / Reddit / Hacker News / Medium / Substack posts. AI transform on the fly: "Action items as checklist", "Cursor-ready reference", "TL;DR in 2 sentences", or type your own intent. Every capture becomes a memory.wiki URL anyone (or any AI) can open. No login required for anonymous captures. Sign in to attach captures to your account.

No tracking. No third-party data sharing. Source on GitHub at raymindai/memory-wiki.

Mac App Store description

memory.wiki Desktop is the native macOS companion to memory.wiki. Sidebar to every doc in your cloud, side by side with local .md files on disk. WYSIWYG editor matches the web exactly (GFM, KaTeX math, Mermaid diagrams, syntax-highlighted code). Two-way sync.

Highlights

• QuickLook for .md files. Press Space on any markdown file in Finder, get a rendered preview instantly.
• Sidebar groups docs by visibility (Public, Shared, Private, View-only) and source (Synced, Local, Cloud-only).
• Every doc you publish gets a memory.wiki URL that Claude, ChatGPT, Cursor, and Gemini all read the same way.
• Drag-and-drop import. Move files between folders. Right-click for full per-doc actions.
• Offline-first. Edit local files anytime; sync resumes when you're back online.

No tracking. No third-party data sharing.

iOS App Store description

memory.wiki for iOS. Capture from anywhere with the Share Extension. Recent docs on Home + Lock screen via the Widget. Spotlight finds your docs by title or body. Offline-first.

Highlights

• Share Extension: select "memory.wiki" from any iOS Share Sheet — Safari, X, Threads, Notes, Mail — to save the source as a clean markdown doc on memory.wiki.
• Widget: recent docs on Home or Lock screen. Tap to open.
• Spotlight indexing: find your docs alongside system search results.
• Renders Markdown the same way memory.wiki does on web (GFM + KaTeX + Mermaid).
• Offline-first: docs cached locally, sync on launch and in the background.

Same account as memory.wiki on web. No tracking. No third-party data sharing.

Android Play Store description (full)

memory.wiki for Android. Capture from any app via the Share Sheet. Home screen widget with recent docs. Offline-first.

Highlights

• Share intent receiver: send any text / URL / image from any app to memory.wiki via Android's Share Sheet.
• Widget: recent docs on your Home screen, configurable size.
• Same renderer as memory.wiki on web (GFM + KaTeX + Mermaid + syntax highlighting).
• Offline-first: docs cached via Room; sync on launch.
• Material 3 themed; light and dark modes follow the system.

Same account as memory.wiki on web. No tracking. No third-party data sharing.

VS Code Marketplace description (if refreshing)

memory.wiki for VS Code. Sidebar to your memory.wiki cloud right inside the IDE. Publish a Markdown file, get a permanent URL Claude, ChatGPT, Cursor, and Gemini all read the same way. WYSIWYG preview matches the web renderer exactly (GFM, KaTeX, Mermaid, code highlighting). Sidebar lists every cloud doc by visibility state. Two-way sync.

memory.wiki landing — feature copy

Per-user AI usage tracking

Every AI call across memory.wiki — chat, polish, format, transform, hub synthesis — writes a row to ai_usage with the action, provider, model, tokens, and cost. The admin Usage tab shows totals, daily trend, per-user spend, and a per-feature breakdown. Pricing is built on real data, not estimates.

Per-site Intent Capture (Chrome extension)

Open the popup on YouTube and the first chip you see is "Summarize from transcript". On arXiv: "Abstract + contributions". On GitHub: "README in 5 bullets". Twenty-four sites covered out of the box. Click a chip, capture, done.

Cross-AI delivery model

Every memory.wiki URL serves a clean markdown payload — no auth wall, no proprietary container, no rendering tricks. Claude, ChatGPT, Cursor, Gemini, Perplexity all fetch the same bytes. The cross-AI moat is the delivery model, not the retrieval.

Manual launch checklist (in order)

Tier 1 — already shipped or one-click away

1. ✅ Web auto-deployed
2. ✅ Desktop DMG v2.7.2 — GitHub Release published
3. ✅ Chrome ext v2.7.0 zip — GitHub Release published
4. ⬜ Chrome Web Store upload (you, ~10 min + 1-3 day review)
   • Go to https://chrome.google.com/webstore/devconsole
   • Package tab → Upload new package → apps/chrome-extension/memory-wiki-clipper-2.7.0.zip
   • Store listing tab → replace screenshots (see Chrome brief above) + paste copy
   • Submit for review
5. ⬜ memory.wiki landing refresh — update Mac download link to v2.7.2, swap in new feature shots

Tier 2 — new stores (multi-week effort)

6. ⬜ Mac App Store first submission (task #165)
   • Create App Store Connect record
   • Build .pkg via cd apps/desktop && ./scripts/build-mas.sh
   • Take 4-5 screenshots per "Mac App Store" brief above
   • Fill privacy nutrition label, export compliance, demo account
   • Submit
7. ⬜ iOS App Store first submission
   • Create App Store Connect record for wiki.memory.MemoryWiki
   • Archive in Xcode → upload via Transporter
   • Take 5+ screenshots at 6.9" per iOS brief above
   • Fill privacy nutrition label, demo account
   • TestFlight 1 internal cycle, then Submit
8. ⬜ Android Play Store first submission
   • Create Play Console app entry
   • Build AAB via ./gradlew :app:bundleRelease
   • Take 4+ phone + 1 tablet screenshot + feature graphic per Android brief above
   • Fill Data Safety form + privacy policy URL
   • Internal testing → closed beta → production

Tier 3 — polish

9. ⬜ VS Code Marketplace gallery refresh (optional)
10. ⬜ Social launch posts (after Chrome Web Store goes live)
11. ⬜ Verify QuickLook on a fresh v2.7.2 install yourself before announcing

What I did automatically before writing this doc

For paper trail:

• Built + notarized + stapled Desktop v2.7.2 DMG (memory.wiki-2.7.2-arm64.dmg)
• Created afterSign.js hook that re-signs the QL .appex with the right entitlements file then refreshes the parent sign chain
• Bumped Chrome extension manifest 2.6.0 → 2.7.0, packaged clean zip (515 KB, 36 files)
• Tagged desktop-v2.7.2, desktop-v2.7.1, chrome-ext-v2.7.0 on origin
• Created GitHub Releases for the desktop and chrome ext
• Pushed everything to main

What remains is human-only: store submissions, new screenshots, copy review.

Generated 2026-06-05. Update in place as items ship; archive when checklist clears.

Update 2026-06-07

Continuing release work today, after the initial audit.

Web — additional polish landed

All auto-deployed via Vercel:

• 6e5d4d63 f72d13a6 5da6aa69 c1f586fa 1fff3b4d — auth popup overhaul: Apple sign-in added across editor + DocumentViewer, 4-pill column layout (no divider, email is the 4th pill), 18px icon slots, Apple visual-center nudge
• a7394d34 — brand sweep: 154 files, Memory.Wiki / Memory Wiki → memory.wiki lowercase (code identifiers like MemoryWikiLogo untouched)
• 72612186 — sidebar: drag catchment area collapses to 0 in idle state (the 120px reserve was making MDs / Bundles look weirdly tall vs. neighbour sections)
• 7c6ab0dc — welcome work reverted per founder request; auth popup kept

Web — download links unified

d020e49a next.config.ts redirects:

• /downloads/memory-wiki-desktop.dmg → desktop-v2.7.2 DMG (GH Releases)
• /download/mac → same (short URL for sharing)
• /downloads/memory-wiki-chrome.zip → chrome-ext-v2.7.0 zip (GH Releases)

Updated InstallPure.tsx + PluginsPure.tsx to use the new stable chrome path (was pointing to a stale v2.2.2 static asset). 308 redirects so users hit GitHub's CDN directly — no 110MB DMG streaming through Vercel, and each release just edits one line per channel.

Apple Sign in setup — note

Apple OAuth for web was failing with "invalid_request — Invalid client id or web redirect url" because Supabase was sending the iOS app's Bundle ID (wiki.memory.MemoryWiki) as the OAuth client_id, but Apple requires a separate Services ID for web flows.

Resolved with founder by:

1. Apple Developer Portal — Services ID wiki.memory.MemoryWiki.signinservice already existed but wasn't wired to Supabase. Verified Primary App ID = wiki.memory.MemoryWiki, domains include gxvhvcuoprbqnxkrieyj.supabase.co + memory.wiki, return URL = https://gxvhvcuoprbqnxkrieyj.supabase.co/auth/v1/callback
2. Supabase Apple provider Client IDs list updated to wiki.memory.MemoryWiki.signinservice,wiki.memory.MemoryWiki — Services ID FIRST so it's used for web OAuth flow, Bundle ID second so iOS native ID-token verification still passes

iOS native Apple sign-in continues to work because Bundle ID is still in the allowed list. Same Apple ID account → same Supabase user across iOS + web.

GitHub OAuth app — needs founder update

The GitHub OAuth consent screen still says "Authorize mdfy.cc" with the old yellow pixel face logo. This is purely a GitHub Developer Settings record, not a code thing.

Founder TODO at https://github.com/settings/developers → OAuth Apps → find "mdfy.cc" entry:

• Application name: mdfy.cc → memory.wiki
• Homepage URL: → https://memory.wiki
• Application logo: upload memory.wiki morph blob (1024×1024)
• Authorization callback URL: keep https://gxvhvcuoprbqnxkrieyj.supabase.co/auth/v1/callback

Same audit needed for Google OAuth consent screen at https://console.cloud.google.com/apis/credentials/consent — app name / homepage / logo all need memory.wiki branding.

MAS .pkg build — in progress

Running ./scripts/build-mas.sh against v2.7.2 source. Output will land at apps/desktop/dist/memory.wiki-2.7.2.pkg. First-time observation: build is currently using the Developer ID Application identity (F3DF…) instead of Apple Distribution (538E…). May need a CSC_NAME env var override before this .pkg passes App Store Connect validation. Will verify once build completes.

Latest channel state

Update 2026-06-07 (continued) — Desktop v2.7.3 shipped

What's new in v2.7.3

Three bugfixes / polish items, one ship:

1. Manual theme toggle in the desktop header. Sun / monitor / moon icon cycles system → light → dark → system, persisted in localStorage as mw-theme. Default stays system so a fresh install still tracks macOS Dark Mode. Light mode CSS tokens were already wired — this just exposes the choice in the UI.
2. Publish button color fix. The header Publish button was reading "우중충한 녹색" (dull green) because the border was hardcoded to rgba(181, 255, 26, 0.25) — leftover from the old micro-lime brand period. Replaced with token-based var(--border) so the chip follows the current palette in either theme.
3. Cloud doc loading no longer hangs forever. Two compounded failure modes:
   • apiPull had no timeout — a stalled network request left the fetch pending indefinitely. Added 15s AbortController timeout with a clear "Network timeout (15s). Check your connection." error.
   • Renderer fired previewCloudDoc IPC without .then() / .catch(), so main-process errors ({error: ...}) never cleared the spinner. Both call sites (sidebar cloud-doc click + Home list click) now surface the error inline with the failure reason.

Also: outline panel (right-side TOC) was going stale on tab switch — required closing + reopening to refresh. Fixed with key={activeTabId} on the inner heading container to force a React remount when the active doc changes. Web side; ships on the next Vercel deploy too.

Build + release

• DMG: apps/desktop/dist/memory.wiki-2.7.3-arm64.dmg (103 MB, notarized + stapled + validated)
• MAS .pkg: apps/desktop/dist/memory.wiki-2.7.3.pkg (102 MB, signed with 3rd Party Mac Developer Installer: Hyunsang Cho (W7NL89YGSD))
• GH Release: https://github.com/raymindai/memory-wiki/releases/tag/desktop-v2.7.3
• Web next.config.ts redirects bumped to v2.7.3 (both /downloads/memory-wiki-desktop.dmg and /download/mac now point at the v2.7.3 DMG)

MAS build script fix (avoid losing the DMG)

Earlier MAS attempt deleted the just-notarized v2.7.3 DMG. scripts/build-mas.sh opened with a blanket rm -rf dist, which wiped every artifact (including the DMG produced minutes before). Fixed with a narrower scope so MAS builds preserve sibling outputs:

bashCopy
rm -rf dist/mas-arm64
rm -f  dist/memory.wiki-*.pkg

Committed in 505cc616. DMG rebuilt cleanly after the patch.

What still needs human action

• MAS Transporter delivery — Transporter.app already opened with the v2.7.3 .pkg loaded; founder clicks DELIVER to upload to App Store Connect.
• iOS 1.1 (1) .ipa upload via Transporter (Transporter previously opened in the prior turn).
• Chrome Web Store — manual upload of v2.7.0 zip + 5 screenshots still pending.
• Mac App Store record + privacy nutrition — still pending for first MAS submission (task #165).
• Android Play Console first submission — still pending.

Latest channel state

Mac App Store 스크린샷 카피 (3-part, iOS 톤 그대로)

8개 옵션 — 첫 3장이 install sheet에 노출되므로 1-3-4 또는 1→3→4→2→6→5→7→8 narrative arc 추천.

1. Hero / overview — "Best Markdown reader and editor"

• Pill — Reader and Editor
• Headline — The best Markdown / reader and editor.
• Sub — Beautifully rendered. Live WYSIWYG editing. / KaTeX, Mermaid, code, all built in.

2. Sidebar (Local + Cloud + Synced)

• Pill — One Sidebar
• Headline — Cloud and local, / in one tree.
• Sub — Synced, local-only, cloud-only — grouped clearly. / Drag between folders. Right-click for everything.

3. WYSIWYG editor (TipTap)

• Pill — WYSIWYG Editor
• Headline — Edit like a doc, / save like a URL.
• Sub — Headings, lists, code, math, diagrams — all live. / Same renderer as memory.wiki on the web.

4. QuickLook in Finder

• Pill — QuickLook
• Headline — Press Space. / See Markdown.
• Sub — Any .md file in Finder previews instantly. / KaTeX math, Mermaid diagrams, code highlighting.

5. Built-in chat (Mac-context version)

• Pill — Built in Chat
• Headline — Chat with / your own notes.
• Sub — Built-in chat over your hub, bundles, and MDs. / Answers cite the source.

6. Bundles

• Pill — Bundles
• Headline — Group docs into / a thinking surface.
• Sub — Bundle related notes, tag a tension to resolve, / share the bundle as one AI-ready URL.

7. Drag-and-drop import

• Pill — Drag To Import
• Headline — Drag files in, / get URLs out.
• Sub — PDF, Word, PowerPoint, HTML, code, Markdown. / Drop them on memory.wiki, get clean Markdown back.

8. Cross-AI (closing slide)

• Pill — Any AI Reads It
• Headline — Paste the URL. / Any AI reads it.
• Sub — Claude, ChatGPT, Cursor, Gemini, Codex — / they all fetch the same Markdown payload.

Recommended order: 1 (best reader/editor) → 3 (WYSIWYG) → 4 (Mac-only QuickLook). 10장 full deck이면 1→3→4→2→6→5→7→8 (reader/editor → 편집 깊이 → finder 차별점 → 관리 → 사고 → 대화 → 가져오기 → 공유).

Mac App Store 스크린샷 제작 가이드

iOS 작업 톤 그대로 + Mac 특수 사항 반영.

1. Apple 요구사항 (Mac)

한 사이즈로 통일 — 2880×1800 추천 (다른 사이즈는 자동 다운스케일 처리).

2. 3-Part Overlay 구조 (iOS와 동일)

Copy
┌─────────────────────────────────────────────┐
│                                             │
│           [ mono pill ]                     │  ← 16-20% from top
│                                             │
│        Headline display                     │  ← 2 lines, large
│        2 lines, period end.                 │
│                                             │
│        Mono sub, two lines.                 │  ← 2 lines, smaller
│        Telegraph style.                     │
│                                             │
│   ┌─────────────────────────────────┐       │
│   │                                 │       │  ← App window screenshot
│   │       app window capture        │       │     inside a Mac frame
│   │       (centered, ~70-75%        │       │     OR clean window
│   │        of canvas width)         │       │     with shadow
│   │                                 │       │
│   └─────────────────────────────────┘       │
│                                             │
└─────────────────────────────────────────────┘

3. Design tokens (정확한 값)

폰트 파일은 이미 repo에: apps/chrome-extension/fonts/CalSans-Regular.ttf, JetBrainsMono-Regular.woff2. Figma에 import해서 사용.

4. Per-screenshot 캡쳐 시나리오

각 스크린샷마다 앱을 어떤 상태로 만들어야 하는지 + 무엇을 캡쳐하는지 + 카피.

#1 Hero — Best Markdown reader and editor (1순위, install sheet 첫 자리)

• 앱 상태 — Split view (사이드바 좌측 + 가운데 에디터 + 우측 preview pane). 가운데 doc에는 마크다운의 모든 기능이 한 화면에 보이게: H1 + 본문 + 코드 블록 (syntax highlight) + KaTeX 수식 한 줄 + Mermaid 다이어그램 (작게) + 표. 이 한 장이 "이거 보이는 거 다 됨" 증명 — reader로서의 렌더링 품질 + editor로서의 WYSIWYG 둘 다 동시 노출이 핵심
• 캡쳐 영역 — 앱 윈도우 전체 (1600×1000 정도). 사이드바는 좁게, 에디터 + preview가 hero
• macOS 메뉴바 — 포함 (더 native하게)
• 팁 — demo 계정에 "Markdown Showcase" doc 하나 미리 만들어두기 (heading + math + mermaid + code + table 한 페이지에 다 들어간 것). 이 doc는 #1 외에 reader/editor 포지셔닝 영상에도 재사용 가능

#2 WYSIWYG editor

• 앱 상태 — 새 doc 만들고 모든 기능 한 화면에 보이게: H1 + 본문 + 인용 + 코드 블록 (highlight) + Mermaid 다이어그램 (작게) + KaTeX 수식 한 줄. 사이드바 접기
• 캡쳐 영역 — 에디터 영역만 크게
• 팁 — demo 계정으로 "Markdown Syntax Guide" doc 같은 거 있으면 그거 띄우면 1초

#3 QuickLook (Mac 유일 차별점)

• 앱 상태 — 앱이 아니라 Finder + QuickLook 미리보기 캡쳐. Finder 열고 .md 파일 하나 선택 → Space → QL 패널 떴을 때
• 캡쳐 영역 — Finder 윈도우 + QL 패널 둘 다
• 팁 — QL 패널 안의 doc은 표 / 수식 / 다이어그램 다 들어간 것. selling point가 곧 차별점

#4 Sidebar (Local + Cloud + Synced)

• 앱 상태 — 사이드바 가장 펼친 상태. Cloud 섹션에 docs 여러 개, Local 섹션에도 몇 개, Synced 섹션에 mix. 폴더 1-2개 expanded
• 캡쳐 영역 — 사이드바 + 살짝의 에디터 (사이드바가 hero가 되도록)

#5 Built-in Chat

• 앱 상태 — 어떤 doc 또는 hub view, 우측 AI Chat 패널 열림. 짧은 대화 한두 턴 (질문 → AI 답변 + citation chip)
• 캡쳐 영역 — 에디터 + AI 패널

#6 Bundles

• 앱 상태 — Bundle 하나 열린 상태. 멤버 docs 3-5개, concept graph 시각화 보이면 더 좋음
• 캡쳐 영역 — Bundle view 전체

#7 Cross-AI (closing)

• 앱 상태 — 본인 hub URL을 가운데에. 또는 doc URL을 Claude/ChatGPT에 paste한 모습 (creative composite — 다른 화면 mockup)
• 캡쳐 영역 — 실제 memory.wiki URL이 보이는 화면

5. 제작 워크플로 (Figma 권장)

1. 새 Figma 파일, 캔버스 2880×1800 frame 7개 만들기 (스크린샷별)
2. 공통 layer를 component로:
   • Background gradient
   • Ambient blob (low opacity SVG)
   • Pill template (auto-layout, 24px 텍스트, padding 12/20)
   • Headline text (Cal Sans 140px)
   • Sub text (JetBrains Mono 42px, line-height 1.45, text-align center)
3. 앱 캡쳐:
   • macOS에서 데스크탑 앱 열고 시나리오대로 setup
   • Cmd+Shift+5 → "Window 캡쳐" 선택 → 윈도우 클릭 → 사진 (.png ~/Desktop)
   • Figma로 drag → 해당 frame에 배치, 75% 너비 + 가운데 정렬 + shadow 적용
4. Export: 각 frame 우클릭 → Export as PNG, 1x (이미 2880px)

대안 (Figma 안 쓰면): macOS 기본 Preview.app + Pixelmator 또는 Acorn도 충분. iOS 스크린샷도 같은 사이즈 + 같은 폰트로 일관성 유지.

6. 캡쳐 전 체크리스트

• [ ] macOS dark mode (앱이 어두운 톤이라 더 통일감)

• [ ] 사이드바 + 우측 패널 너비를 매 캡쳐마다 일관되게

• [ ] 본인 demo doc들 미리 정리해놓기 (제목 자연스럽게, 본인 실명 노출 X, "Ron's hub" 같은 가명)

• [ ] 알림 / dock badges OFF

• [ ] 시계는 9:41 (Apple 관습) 또는 신경 안 써도 됨 (Mac은 iOS만큼 엄격하지 않음)

• [ ] AI panel 텍스트는 데모스러운 자연스러운 문장 (lorem ipsum X)

7. FAQ

Q: Mac window를 device bezel로 감싸야 함?A: 안 해도 됨. App Store는 그냥 PNG 보여줌. 윈도우 자체의 traffic lights + title bar가 자연스러운 frame. 더 marketing-스럽게 보이려면 mockuphone.com 등에서 MacBook bezel composite 가능.

Q: 캡션 텍스트가 클러터되면?A: Pill / Headline / Sub 사이 spacing을 30-40px씩. Headline과 윈도우 사이는 80-120px.

Q: 첫 3장만 만들어도 됨?A: 됨. 첫 3장이 가장 노출되고, 나머지 7장은 점진적으로 추가 가능 (리뷰 통과 후에도 수정 OK).

Chrome Web Store v2.7.1 — Store listing copy

Web Store 거절 사유 fix: manifest description 167자 → 122자 (132자 한도). 같이 brand "no em-dash" 룰 적용. v2.7.0 zip은 reject됐고 v2.7.1로 re-pack.

Manifest / Short description (132자 max)

Copy
Save pages, AI chats, social posts, images to a memory.wiki URL any AI reads. Per-site capture suggestions, AI transforms.

122자. extension management 화면 + Web Store 검색 결과 카드에 노출. apps/chrome-extension/manifest.json의 description 필드와 동기화.

Detailed description (16,000자 max) — Intent Capture 헤드라인 + companion 프레임

Copy
memory.wiki Clipper is the Chrome companion to memory.wiki on the web. Tell the extension what you want — it captures the page and writes it as a clean memory.wiki URL any AI tool can read.

The headline: Per-site Intent Capture

Open the popup on YouTube and the first chip is "Summarize from transcript." On Wikipedia: "Overview + key dates." On Reddit: "Top comments distilled." On Stack Overflow: "Accepted answer + code." On GitHub: "README in 5 bullets." On Medium: "Main argument + evidence." 24+ sites have hand-tuned intent suggestions out of the box. Click a chip, capture, done — no typing.

For sites without a curated chip, type whatever you want ("action items as a checklist", "Cursor-ready reference", "rewrite for a teammate", "TL;DR in 2 sentences") and the extension runs that intent against the page before saving. Your prompt, your call.

What it captures

- Any web page (Readability extracts the article body, drops nav and ads).
- The current selection (highlight, click capture — only the selected text saves).
- AI chats end to end (ChatGPT, Claude, Gemini, Perplexity — user and assistant turns preserved with proper formatting).
- Per-message capture from inside AI chats (hover any message, click the inline "Save" button).
- Social posts (X, Threads, Reddit, Hacker News, Medium, Substack) with the post body, author, and embedded media intact.
- GitHub .md files (rendered as a memory.wiki URL with KaTeX, Mermaid, syntax-highlighted code).

What lands on memory.wiki

Every capture publishes as a clean Markdown document and gets a permanent memory.wiki URL like memory.wiki/abc123. That URL serves the same Markdown payload to every AI tool — Claude, ChatGPT, Cursor, Gemini, Perplexity, Codex — so pasting the URL into any model gives that model your captured context.

After every capture, the sentence "Use memory.wiki/abc123 as my context." is copied to your clipboard. Paste-into-next-AI is one keystroke.

What's new in 2.7

- Per-site Intent Capture (24+ curated sites).
- Chip rail wraps at the ends, no more dead clicks.
- X quote-tweet body leak fixed (captures the focal tweet, not the quoted one).
- Threads long-post body extraction fixed (falls back to og:description on permalinks).
- Add button no longer covers the pencil or more-menu icons on social sites.

Keyboard shortcuts

- Cmd+Shift+E (Ctrl+Shift+E on Windows) — capture the current page.
- Cmd+Shift+X — capture only the highlighted selection.

What this extension is NOT

It is a capture surface, not the full memory.wiki product. Editing existing documents, organising into bundles and hubs, the AI chat panel, account management, and sharing permissions all live on memory.wiki on the web. Use the extension to feed material in, then jump to memory.wiki to organise and share.

Account

No login required for one-off captures. Sign in (free during beta, sign up at memory.wiki) to attach captures to your account, search across them, and keep them in sync with the Mac, iOS, Android, VS Code, and CLI surfaces.

Privacy

No tracking. No third-party data sharing. No ads. Source on GitHub at github.com/raymindai/memory-wiki. The extension only contacts memory.wiki for publishing and the AI providers your captures route through (Claude or GPT for intent transforms) — see memory.wiki/privacy for the full policy.

카피 결정 사항

• Intent Capture를 헤드라인으로 — 첫 두 단락이 모두 Per-site Intent Capture에 할애. 24+ 사이트 예시 (YouTube / arXiv / Stack Overflow / GitHub) 구체적으로 명시. 검색 매칭에 강함.
• Companion 프레임 — 첫 문장이 "Chrome companion to memory.wiki on the web." iOS / Android / Mac 채널들과 메시지 일관성.
• "What this extension is NOT" 섹션 — Play / App Store 리뷰어 + 사용자 기대치 관리. extension은 capture-only surface임을 명시. 편집 / 조직 / AI chat은 웹에 있다고 분명히.
• Truthfulness — 6개 capture surface 모두 실제 동작 확인된 것만 (general web / selection / AI chats / per-message / social posts / GitHub md).
• Cross-AI 강조 — Claude, ChatGPT, Cursor, Gemini, Perplexity, Codex 6개 클라이언트 명시. "one URL every AI reads" 무한 반복 안 하고 한 단락에 집중.

저장 위치

• 위 카피 모두 apps/chrome-extension/STORE_LISTING.md에 canonical로 저장. 다음 버전 description 수정 시 그 파일 먼저 → 그 다음 Web Store 대시보드 반영.

Outcome

• v2.7.1 zip (513KB) 새로 packing — apps/chrome-extension/memory-wiki-clipper-2.7.1.zip.
• 이전 v2.7.0 zip은 description 길이 reject로 무효화.
• Manifest commit: d90dd97a.

Chrome Web Store v2.7.1 — 스크린샷 5장 계획

Web Store는 스크린샷 5장 한도, 1280×800 PNG. Caption은 carousel 아래 별도 렌더링 안 되니까 오버레이 텍스트를 PNG에 baked-in (Mac App Store와 같은 3-part 구조: Pill / Headline / Sub).

순서 결정 — install sheet 노출 = 앞 3장이 가장 중요

추천 순서 (위에서부터 1→5):

1. Hero — Per-site Intent (1순위, install sheet 첫 자리)

• 파일: chrome/01-intent-hero.png
• Pill: Per-site Intent
• Headline: It knows where / you are.
• Sub: YouTube: Summarize transcript. Reddit: Top / comments distilled. Stack Overflow: Accepted answer.
• 앱 상태:
  • Chrome 창에 youtube.com 열림 (의미있는 동영상 — Andrej Karpathy lecture 같은 거)
  • 우상단 확장 popup 띄움 (popup-v25.html)
  • chip rail 가장 앞에 YouTube intents 3개 보이게: "Summarize from transcript" / "Key moments + timestamps" / "Action items only"
  • 첫 chip에 살짝 hover 효과 (좋게)
  • AI sparkle icon 챠음 chip 옆에 보이게 (this is the v2.7 marker)
• 캡쳐 영역: Chrome 윈도우 전체 (탭바 + URL 바 + popup). 1600×1000 정도 capture 후 1280×800 frame에 배치

2. Cross-AI URL (2순위, install sheet)

• 파일: chrome/02-cross-ai.png
• Pill: Any AI Reads It
• Headline: One URL. / Every AI reads it.
• Sub: Claude, ChatGPT, Cursor, Gemini, Perplexity / all fetch the same Markdown payload.
• 앱 상태 (composite mockup):
  • 가운데: memory.wiki/abc123 URL chip (큼직하게, 모노 폰트)
  • 4개 방향으로 화살표 → Claude / ChatGPT / Cursor / Gemini 로고
  • 각 AI 클라이언트의 작은 mockup window (URL 붙여넣어진 모습)
  • 또는 더 simple하게: 1개 클라이언트(예: Claude)에 URL paste 한 화면 + "Cursor / ChatGPT / Gemini also read this." 같은 footer
• 캡쳐 영역: 1280×800 캔버스에 직접 mockup (실제 캡쳐 X, composite design)

3. AI Chat capture (3순위, install sheet 마지막)

• 파일: chrome/03-ai-chat.png
• Pill: AI Chats Saved
• Headline: Save a chat. / Open it anywhere.
• Sub: ChatGPT, Claude, Gemini, Perplexity captured / end to end. URL works in any other AI.
• 앱 상태:
  • Claude 또는 ChatGPT 창 열림, 길지 않은 conversation (2-3턴) 보이게
  • 각 message에 hover 시 나오는 작은 "Save" 버튼이 한 message에 명시되게 (강조 화살표 또는 highlight)
  • 우상단에 popup 또는 floating dock에 "Save all" 버튼 보이면 더 좋음
  • 캡쳐 직후 결과 toast ("Captured. URL copied to clipboard.") 살짝 노출
• 캡쳐 영역: AI 채팅 화면 + extension overlay. 메시지 길이 적당히 줄이기

4. Social post capture

• 파일: chrome/04-social.png
• Pill: Social Posts
• Headline: Posts, not / screenshots.
• Sub: X, Threads, Reddit captured as Markdown / with author and body intact.
• 앱 상태:
  • 왼쪽: X 또는 Threads 게시물 1개 (의미 있는 thread, Korean OK)
  • 게시물 옆에 우리 inline "Add" 버튼 (v2.7에서 위치 fix된 거 — pencil/more 아이콘 가리지 않는 상태)
  • 오른쪽: 캡쳐된 결과 memory.wiki URL preview (author/body/timestamps 깔끔하게 markdown으로 들어간 모습)
  • Split layout으로 before(원본) → after(markdown) 비교
• 캡쳐 영역: 분할 화면, 좌측 X/Threads, 우측 memory.wiki 뷰어

5. Custom intent transform (5순위, narrative close)

• 파일: chrome/05-custom-intent.png
• Pill: Type Any Intent
• Headline: Tell it what / you want.
• Sub: "Action items as a checklist." "TL;DR / in 2 sentences." Your prompt, your call.
• 앱 상태:
  • Popup 열림 (popup-v25.html)
  • Intent textarea에 사용자 정의 prompt 입력된 상태: Action items as a checklist
  • Capture 버튼 highlighted
  • 결과 영역에 transform된 markdown preview (체크박스 리스트 형태)
• 캡쳐 영역: Popup 클로즈업 (전체 브라우저보다 popup 자체에 집중)

디자인 토큰 — Mac App Store 가이드 (위 섹션)와 동일

Promo tile (별도 — Web Store 옵션)

스크린샷 5장과 별도로:

• chrome/00-promo-440x280.png (small promo tile, 440×280) — featured / search tile에 노출. 디자인: morph blob 좌측 + "memory.wiki Clipper" wordmark 우측, sub "Capture, with intent.", mono "v2.7" corner pill. Dark.
• chrome/00-marquee-1400x560.png (optional marquee) — Chrome Web Store가 우리 ext를 featured에 올릴 때 사용. 만들 시간 없으면 skip.

제작 워크플로 — Figma 권장 (Mac App Store와 동일)

1. 새 Figma 파일, 1280×800 frame 5개 + 440×280 frame 1개
2. 공통 component:
   • Background gradient + blob
   • Pill template (auto-layout, 16px text, padding 8/14)
   • Headline (Cal Sans 72px)
   • Sub (JetBrains Mono 22px, line-height 1.5)
3. 앱 캡쳐:
   • Chrome 사용자 프로필로 demo 계정 sign-in
   • 시나리오대로 페이지 열고 extension 띄움
   • Cmd+Shift+5 → "Window 캡쳐" 또는 area 캡쳐
   • Figma drag, scale to 75-80% width, shadow 적용
4. Export: 각 frame Export as PNG, 1x

폰트 파일: apps/chrome-extension/fonts/CalSans-Regular.ttf + JetBrainsMono-Regular.woff2 (이미 repo에).

캡쳐 전 체크리스트

• [ ] Chrome 창에 다른 확장 아이콘 다 숨김 (clutter 줄이기)

• [ ] Bookmarks bar 끔

• [ ] 시계 9:41 (Apple 관습) 또는 자연 그대로

• [ ] 사인인 상태 (demo 계정 또는 본인 가명)

• [ ] popup 열린 상태에서 hover 효과는 살리되 dropdown 열리지 X

• [ ] AI 채팅 캡쳐의 경우, 메시지 본문은 demo-friendly (lorem 안 됨, 실제 의미)

Outcome

• 위 5장 + 1개 promo tile 만들면 Web Store 제출 완성
• 우선순위 1-2-3 (Hero / Cross-AI / AI Chat)이 install sheet 결정
• 나머지 (4-5)는 carousel 후반에 노출, 클릭한 사용자 conversion 도움

Generated 2026-06-10. Update in place as each PNG ships.

스크린샷 데모 콘텐츠 추천

각 장에 뭘 띄울지 구체적 추천. demo-friendly (lorem 안 됨) + 의미있음 + 본인 / 개인 정보 노출 X.

Screenshot #1 (Hero) — YouTube로 무엇을 열까

YouTube 페이지 위에 popup 띄워서 "Summarize from transcript" chip 강조하는 장면.

추천 영상 (recognizable 우선순위):

1순위: Karpathy "Let's build GPT" — AI 사람들 다 알고, "긴 강의 요약" = perfect use case 시연.

Screenshot #3 (AI Chat capture) — ChatGPT/Claude에 뭘 물어볼까

대화 2-3턴 보이게 캡쳐. 답변은 구조화된 markdown (코드 / 표 / 리스트)이 나오는 prompt가 우리 renderer 강점 + companion 메시지 둘 다 강조.

프롬프트 후보 3개:

A. AI/ML 타겟 (recommended)

Copy
Explain transformer attention to someone who knows
linear algebra but has never seen Q/K/V.
Use small numbers in a worked example, not jargon.

• 출력: 수식 (KaTeX 렌더링 강조), 작은 행렬, step-by-step
• 우리 target audience (AI builders) 정확히 hit
• "이런 답변 다른 AI에도 들고 가고 싶다" 자연스러운 use case

B. Builder/founder 타겟

Copy
Compare Stripe, Lemon Squeezy, and Paddle for an
indie SaaS doing $5k MRR. Tax handling, fees,
checkout UX, payouts. Table.

• 출력: 비교 표 (table 렌더링 강조)
• founder / indie hacker 공감
• 결정 도구로 다른 AI들에 paste 자연스러움

C. 범용 (가장 안전)

Copy
Plan a 5-day Lisbon itinerary for two, balancing
food, history, and beach. Skip museums day 1.
Day-by-day with timing.

• 출력: day-by-day 리스트 (typography 강조)
• non-tech도 매력적, "이 itinerary URL 친구한테 paste" 자연스러움
• 안전한 demo (controversial 요소 X)

추천: A — 타겟과 직결되고 KaTeX 렌더링 자랑할 수 있는 답변. Backup으로 B.

Screenshot #4 (Social capture) — X / Threads 어떤 post

X 후보:

• Karpathy의 "I keep forgetting the difference between..." 류 짧고 인사이트 있는 thread
• Paul Graham의 essay quote tweet
• 본인의 빌드인공공 thread (가장 친근하지만 self-promotion 느낌 우려)

추천: 본인 thread 1개 — 빌딩 인 퍼블릭 voice 그대로 보여줌. 단 thread 본문이 universally interesting해야 (e.g., "We just shipped X. Here's what worked / didn't" 류).

대안: Karpathy / Andrej / Aravind Srinivas 같은 AI founder의 인사이트 thread. 익숙 + 우리 audience와 일치.

Threads 후보:

• Korean Threads thread (다국어 지원 증명 + home market)
• 본인의 Korean post — Threads에 활성 사용자면 가장 자연스러움

추천: X는 본인 또는 Karpathy thread, Threads는 본인의 한국어 post (multi-language 강조).

Screenshot #5 (Custom intent transform) — 어떤 사용자 정의 intent

popup에 사용자가 직접 타이핑한 intent. 결과가 instantly 알아볼 수 있어야 효과적.

Intent 후보 (typeable 짧기):

추천: Action items as a checklist — 가장 visual (checkbox), 가장 universal use case, 결과가 markdown 렌더링 강점 보여줌.

캡쳐 시 보이는 결과 미리보기:

markdownCopy
- [ ] Set up the staging database
- [ ] Wire up Stripe webhook handler
- [ ] Add user_id index on documents
- [ ] Push v2.7.1 to Chrome Web Store

(실제 미팅 노트 / 글 / 페이지를 input으로 잡고 위 intent 돌렸을 때 나오는 합리적인 출력)

Site별 캡쳐 시나리오 — 어디서 띄울까

스크린샷에 안 들어가더라도 데모 영상 / 마케팅에 재사용 가능한 시나리오:

추가 Intent 추천 — 코드에 더할지 검토

현재 popup-v25.js SITE_SUGGESTIONS에 24+ 사이트 있음. 추가하면 좋은 사이트 + intent:

가장 high-leverage 추가 3개:

1. claude.ai / chat.openai.com — AI 사용자의 자기 chat 보관 use case
2. github.com PR/Issue URLs — dev 가장 trafficked 사이트
3. producthunt.com — founder / builder 매일 방문

이거 추가하면 → popup이 "이 사이트도 알고 있네" 인식 → install conversion 강화.

종합 권장

스크린샷 콘텐츠 픽:

• #1: YouTube — Karpathy "Let's build GPT"
• #3: ChatGPT/Claude — "Explain transformer attention with worked example" prompt
• #4: X (Karpathy thread) + Threads (본인 한국어 post)
• #5: Custom intent "Action items as a checklist"

코드에 추가하면 좋은 새 site intent: claude.ai / chat.openai.com, github PR/Issue, producthunt.com.

Chrome Web Store v2.7.4 — Keyword-spam rejection (2026-06-10)

Google rejected v2.7.4 description with Keyword Spam violation. Specific flagged content:

Social posts (X, Threads, Reddit, Hacker News, Medium, Substack) with the post body...

Google's enforcement: "Having excessive and / or irrelevant keywords in the item's description."

Pattern that triggered

Parenthetical / comma-separated brand lists. Single brand mentions in context are fine (e.g. "Open the popup on YouTube and the first chip is..."). Multi-brand lineups like (X, Threads, Reddit, ...) or Claude, ChatGPT, Cursor, Gemini, Perplexity, Codex read as SEO keyword stuffing.

Lines that needed rewriting (proactive — Google only flagged one but several matched the pattern)

What's still safe

• YouTube mentioned once in the per-site intent showcase (it leads the example list across one sentence — not a comma lineup)
• Cmd+Shift+E keyboard shortcut codes
• memory.wiki brand name (our own)
• github.com/raymindai/memory-wiki (source link)

Resubmit path

1. Web Store dashboard → memory.wiki Clipper → Store listing tab
2. Replace entire Detailed description with rewritten version (canonical at apps/chrome-extension/STORE_LISTING.md and below)
3. Save draft → Submit for review
4. Zip unchanged — v2.7.4 metadata-only resubmission (no manifest/code change needed)

Permanent rule for future Web Store copy

No parenthetical brand-name lists. If listing brand compatibility is necessary, split across sentences or use generic phrasing ("any AI tool", "social platforms", "code repositories"). Single brand mentions tied to a concrete behaviour are OK.

Rewritten description (canonical)

Copy
memory.wiki Clipper is the Chrome companion to memory.wiki on the web. Tell the extension what you want — it captures the page and writes it as a clean memory.wiki URL any AI tool can read.

The headline: Per-site Intent Capture

Open the popup on YouTube and the first chip is "Summarize from transcript." On a Q&A site: "Accepted answer + code." On a code repository: "README in 5 bullets." On a discussion thread: "Top comments distilled." 24+ sites have hand-tuned intent suggestions out of the box. Click a chip, capture, done — no typing.

For sites without a curated chip, type whatever you want ("action items as a checklist", "Cursor-ready reference", "rewrite for a teammate", "TL;DR in 2 sentences") and the extension runs that intent against the page before saving. Your prompt, your call.

What it captures

- Any web page (Readability extracts the article body, drops nav and ads).
- The current selection (highlight, click capture — only the selected text saves).
- AI chat conversations end to end (user and assistant turns preserved with proper formatting).
- Per-message capture from inside AI chats (hover any message, click the inline "Save" button).
- Posts from social platforms, with the post body, author, and embedded media intact.
- Markdown files on code repositories (rendered as a memory.wiki URL with math, diagrams, syntax-highlighted code).

What lands on memory.wiki

Every capture publishes as a clean Markdown document and gets a permanent memory.wiki URL like memory.wiki/abc123. That URL serves the same Markdown payload to every AI tool — paste it into any model to give that model your captured context.

After every capture, the sentence "Use memory.wiki/abc123 as my context." is copied to your clipboard. Paste-into-next-AI is one keystroke.

What's new in 2.7

- Per-site Intent Capture (24+ curated sites).
- Chip rail wraps at the ends, no more dead clicks.
- Social post capture: quote-tweet body leak fixed; long-post body extraction improved.
- Add button no longer covers icons on social sites.

Keyboard shortcuts

- Cmd+Shift+E (Ctrl+Shift+E on Windows) — capture the current page.
- Cmd+Shift+X — capture only the highlighted selection.

What this extension is NOT

It is a capture surface, not the full memory.wiki product. Editing existing documents, organising into bundles and hubs, the AI chat panel, account management, and sharing permissions all live on memory.wiki on the web. Use the extension to feed material in, then jump to memory.wiki to organise and share.

Account

No login required for one-off captures. Sign in (free during beta, sign up at memory.wiki) to attach captures to your account, search across them, and keep them in sync with other surfaces.

Privacy

No tracking. No third-party data sharing. No ads. Source on GitHub at github.com/raymindai/memory-wiki. The extension only contacts memory.wiki for publishing and the AI providers your captures route through — see memory.wiki/privacy for the full policy.