02-sops

rdco website polish workflow

Mon May 04 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·sop ·status: active
workflowdesign-pipelinecoo-orchestrationskill-compositionteam-of-specialists

RDCO website-build-and-polish workflow (reusable pipeline)

Founder direction 2026-05-05 19:55 ET: “You need to be thinking like a COO. What’s the operational workflow? What specialists or specialized skills do we need to achieve the best result from that workflow? What are the skills we have, which need to be developed, adapted or improved? how do they sequence to produce the outcome? It doesn’t all have to be on you, but I do need you to plan out the solution and own the team that delivers it.”

This SOP is the COO-mode plan: end-to-end workflow for building / polishing any RDCO-owned web surface, with explicit skill assignment per stage, owner assigned to each step, and gap-flagging where a step has no current specialist.

The 12-stage workflow

#StageOwner (specialist / skill)Status
1Positioning brief (ICP, value prop, hero hook, CTA)RDCO COO (me, direct) - distill founder direction + relevant L5/Naval/sector evidencealways-on
2Design-reference scan (5-7 URL shortlist with steal-targets)mcp__mobbin__search_screens queries against Mobbin, parent COO synthesisOPERATIONAL (installed 2026-05-05)
3Brand-spec interpretation (palette, type, voice rules per surface)~/.claude/skills/ray-data-co-design/ umbrella + child skills (sanity-check-design, mac-pack-design, squarely-design, hq-design)partial: MAC needs its own child design spec OR explicit decision to inherit from umbrella
4Build implementation (Astro + CF Pages scaffolding, components, copy)~/.claude/skills/build-landing-page/ OR ~/.claude/skills/build-project/ OR frontend-design plugin specialist (depending on scope)OPERATIONAL but underused; MAC v0 went through ad-hoc subagent instead of build-landing-page skill
5Component creative production (hero, sections, illustrations, forms)frontend-design:frontend-design plugin specialist - “avoids generic AI aesthetics”OPERATIONAL but unused so far
6Animation / motion layer (hero animations, scroll reveals, micro-interactions)animation-components:* plugins (motion-framer, animejs, scroll-reveal-libraries, react-spring-physics, lottie-animations)OPERATIONAL but unused so far
7Performance audit (Core Web Vitals, render-blocking, accessibility)cloudflare:web-perf plugin specialistOPERATIONAL but unused so far
8Design critique against the founder’s taste synthesis~/.claude/skills/design-critic/ - autonomous critic that scores any RDCO surface BEFORE iterations reach the founderOPERATIONAL but unused for MAC v0
9Critic iteration loop (feedback -> rebuild -> re-critique until PASS)composition: design-critic + frontend-design in a loop, COO orchestratespartially exists in the build-landing-page skill’s “four-layer review loop”
10A/B variant generation (3 distinctive variants for founder visual pick)GAP - no current specialist; could compose frontend-design + design-criticGAP
11Marketing-copy iteration (sales-page rhythm, hook-density, CTA conversion)GAP - exists for newsletter (draft-review, voice-match) but not for landing-page sales copyGAP
12Deploy + monitor (Cloudflare Pages, env vars, DNS, observability)cloudflare:cloudflare + wrangler skills + manual env configOPERATIONAL

Existing skill inventory for this pipeline

What we have that I have NOT been using fully (this is the IC-mode honest read):

Design + creative

Plugin specialists (claude-plugins-official + addons)

Tools

Gaps to develop

Gap 1: A/B variant generation skill

What’s missing: ability to spin up 3 distinctive design variants of a hero section (or full page) for founder visual pick, using the design-critic as a quality gate per variant.

Composition: would chain frontend-design (3 variants in parallel) + design-critic (per-variant PASS/ITERATE/SCRAP verdict) + COO (final pick + reasoning).

Build cost: medium. Could ship as ~/.claude/skills/design-variants/SKILL.md in 2-3 hours.

Gap 2: Marketing-copy iteration skill

What’s missing: landing-page-sales-copy iteration skill. We have draft-review and voice-match for newsletter copy (Sanity Check shape), but landing pages need different rhythm (hook density, scannable structure, scroll-pacing, CTA conversion). The MAC anchor article was a Substack-style essay re-sourced for the page, but landing-page copy needs its own iteration discipline.

Composition: new skill ~/.claude/skills/landing-copy-review/ that scores against landing-page-specific patterns (Justin Jackson’s writing-for-conversion principles, Amy Hoy’s “feature -> benefit -> outcome” ladder, etc.). Could pair with voice-match for founder voice consistency.

Build cost: medium. 3-4 hours for the skill spec + rule corpus.

Gap 3: Asset-generation orchestration skill

What’s missing: when a design needs custom illustrations / hero images / scene videos, we have the individual generators (xAI, OpenAI, Kling, Seedance, HeyGen, ray-mascot-anim) but no orchestrator skill that takes a creative brief, picks the right generator(s), produces variants, and feeds back into the design pipeline.

Composition: new skill ~/.claude/skills/asset-orchestrator/ that maps creative brief -> generator choice -> variant production -> design-critic vetting.

Build cost: medium. 3-4 hours.

The MAC v0 polish team-of-specialists (concrete next dispatch)

Applying the workflow to the MAC v0 polish task right now, here’s the team I’d compose. Each is a sub-agent dispatched in sequence (some parallel where independent):

Round 1: Critique baseline (parallel, 1 sub-agent)

Round 2: Polish iteration (sequential, 1 sub-agent)

Round 3: Re-critique + perf (parallel, 2 sub-agents)

Round 4: Deploy preview + founder visual pick

ETA: 60-90 min for all 4 rounds.

What I OWN as the COO going forward

  1. Workflow design - this doc, kept current as gaps fill.
  2. Specialist orchestration - dispatch the right sub-agent at the right stage; don’t try to do their work myself.
  3. Quality gates - design-critic MUST run before founder sees a variant; perf MUST be checked before promotion to production; em-dash + brand-spec compliance audited silently per the verify-action rules.
  4. Decision surface to founder - founder sees only the PASS-grade output + the 1-3 ripe decisions, not the 4-stage rubble.
  5. Gap registry - this doc tracks where the workflow has missing specialists; the gap-fill work is itself queueable to /check-board as Ray-Medium tasks.

What the founder OWNS

  1. Strategic direction - ICP + value prop + brand boundary calls (e.g., “MAC for the 16% manager-data-lead, not generic IC”)
  2. Visual taste calibration - final pick when 3 variants reach PASS-grade
  3. Domain + payment commitments - registrar purchases, Cloudflare DNS, env-var setting
  4. Quality bar overrides - if the design-critic PASSes something he hates, his override is the higher signal

Cross-references