From magic-powers
Use when defining how an AI product stands out — defensibility assessment, outcome-based messaging, feature vs product decision, competitive moat design, and positioning for a specific niche.
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
- Writing landing page copy that doesn't convert
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Critical strategic decision with huge implications:
| Dimension | AI Feature | AI Product |
|---|---|---|
| Core value | Enhancement to existing workflow | Solves a standalone problem |
| Business model | Bundled with main product | Standalone subscription |
| Marketing | "Now with AI" | "The AI for [specific problem]" |
| Retention | Tied to main product | Must be independently indispensable |
| Risk | Low (bundled) | High (must acquire users) |
| Upside | Limited | Unlimited |
Test: Can users pay for JUST the AI capability, separately from everything else? If yes → product. If no → feature.
Rate your moat across 4 dimensions (0-3 each):
Data moat (0-3):
0 = any user can get same results from ChatGPT
1 = you use industry-specific data users provide
2 = you collect data across ALL users that improves the product
3 = proprietary dataset nobody else has access to
Workflow moat (0-3):
0 = one-off use, no workflow integration
1 = part of existing workflow but easily replaced
2 = deeply embedded, switching costs >1 day
3 = critical path — production breaks without it
Trust moat (0-3):
0 = any AI can do this, no personalization
1 = remembers user preferences
2 = knows user's industry/company context deeply
3 = irreplaceable knowledge of user's specific situation
Niche moat (0-3):
0 = generic tool for everyone
1 = vertical focus (marketing tools)
2 = specific role (CMO tools)
3 = specific workflow for specific person (CMO weekly report)
Score: 0-4 = thin wrapper (high risk), 5-8 = defensible, 9-12 = strong moat
Move from feature language to outcome language:
Feature language (weak): Outcome language (strong):
"Uses GPT-4 to analyze..." "Save 3 hours per week on..."
"AI-powered document search" "Find any clause in your 500-page contract in 10 seconds"
"Automates report generation" "Get your Monday board report done in 15 minutes, not 3 hours"
"Multi-agent AI assistant" "Your AI team that never sleeps — replies to leads while you do"
Messaging formula:
[Specific person] who [does specific thing] can now [achieve outcome] in [time/effort saved]
without [painful part of current process].
Test your messaging:
The narrower your ICP, the stronger your positioning:
Too broad: "For businesses using AI"
Better: "For marketing teams using AI"
Best: "For B2B SaaS CMOs who write weekly board decks"
Brilliant: "For B2B SaaS CMOs at Series A-B companies who present to board monthly"
Narrowing exercise:
Find the white space competitors don't occupy:
Positioning axes (pick 2 that matter most to your ICP):
- Speed ↔ Thoroughness
- Ease of use ↔ Customization
- Cheap ↔ Premium
- General ↔ Specialized
- Self-serve ↔ Human-assisted
Plot: Where are competitors? Where is the gap?
Position in the gap your ICP values most.
ai-product-validation (validated problem → now position clearly)solo-founder-gtm (positioning drives all GTM messaging)ai-product-monetization (stronger moat → higher price ceiling)@solo-ai-builder runs positioning analysis before writing landing page copy