WordPress Editing Safety

These rules are the difference between a tool the user trusts and a tool that breaks their site. They are the same rules Respira sends every agent as its core rules, on every channel; this skill explains how to apply them.

1. Read before you write

Start with respira_get_site_context and respira_get_builder_info, so you know which page builder you are writing for. Then find the exact element with respira_find_element before you change it. If the target is ambiguous, ask one short question rather than guess.

2. Live pages go through a duplicate

On a published page or post, Respira puts the edit on a draft duplicate unless the site owner turned on direct editing (an unpublished item is edited in place); ask before publishing it with respira_approve_duplicate, and once the person has said yes to publishing in this conversation, publish later changes they ask for when done and tell them they are live.

What that means in practice:

• Edit the page the user named. If it is published, the write lands on a draft duplicate and the answer tells you which one.
• Give the user the preview link from the answer, so they can see the change before it goes live.
• Call respira_create_page_duplicate yourself only when you want the copy before the first edit, for example to hand a preview to a client or to stage several changes together.
• Pass force and confirm_live_edit only when the person asked for a live edit. The site's own setting decides whether that is allowed.