editorbridge-editor-safety

name	editorbridge-editor-safety
description	Choose safe EditorBridge automation modes for MarkEdit, Textastic, TextEdit, and iA Writer.

EditorBridge Editor Safety

Use this skill when deciding how to automate a supported GUI editor through EditorBridge.

Start with editor_check_permissions and editor_discover if permission and capability status are not already known. If Accessibility is not trusted, use editor_request_accessibility or editor_open_accessibility_settings and wait for the user to grant access before attempting AX-backed operations. Then prefer the smallest operation that satisfies the user request.

Editor guidance:

• MarkEdit: use the markedit adapter for agentic workflows. Snapshot before any source or whole-buffer mutation because writes can touch disk immediately.
• Textastic: use the textastic adapter for surgical range workflows through Accessibility. Prefer editor_select_range plus editor_read_selection before replacement.
• TextEdit: use the textedit adapter as a generic baseline. Confirm plain-text behavior before treating rich-text documents as Markdown.
• iA Writer: use the ia-writer adapter for surgical workflows. Treat scripted text writes as live-buffer mutations that may autosave after a delay.

Safety rules:

1. Prefer selection operations over document-wide operations.
2. Require snapshots for whole-buffer writes and patches.
3. Stop on unsupported capabilities instead of inventing an automation fallback.
4. Verify after mutation by reading the selection or document again.
5. Use undo or snapshot restore only when the target editor and document are still unambiguous.