office-tiptap-richtext

What problem does it solve?

Prevents CT_office manual editor content from being lost, corrupted, or malformed when saving, converting, migrating, or rendering Tiptap-based rich-text documents.

Core Features & Use Cases

• Preserves the existing Tiptap document structure: keeps the stored Tiptap JSON/document format intact instead of guessing or re-encoding.
• Guards against invalid writes: blocks empty strings, invalid JSON, and partial documents from being persisted.
• Supports safe migration and UI changes: validates by reading back, checking editor flows (save/load/preview/cancel), and defers migration until backup and verification are confirmed.
• Use case: when a developer updates the manual editor UI or introduces conversion logic, this skill helps ensure previously saved manual bodies still open and render correctly after refresh.

Quick Start

Use the office-tiptap-richtext skill to review the CT_office manual editor save/load and conversion logic before changing anything that could affect stored Tiptap content.