Inspect a page's block structure before you edit it

The worst edits happen when you do not know how a page is put together. You change a heading, and it turns out that heading lived in a synced block used on nine other pages, so now all nine are wrong. Or you spend ten minutes hunting for a paragraph in the editor that is actually being pulled in from a reusable block you forgot existed.

This is the look-before-you-touch prompt. It reads the page, maps every block in order, and opens any shared blocks so you can see what an edit would really affect. It cannot change a thing.

Before I edit this, map out how the page is built. Read only, change nothing.

The page is [the About page, id 42]. Read it and give me an outline of its
blocks from top to bottom in the order they appear. Wherever a synced
(reusable) block is pulled in instead of written inline, mark it clearly.

For each synced block you find, open it and tell me its title and a short
summary of what is inside, so I know that editing it would change every page
that uses it. Finish with a heads-up on anything fragile: a shared block I
could edit by accident, or a section that is really coming from somewhere else.

Why this is safe to run

Every ability behind this prompt is a read. Pulling the page, listing the synced blocks, and opening each one writes nothing, so the worst case is that a read you left switched off quietly returns nothing. There is no approval step because there is nothing to approve: no value is ever saved.

The payoff is knowing what is shared before you start. A synced block edit is not local, it lands on every page that uses that block, and this is the one prompt that tells you which parts of the page are wired together that way. Read it first, then edit with your eyes open.

Already connected? Skip the paste. Ask your agent for the “inspect a page’s block structure” recipe, or just ask it to outline how a page is built, and it runs the same reads on your own install.