Stop briefing.
Start building.

I'm starting a draft for a new campaign:
- Slug (URL-friendly): [LIKE earning-season-berlin OR mini-app-bounty]
- Hero eyebrow: [SHORT-CAPS-LINE, e.g. "Earning Season · Berlin"]
- Hero headline: [ONE-PUNCHY-LINE in Gnosis voice (Fork x, Own y)]
- Theme: [ONE-SENTENCE. What changes for the visitor]
- Audience: [WHO. e.g. "Berlin neobank users curious about Gnosis Card"]
- Briefing link: [NOTION-OR-FIGMA-URL if you have one, otherwise skip]

Please:
1. Read website/CLAUDE.md and website/src/pages/drafts/CLAUDE.md.
2. Copy _starter-template.astro to a new draft using my slug.
3. Update DraftPage props (title, owner=ME, briefingUrl, status=sketch).
4. Replace the hero with my eyebrow + headline.
5. Use existing FeatureCard / PlanetHero / Button components.
6. Open a PR.

Stay in drafts. Don't promote to production.

When done, tell me the localhost URL where I can see this change
(it will be http://localhost:4321/drafts/[SLUG] for that draft).
If the dev server is not running, tell me to run `npm run dev` first.

In src/pages/drafts/[SLUG].astro, add a new section between the
[CURRENT-SECTION] and the [NEXT-SECTION].

The new section is: [DESCRIBE, e.g. "a row of three feature cards
about earning, creating, and building"].

Use existing components from src/components/ if any fit. List them
for me first and pick the closest match. If nothing fits, build it
inline in the draft (don't add new files to src/components/).

When done, tell me the localhost URL where I can see this change
(it will be http://localhost:4321/drafts/[SLUG] for that draft).
If the dev server is not running, tell me to run `npm run dev` first.

My one-line briefing: "[ONE SENTENCE. Examples:
  • Recruit Berlin coffee shops to accept CRC.
  • Landing for the next Earning Season cohort.
  • Mini App Bounty pitched to Polymarket builders.
  • Gnosis Pay vs Revolut, framed for the no-crypto crowd.]"

Please make a fast first-pass draft from this:
1. Invent a slug, hero eyebrow, hero headline, and 3 feature blocks
   that fit my one-liner. Use the brand voice (Satoshi x Deadpool,
   confident, irreverent, on-message).
2. Scaffold the draft following the starter template.
3. Add HTML comments inside the file marking which parts you
   invented (so I can see your assumptions and override them).
4. Open a PR titled "Draft v0: [SLUG]" so I know this is your
   first guess, not a final version.

Stay in drafts.

When done, tell me the localhost URL where I can see this change
(it will be http://localhost:4321/drafts/[SLUG] for that draft).
If the dev server is not running, tell me to run `npm run dev` first.

I'm describing a Figma mock. Build a draft that approximates it
using existing canonical components.

The mock has, top to bottom:
- [DESCRIBE-SECTION-1: e.g. "a hero with a centered headline and CTA"]
- [DESCRIBE-SECTION-2: e.g. "a 2-column block with text on the left and an image on the right"]
- [DESCRIBE-SECTION-3: e.g. "three cards in a row"]
- [DESCRIBE-SECTION-4: e.g. "a quote / testimonial"]
- [DESCRIBE-SECTION-5: e.g. "a final CTA on a dark band"]

Please:
1. Match each described section to an existing component when possible
   (FeatureBlock, FeatureCard, PlanetHero, FinalCta, etc.).
2. Where no component fits, invent inline within the draft and tell me.
3. Use placeholder copy (Lorem-ipsum-but-on-brand) so I can read the
   layout without copy distractions.
4. Open a PR.

When done, tell me the localhost URL where I can see this change
(it will be http://localhost:4321/drafts/[SLUG] for that draft).
If the dev server is not running, tell me to run `npm run dev` first.

I want to use a component pattern that doesn't exist in
src/components/ yet. The pattern is described / linked here:
[PASTE LINK or DESCRIPTION, e.g. "the pricing table from
ui.shadcn.com/blocks/pricing-1" or "the bento grid from
magicui.design/docs/components/bento-grid"]

Please:
1. Fetch / read the source if it's a URL.
2. Summarize the structural + visual idea in 3 bullets.
3. Check src/components/ for anything that already gets close.
4. If nothing close exists, port the pattern into my draft at
   src/pages/drafts/[SLUG].astro inline:
   - Astro idiom (HTML + scoped CSS, minimal JS)
   - Use Gnosis tokens (--space-*, brand colours, motion)
   - Don't copy their colours/copy verbatim, translate
   - Drop any framework dependencies (no React-only patterns)
5. Tell me whether this looks like a strong candidate for
   promotion to a shared component.

When done, tell me the localhost URL.

I want to update the copy on the draft at
src/pages/drafts/[SLUG].astro.

Specifically:
- Change [WHAT-IT-CURRENTLY-SAYS] to [WHAT-IT-SHOULD-SAY]
- [ANY-OTHER-CHANGES]

Keep all the structure and components the same, just update the text.
After: summarize what you changed and remind me to open a PR.

When done, tell me the localhost URL where I can see this change
(it will be http://localhost:4321/drafts/[SLUG] for that draft).
If the dev server is not running, tell me to run `npm run dev` first.

In src/pages/drafts/[SLUG].astro, change the hero title to:

  "[NEW HEADLINE HERE]"

Keep everything else the same. After: tell me what the live URL will
be once I push, so I can share it with the team.

When done, tell me the localhost URL where I can see this change
(it will be http://localhost:4321/drafts/[SLUG] for that draft).
If the dev server is not running, tell me to run `npm run dev` first.

Look up the homepage of [BRAND, e.g. Linear / Stripe / Monzo /
Notion / Apple / Revolut / Wise / Coinbase / Phantom / Arc Browser].
Read its hero + first 3 sections. Then:

1. Summarize in 3 bullets what makes their headline writing
   distinctive (rhythm, length, pronoun usage, tense, attitude).

2. Generate 5 alternate hero headlines for my draft at
   src/pages/drafts/[SLUG].astro that BORROW that distinctive
   feeling but TRANSLATE through the Gnosis voice (Satoshi x
   Deadpool, confident, irreverent, mother-brand verb "Fork").

3. Brief on each:
   - Headline 1: [your version]. Borrowing: [what specifically].
   - Headline 2: ...
   ...up to 5.

Don't change the file yet. I'll pick one.

Look up [BRAND]'s [PAGE, e.g. "homepage" or "pricing page" or
"feature page"]. Study the [SECTION, e.g. "hero" or "feature
comparison" or "testimonial section"].

Then on my draft at src/pages/drafts/[SLUG].astro, REMIX that
section's structural idea into a Gnosis-tokenized version:

1. Summarize the structural idea in 3 bullets (what's the layout
   doing? what's the visual hierarchy? what's the motion / hover?).
2. Translate it through the Gnosis brand:
   - Use our tokens (colours, spacing, motion) only.
   - Use Gnosis voice for any new copy.
   - Use our existing components when they map cleanly.
   - Invent inline only where their structure has no equivalent.
3. Replace [the relevant section] in my draft.

Important: this should NOT look like an imitation. The reader
should think "fresh," not "they're copying X." If you find
yourself replicating their colours or copy, stop and re-translate.

When done, tell me the localhost URL where I can see this change.

The draft at src/pages/drafts/[SLUG].astro needs a German version.

Please:
1. Read existing de/ copy files for tone reference.
2. Create src/copy/drafts/de/[SLUG].md mirroring src/copy/drafts/en/[SLUG].md.
3. Translate all user-facing copy to German.
4. Keep brand-specific terms in English: Gnosis, Circles, CRC, Visa,
   Earning Season, tier names (Top Earner, Power Earner, etc.).
5. Use commas as decimal separators (1,5 not 1.5).
6. No long dashes. Use commas, periods, or middle-dot (·).

When done, tell me the localhost URL where I can see this change
(it will be http://localhost:4321/drafts/[SLUG] for that draft).
If the dev server is not running, tell me to run `npm run dev` first.

My draft at src/pages/drafts/[SLUG].astro is ready for stakeholder
review and possibly production.

Please:
1. Update the DraftPage status from "sketch" / "review" to "approved".
2. Run npm run check and fix anything that fails (with me reviewing
   each fix before applying).
3. Add a one-line summary at the top of the file describing what
   needs to happen for promotion (URLs to add to the registry, copy
   to move to production locales, etc.).
4. Open a PR titled "Draft ready for review: [CAMPAIGN NAME]" and
   tag the designer.

Don't promote yourself. Wait for designer approval.

Read the draft at src/pages/drafts/[SLUG].astro and roast it for me.

Specifically:
1. What's the weakest line of copy? (One pick, with reasoning.)
2. Which section feels most generic or interchangeable?
3. Where does the energy drop?
4. Is the CTA earned by the end of the page?
5. Does the headline survive a 3-second skim?
6. What's something a competitor brand could say identically?

Be direct. Don't soften. Don't fix anything yet. I want a brutal
read first, then I'll tell you which parts to rework.

Audit src/pages/drafts/[SLUG].astro for mobile (≤480px) issues.

Please:
1. List every place where text might overflow, sizing breaks, or
   layout fights itself on a 375px viewport.
2. For each issue, propose a fix using existing tokens
   (--space-*, clamp(), media queries), no new hardcoded breakpoints.
3. Don't apply fixes yet. Show me the list first; I'll pick which
   ones to apply.

After: tell me what's currently fine on mobile too, I want to
know what I don't have to worry about.

I'm stuck. Please diagnose:

1. Run npm run check and tell me what (if anything) fails, in plain
   English.
2. If npm run build also fails, run it and surface the error.
3. Look at git status and tell me what's uncommitted.
4. If you see something I should revert, tell me before doing it.

I want to understand what went wrong, not just have it fixed silently.

List every component in src/components/ with:
- One-line description of what it does
- A code example of how to use it (props + slot if any)
- A link to where it's used in production (which page)

Format as a table. I want a quick reference for what I can compose
in my drafts without inventing anything new.

In the last 3-5 turns, you made changes I don't fully understand.

Please:
1. Summarize, in plain English, every file you changed and why.
2. For each change, tell me one alternative you considered but
   rejected, and why.
3. Tell me if any of the changes have side effects I should know
   about (e.g. affects another page, requires a new env var,
   touches the link registry).
4. Tell me what would happen if I git-revert the last commit,
   what gets lost and what stays.

I want to understand the system, not just the keystrokes.

I want to undo my last change without breaking anything else.

Please:
1. Show me what's currently in git status / git diff.
2. Tell me which files I'd need to revert to roll back ONLY my
   recent change (keeping everyone else's work intact).
3. Walk me through the safest revert path: cherry-pick a revert
   commit? git restore individual files? git reset?
4. Don't run any destructive commands. Show me the commands you'd
   run, then wait for me to say "go" before executing.

I'd rather take 5 extra minutes and get this right than wreck
someone else's work.