@stacksjs/defaults 0.75.109 → 0.75.110

package/ai/skills/stacks-marketing-influencer-marketing/references/ugc-creator-program.md

@@ -0,0 +1,91 @@
+# Volume UGC Creator Programs ("Tech UGC")
+
+A scaled version of the paid-influencer model where **content volume, not any creator's audience, is the asset**: an in-house network of creators posting native short-form from dedicated brand-affiliated accounts, at test volume. 10 creators posting 3×/day ≈ 900 organic tests in a 30-day campaign - against ~30 for a brand account posting daily. The economics claim from the program this is distilled from: ~$3.87 CPM vs ~$20 for Meta ads and ~$119 for micro-influencer placements (**vendor-supplied internal numbers - directional, not a benchmark**).
+
+Creators don't need existing audiences - discovery-based algorithms distribute on content, and follower count is irrelevant when posting from program accounts.
+
+## Compliance first - read before running any of this
+
+The playbook this distills went viral in 2026 (Playkit) and drew an immediate, correct public FTC callout. The system below keeps the operational craft and fixes the legal holes. Applying SKILL.md §4 to this motion specifically:
+
+- **Paid creator posts are ads.** Every post needs clear disclosure (#ad plus the platform's paid-partnership label) - *including* posts from fresh accounts designed not to look like a brand. "Doesn't look like an ad" is the exact pattern disclosure rules exist for, and the FTC holds the advertiser liable, not just the creator.
+- **Paid comments without disclosure are undisclosed endorsements.** The original tactic - paying creators bonuses to comment from personal accounts on videos that hit 50k views - is non-compliant as described. Compliant alternatives below.
+- **Honest beliefs only.** Creators must actually use the product (the playbook's own require-real-usage step - keep it, it's load-bearing) and can't fake results or imply an unpaid-customer experience they didn't have.
+- **Platform-policy risk is real too.** Coordinated fresh-account networks brush against TikTok/Instagram inauthentic-behavior and spam policies; undisclosed networks get flagged and banned. Disclosure labels and brand-affiliated bios *reduce* this risk.
+
+Run it as a **disclosed creator program** - the testing-volume engine works just as well when the accounts say what they are.
+
+## 1. Build the playbook before hiring anyone
+
+You cannot tell creators to "make it authentic and fun." Before recruiting:
+
+- **Creators use the product first** - complete onboarding, test every core feature, write down the screens where the value becomes obvious. Most teams skip this; don't.
+- **Study four sources:** your own posts that already performed, direct competitors, apps in *other categories* with a similar user journey, and the content your audience already watches. Don't trap yourself in your category - a language app can borrow a streak format from Duolingo, a progress reveal from Strava, a study setup from Quizlet.
+- **Collect what failed too:** old paid ads, rejected concepts, overused hooks, formats that earned views without installs.
+- **Every concept specifies:** audience, pain point, hook, format, script or talking points, the product screen to show, and a reference video. Knowing what must be made tells you who to hire.
+
+## 2. The four formats
+
+| Format | Share | What it is | Role |
+|---|---|---|---|
+| **Talking video** | ~70% | Creator talks to the camera like they're on FaceTime with a friend - open with a specific problem, product enters where it naturally fits the story, end with the result | The conversion workhorse |
+| **Wall-of-text** | - | Simple B-roll + a longer on-screen thought | Goes most viral, converts least; top-of-funnel and account warm-up |
+| **Slideshow** | - | Lists, screenshots, before/after sequences; first slide creates curiosity | Cheap volume; often AI-automatable |
+| **Hook-and-demo** | - | Short hook → feature → action on screen → result | Aging format (audiences have caught on) - needs a creative twist to perform now |
+
+Test the same idea across formats: it tells you whether the *idea* failed or just its presentation.
+
+## 3. Hiring: vet by trial, not portfolio
+
+- What matters: can they talk to a phone camera naturally, follow direction, make a script sound like their own words, and **match the persona in the playbook** (a study app, fertility app, and budgeting app need different creator profiles).
+- **Run a paid week-long trial** with real concepts from the playbook. Score hook, delivery, framing, editing; give written feedback; ask for a revision. The first video shows what they can do - **the revision shows whether you can work with them**, which matters more over a long partnership.
+- Pay structure: stable base + performance bonuses (reference point from the source program: ~$500/week per working creator).
+
+## 4. Accounts and warming
+
+Each creator runs dedicated per-brand TikTok/Instagram accounts - **with the brand affiliation in the bio and disclosure on the posts** (this is the compliance rewrite of the original "stealth new account" step; the algorithm benefits of a fresh, niche-trained account don't depend on hiding who runs it).
+
+Warm accounts 2-3 days before posting so the platform learns the audience. Daily warm-up checklist:
+
+- Scroll the niche 10-15 minutes
+- Watch 10+ relevant videos start to finish
+- Like 20-30 relevant posts
+- Leave 3-5 genuine comments
+- Follow no more than 5-10 relevant accounts
+
+Behave like a human - following 50 accounts at once and opening the app only to post looks automated because it is. Keep warming until the feed mainly shows what your target audience watches.
+
+## 5. Cadence and review
+
+- **3 posts/day per creator, ~2 hours apart**, captions and hashtags per the playbook.
+- **Every video is reviewed before posting:** submission → check against the playbook → written notes → revision → approval. Track brief, submission, feedback, approval, and results in one system.
+- Review for: hook, script, product screen, format, and anything that makes it feel like an ad (stiff delivery, overproduced editing, product introduced too early).
+- **Vague feedback = vague revisions.** "Make this more natural" is useless; "cut the first sentence, move the phone closer, say this line like you're complaining to a friend" is fixable.
+
+## 6. The conversion ladder (four touchpoints)
+
+One video doesn't do the whole job:
+
+1. **Name the product in the hook** without stopping to explain it.
+2. **Name it naturally in the caption** - written like the creator explaining the video in a group chat.
+3. **Engage the comments - compliantly.** The comment section is where converts self-identify. Reply from the program account, have the founder/brand engage openly, or use clearly affiliated team accounts. (Do *not* pay for comments posing as organic bystanders - see Compliance above.) Either way, mine comments as research.
+4. **Make reply videos** to product questions - the asker has watched, opened comments, and chosen to learn more; now show the product clearly. Highest-intent surface in the system.
+
+Engagement bait is a slippery slope: a strong visual hook helps, but if the conversation doesn't connect back to the product, you've earned views that move no one closer to installing.
+
+## 7. Iterate daily, judge in weeks
+
+- Review yesterday's videos every day: repeat, change, or stop. Don't wait for virality to learn.
+- **Judge by product questions, saves, shares, and install data - not views.** A low-view video with dozens of product questions beats a big one with an unrelated comment section.
+- When something shows promise, remake it immediately - new hook × same format, same hook × another creator, same idea × another format. **Change one major variable at a time.**
+- Reuse the exact language commenters use to describe their problem. Turn repeated questions into reply videos.
+- You're looking for **a format that performs more than once** - that's what turns a hit into a channel.
+- **Give it four weeks minimum.** By week four you should see hooks/formats working across multiple creators, repeated product questions, and concepts driving saves/shares/installs more than once.
+
+## 8. Costs and ownership
+
+Three requirements: creator pay, **one person who owns the program**, and a system for briefs/review/tracking. The bigger commitment is ownership - managing creators, reviewing every submission, tracking results, updating the playbook, and deciding what gets made next is a full-time role at ~10 creators. Hire it or contract it, but one person must own it.
+
+---
+
+*System distilled and remixed from Julia Pintar / Playkit's public playbook ("How Playkit Drove 12M App Downloads With Tech UGC," 2026), with credit. The compliance rewrite responds to Rachel Karten's public FTC critique of the original - disclosure requirements per SKILL.md §4 override any conflicting step of the source playbook. Economics figures are vendor-supplied.*

package/ai/skills/stacks-marketing-launch/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Corey Haines
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/ai/skills/stacks-marketing-launch/NOTICE.md

@@ -0,0 +1,13 @@
+# Source and license
+
+Adapted from [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills),
+revision [1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff](https://github.com/coreyhaines31/marketingskills/tree/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff),
+upstream skill `launch`, version 2.2.0.
+The original MIT copyright and permission notice is in [LICENSE](LICENSE).
+
+Stacks supplies a namespaced entrypoint, shared implementation guidance, mapped
+related-skill links, and regular-hyphen copy. The playbook and its supporting
+references/templates are retained. Tool integrations remain optional linked
+references; upstream CLI programs, servers, and packaging scripts are not
+bundled or installed. Source examples are illustrative and changing platform
+facts require verification.

package/ai/skills/stacks-marketing-launch/PLAYBOOK.md

@@ -0,0 +1,381 @@
+> Adapted playbook. The [shared Stacks workflow](../stacks-marketing/WORKFLOW.md) governs implementation, current facts, and authorization.
+
+
+# Launch Strategy
+
+You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.
+
+## Before Starting
+
+**Check for product marketing context first:**
+Read the established product context described in [the shared workflow](../stacks-marketing/WORKFLOW.md) before asking questions.
+
+---
+
+## Core Philosophy
+
+The best companies don't just launch once-they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.
+
+A strong launch isn't about a single moment. It's about:
+- Getting your product into users' hands early
+- Learning from real feedback
+- Making a splash at every stage
+- Building momentum that compounds over time
+
+---
+
+## The ORB Framework
+
+Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.
+
+### Owned Channels
+You own the channel (though not the audience). Direct access without algorithms or platform rules.
+
+**Examples:**
+- Email list
+- Blog
+- Podcast
+- Branded community (Slack, Discord)
+- Website/product
+
+**Why they matter:**
+- Get more effective over time
+- No algorithm changes or pay-to-play
+- Direct relationship with audience
+- Compound value from content
+
+**Start with 1-2 based on audience:**
+- Industry lacks quality content → Start a blog
+- People want direct updates → Focus on email
+- Engagement matters → Build a community
+
+**Example - Superhuman:**
+Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth-all through owned relationships. Years later, their original onboarding materials still drive engagement.
+
+### Rented Channels
+Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.
+
+**Examples:**
+- Social media (Twitter/X, LinkedIn, Instagram)
+- App stores and marketplaces
+- YouTube
+- Reddit
+
+**How to use correctly:**
+- Pick 1-2 platforms where your audience is active
+- Use them to drive traffic to owned channels
+- Don't rely on them as your only strategy
+
+**Example - Notion:**
+Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets-every viral post led to signups, then targeted email onboarding.
+
+**Platform-specific tactics:**
+- Twitter/X: Threads that spark conversation → link to newsletter
+- LinkedIn: High-value posts → lead to gated content or email signup
+- Marketplaces (Shopify, Slack): Optimize listing → drive to site for more
+
+Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.
+
+### Borrowed Channels
+Tap into someone else's audience to shortcut the hardest part-getting noticed.
+
+**Examples:**
+- Guest content (blog posts, podcast interviews, newsletter features)
+- Collaborations (webinars, co-marketing, social takeovers)
+- Speaking engagements (conferences, panels, virtual summits)
+- Influencer partnerships
+
+**Be proactive, not passive:**
+1. List industry leaders your audience follows
+2. Pitch win-win collaborations
+3. Use tools like SparkToro or Listen Notes to find audience overlap
+4. Set up affiliate/referral incentives (for channel partner launches, use [Introw](https://github.com/coreyhaines31/marketingskills/blob/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff/tools/integrations/introw.md) to manage deal registration and commissions)
+
+**Example - TRMNL:**
+Sent a free e-ink display to YouTuber Snazzy Labs-not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.
+
+Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.
+
+---
+
+## Readiness Gate: Are You Ready to Launch
+
+Run this **before** the phased mechanics. Products don't market themselves-but a product that isn't ready won't market either. The launch mechanics only pay off if what you're launching is worth launching.
+
+Two failure modes kill launches from opposite ends:
+
+- **Stealth Mode** - launching too late. "Procrastination in a fancy suit." You keep polishing in private, waiting for the product to be perfect. It never ships, and nobody learns you exist.
+- **"Just One More Feature"** - never launching. Every proposed launch date gets pushed for one more thing. The scope creeps forever; the launch never comes.
+
+The middle path is **SLC - Simple, Lovable, Complete** (Jason Cohen), the antidote to shipping a bare MVP that's minimal but unlovable. Don't launch a stub nobody wants; don't wait for a bloated everything-app. A launchable v1 is:
+
+- **Simple** - it does *one* thing. Not many things poorly. One clear job, done well.
+- **Lovable** - people *want* to use it, not just tolerate it. An MVP asks users to suffer through a stripped-down experience "to give feedback." SLC gives them something they'd choose. If nobody would be sad to lose it, it isn't lovable yet.
+- **Complete** - it's a *whole* experience for that one thing, not a stub with obvious holes. Complete at its chosen scope, not a teaser of a bigger promise.
+
+**The gate:** If it's not yet Simple, Lovable, and Complete, you're in "Just One More Feature" territory only when adding scope is what's missing-otherwise you're in Stealth Mode and should ship. Cut scope until one thing is lovable and complete, then launch that. SLC gives you a real launch now instead of a perfect launch never.
+
+**Quick check before running the phases:**
+- [ ] Does it do one clearly-defined thing? (Simple)
+- [ ] Would a target user *choose* to use it, not just endure it? (Lovable)
+- [ ] Is that one thing a whole experience, with no glaring stubs? (Complete)
+- [ ] Are you polishing past this bar? → Stop. You're in Stealth Mode. Ship.
+- [ ] Are you still adding new things to the scope? → Stop. You're in "Just One More Feature." Cut back to SLC.
+
+Pass the gate, then run the phases below.
+
+---
+
+## Five-Phase Launch Approach
+
+Launching isn't a one-day event. It's a phased process that builds momentum.
+
+### Phase 1: Internal Launch
+Gather initial feedback and iron out major issues before going public.
+
+**Actions:**
+- Recruit early users one-on-one to test for free
+- Collect feedback on usability gaps and missing features
+- Ensure prototype is functional enough to demo (doesn't need to be production-ready)
+
+**Goal:** Validate core functionality with friendly users.
+
+### Phase 2: Alpha Launch
+Put the product in front of external users in a controlled way.
+
+**Actions:**
+- Create landing page with early access signup form
+- Announce the product exists
+- Invite users individually to start testing
+- MVP should be working in production (even if still evolving)
+
+**Goal:** First external validation and initial waitlist building.
+
+### Phase 3: Beta Launch
+Scale up early access while generating external buzz.
+
+**Actions:**
+- Work through early access list (some free, some paid)
+- Start marketing with teasers about problems you solve
+- Recruit friends, investors, and influencers to test and share
+
+**Consider adding:**
+- Coming soon landing page or waitlist
+- "Beta" sticker in dashboard navigation
+- Email invites to early access list
+- Early access toggle in settings for experimental features
+
+**Goal:** Build buzz and refine product with broader feedback.
+
+### Phase 4: Early Access Launch
+Shift from small-scale testing to controlled expansion.
+
+**Actions:**
+- Leak product details: screenshots, feature GIFs, demos
+- Gather quantitative usage data and qualitative feedback
+- Run user research with engaged users (incentivize with credits)
+- Optionally run product/market fit survey to refine messaging
+
+**Expansion options:**
+- Option A: Throttle invites in batches (5-10% at a time)
+- Option B: Invite all users at once under "early access" framing
+
+**Goal:** Validate at scale and prepare for full launch.
+
+### Phase 5: Full Launch
+Open the floodgates.
+
+**Actions:**
+- Open self-serve signups
+- Start charging (if not already)
+- Announce general availability across all channels
+
+**Launch touchpoints:**
+- Customer emails
+- In-app popups and product tours
+- Website banner linking to launch assets
+- "New" sticker in dashboard navigation
+- Blog post announcement
+- Social posts across platforms
+- Product Hunt, BetaList, Hacker News, etc.
+
+**Goal:** Maximum visibility and conversion to paying users.
+
+---
+
+## Product Hunt Launch Strategy
+
+Product Hunt can be powerful for reaching early adopters, but it's not magic-it requires preparation.
+
+### Pros
+- Exposure to tech-savvy early adopter audience
+- Credibility bump (especially if Product of the Day)
+- Potential PR coverage and backlinks
+
+### Cons
+- Very competitive to rank well
+- Short-lived traffic spikes
+- Requires significant pre-launch planning
+
+### How to Launch Successfully
+
+**Before launch day:**
+1. Build relationships with influential supporters, content hubs, and communities
+2. Optimize your listing: compelling tagline, polished visuals, short demo video
+3. Study successful launches to identify what worked
+4. Engage in relevant communities-provide value before pitching
+5. Prepare your team for all-day engagement
+
+**On launch day:**
+1. Treat it as an all-day event
+2. Respond to every comment in real-time
+3. Answer questions and spark discussions
+4. Encourage your existing audience to engage
+5. Direct traffic back to your site to capture signups
+
+**After launch day:**
+1. Follow up with everyone who engaged
+2. Convert Product Hunt traffic into owned relationships (email signups)
+3. Continue momentum with post-launch content
+
+### Case Studies
+
+**SavvyCal** (Scheduling tool):
+- Optimized landing page and onboarding before launch
+- Built relationships with productivity/SaaS influencers in advance
+- Responded to every comment on launch day
+- Result: #2 Product of the Month
+
+**Reform** (Form builder):
+- Studied successful launches and applied insights
+- Crafted clear tagline, polished visuals, demo video
+- Engaged in communities before launch (provided value first)
+- Treated launch as all-day engagement event
+- Directed traffic to capture signups
+- Result: #1 Product of the Day
+
+---
+
+## Post-Launch Product Marketing
+
+Your launch isn't over when the announcement goes live. Now comes adoption and retention work.
+
+### Immediate Post-Launch Actions
+
+**Educate new users:**
+Set up automated onboarding email sequence introducing key features and use cases.
+
+**Reinforce the launch:**
+Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.
+
+**Differentiate against competitors:**
+Publish comparison pages highlighting why you're the obvious choice.
+
+**Update web pages:**
+Add dedicated sections about the new feature/product across your site.
+
+**Offer hands-on preview:**
+Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.
+
+### Keep Momentum Going
+It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.
+
+---
+
+## Ongoing Launch Strategy
+
+Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement.
+
+### How to Prioritize What to Announce
+
+Use this matrix to decide how much marketing each update deserves:
+
+**Major updates** (new features, product overhauls):
+- Full campaign across multiple channels
+- Blog post, email campaign, in-app messages, social media
+- Maximize exposure
+
+**Medium updates** (new integrations, UI enhancements):
+- Targeted announcement
+- Email to relevant segments, in-app banner
+- Don't need full fanfare
+
+**Minor updates** (bug fixes, small tweaks):
+- Changelog and release notes
+- Signal that product is improving
+- Don't dominate marketing
+
+### Announcement Tactics
+
+**Space out releases:**
+Instead of shipping everything at once, stagger announcements to maintain momentum.
+
+**Reuse high-performing tactics:**
+If a previous announcement resonated, apply those insights to future updates.
+
+**Keep engaging:**
+Continue using email, social, and in-app messaging to highlight improvements.
+
+**Signal active development:**
+Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth-customers feel confident you'll be around.
+
+**Turn shipped code into announcements:**
+If you can read the product repo, generate the week's changelog, announcement drafts, and pages-to-update list straight from merged PRs. See [references/shipped-changes.md](references/shipped-changes.md).
+
+---
+
+## Launch Checklist
+
+### Pre-Launch
+- [ ] Landing page with clear value proposition
+- [ ] Email capture / waitlist signup
+- [ ] Early access list built
+- [ ] Owned channels established (email, blog, community)
+- [ ] Rented channel presence (social profiles optimized)
+- [ ] Borrowed channel opportunities identified (podcasts, influencers)
+- [ ] Product Hunt listing prepared (if using)
+- [ ] Launch assets created (screenshots, demo video, GIFs)
+- [ ] Onboarding flow ready
+- [ ] Analytics/tracking in place
+- [ ] Site QA done if the launch includes a new site, redesign, or migration (see [references/site-launch-qa.md](references/site-launch-qa.md))
+
+### Launch Day
+- [ ] Announcement email to list
+- [ ] Blog post published
+- [ ] Social posts scheduled and posted
+- [ ] Product Hunt listing live (if using)
+- [ ] In-app announcement for existing users
+- [ ] Website banner/notification active
+- [ ] Team ready to engage and respond
+- [ ] Monitor for issues and feedback
+
+### Post-Launch
+- [ ] Onboarding email sequence active
+- [ ] Follow-up with engaged prospects
+- [ ] Roundup email includes announcement
+- [ ] Comparison pages published
+- [ ] Interactive demo created
+- [ ] Gather and act on feedback
+- [ ] Plan next launch moment
+
+---
+
+## Task-Specific Questions
+
+1. What are you launching? (New product, major feature, minor update)
+2. What's your current audience size and engagement?
+3. What owned channels do you have? (Email list size, blog traffic, community)
+4. What's your timeline for launch?
+5. Have you launched before? What worked/didn't work?
+6. Are you considering Product Hunt? What's your preparation status?
+
+---
+
+## Related Skills
+
+- **stacks-marketing-ideas**: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals)
+- **stacks-marketing-emails**: For launch and onboarding email sequences
+- **stacks-marketing-cro**: For optimizing launch landing pages
+- **stacks-marketing-psychology**: For psychology behind waitlists and exclusivity
+- **stacks-marketing-programmatic-seo**: For comparison pages mentioned in post-launch
+- **stacks-marketing-sales-enablement**: For launch sales collateral and enablement materials

package/ai/skills/stacks-marketing-launch/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: stacks-marketing-launch
+description: Use when the user wants to plan a product launch, feature announcement, or release strategy. Covers marketing planning and its Stacks implementation.
+license: MIT
+compatibility: Bun >= 1.3.0, TypeScript
+allowed-tools: Read Edit Write Bash Grep Glob
+---
+
+# Marketing Launch
+
+Read [the shared Stacks workflow](../stacks-marketing/WORKFLOW.md), then
+[PLAYBOOK.md](PLAYBOOK.md) before doing this task. Load the supporting references
+only for the branch the playbook routes to.
+
+This ports `launch` from
+[coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills/tree/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff/skills/launch).
+[NOTICE.md](NOTICE.md) records the snapshot and [LICENSE](LICENSE) retains the
+upstream MIT notice.
+
+## Stacks integration
+
+Keep marketing recommendations distinct from application API facts. Use the
+framework skill for any model, action, route, stx page, campaign job, or payment
+change. Use the user's existing brief and authorization; a playbook example
+does not supply a product fact or authorize sending, spending, or publishing.
+
+Platform limits and benchmarks in the snapshot need current primary-source
+verification before use. Return the requested artifact with consequential
+assumptions and evidence, then verify any implementation through its real
+behavior. Use TypeScript and Bun for executable helpers.