What problem does it solve? Integrating the react-reason-editor package is error-prone: it ships two editor engines (Plate by default, Tiptap for unported features), 59 extensions with per-extension subpath exports, a required sidebar injection, and a schema that is fixed at mount. This Skill guides you through picking the right entry point, configuring extensions, and avoiding the common pitfalls. ## Core Features & Use Cases - Entry point selection: Choose between ReasonDocs (full document app), editor-kit (host-owned lifecycle), NovelEditor/RichTextProvider, or single-extension subpath imports. - Extension and configuration management: Add extensions via the plugin registry, rebuild the schema with rebuildKey, manage EditorConfig persisted in localStorage, and switch KaTeX/Mermaid between CDN and bundled loading. - Troubleshooting and collaboration: Diagnose unstyled editors, SSR hydration errors, and engine mismatches, and wire Yjs/Hocuspocus collaborative editing. - Use Case: You are embedding the editor in a VS Code custom editor and your new extension appears to do nothing — the Skill explains that the schema is fixed at mount and you must pass a new rebuildKey. ## Quick Start Ask how to embed react-reason-editor in your host app with a custom extension set and toolbar.
