bobo-ai-cli 1.0.1

package/knowledge/skills/positioning-angles.md

@@ -0,0 +1,330 @@
+---
+id: "positioning-angles"
+title: "Positioning & Angles"
+category: "marketing"
+tags: ["positioning & angles", "the core job", "the angle-finding process", "output format", "how this skill gets invoked", "what this skill is not", "the test", "references"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/positioning-angles"
+---
+
+---
+name: positioning-angles
+description: "Find the angle that makes something sell. Use when launching a product, creating a lead magnet, writing a landing page, crafting an offer, or when marketing isn't converting. Triggers on: find angles for X, how should I position X, what's the hook, why isn't this selling, make this stand out, differentiate this, or when copy/landing page work needs a strong angle first. Outputs 3-5 distinct positioning options with headline directions for each."
+---
+
+# Positioning & Angles
+
+The same product can sell 100x better with a different angle. Not a different product. Not better features. Just a different way of framing what it already does.
+
+This skill finds those angles.
+
+---
+
+## The core job
+
+When someone asks about positioning or angles, the goal isn't to find THE answer. It's to surface **multiple powerful options** they can choose from.
+
+Every product has several valid angles. The question is which one resonates most with the specific audience at the specific moment.
+
+Output format: **3-5 distinct angle options**, each with:
+
+- The angle (one sentence)
+- Why it works (the psychology)
+- Headline direction (how it would sound in copy)
+- When to use it (market conditions, audience segments)
+
+---
+
+## The angle-finding process
+
+### Step 1: Identify what they're actually selling
+
+Not the product. The transformation.
+
+Ask: What does the customer's life look like AFTER? What pain disappears? What capability appears? What status changes?
+
+A fitness program doesn't sell workouts. It sells "fit into your old jeans" or "keep up with your kids" or "look good naked."
+
+A SaaS tool doesn't sell features. It sells "close your laptop at 5pm" or "never lose a lead" or "stop the spreadsheet chaos."
+
+**The transformation is the raw material for angles.**
+
+---
+
+### Step 2: Map the competitive landscape
+
+What would customers do if this didn't exist? Not competitors—alternatives.
+
+- Do nothing (live with the problem)
+- DIY (cobble together a solution)
+- Hire someone (consultant, freelancer, agency)
+- Buy a different category (different approach entirely)
+- Buy a direct competitor
+
+Each alternative has weaknesses. Those weaknesses become angle opportunities.
+
+**Angle opportunity:** What's frustrating about each alternative that this solves?
+
+---
+
+### Step 3: Find the unique mechanism
+
+The mechanism is HOW the product delivers results differently.
+
+Not "we help you lose weight" (that's the promise).
+"We help you lose weight through intermittent fasting optimized for your metabolic type" (that's the mechanism).
+
+The mechanism makes the promise believable. It answers: "Why will this work when other things haven't?"
+
+**Questions to surface the mechanism:**
+
+- What's the proprietary process, method, or system?
+- What do you do differently than the obvious approach?
+- What's the counterintuitive insight that makes this work?
+- What's the "secret" ingredient, step, or element?
+
+Even if nothing is truly proprietary, there's always a mechanism. Name it.
+
+---
+
+### Step 4: Assess market sophistication
+
+Where is the market on Schwartz's awareness scale?
+
+**Stage 1 (New category):** The market hasn't seen this before.
+→ Angle: Simple announcement. "Now you can [do thing]."
+
+**Stage 2 (Growing awareness):** Competition exists, market is warming.
+→ Angle: Claim superiority. "The fastest/easiest/most complete way to [outcome]."
+
+**Stage 3 (Crowded):** Many players, similar claims, skepticism rising.
+→ Angle: Explain the mechanism. "Here's WHY this works when others don't."
+
+**Stage 4 (Jaded):** Market has seen everything, needs new frame.
+→ Angle: Identity and belonging. "For people who [identity marker]."
+
+**Stage 5 (Iconic):** Established leaders, brand loyalty matters.
+→ Angle: Exclusive access. "Join the [tribe/movement]."
+
+**The market stage determines which angle TYPE will work.**
+
+---
+
+### Step 5: Run the angle generators
+
+Now generate options using multiple frameworks:
+
+#### The Contrarian Angle
+
+What does everyone in this market believe that might not be true?
+Challenge that assumption directly.
+
+> "Everything you've been told about [topic] is wrong."
+> "Stop [common practice]. Here's what actually works."
+
+Works when: Market is frustrated with conventional approaches. Audience sees themselves as independent thinkers.
+
+#### The Unique Mechanism Angle
+
+Lead with the HOW, not just the WHAT.
+Name the proprietary process or insight.
+
+> "The [Named Method] that [specific result]"
+> "How [mechanism] lets you [outcome] without [usual sacrifice]"
+
+Works when: Market is sophisticated (Stage 3+). Similar promises exist. Need to differentiate.
+
+#### The Transformation Angle
+
+Before and after. The gap between current state and desired state.
+
+> "From [painful current state] to [desired outcome]"
+> "Go from [specific bad metric] to [specific good metric] in [timeframe]"
+
+Works when: The transformation is dramatic and specific. Market is problem-aware.
+
+#### The Enemy Angle
+
+Position against a common enemy (not a competitor—a problem, a mindset, an obstacle).
+
+> "Stop letting [enemy] steal your [valuable thing]"
+> "The [enemy] is lying to you. Here's the truth."
+
+Works when: Audience has shared frustrations. There's a clear villain to rally against.
+
+#### The Speed/Ease Angle
+
+Compress the time or reduce the effort.
+
+> "[Outcome] in [surprisingly short time]"
+> "[Outcome] without [expected sacrifice]"
+
+Works when: Alternatives require significant time or effort. Speed/ease is genuinely differentiated.
+
+#### The Specificity Angle
+
+Get hyper-specific about who it's for or what it delivers.
+
+> "For [very specific avatar] who want [very specific outcome]"
+> "The [specific number] [specific things] that [specific result]"
+
+Works when: Competing with generic offerings. Want to signal "this is built for YOU."
+
+#### The Social Proof Angle
+
+Lead with evidence, not claims.
+
+> "[Specific result] for [number] [type of people]"
+> "How [credible person/company] achieved [specific outcome]"
+
+Works when: Have strong proof. Market is skeptical. Trust is the primary barrier.
+
+#### The Risk Reversal Angle
+
+Make the guarantee the headline.
+
+> "[Outcome] or [dramatic consequence for seller]"
+> "Try it for [time period]. [Specific guarantee]."
+
+Works when: Risk is the primary objection. Confidence in delivery is high.
+
+---
+
+## Output format
+
+When finding angles, deliver this:
+
+### Angle Options for [Product/Offer]
+
+**Angle 1: [Name]**
+
+- The angle: [One sentence positioning]
+- Why it works: [Psychology/market insight]
+- Headline direction: "[Example headline]"
+- When to use: [Conditions where this angle is strongest]
+
+**Angle 2: [Name]**
+
+- The angle: [One sentence positioning]
+- Why it works: [Psychology/market insight]
+- Headline direction: "[Example headline]"
+- When to use: [Conditions where this angle is strongest]
+
+**Angle 3: [Name]**
+
+- The angle: [One sentence positioning]
+- Why it works: [Psychology/market insight]
+- Headline direction: "[Example headline]"
+- When to use: [Conditions where this angle is strongest]
+
+[Continue for 4-5 total options]
+
+**Recommended starting point:** [Which angle to test first and why]
+
+---
+
+## Example: Finding angles for a "Claude Skills Pack"
+
+### Context
+
+- Product: 10 marketing skills for Claude Code
+- Transformation: Better marketing output without becoming a marketer
+- Alternatives: Generic prompting, hiring copywriters, learning marketing yourself
+- Mechanism: Skills transfer expertise through principles, not just prompts
+
+### Angle Options
+
+**Angle 1: The Capability Transfer**
+
+- The angle: Give Claude marketing superpowers so you don't need them yourself
+- Why it works: Buyers want the outcome without the learning curve
+- Headline direction: "Turn Claude into a marketing team that actually sells."
+- When to use: Audience is technical/builder-focused, not marketing-focused
+
+**Angle 2: The Anti-Generic**
+
+- The angle: Stop getting generic AI output that sounds like everyone else
+- Why it works: Universal frustration with AI output quality
+- Headline direction: "Same Claude. Different playbook. 10x output."
+- When to use: Audience has tried Claude and been disappointed
+
+**Angle 3: The Methodology Transfer**
+
+- The angle: Packaged expertise from $400k+ in real results
+- Why it works: Credibility through specific proof, not theory
+- Headline direction: "The marketing methodology behind $400k+ in 9 months—now packaged for Claude."
+- When to use: Audience values proven systems over promises
+
+**Angle 4: The Time Recapture**
+
+- The angle: Stop spending hours on AI babysitting
+- Why it works: Quantifies the hidden cost of current approach
+- Headline direction: "You're burning 10+ hours a month on AI babysitting. Skills fix this."
+- When to use: Audience is time-constrained, values efficiency
+
+**Angle 5: The Specialist Unlock**
+
+- The angle: Access copywriter/marketer expertise without hiring one
+- Why it works: Positions against the expensive alternative
+- Headline direction: "Specialist marketing output without specialist costs."
+- When to use: Audience has considered hiring but balked at price
+
+**Recommended starting point:** Angle 1 (Capability Transfer) for a technical/builder audience, Angle 3 (Methodology Transfer) for a results-focused audience.
+
+---
+
+## How this skill gets invoked
+
+This skill activates when:
+
+- User asks "how should I position X"
+- User asks "what's the angle for X"
+- User asks "why isn't this selling"
+- User asks to "find the hook" or "make this stand out"
+- User is about to write copy/landing page but hasn't established positioning
+- Direct-response-copy skill needs an angle to write from
+- Landing-page skill needs a core positioning to build around
+
+When another skill needs an angle, run this first. The angle informs everything downstream.
+
+---
+
+## What this skill is NOT
+
+This skill finds positioning and angles. It does NOT:
+
+- Write the actual copy (that's direct-response-copy)
+- Build the landing page structure (that's landing-page)
+- Research the audience from scratch (assumes you know who you're selling to)
+- Pick a single "right" answer (it gives options to choose from)
+
+The output is strategic direction, not finished marketing.
+
+---
+
+## The test
+
+Before delivering angles, verify each one:
+
+1. **Is it specific?** Vague angles ("better results") fail. Specific angles ("20 lbs in 6 weeks") convert.
+
+2. **Is it differentiated?** Could a competitor claim the same thing? If yes, sharpen it.
+
+3. **Is it believable?** Does the mechanism or proof support the claim?
+
+4. **Is it relevant to THIS audience?** An angle that works for beginners fails for experts.
+
+5. **Does it lead somewhere?** Can you imagine the headline, the landing page, the copy? If not, it's too abstract.
+
+---
+
+## References
+
+For deeper frameworks, see the `references/` folder:
+
+- `dunford-positioning.md` — April Dunford's 5-component positioning methodology
+- `schwartz-sophistication.md` — Eugene Schwartz's market awareness levels
+- `unique-mechanism.md` — How to find and name your mechanism
+- `angle-frameworks.md` — Halbert, Ogilvy, Hopkins, Bencivenga, Kennedy approaches
+- `hormozi-offer.md` — Value equation and Grand Slam Offer thinking

package/knowledge/skills/pr-review-toolkit.md

@@ -0,0 +1,359 @@
+---
+id: "pr-review-toolkit"
+title: "PR Review Toolkit"
+category: "dev-tools"
+tags: ["pr review toolkit", "overview", "agents", "usage patterns", "installation", "find 'pr-review-toolkit'", "install", "agent details", "best practices", "tips"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/pr-review-toolkit"
+---
+
+# PR Review Toolkit
+
+A comprehensive collection of specialized agents for thorough pull request review, covering code comments, test coverage, error handling, type design, code quality, and code simplification.
+
+## Overview
+
+This plugin bundles 6 expert review agents that each focus on a specific aspect of code quality. Use them individually for targeted reviews or together for comprehensive PR analysis.
+
+## Agents
+
+### 1. comment-analyzer
+
+**Focus**: Code comment accuracy and maintainability
+
+**Analyzes:**
+
+- Comment accuracy vs actual code
+- Documentation completeness
+- Comment rot and technical debt
+- Misleading or outdated comments
+
+**When to use:**
+
+- After adding documentation
+- Before finalizing PRs with comment changes
+- When reviewing existing comments
+
+**Triggers:**
+
+```
+"Check if the comments are accurate"
+"Review the documentation I added"
+"Analyze comments for technical debt"
+```
+
+### 2. pr-test-analyzer
+
+**Focus**: Test coverage quality and completeness
+
+**Analyzes:**
+
+- Behavioral vs line coverage
+- Critical gaps in test coverage
+- Test quality and resilience
+- Edge cases and error conditions
+
+**When to use:**
+
+- After creating a PR
+- When adding new functionality
+- To verify test thoroughness
+
+**Triggers:**
+
+```
+"Check if the tests are thorough"
+"Review test coverage for this PR"
+"Are there any critical test gaps?"
+```
+
+### 3. silent-failure-hunter
+
+**Focus**: Error handling and silent failures
+
+**Analyzes:**
+
+- Silent failures in catch blocks
+- Inadequate error handling
+- Inappropriate fallback behavior
+- Missing error logging
+
+**When to use:**
+
+- After implementing error handling
+- When reviewing try/catch blocks
+- Before finalizing PRs with error handling
+
+**Triggers:**
+
+```
+"Review the error handling"
+"Check for silent failures"
+"Analyze catch blocks in this PR"
+```
+
+### 4. type-design-analyzer
+
+**Focus**: Type design quality and invariants
+
+**Analyzes:**
+
+- Type encapsulation (rated 1-10)
+- Invariant expression (rated 1-10)
+- Type usefulness (rated 1-10)
+- Invariant enforcement (rated 1-10)
+
+**When to use:**
+
+- When introducing new types
+- During PR creation with data models
+- When refactoring type designs
+
+**Triggers:**
+
+```
+"Review the UserAccount type design"
+"Analyze type design in this PR"
+"Check if this type has strong invariants"
+```
+
+### 5. code-reviewer
+
+**Focus**: General code review for project guidelines
+
+**Analyzes:**
+
+- CLAUDE.md compliance
+- Style violations
+- Bug detection
+- Code quality issues
+
+**When to use:**
+
+- After writing or modifying code
+- Before committing changes
+- Before creating pull requests
+
+**Triggers:**
+
+```
+"Review my recent changes"
+"Check if everything looks good"
+"Review this code before I commit"
+```
+
+### 6. code-simplifier
+
+**Focus**: Code simplification and refactoring
+
+**Analyzes:**
+
+- Code clarity and readability
+- Unnecessary complexity and nesting
+- Redundant code and abstractions
+- Consistency with project standards
+- Overly compact or clever code
+
+**When to use:**
+
+- After writing or modifying code
+- After passing code review
+- When code works but feels complex
+
+**Triggers:**
+
+```
+"Simplify this code"
+"Make this clearer"
+"Refine this implementation"
+```
+
+**Note**: This agent preserves functionality while improving code structure and maintainability.
+
+## Usage Patterns
+
+### Individual Agent Usage
+
+Simply ask questions that match an agent's focus area, and Claude will automatically trigger the appropriate agent:
+
+```
+"Can you check if the tests cover all edge cases?"
+→ Triggers pr-test-analyzer
+
+"Review the error handling in the API client"
+→ Triggers silent-failure-hunter
+
+"I've added documentation - is it accurate?"
+→ Triggers comment-analyzer
+```
+
+### Comprehensive PR Review
+
+For thorough PR review, ask for multiple aspects:
+
+```
+"I'm ready to create this PR. Please:
+1. Review test coverage
+2. Check for silent failures
+3. Verify code comments are accurate
+4. Review any new types
+5. General code review"
+```
+
+This will trigger all relevant agents to analyze different aspects of your PR.
+
+### Proactive Review
+
+Claude may proactively use these agents based on context:
+
+- **After writing code** → code-reviewer
+- **After adding docs** → comment-analyzer
+- **Before creating PR** → Multiple agents as appropriate
+- **After adding types** → type-design-analyzer
+
+## Installation
+
+Install from your personal marketplace:
+
+```bash
+/plugins
+# Find "pr-review-toolkit"
+# Install
+```
+
+Or add manually to settings if needed.
+
+## Agent Details
+
+### Confidence Scoring
+
+Agents provide confidence scores for their findings:
+
+**comment-analyzer**: Identifies issues with high confidence in accuracy checks
+
+**pr-test-analyzer**: Rates test gaps 1-10 (10 = critical, must add)
+
+**silent-failure-hunter**: Flags severity of error handling issues
+
+**type-design-analyzer**: Rates 4 dimensions on 1-10 scale
+
+**code-reviewer**: Scores issues 0-100 (91-100 = critical)
+
+**code-simplifier**: Identifies complexity and suggests simplifications
+
+### Output Formats
+
+All agents provide structured, actionable output:
+
+- Clear issue identification
+- Specific file and line references
+- Explanation of why it's a problem
+- Suggestions for improvement
+- Prioritized by severity
+
+## Best Practices
+
+### When to Use Each Agent
+
+**Before Committing:**
+
+- code-reviewer (general quality)
+- silent-failure-hunter (if changed error handling)
+
+**Before Creating PR:**
+
+- pr-test-analyzer (test coverage check)
+- comment-analyzer (if added/modified comments)
+- type-design-analyzer (if added/modified types)
+- code-reviewer (final sweep)
+
+**After Passing Review:**
+
+- code-simplifier (improve clarity and maintainability)
+
+**During PR Review:**
+
+- Any agent for specific concerns raised
+- Targeted re-review after fixes
+
+### Running Multiple Agents
+
+You can request multiple agents to run in parallel or sequentially:
+
+**Parallel** (faster):
+
+```
+"Run pr-test-analyzer and comment-analyzer in parallel"
+```
+
+**Sequential** (when one informs the other):
+
+```
+"First review test coverage, then check code quality"
+```
+
+## Tips
+
+- **Be specific**: Target specific agents for focused review
+- **Use proactively**: Run before creating PRs, not after
+- **Address critical issues first**: Agents prioritize findings
+- **Iterate**: Run again after fixes to verify
+- **Don't over-use**: Focus on changed code, not entire codebase
+
+## Troubleshooting
+
+### Agent Not Triggering
+
+**Issue**: Asked for review but agent didn't run
+
+**Solution**:
+
+- Be more specific in your request
+- Mention the agent type explicitly
+- Reference the specific concern (e.g., "test coverage")
+
+### Agent Analyzing Wrong Files
+
+**Issue**: Agent reviewing too much or wrong files
+
+**Solution**:
+
+- Specify which files to focus on
+- Reference the PR number or branch
+- Mention "recent changes" or "git diff"
+
+## Integration with Workflow
+
+This plugin works great with:
+
+- **build-validator**: Run build/tests before review
+- **Project-specific agents**: Combine with your custom agents
+
+**Recommended workflow:**
+
+1. Write code → **code-reviewer**
+2. Fix issues → **silent-failure-hunter** (if error handling)
+3. Add tests → **pr-test-analyzer**
+4. Document → **comment-analyzer**
+5. Review passes → **code-simplifier** (polish)
+6. Create PR
+
+## Contributing
+
+Found issues or have suggestions? These agents are maintained in:
+
+- User agents: `~/.claude/agents/`
+- Project agents: `.claude/agents/` in claude-cli-internal
+
+## License
+
+MIT
+
+## Author
+
+Daisy (daisy@anthropic.com)
+
+---
+
+**Quick Start**: Just ask for review and the right agent will trigger automatically!