Enter the access code to continue.
Copy-paste recipes for the jobs you'll do most, how to prompt so the work comes out good, the features worth knowing, and the guardrails that keep everything safe.
👋 New to all this? If words like "branch", "commit" or "deploy" mean nothing to you, read the 2-minute plain-English explainer in SOP 01 first. It covers everything the recipes below assume. Read it →Ready-to-use prompts
Steal these. Swap the client name and details for yours. Each one already tells Claude the client, the goal and the format — which is exactly what makes it come out good.
🆕 Build a new landing page
Starting a page from scratch for a client.
✏️ Update an existing client page
Changing something on a page that already exists.
💡 Not sure which file it is? Just ask: "Which file is Wiltshire's landing page?" — Claude will find it before changing anything.
✉️ Create a welcome email
Drafting client-facing email copy.
🔒 Something you can't edit (a live system)
Systems with logins/databases — like the boiler quote portal — are locked to Tom.
Live apps and portals (the Gas Tech boiler quote system, lead forms wired to a database, anything with client logins) are not in your Team Vault — they're Tom-only by design. You can't and shouldn't try to edit these. Instead:
The #1 skill
Claude is only as good as what you ask. A good prompt gives it four things: the client, the goal, who it's for, and the format. You won't nail it in one go — that's normal. Get a first version, then refine: "make it shorter", "more casual", "add a section on pricing".
The features worth knowing
Drag in anything that helps — a brand logo, a screenshot of a competitor's page, a PDF of the client's offer, a photo. Claude will use it. "Match the style of this screenshot" works great.
Type / to see built-in tools (e.g. /dataviz for charts). You mostly won't need these — plain English does 95% of the work — but they're there.
For anything bigger, ask "plan it first, don't build yet." Claude lays out the steps; you check it, then say go. Stops it running off in the wrong direction.
Claude asks permission before some steps. Approve normal build & edit steps. "Auto" lets it run a run of steps without asking each time — fine once you trust the task; keep it off when you're unsure.
What you can do freely — and what waits for Tom
The only two phrases to remember
| When | Type this | What happens |
|---|---|---|
| You've finished a task | attain-complete | Logged as a completion Tom can see. |
| It needs Tom's review | attain-review | Added to Tom's review queue with your note. |
Add a few words after either one, e.g. attain-review wiltshire landing page — check the new headline. Everything else is captured automatically — you don't have to report anything else.
Why you can relax and just build
Everything you do is saved with your name and the exact time, and every version is kept forever. If a mistake happens — wrong file, deleted something, a change that broke a page — it's recoverable in seconds, and Tom can always roll back. This isn't there to watch over you; it's there so you can experiment and move fast without fear. Build boldly. Preview. Hand it to Tom. That's the whole job.
Attain Digital · Team SOP 03 of 03 · a living document — ask Tom if anything's unclear.