From superpowers
Generates 3-5 viral social media hooks using psychological patterns from hook-patterns.md and trigger words from trigger_words.md. Useful for attention-grabbing openings on X, LinkedIn, Instagram, TikTok.
npx claudepluginhub lunartech-x/superpowers --plugin superpowersThis skill uses the workspace's default tool permissions.
Generate 3-5 viral hook options using proven psychological patterns that create curiosity, provide value, and drive engagement. Hooks are optimized for social platforms (X/Twitter, LinkedIn, Instagram, TikTok).
Generates 3-5 viral social media hooks using psychological patterns from hook-patterns.md and trigger words from trigger_words.md. Useful for attention-grabbing openings on X, LinkedIn, Instagram, TikTok.
Generates persuasive social media copy using hooks, power words, storytelling frameworks, and psychological triggers optimized for Instagram swipes and X/Twitter clicks.
Generates 6 clickbait-style two-line LinkedIn hooks for any topic: 40-char punchy opener + contrast line with digits, 'How I'/'I' statements, metrics. Triggers on 'write me hooks', 'hook ideas', topic requests.
Share bugs, ideas, or general feedback.
Generate 3-5 viral hook options using proven psychological patterns that create curiosity, provide value, and drive engagement. Hooks are optimized for social platforms (X/Twitter, LinkedIn, Instagram, TikTok).
Check $ARGUMENTS first to determine execution mode:
Respond with: "viral-hook-creator loaded, proceed with additional instructions"
Then wait for the user to provide their requirements in the next message.
Proceed immediately to Task Execution (skip the "loaded" message).
When user requirements are available (either from initial $ARGUMENTS or follow-up message):
BLOCKING REQUIREMENT - DO NOT SKIP THIS STEP
Before doing ANYTHING else, you MUST use the Read tool to read BOTH reference files. This is non-negotiable:
Read: ./references/hook-patterns.md
Read: ./references/trigger_words.md
What you will find:
DO NOT PROCEED to step 2 until you have read both files and have the patterns and trigger words loaded in context.
Check if FOUNDER_CONTEXT.md exists in the project root.
From the user's requirements, extract:
For any missing information, apply defaults from the "Defaults & Assumptions" section.
Using the patterns and trigger words you read in Step 1, create hooks:
Select patterns from hook-patterns.md using the Pattern Selection Matrix (match user's goal + platform)
Draft each hook using the pattern template as your starting point
Integrate 1-2 trigger words from trigger_words.md into each hook as you write:
Follow all Writing Rules (Core Rules, Pattern-Specific Rules, Platform-Specific Adaptations)
Ensure differentiation - each hook must use a unique pattern
Verify natural integration - trigger words should enhance, not distract
Hard constraints. No interpretation.
Clean and simple. Just hooks with their pattern type as a headline.
### [Pattern Name]
[Hook text]
### [Pattern Name]
[Hook text]
### [Pattern Name]
[Hook text]
Example:
### Authority Credibility
I run a 23-person software agency. Here are 5 things I would never do again.
### Data-Driven Insight
I analyzed 1,000 LinkedIn posts. Here are the top 5 patterns that drove engagement.
### Contrarian
Everyone tells you to post daily. I posted 3x per week and got 10x more engagement.
Use these unless overridden.
These files MUST be read using the Read tool before generating any hooks (see Step 1 of Task Execution):
| File | Purpose |
|---|---|
./references/hook-patterns.md | 18 proven hook patterns with templates, psychology, and Pattern Selection Matrix |
./references/trigger_words.md | Viral trigger word categories (Insider, Helper, Thinker, Amplifiers) |
Why both matter: Hook patterns provide psychological structure. Trigger words amplify emotional impact. Patterns alone = good hook. Patterns + trigger words = viral hook (~10x more engagement).
Before finalizing, verify ALL of the following:
./references/hook-patterns.md before generating hooks./references/trigger_words.md before generating hooksIf ANY hook is missing trigger words from the reference file or uses patterns not from hook-patterns.md → revise before presenting.