faq ▸ straight answers

No. The skill is plain SKILL.md + templates your agent reads. Nothing runs on someone else's server. The only third-party services are ones YOU authorize: Cloudflare (deploy + D1), Google Search Console verification, GitHub.

Never. The pipeline drafts everything — thread, Discord intro, forum posts, PH pack — and leaves the posting to you with copy-paste-ready files and etiquette rules. You keep the keyboard.

No. The ads phase generates creative images and a copy-variant grid with a ramp plan. Launching campaigns with real spend is always your manual act.

READMEs: the pipeline drafts a candidate and shows a git diff — existing content ships only when you approve. An existing site becomes the deploy target instead of a new page. Existing marketing/plan.md means interview is skipped on later runs.

Any of OpenCode, Claude Code, Codex — the installer writes to all three discovery trees. OpenCode got the deepest polish as primary dev target, but all three run the same 9 phases.

Delegated to the HyperFrames skill: composition from your pillars, 15–30s, music bed resolved via media-use, voiceover by provider and voice you picked at interview (Cartesia by default), rendered as MP4 + README-friendly GIF. No tool? A static creative set is the fallback.

The brief asked for it — the product is terminal-native, so the aesthetics live in the same box-drawing alphabet. Also a cleaner meta-point: nothing here needed a marketing agency, it came out of phase 3.

Gates: first deploy, repo creation, push, README replacement. Real-world, hard-to-reverse actions need an explicit yes. After the first approval, cheap redeploys stop asking.

Yes — the interview covers software/tool · game · content/media · physical product · service, and templates like JSON-LD schema and channel playbooks adapt per type.

Voices: this repo IS the roadmap — /marketing on itself. Every launch artifact here (plan, page, video, posts) is also the proof the pipeline works.