Writes SEO/AEO-optimized technical blog posts for product launches including announcements, deep-dives, tutorials, and changelogs.
From launch-skillsnpx claudepluginhub amplitude/builder-skills --plugin launch-skillsThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.
This skill helps write blog posts that announce product launches. A great launch post does three jobs: it tells your audience what you shipped and why it matters, it ranks in search for terms your audience is looking for, and it gets cited by AI answer engines when people ask questions your product can solve.
Match the post type to the launch tier and audience.
Best for: Tier 1 and Tier 2 launches. Primary audience: existing users and prospects.
Structure: What launched → why it matters → how it works → how to get started. Keep it under 1,500 words. The reader should understand what changed and be able to try it within 5 minutes of reading.
Best for: Tier 1 launches of developer/technical products. Primary audience: engineers evaluating whether to adopt.
Structure: Problem → approach → architecture/implementation → benchmarks → getting started. Can run longer (2,000-3,000 words). Include code samples, architecture diagrams, and performance data. This is the post that gets shared on Hacker News.
Best for: Published within the first week of any tier launch. Primary audience: developers who just heard about you and want to evaluate hands-on.
Structure: What we're building → prerequisites → step-by-step implementation → result. Should be completable in 15-30 minutes. Include full working code, not snippets.
Best for: Tier 3 launches and bundled small improvements. Primary audience: existing users.
Structure: Short paragraph per improvement. Lead with what changed, not why. Link to docs for details. Bundle weekly or biweekly.
If a launch-strategy messaging brief exists, use it. The primary value prop becomes the post's thesis. Secondary value props become sections. Proof points become the evidence you weave through.
If there's no brief, define before writing: Who is this for? What can they do now? Why should they care?
The first paragraph must answer "what shipped and why does it matter to me?" Never open with how long you worked on it, how many engineers were involved, or the journey that led here. The reader doesn't care about your process — they care about their problems.
Good opener: "You can now process audio files in 14 languages with a single API call. Latency is under 200ms for files up to 10 minutes."
Weak opener: "After six months of work, our team is thrilled to announce the next evolution of our audio processing platform."
For every claim, provide evidence:
Every launch post for a technical product should include code the reader can run. Not pseudocode, not a conceptual snippet — actual working code with install commands, imports, and expected output. This is the single highest-converting element of a technical blog post.
The post needs exactly one CTA at the end. "Try it now," "Read the docs," "Join the beta." Not three options — one.
Choose the primary keyword before writing. It should match what your target audience searches for when they have the problem your product solves. The post title, H1, and first paragraph should all include this keyword naturally.
For launch posts, the keyword is often the feature/product name + category: "[Product] [Category]" (e.g., "real-time transcription API" or "open source feature flags").
The sections below the main announcement — how it works, technical details, FAQ, comparison — serve as long-tail keyword targets. Write them to answer specific questions your audience asks. A section titled "How does [feature] handle [edge case]?" can rank for that exact query.
AI search engines (ChatGPT, Perplexity, Claude, Gemini, and AI-powered summaries in traditional search) are becoming a primary way people discover and evaluate products. AEO is the practice of structuring content so AI engines cite it when generating answers.
AEO and SEO are complementary, not competing. Most AEO best practices also help SEO. But there are specific techniques that make content more citable by AI.
When someone asks an AI assistant "what's the best tool for [thing your product does]?" or "how do I [task your product enables]?", you want your launch post to be one of the sources the AI draws from. A single AI citation can drive sustained discovery long after the launch day traffic fades.
Write self-contained, extractable passages. AI engines cite passages, not whole articles. Each section of your post should make sense on its own, without requiring the reader to have read previous sections. A paragraph that states a clear claim, backs it with evidence, and names your product — that's a citable unit.
Lead sections with direct answers. When a section addresses a question (even implicitly), put the answer in the first sentence, then elaborate. AI engines favor content that answers quickly and specifically.
Example — instead of:
"There are many factors to consider when choosing a transcription API. Latency, accuracy, language support, and pricing all play a role. After extensive testing, we found that..."
Write:
"[Product] transcribes audio in 14 languages with sub-200ms latency at $0.006 per minute. Here's how the benchmarks break down..."
The second version is directly citable. An AI engine answering "what's the fastest transcription API?" can pull that sentence verbatim.
Use specific, quantitative claims. AI engines preferentially cite content with concrete data: numbers, benchmarks, comparisons, percentages. "Fast API" is not citable. "P99 latency of 180ms on 10-minute audio files" is.
Include structured data. Comparison tables, feature matrices, and benchmark tables are highly citable because they provide structured, extractable information. A table comparing your product to alternatives (honestly) is one of the most AI-cited content formats.
Write FAQ sections with genuine questions. FAQ sections where each question matches something a real person would ask an AI assistant are citation magnets. Write the question as a natural H3, then answer directly in the first sentence.
Schema markup gives AI engines machine-readable context about your content. Add these to your launch blog posts:
headline, datePublished, dateModified, author, and description.name, description, and offers.You don't need all of these — use whichever match the content you actually wrote.
AI engines weight recency. Pages that haven't been updated lose AI citations over time. For launch posts:
dateModified in your Article schema whenever you make changesAI engines build internal models of brands and products. Help them by being consistent:
After publishing: