Make Packs
Packs for producing visual, written, and branded artifacts — Media, WriteStory, CinematicLanding, DesignSystem, Brand.
Five Packs cover the production surface. Media ships pixels, frames, and audio. WriteStory writes fiction as fiction, not as marketing copy with characters. CinematicLanding upgrades a landing page through structured tiers. DesignSystem pins the design tokens that make every subsequent UI generation deterministic. Brand sits upstream of all of them — research, strategy, and code-shaped output the rest of the Pack catalog can consume.
Media
What it is — one front door to 5 image models (Flux, Nano Banana, GPT-Image-1, Midjourney, Recraft SVG), Remotion video production, ElevenLabs speech and voice cloning, 6 AI video models (Seedance, Kling, Veo, Runway, Grok, Wan), D3 dashboards, and sub-skills for background removal, face swap, emoji, music, upscale, and image restoration. 20+ workflows behind a single dispatcher.
When to use it — any time the artifact is visual, audio, or video. "create a header image for my blog post," "narrate this essay in PT-BR," "make a podcast intro with music," "upscale this photo 4x," "remove the background."
Example outcome — you ask for a header image for an essay on AI agents. Media routes to the Art essay workflow, picks Midjourney for the charcoal aesthetic, generates, and drops the final file into ~/Downloads/ for preview. Swap the request to "narrate this in PT-BR" and the same Pack routes to ElevenLabs instead.
WriteStory
What it is — a fiction system built on Will Storr's storytelling science and Mark Forsyth's rhetorical figures. Every story is constructed across seven simultaneous dimensions: meaning, character change, plot, mystery, world, relationships, and prose. A story weak in any one layer feels off even when readers can't articulate why.
When you'd reach for it
You have a novel, not a blog post. Chapter 3 needs the mentor confrontation, and you want the sacred-flaw arc intact, the mystery questions planted, the prose carrying rhetorical figures at the sentence level — not an LLM-shaped "emotional beat."
Example outcome — you ask for chapter 3 and WriteStory delivers it with the sacred-flaw arc locked against the story bible, a cause-and-effect plot chain traceable to chapter 2's setups, planted mystery questions that pay off in chapter 5, and prose with Forsyth figures worked into the sentence structure. Consistency checks against the seven layers run before the chapter is handed back.
CinematicLanding
What it is — a tiered landing-page delivery pipeline. Audit → PRD → Tier 1 (quick wins) → Tier 2 (scroll-driven storytelling with GSAP ScrollTrigger) → Tier 3 (WebGL, ambient sound, micro-animations). Ships concrete component patterns (ParticleField, CinematicSection) rather than vague delegation. Every tier passes typecheck and lint before handoff.
When to use it — upgrading an existing landing page, auditing one before a redesign, or building a new page to an Awwwards-level bar. Triggers: "audit my landing page," "build tier 2," "create a landing page PRD," "fix the section overlap."
Example outcome — you ask for Tier 2 on the hero and pricing sections. CinematicLanding ships GSAP ScrollTrigger animations, parallax reveals, theme-aware components that respect the project's DESIGN.md, and a typecheck-clean PR in one pass.
DesignSystem
What it is — an AI-native design system pinned to a DESIGN.md file at the project root. Semantic tokens in a three-layer architecture (option → decision → component) make UI generation deterministic — brand-primary always resolves to the same CSS variable, no hallucinated hex codes, no drift between components.
When you'd reach for it
Your generated components keep picking slightly different blues. Run Init, let DesignSystem write a DESIGN.md with OKLCH palettes and component blueprints, and every subsequent Skill("Media") or Skill("CinematicLanding") call reads from the same contract.
Example outcome — you run Init with "dark mode, blue primary, Inter font" and DesignSystem generates DESIGN.md with an OKLCH color palette, typography scale, spacing ramp, and component blueprints for buttons, cards, and forms. Every downstream UI generation reads that file first — which is the whole point.
Brand
What it is — a brand system that goes all the way from research to code. 9 parallel research agents across three provider types, a three-layer token architecture, StoryBrand messaging (character / problem / guide / plan / CTA), logo design, icon systems, and direct handoff to CinematicLanding. Brand-as-code, not brand-as-PDF — the output is theme.css, fonts.ts, stage-colors.ts, and motion-tokens.ts.
When to use it — any brand moment. Reverse-engineering a competitor's brand to understand it. Defining a brand for a new product. Designing a logo or icon system. Generating a BrandScript for a new launch.
Example outcome — you ask Brand to reverse-engineer stripe.com. Nine agents run in parallel, the Pack produces a three-layer token architecture, a BrandScript framing, and code artifacts ready to drop into a landing page. Hand the output to CinematicLanding and the landing page inherits the tokens directly.
Was this page helpful?