@hienlh/ppm 0.9.81 → 0.9.83

package/.opencode/skills/copywriting/references/workflow-cro.md

@@ -1,83 +0,0 @@
-# CRO (Conversion Rate Optimization) Workflow
-
-Analyze content and optimize for conversion based on user-reported issues.
-
-## Conversion Optimization Framework
-
-25 principles for high-converting copy:
-
-### Headlines & Value Prop
-1. **4-U Headline Formula**: Useful, Unique, Urgent, Ultra-specific (80% won't read past headline)
-2. **Above-Fold Value**: Customer problem focus, no company story, zero scroll required
-3. **Benefit-First Language**: Features tell, benefits sell, transformations compel
-
-### CTAs & Forms
-4. **First-Person CTAs**: "Get MY Guide" vs "Get YOUR Guide" (90% more clicks)
-5. **5-Field Max Forms**: Every field kills conversions, progressive profiling for rest
-6. **Micro-Commitment Ladder**: Small yes → big yes, start email only
-
-### Psychology & Trust
-7. **Message Match**: Ad copy = landing headline, broken promises = bounce
-8. **Social Proof Near CTAs**: Testimonials with faces/names/results at decision points
-9. **Cognitive Bias Stack**: Loss aversion (fear), social proof (FOMO), anchoring (pricing)
-10. **PAS Framework**: Problem → Agitate → Solve, emotion before logic
-
-### Pricing & Urgency
-11. **Genuine Urgency Only**: Real deadlines, actual limits—fake timers destroy trust
-12. **Price Anchoring**: Show expensive option first, real price feels like relief
-13. **Trust Signal Clustering**: Security badges, guarantees, policies visible together
-
-### Layout & UX
-14. **Visual Hierarchy F-Pattern**: Eyes scan F-shape, put conversions in path
-15. **Lead Magnet Hierarchy**: Templates > Checklists > Guides (instant > delayed)
-16. **Objection Preemption**: Address top 3 concerns before they think them, FAQ near CTA
-17. **Mobile Thumb Zone**: CTAs where thumbs naturally rest
-18. **White Space = Focus**: Empty space makes CTAs impossible to miss
-
-### Testing & Optimization
-19. **One-Variable Testing**: Change one thing, measure impact, compound wins
-20. **Post-Conversion Momentum**: Thank you page sells next step while excitement peaks
-21. **Cart Recovery Sequence**: Email 1hr, retarget 4hr, incentive 24hr
-
-### Copy Quality
-22. **Grade 6 Reading Level**: Smart people prefer simple, 11-word sentences, short paragraphs
-23. **TOFU/MOFU/BOFU Logic**: Awareness ≠ decision content, match intent
-24. **Specificity > Vague Claims**: Numbers, timeframes, concrete outcomes
-25. **Weekly Optimization Ritual**: Review Monday, test Tuesday, iterate/scale
-
-## Workflow Steps
-
-1. **Screenshots provided** → Use `ck:ai-multimodal` skill to analyze conversion issues
-2. **Videos provided** → Use `ck:ai-multimodal` video-analysis for bottleneck identification
-3. **URL provided** → Use `web_fetch` tool to fetch and analyze current issues
-4. **Scout codebase** → `/ck:scout ext` (preferred) or `/ck:scout` to find relevant files
-5. **Implement** → Use `fullstack-developer` agent to write enhanced copy into code files
-
-## CRO Plan Creation Workflow
-
-Use when creating a structured CRO optimization plan (e.g., via `/ck:plan --hard` with CRO-specific requirements).
-
-### Steps
-
-1. **Analyze** → Gather issues from screenshots/videos/URLs using steps above
-2. **Activate** `ck:plan` skill for plan structure
-3. **Create plan directory** using naming pattern from `## Naming` section (hook-injected)
-4. **Write `plan.md`** with required YAML frontmatter:
-   ```yaml
-   ---
-   title: "{Brief title}"
-   description: "{One sentence for card preview}"
-   status: pending
-   priority: P2
-   effort: {sum of phases, e.g., 4h}
-   branch: {current git branch}
-   tags: [cro, conversion]
-   created: {YYYY-MM-DD}
-   ---
-   ```
-5. Keep `plan.md` generic, under 80 lines, list each phase with status/progress and links
-6. **Create phase files** (`phase-XX-phase-name.md`) with sections: Context links, Overview (date/priority/statuses), Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps
-7. Keep research markdown reports ≤150 lines with citations
-8. **Wait** for user approval before implementing
-
-Sacrifice grammar for concision. List unresolved questions at end of reports.

package/.opencode/skills/copywriting/references/workflow-enhance.md

@@ -1,32 +0,0 @@
-# Copy Enhancement Workflow
-
-Analyze existing copy issues and enhance for better performance.
-
-## When to Use
-
-- User reports copy problems (unclear messaging, low engagement, weak CTAs)
-- Content needs polish without complete rewrite
-- Quick improvements to existing marketing materials
-
-## Workflow Steps
-
-1. **Screenshots provided** → Use `ck:ai-multimodal` skill to analyze and describe issues in detail
-2. **Videos provided** → Use `ck:ai-multimodal` video-analysis to extract relevant copy issues
-3. **Scout codebase** → `/ck:scout ext` (preferred) or `/ck:scout` to find files needing enhancement
-4. **Implement** → Use `fullstack-developer` agent to write enhanced copy into code files
-
-## Enhancement Checklist
-
-- [ ] Headlines grab attention (4-U formula)
-- [ ] Benefits lead, features follow
-- [ ] CTAs clear and action-oriented
-- [ ] Social proof present
-- [ ] Objections addressed
-- [ ] Reading level appropriate (Grade 6-8)
-- [ ] Mobile-friendly formatting
-
-## Related References
-
-- `workflow-cro.md` - Full CRO framework
-- `copy-formulas.md` - AIDA, PAS, BAB structures
-- `headline-templates.md` - Headline patterns

package/.opencode/skills/copywriting/references/workflow-fast.md

@@ -1,29 +0,0 @@
-# Fast Copy Workflow
-
-Quick, creative copy generation with minimal research.
-
-## When to Use
-
-- Simple copy requests (social posts, short descriptions)
-- Time-sensitive content needs
-- Clear context already provided
-
-## Workflow Steps
-
-1. **Screenshots provided** → Use `ck:ai-multimodal` skill to analyze context
-2. **Videos provided** → Use `ck:ai-multimodal` video-analysis for context
-3. **Write** → Use `fullstack-developer` agent directly to produce copy
-
-## Speed Optimization
-
-- Skip research phase—use provided context
-- Apply formulas from `copy-formulas.md` directly
-- Single-pass writing, minimal revision
-
-## Best For
-
-- Social media posts
-- Short product descriptions
-- Quick email drafts
-- Ad variations
-- Micro-copy (buttons, labels, tooltips)

package/.opencode/skills/copywriting/references/workflow-good.md

@@ -1,39 +0,0 @@
-# Quality Copy Workflow
-
-Thorough copy development with research, planning, and execution.
-
-## When to Use
-
-- High-stakes content (landing pages, sales pages, campaigns)
-- Complex products/services requiring deep understanding
-- Brand-critical messaging
-
-## Workflow Steps
-
-1. **Screenshots provided** → Use `ck:ai-multimodal` skill for detailed context analysis
-2. **Videos provided** → Use `ck:ai-multimodal` video-analysis for comprehensive context
-3. **Research** → Spawn multiple `researcher` agents in parallel:
-   - Competitor messaging analysis
-   - Target audience insights
-   - Industry best practices
-   - Product/service details
-4. **Scout codebase** → `/ck:scout ext` (preferred) or `/ck:scout` to find relevant files
-5. **Plan** → Use `planner` agent to outline copy structure and strategy
-6. **Write** → Use `fullstack-developer` agent to execute plan
-
-## Quality Checklist
-
-- [ ] Research validates messaging direction
-- [ ] Plan reviewed against user requirements
-- [ ] Copy follows chosen formula (AIDA, PAS, etc.)
-- [ ] Multiple headline options provided
-- [ ] CTAs tested for clarity
-- [ ] Social proof integrated
-- [ ] Objections anticipated and addressed
-
-## Related References
-
-- `copy-formulas.md` - Core copywriting structures
-- `headline-templates.md` - Headline variations
-- `landing-page-copy.md` - Page structure
-- `writing-styles.md` - Voice and tone options

package/.opencode/skills/copywriting/references/writing-styles.md

@@ -1,247 +0,0 @@
-# Writing Styles Guide
-
-Define, extract, and apply consistent writing voices across content.
-
-## Style Dimensions Framework
-
-Every writing style can be mapped across these dimensions:
-
-| Dimension | Spectrum | Description |
-|-----------|----------|-------------|
-| Tone | Formal ↔ Casual | How official or relaxed |
-| Pace | Fast ↔ Measured | Sentence length, rhythm |
-| Vocabulary | Simple ↔ Technical | Word complexity level |
-| Emotion | Reserved ↔ Expressive | Emotional intensity |
-| Humor | Serious ↔ Playful | Use of wit, jokes |
-| Perspective | Third-person ↔ First-person | Pronoun usage |
-| Authority | Peer ↔ Expert | Positioning relative to reader |
-
-## Pre-Built Style Definitions
-
-### Casual Conversational
-
-**Best for:** Indie hackers, startups, personal brands
-
-**Dimensions:**
-- Tone: Casual
-- Pace: Fast
-- Vocabulary: Simple
-- Emotion: Expressive
-- Humor: Playful
-- Perspective: First-person
-
-**Characteristics:**
-- Contractions ("you're", "isn't")
-- Short sentences, fragments OK
-- Personal pronouns ("I", "you")
-- Informal transitions ("So here's the thing...")
-- Emoji usage acceptable
-
-**Example:**
-> "Look, I get it. Marketing feels overwhelming. But here's what I learned after burning through $10k on ads that didn't work—it doesn't have to be complicated."
-
----
-
-### Professional Authoritative
-
-**Best for:** Enterprise SaaS, B2B, consulting
-
-**Dimensions:**
-- Tone: Formal
-- Pace: Measured
-- Vocabulary: Technical
-- Emotion: Reserved
-- Humor: Serious
-- Perspective: Third-person / We
-
-**Characteristics:**
-- Complete sentences
-- Industry terminology
-- Data-driven claims
-- Formal transitions
-- No emoji
-
-**Example:**
-> "Organizations that implement structured content strategies outperform competitors by 3.5x in lead generation. This comprehensive guide examines the frameworks that drive measurable results."
-
----
-
-### Edgy Provocative
-
-**Best for:** Disruptor brands, hot takes, thought leadership
-
-**Dimensions:**
-- Tone: Casual-to-Formal (varies)
-- Pace: Fast
-- Vocabulary: Simple with punchy terms
-- Emotion: Expressive
-- Humor: Playful but sharp
-- Perspective: First-person
-
-**Characteristics:**
-- Bold claims
-- Contrarian positions
-- Short, punchy sentences
-- Pattern interrupts
-- Strategic use of questions
-
-**Example:**
-> "Everything you know about content marketing is wrong. Seriously. The 'best practices' everyone follows? They're why you're invisible. Let me show you what actually works."
-
----
-
-### Luxe Minimalist
-
-**Best for:** Premium products, luxury brands, high-end services
-
-**Dimensions:**
-- Tone: Formal
-- Pace: Measured, spacious
-- Vocabulary: Elegant, selective
-- Emotion: Reserved but refined
-- Humor: Subtle or absent
-- Perspective: Second-person
-
-**Characteristics:**
-- Fewer words, more impact
-- White space between ideas
-- Refined vocabulary
-- Understated confidence
-- No hard sell
-
-**Example:**
-> "Exceptional results require exceptional attention. We work with founders who understand that true growth cannot be rushed. By invitation only."
-
----
-
-### Warm Supportive
-
-**Best for:** Wellness, coaching, education, community
-
-**Dimensions:**
-- Tone: Casual
-- Pace: Measured
-- Vocabulary: Simple
-- Emotion: Expressive
-- Humor: Gentle
-- Perspective: First-person plural ("we")
-
-**Characteristics:**
-- Empathetic language
-- Inclusive pronouns
-- Encouraging tone
-- Validation before advice
-- Gentle CTAs
-
-**Example:**
-> "It's okay if you're feeling stuck. We've all been there. The journey isn't always linear, and that's completely normal. Let's explore some gentle ways to move forward together."
-
----
-
-### Technical Educator
-
-**Best for:** Developer content, technical tutorials, documentation
-
-**Dimensions:**
-- Tone: Neutral-to-Casual
-- Pace: Measured
-- Vocabulary: Technical but explained
-- Emotion: Reserved
-- Humor: Dry/nerdy
-- Perspective: Second-person
-
-**Characteristics:**
-- Code examples
-- Step-by-step structure
-- Precise terminology
-- Assumes competence
-- Occasional dry humor
-
-**Example:**
-> "Here's the thing about async/await—it's not magic, it's just syntactic sugar over Promises. Let's break down what's actually happening under the hood, and why your code isn't working the way you expect."
-
-## Style Extraction Prompt
-
-Use this prompt to analyze existing content and extract its style:
-
-```
-Analyze this content and extract the writing style:
-
-[PASTE CONTENT]
-
-Provide:
-1. Tone (formal ↔ casual):
-2. Pace (fast ↔ measured):
-3. Vocabulary (simple ↔ technical):
-4. Emotion (reserved ↔ expressive):
-5. Humor (serious ↔ playful):
-6. Perspective (pronoun usage):
-7. Sentence structure patterns:
-8. Signature phrases/patterns:
-9. What to DO in this style:
-10. What to AVOID in this style:
-```
-
-## Style Application Prompt
-
-Use this prompt to write in a specific style:
-
-```
-Write [CONTENT TYPE] in the following style:
-
-**Tone:** [casual/formal]
-**Pace:** [fast/measured]
-**Vocabulary:** [simple/technical]
-**Emotion:** [reserved/expressive]
-**Perspective:** [first/second/third person]
-
-**DO:**
-- [specific patterns to use]
-
-**DON'T:**
-- [patterns to avoid]
-
-Topic: [TOPIC]
-```
-
-## Writing Style File Format
-
-Store custom styles in `assets/writing-styles/`:
-
-```yaml
-# assets/writing-styles/indie-hacker.yaml
-name: Indie Hacker
-description: Authentic, scrappy, behind-the-scenes vibe
-
-dimensions:
-  tone: casual
-  pace: fast
-  vocabulary: simple
-  emotion: expressive
-  humor: self-deprecating
-  perspective: first-person
-
-patterns:
-  - Short sentences
-  - Fragments for emphasis
-  - Numbers and specifics
-  - "Here's what I learned"
-  - Behind-the-scenes honesty
-
-avoid:
-  - Corporate speak
-  - Passive voice
-  - Vague claims
-  - Salesy language
-
-examples:
-  - "Shipped v1 in 48 hours. It was broken. People loved it anyway."
-  - "Revenue last month: $4,293. Not life-changing, but real."
-```
-
-## Integration
-
-Use with:
-- `brand` skill - Align with brand voice
-- `/youtube:blog` command - Apply style to video-to-article
-- `/content:good` command - Style-aware content generation