Talking to your developer

Write like you would to a skilled developer you trust. PressHelm looks at your site first, asks when something is unclear, and shows its work.

How to ask#

• Say the goal, not the steps. “Make the contact page friendlier and add a map” works better than a list of block changes.
• Name the place. A page title, a URL, or “the homepage hero” helps it find the right spot fast.
• Show it. Send a screenshot or a photo; it understands images.
• Bigger jobs are fine. It will propose a plan you approve once (see Plans).

Looking for ideas? Browse the Playbook: more than 2,000 plays you can copy and send.

What happens when you ask#

1. It reads first. Reads (pages, settings, logs, products) run at once and change nothing.
2. It asks when it matters. Changes go through your approval unless your rules let small, safe ones run at once.
3. It checks. After every change the site is tested; a breaking change is undone automatically.
4. It reports. A receipt lists what changed, taken from PressHelm’s own records (not from the AI’s memory), with Undo buttons.

Memory#

PressHelm can remember notes you want it to keep, for one site or all of them: your brand colours, your tone of voice, “never touch the checkout page”. Just say “remember that…”. Ask “what do you remember?” to see the notes, and “forget …” to remove one.

Starting fresh#

Send /new to start a new conversation (useful when you switch topics). Send /stop to stop what it is doing right now. See all commands.