Day-to-day iteration

The hard part is done. Day-to-day, you’ll mostly be editing content — your bio, your writing — not the design. This chapter is the loop you’ll use repeatedly.

The mental model

There are two layers and they don’t interact:

99% of your iteration is the content layer.

Editing the bio

Paste into Claude Code:

Open content/shell.yaml. Help me tighten the bio paragraph. The audience is recruiters and senior peers evaluating me for executive roles. Keep it to 3 to 4 sentences. Show me 3 versions and let me pick.

Pick the version you like. Ask Claude to update the file with your choice.

Copy review through Nexus-Council

Before you publish a meaningful change to your bio (or a new article), run a quick expert review:

Use the nexus-council MCP. Run a copy review with these personas:
- Brand Strategist
- Conversion Copywriter
- Connected Intelligence Advisor

Inputs:
- The draft text I want to review (paste below).
- My role goal: executive job search, audience is recruiters and senior peers.
- My tone tags: [paste from content/shell.yaml]

Each persona should:
1. Score the draft 1 to 5 on tone, clarity, and credibility.
2. Note one specific phrase that lands.
3. Note one specific phrase that doesn't.
4. Suggest a sharper version of any sentence they'd change.

Then synthesize the three persona views into a short summary and a single recommended revision.

Draft to review:
---
[paste your draft here]
---

Read the synthesis. Take what’s useful, ignore what isn’t. Update the file.

Adding an article

Create a new file in content/articles/ named YYYY-MM-DD-short-slug.md. Paste into Claude Code:

Create a new article at content/articles/2026-MM-DD-<topic>.md. Frontmatter: title, date (today’s date), summary in one sentence. Body: I’ll write the draft, but help me outline 5 beats first based on this idea: [your idea]. Then I’ll fill in each beat.

Iterate on the draft. When it’s ready, run the same copy-review prompt above.

Push and deploy

Paste into Claude Code:

Stage and commit my changes with a clear message. Push to GitHub. Then run npm run build and wrangler pages deploy dist --project-name=megmude-site --branch=main --commit-dirty=true.

Within ~30 seconds the update is live at megmude.com.

When to spawn variants again

If you want a visual refresh — new typography, new color, new layout — go back to chapter 04 and spawn a new round of variants. Your content stays put through the redesign.

Don’t run variants for content changes. They’re expensive (each variant is a parallel agent run) and they don’t help with copy.