bobo-ai-cli 1.0.1

package/knowledge/skills/copywriting.md

@@ -0,0 +1,510 @@
+---
+id: "copywriting"
+title: "Copywriting"
+category: "marketing"
+tags: ["copywriting", "before writing", "copywriting principles", "writing style rules", "best practices", "page structure framework", "landing page section variety", "cta copy guidelines", "output format", "page-specific guidance"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/copywriting"
+---
+
+---
+name: copywriting
+description: When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
+---
+
+# Copywriting
+
+You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.
+
+## Before Writing
+
+Gather this context (ask if not provided):
+
+### 1. Page Purpose
+
+- What type of page is this? (homepage, landing page, pricing, feature, about)
+- What is the ONE primary action you want visitors to take?
+- What's the secondary action (if any)?
+
+### 2. Audience
+
+- Who is the ideal customer for this page?
+- What problem are they trying to solve?
+- What have they already tried?
+- What objections or hesitations do they have?
+- What language do they use to describe their problem?
+
+### 3. Product/Offer
+
+- What are you selling or offering?
+- What makes it different from alternatives?
+- What's the key transformation or outcome?
+- Any proof points (numbers, testimonials, case studies)?
+
+### 4. Context
+
+- Where is traffic coming from? (ads, organic, email)
+- What do visitors already know before arriving?
+- What messaging are they seeing before this page?
+
+---
+
+## Copywriting Principles
+
+### Clarity Over Cleverness
+
+- If you have to choose between clear and creative, choose clear
+- Every sentence should have one job
+- Remove words that don't add meaning
+
+### Benefits Over Features
+
+- Features: What it does
+- Benefits: What that means for the customer
+- Always connect features to outcomes
+
+### Specificity Over Vagueness
+
+- Vague: "Save time on your workflow"
+- Specific: "Cut your weekly reporting from 4 hours to 15 minutes"
+
+### Customer Language Over Company Language
+
+- Use words your customers use
+- Avoid jargon unless your audience uses it
+- Mirror voice-of-customer from reviews, interviews, support tickets
+
+### One Idea Per Section
+
+- Don't try to say everything everywhere
+- Each section should advance one argument
+- Build a logical flow down the page
+
+---
+
+## Writing Style Rules
+
+Follow these core principles. For detailed editing checks and word-by-word polish, use the **copy-editing** skill after your initial draft.
+
+### Core Style Principles
+
+1. **Simple over complex** — Use everyday words. "Use" instead of "utilize," "help" instead of "facilitate."
+
+2. **Specific over vague** — Avoid words like "streamline," "optimize," "innovative" that sound good but mean nothing.
+
+3. **Active over passive** — "We generate reports" not "Reports are generated."
+
+4. **Confident over qualified** — Remove hedging words like "almost," "very," "really."
+
+5. **Show over tell** — Describe the outcome instead of using adverbs like "instantly" or "easily."
+
+6. **Honest over sensational** — Never fabricate statistics, claims, or testimonials.
+
+### Quick Quality Check
+
+Before finalizing, scan for:
+
+- Jargon that could confuse outsiders
+- Sentences trying to do too much (max 3 conjunctions)
+- Passive voice constructions
+- Exclamation points (remove them)
+- Marketing buzzwords without substance
+
+For a thorough line-by-line review, run the copy through the **copy-editing** skill's Seven Sweeps framework.
+
+---
+
+## Best Practices
+
+### Be Direct
+
+Get to the point. Don't bury the value in qualifications.
+
+❌ Slack lets you share files instantly, from documents to images, directly in your conversations
+
+✅ Need to share a screenshot? Send as many documents, images, and audio files as your heart desires.
+
+### Use Rhetorical Questions
+
+Questions engage readers and make them think about their own situation.
+
+✅ Hate returning stuff to Amazon?
+
+✅ Need to share a screenshot?
+
+✅ Tired of chasing approvals?
+
+### Use Analogies and Metaphors
+
+When appropriate, analogies make abstract concepts concrete and memorable.
+
+❌ Slack lets you share files instantly, from documents to images, directly in your conversations
+
+✅ Imagine Slack's file-sharing as a digital whiteboard where everyone can post files, images, and updates in real time.
+
+### Pepper in Humor (When Appropriate)
+
+Puns, wit, and humor make copy memorable—but only if it fits the brand and doesn't undermine clarity.
+
+---
+
+## Page Structure Framework
+
+### Above the Fold (First Screen)
+
+**Headline**
+
+- Your single most important message
+- Should communicate core value proposition
+- Specific > generic
+
+**Headline Formulas:**
+
+**{Achieve desirable outcome} without {pain point}**
+_Example: Understand how users are really experiencing your site without drowning in numbers_
+
+**The {opposite of usual process} way to {achieve desirable outcome}**
+_Example: The easiest way to turn your passion into income_
+
+**Never {unpleasant event} again**
+_Example: Never miss a sales opportunity again_
+
+**{Key feature/product type} for {target audience}**
+_Example: Advanced analytics for Shopify e-commerce_
+
+**{Key feature/product type} for {target audience} to {what it's used for}**
+_Example: An online whiteboard for teams to ideate and brainstorm together_
+
+**You don't have to {skills or resources} to {achieve desirable outcome}**
+_Example: With Ahrefs, you don't have to be an SEO pro to rank higher and get more traffic_
+
+**{Achieve desirable outcome} by {how product makes it possible}**
+_Example: Generate more leads by seeing which companies visit your site_
+
+**{Key benefit of your product}**
+_Example: Sound clear in online meetings_
+
+**{Question highlighting the main pain point}**
+_Example: Hate returning stuff to Amazon?_
+
+**Turn {input} into {outcome}**
+_Example: Turn your hard-earned sales into repeat customers_
+
+**Additional formulas:**
+
+- "[Achieve outcome] in [timeframe]"
+- "The [category] that [key differentiator]"
+- "Stop [pain]. Start [pleasure]."
+- "[Number] [people] use [product] to [outcome]"
+
+**Subheadline**
+
+- Expands on the headline
+- Adds specificity or addresses secondary concern
+- 1-2 sentences max
+
+**Primary CTA**
+
+- Action-oriented button text
+- Communicate what they get, not what they do
+- "Start Free Trial" > "Sign Up"
+- "Get Your Report" > "Submit"
+
+**Supporting Visual**
+
+- Product screenshot, demo, or hero image
+- Should reinforce the message, not distract
+
+### Social Proof Section
+
+Options (use 1-2):
+
+- Customer logos (recognizable > many)
+- Key metric ("10,000+ teams")
+- Short testimonial with attribution
+- Star rating with review count
+
+### Problem/Pain Section
+
+- Articulate the problem better than they can
+- Show you understand their situation
+- Create recognition ("that's exactly my problem")
+
+Structure:
+
+- "You know the feeling..." or "If you're like most [role]..."
+- Describe the specific frustrations
+- Hint at the cost of not solving it
+
+### Solution/Benefits Section
+
+- Bridge from problem to your solution
+- Focus on 3-5 key benefits (not 10)
+- Each benefit: headline + short explanation + proof point if available
+
+Format options:
+
+- Benefit blocks with icons
+- Before/after comparison
+- Feature → Benefit → Proof structure
+
+### How It Works Section
+
+- Reduce perceived complexity
+- 3-4 step process
+- Each step: simple action + outcome
+
+Example:
+
+1. "Connect your tools (2 minutes)"
+2. "Set your preferences"
+3. "Get automated reports every Monday"
+
+### Social Proof (Detailed)
+
+- Full testimonials with:
+  - Specific results
+  - Customer name, role, company
+  - Photo if possible
+- Case study snippets
+- Logos section (if not above)
+
+### Objection Handling
+
+Common objections to address:
+
+- "Is this right for my situation?"
+- "What if it doesn't work?"
+- "Is it hard to set up?"
+- "How is this different from X?"
+
+Formats:
+
+- FAQ section
+- Comparison table
+- Guarantee/promise section
+- "Built for [specific audience]" section
+
+### Final CTA Section
+
+- Recap the value proposition
+- Repeat the primary CTA
+- Add urgency if genuine (deadline, limited availability)
+- Risk reversal (guarantee, free trial, no credit card)
+
+---
+
+## Landing Page Section Variety
+
+A great landing page isn't just a list of features. Use a variety of section types to create an engaging, persuasive narrative. Mix and match from these:
+
+### Section Types to Include
+
+**How It Works (Numbered Steps)**
+Walk users through the process in 3-4 clear steps. Reduces perceived complexity and shows the path to value.
+
+**Alternative/Competitor Comparison**
+Show how you stack up against the status quo or competitors. Tables, side-by-side comparisons, or "Unlike X, we..." sections.
+
+**Founder Manifesto / Our Story**
+Share why you built this and what you believe. Creates emotional connection and differentiates from faceless competitors.
+
+**Testimonials**
+Customer quotes with names, photos, and specific results. Multiple formats: quote cards, video testimonials, tweet embeds.
+
+**Case Studies**
+Deeper stories of customer success. Problem → Solution → Results format with specific metrics.
+
+**Use Cases**
+Show different ways the product is used. Helps visitors self-identify: "This is for people like me."
+
+**Personas / "Built For" Sections**
+Explicitly call out who the product is for: "Perfect for marketers," "Built for agencies," etc.
+
+**Stats and Social Proof**
+Key metrics that build credibility: "10,000+ customers," "4.9/5 rating," "$2M saved for customers."
+
+**Demo / Product Tour**
+Interactive demos, video walkthroughs, or GIF previews showing the product in action.
+
+**FAQ Section**
+Address common objections and questions. Good for SEO and reducing support burden.
+
+**Integrations / Partners**
+Show what tools you connect with. Logos build credibility and answer "Will this work with my stack?"
+
+**Pricing Preview**
+Even on non-pricing pages, a pricing teaser can move decision-makers forward.
+
+**Guarantee / Risk Reversal**
+Money-back guarantee, free trial terms, or "cancel anytime" messaging reduces friction.
+
+### Recommended Section Mix
+
+For a landing page, aim for variety. Don't just stack features:
+
+**Typical Feature-Heavy Page (Weak):**
+
+1. Hero
+2. Feature 1
+3. Feature 2
+4. Feature 3
+5. Feature 4
+6. CTA
+
+**Varied, Engaging Page (Strong):**
+
+1. Hero with clear value prop
+2. Social proof bar (logos or stats)
+3. Problem/pain section
+4. How it works (3 steps)
+5. Key benefits (2-3, not 10)
+6. Testimonial
+7. Use cases or personas
+8. Comparison to alternatives
+9. Case study snippet
+10. FAQ
+11. Final CTA with guarantee
+
+---
+
+## CTA Copy Guidelines
+
+**Weak CTAs (avoid):**
+
+- Submit
+- Sign Up
+- Learn More
+- Click Here
+- Get Started
+
+**Strong CTAs (use):**
+
+- Start Free Trial
+- Get [Specific Thing]
+- See [Product] in Action
+- Create Your First [Thing]
+- Book My Demo
+- Download the Guide
+- Try It Free
+
+**CTA formula:**
+[Action Verb] + [What They Get] + [Qualifier if needed]
+
+Examples:
+
+- "Start My Free Trial"
+- "Get the Complete Checklist"
+- "See Pricing for My Team"
+
+---
+
+## Output Format
+
+When writing copy, provide:
+
+### Page Copy
+
+Organized by section with clear labels:
+
+- Headline
+- Subheadline
+- CTA
+- Section headers
+- Body copy
+- Secondary CTAs
+
+### Annotations
+
+For key elements, explain:
+
+- Why you made this choice
+- What principle it applies
+- Alternatives considered
+
+### Alternatives
+
+For headlines and CTAs, provide 2-3 options:
+
+- Option A: [copy] — [rationale]
+- Option B: [copy] — [rationale]
+- Option C: [copy] — [rationale]
+
+### Meta Content (if relevant)
+
+- Page title (for SEO)
+- Meta description
+
+---
+
+## Page-Specific Guidance
+
+### Homepage Copy
+
+- Serve multiple audiences without being generic
+- Lead with broadest value proposition
+- Provide clear paths for different visitor intents
+- Balance "ready to buy" and "still researching"
+
+### Landing Page Copy
+
+- Single message, single CTA
+- Match headline to ad/traffic source
+- Complete argument on one page
+- Remove distractions (often no nav)
+
+### Pricing Page Copy
+
+- Help visitors choose the right plan
+- Clarify what's included at each level
+- Address "which is right for me?" anxiety
+- Make recommended plan obvious
+
+### Feature Page Copy
+
+- Connect feature to benefit to outcome
+- Show use cases and examples
+- Differentiate from competitors' versions
+- Clear path to try or buy
+
+### About Page Copy
+
+- Tell the story of why you exist
+- Connect company mission to customer benefit
+- Build trust through transparency
+- Still include a CTA (it's still a marketing page)
+
+---
+
+## Voice and Tone Considerations
+
+Before writing, establish:
+
+**Formality level:**
+
+- Casual/conversational
+- Professional but friendly
+- Formal/enterprise
+
+**Brand personality:**
+
+- Playful or serious?
+- Bold or understated?
+- Technical or accessible?
+
+Maintain consistency throughout, but adjust intensity:
+
+- Headlines can be bolder
+- Body copy should be clearer
+- CTAs should be action-oriented
+
+---
+
+## Related Skills
+
+- **copy-editing**: For polishing and improving existing copy (use after writing your first draft)
+- **page-cro**: If the page structure/strategy needs work, not just copy
+- **email-sequence**: For email copywriting
+- **popup-cro**: For popup and modal copy
+- **ab-test-setup**: To test copy variations properly

package/knowledge/skills/csharp-lsp.md

@@ -0,0 +1,40 @@
+---
+id: "csharp-lsp"
+title: "csharp-lsp"
+category: "other"
+tags: ["csharp-lsp", "supported extensions", "installation", "requirements", "more information"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/csharp-lsp"
+---
+
+# csharp-lsp
+
+C# language server for Claude Code, providing code intelligence and diagnostics.
+
+## Supported Extensions
+
+`.cs`
+
+## Installation
+
+### Via .NET tool (recommended)
+
+```bash
+dotnet tool install --global csharp-ls
+```
+
+### Via Homebrew (macOS)
+
+```bash
+brew install csharp-ls
+```
+
+## Requirements
+
+- .NET SDK 6.0 or later
+
+## More Information
+
+- [csharp-ls GitHub](https://github.com/razzmatazz/csharp-language-server)
+- [.NET SDK Download](https://dotnet.microsoft.com/download)

package/knowledge/skills/decision-making-framework.md

@@ -0,0 +1,154 @@
+---
+id: "decision-making-framework"
+title: "Decision Making Framework"
+category: "agent-engineering"
+tags: ["decision making framework", "decision modes", "decision triggers", "high-agency behaviors", "structured decision template", "anti-patterns (avoid)", "integration with work mode"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/decision-making-framework"
+---
+
+---
+name: decision-making-framework
+description: Unified decision framework - combines high-agency (autonomous decisions) + structured-decision-alignment (systematic decision-making). Use when facing complex choices, architectural decisions, or conflicting requirements.
+---
+
+# Decision Making Framework
+
+> **Merged from**: high-agency + structured-decision-alignment
+> **Core principle**: Decide fast, decide well, decide once
+
+## Decision Modes
+
+### Mode 1: Autonomous (95% of decisions)
+
+For decisions where the codebase, conventions, or best practices provide clear guidance:
+
+```
+1. Check existing patterns in codebase
+2. Apply the most common convention
+3. Execute without asking
+4. Document the choice in commit message
+```
+
+**Examples**: File naming, code style, dependency versions, UI details, test strategy
+
+### Mode 2: Structured (4% of decisions)
+
+For decisions with multiple valid approaches:
+
+```
+1. State the decision clearly
+2. List top 2-3 options with trade-offs
+3. Apply scoring matrix
+4. Choose highest-scoring option
+5. Document reasoning
+```
+
+**Scoring Matrix**:
+| Criterion | Weight |
+|-----------|--------|
+| Maintains existing patterns | 3x |
+| Simpler implementation | 2x |
+| Better performance | 2x |
+| Easier to test | 1x |
+| More flexible | 1x |
+
+### Mode 3: Blocking (1% of decisions)
+
+Only 4 situations require user input:
+1. **Missing credentials** — API keys, passwords, private keys
+2. **Opposing approaches** — REST vs GraphQL, SQL vs NoSQL
+3. **Contradictory requirements** — "Fast but perfect"
+4. **Irreversible risk** — Delete production data, force push
+
+---
+
+## Decision Triggers
+
+| Signal | Mode | Action |
+|--------|------|--------|
+| Codebase has existing pattern | Autonomous | Follow it |
+| Best practice is clear | Autonomous | Apply it |
+| Language convention exists | Autonomous | Use it |
+| 2+ equally valid approaches | Structured | Score and choose |
+| Requirements contradict | Blocking | Ask user |
+| Risk is irreversible | Blocking | Confirm with user |
+
+---
+
+## High-Agency Behaviors
+
+### Do Immediately (No Permission Needed)
+- Create files following project conventions
+- Install needed dependencies
+- Run tests to verify changes
+- Fix obvious bugs encountered
+- Refactor to follow existing patterns
+
+### Do After Documenting Intent
+- Architecture changes (document in commit)
+- New feature additions (document in plan)
+- Performance optimizations (document why)
+
+### Never Do Without Explicit Permission
+- Delete production data
+- Force push to shared branches
+- Modify CI/CD pipelines
+- Send messages to external services
+- Upload sensitive content
+
+---
+
+## Structured Decision Template
+
+When facing a non-trivial decision:
+
+```markdown
+## Decision: [What needs to be decided]
+
+### Context
+[Why this decision is needed]
+
+### Options Considered
+1. **Option A**: [Description]
+   - Pros: [...]
+   - Cons: [...]
+   - Score: [X/10]
+
+2. **Option B**: [Description]
+   - Pros: [...]
+   - Cons: [...]
+   - Score: [X/10]
+
+### Decision
+**Chosen**: Option [X]
+**Reason**: [Why]
+**Trade-off**: [What we give up]
+```
+
+---
+
+## Anti-Patterns (Avoid)
+
+1. **Analysis Paralysis** — Spending more time deciding than doing
+2. **Premature Abstraction** — Designing for hypothetical futures
+3. **Bikeshedding** — Debating trivial details
+4. **Decision Reversal** — Reopening closed decisions without new information
+
+---
+
+## Integration with Work Mode
+
+```
+Receive task
+  ↓
+Quick plan → TodoList
+  ↓
+For each step:
+  ├─ Can decide autonomously? → Execute
+  ├─ Need structured analysis? → Score and choose
+  └─ Hit blocking condition? → Ask user (4 types only)
+  ↓
+Complete and verify
+```