From ultraship
Prepares projects for product launch: analyzes with Node script, defines audience positioning, checklists for product/SEO/analytics/legal/social proof readiness, generates copy for Product Hunt/social media.
npx claudepluginhub houseofmvps/ultraship --plugin ultrashipThis skill uses the workspace's default tool permissions.
A launch is not a deploy. A deploy puts code on a server. A launch puts a product in front of people who need it, at the right time, with the right message, on the right channels. This skill treats launch as a coordinated campaign, not a checkbox.
Designs and executes launch plans for products/features: Product Hunt, HN Show HN, newsletters, social posts, community coordination. Use for 'launch [product]', 'plan a launch', or announcement queries.
Plans Product Hunt launches with objectives, success metrics, 4-6 week timelines, preparation checklists, and strategies for visibility, acquisition, social proof, or feedback.
Guides product launch execution with checklists, timelines, channel mixes (PR, paid, organic, email), and cross-functional coordination for new products or major features.
Share bugs, ideas, or general feedback.
A launch is not a deploy. A deploy puts code on a server. A launch puts a product in front of people who need it, at the right time, with the right message, on the right channels. This skill treats launch as a coordinated campaign, not a checkbox.
node ${CLAUDE_PLUGIN_ROOT}/tools/launch-prep.mjs <project-directory> --url=<production-url>
Parse the JSON output for project info, launch copy, checklist, and press kit.
Before writing a single word of copy, nail the positioning:
Who is this for?
Positioning statement:
For [target user] who [pain point], [product] is a [category] that [key benefit]. Unlike [alternatives], it [differentiator].
This positioning statement drives ALL copy below. Every piece of content should map back to it.
Competitive angle:
Present the launch checklist with pass/fail/warn status:
Product Ready:
SEO + AI visibility Ready:
llms.txt for AI discoverabilityAnalytics Ready:
Legal Ready:
Social Proof Ready:
For any FAIL items, fix them immediately.
Product Hunt:
Twitter/X Thread (5-7 tweets):
LinkedIn Post:
Hacker News (Show HN):
Launching on platforms is necessary but not sufficient. The products that break through have community presence before launch day:
Pre-launch (1-2 weeks before):
Launch day amplification:
Post-launch (3-7 days after):
Present the press kit components:
If a production URL was provided:
node ${CLAUDE_PLUGIN_ROOT}/tools/health-check.mjs <production-url>
Verify the site is up, fast, and SSL is valid. Run /seo to ensure all SEO + AI visibility signals are in place. Nothing worse than going viral with a broken OG image or a 4-second LCP.
Generate a suggested launch day timeline (all times in user's timezone):
| Time | Action | Why |
|---|---|---|
| 6:00 AM PT | Submit to Product Hunt | Optimal for full-day upvote accumulation |
| 6:15 AM PT | Post maker's first comment on PH | Sets the tone, shows you're responsive |
| 7:00 AM PT | Tweet the announcement thread | Catches morning scrollers |
| 7:30 AM PT | Post in 2-3 Slack/Discord communities | Warm audiences convert best |
| 8:00 AM PT | Post on LinkedIn | Professional audience online |
| 9:00 AM PT | Submit to Hacker News (Show HN) | HN peaks mid-morning ET |
| 12:00 PM PT | Engage with all platform comments | Engagement velocity signals quality |
| 3:00 PM PT | Share progress update with real numbers | Social proof drives late-day interest |
| 6:00 PM PT | Thank early users, share key metrics | Gratitude posts perform well |
| Next day | Follow up everywhere, respond to all comments | Sustained engagement > launch-day spike |