Talking to Claude Code

Principle#

No skill names, no command names. You state the task; the agent picks the skill, asks for missing pieces, and does the work.

The main rule: if you are not sure whether a request is allowed, ask. The worst case is that operation does not exist, talk to a developer. In most cases the answer is got it and the work is done.

What Claude Code can do#

Create a page from scratch.

create /contact — heading 'Get in touch', a form with name, email, and message, and our address below.

The agent picks the right sections, fills the copy, opens the draft in preview.

Build a page from a free-form brief.

make a team page — three staff cards with photo, name, role, short bio. A short heading on top, a join-us call to action at the bottom.

The agent decides which sections to use (TeamGrid, Hero, CTA) and assembles the page.

Rewrite a section or a whole page.

rewrite the hero on the home page — focus on speed, not price.

make /about shorter and friendlier — the tone is too formal.

Replace one section with another.

remove the pricing block on the home page and put a five-question FAQ about shipping in its place.

Reorder sections.

move testimonials above pricing on /pricing.

Publish and roll back.

publish the team page draft.

roll /pricing back to before today's edits.

Unpublish.

take /old-promo off the site but do not delete it — we might need it later.

How to phrase well#

• Name the page. On the home page, /pricing, the team page — any of these works. Do not say that page.
• State a concrete result. Cut to two paragraphs beats improve. Switch to second person, drop the word 'client' beats make it warmer.
• If you are editing existing copy, say what is wrong. Too long, too formal, no call to action at the end.
• Do not be afraid of big tasks. The agent handles create a blog section with three posts about X, Y, Z as easily as fix a typo.

What the agent does on its own#

• Creates or updates a draft. The published version is not touched without your command.
• Snapshots the previous version before publishing — rollback is always available.
• Asks for confirmation before deleting a page or making a sweeping change.
• Tells you if the request is not one of the known operations.

What the agent will not do#

• Change the design. Colours, fonts, and section layout are a developer's job. If a whole section looks wrong, that is a developer ticket.
• Invent new section types silently. If the task needs a section type that does not exist in the project (for example, you have no video block), the agent says so.
• Touch the live site directly. The agent works with drafts and published files in the project. Changes reach visitors only after deploy — see Publishing and deploy.

If something goes wrong#

Every publish stores a snapshot of the previous version. Say: roll /name back to the previous version. The agent shows the snapshot list and asks which one to restore.

If you dislike an edit before publishing, it is still just a draft. Say undo the last changes on /name or return the hero to what it was before your edit.