capture▌

Capture conversations and decisions into structured, linkable Notion pages for wikis, how-tos, FAQs, and decision logs. \n \n Supports six content types: decisions, how-to guides, FAQs, wiki entries, learning notes, and documentation pages, each with dedicated database templates and schemas. \n Includes a five-step workflow: define capture purpose, locate the target database, extract and structure content, create or update the Notion page, and link from related hub pages. \n Provides reference g

Capture screenshots of the desktop or specific applications, with options for saving locations and modes.

Capture conversations and decisions into structured, linkable Notion pages for documentation and knowledge reuse. \n \n Supports six content types: decisions, how-to guides, FAQs, wiki entries, learning notes, and documentation pages, each with dedicated database templates and schemas. \n Workflow includes search and fetch of existing Notion pages to avoid duplication and establish proper linking and relations. \n Requires Notion MCP connection; includes setup steps for OAuth login and remote MC

Help the user quickly capture ideas, thoughts, meeting insights, reading annotations, and any fleeting information into their personal Yuque knowledge base with minimal friction.

Systematic troubleshooting for AVFoundation camera issues: frozen preview, wrong rotation, slow capture, session interruptions, and permission problems.

Central coordinator for capture data flow.

Guides you through implementing camera capture: session setup, photo capture, video recording, responsive capture UX, rotation handling, and session lifecycle management.

Transforms conversations, discussions, and insights into structured documentation in your Notion workspace. Captures knowledge from chat context, formats it appropriately, and saves it to the right location with proper organization and linking.

Store and manage API response test fixtures for provider parsing validation. \n \n Fixtures are organized in __fixtures__ subfolders within provider packages, using naming conventions documented in existing examples \n Supports two testing patterns: generateText (log raw response to console and copy into fixture) and streamText (use includeRawChunks and saveRawChunks helper to capture streaming chunks) \n Recommends storing true provider responses unless size constraints require semantic-preserv