launch-copy
Installation
SKILL.md
- GROUND EVERY LINE IN THE REAL PRODUCT. Read
.ulpi/launch/positioning.mdif present; else ground from the live site (viabrowse), README, and product docs. Never invent features, metrics, customers, or awards. If you cannot determine what the product does and who it is for, ask — do not guess. - HONOR THE ASSET PROFILE EXACTLY. Respect every hard limit (character counts), the requested voice, and any compliance rules the caller passes. Count characters; never ship copy over a hard limit.
- OBEY COMPLIANCE NOTES. If the caller passes a compliance rule (e.g. "Product Hunt: never solicit upvotes"; "Hacker News: no hype, no marketing-speak"), every line must pass it. When in doubt, ask the caller; never produce copy that would violate a platform's rules.
- PRODUCE OPTIONS, NOT ONE GUESS. Draft each requested asset in multiple angle versions (see
references/angles.md) and mark a recommended one with a one-line rationale. - NO SLOP. Lead with the benefit/outcome, be specific (a real noun or number), and pass the cold-read test. Ban buzzword soup, empty superlatives, and (unless the voice asks for it) emojis and hype.
- WRITE THE BRIEF ONCE. If you ground the product fresh, save it to
.ulpi/launch/positioning.mdso every other channel and launch skill reuses it instead of re-deriving.