@hienlh/ppm 0.9.81 → 0.9.83

package/.opencode/skills/email/references/flow.md

@@ -1,165 +0,0 @@
-# Email Flow Generator
-
-Create complete email automation sequences with timing, content, and decision branches.
-
-<flow_request>$ARGUMENTS</flow_request>
-
-## Workflow
-
-1. **Identify Flow Type**
-   - Activate `email` skill
-   - Load `references/automation-flows.md` for templates
-   - Match request to flow template:
-
-   | Flow Type | Trigger | Duration |
-   |-----------|---------|----------|
-   | welcome | New subscriber | 14 days |
-   | cart | Abandoned cart | 7 days |
-   | onboarding | New customer | 30 days |
-   | nurture | Lead magnet download | 21 days |
-   | re-engagement | Inactive 60+ days | 21 days |
-   | upsell | Purchase complete | 30 days |
-   | renewal | Subscription expiring | 30 days |
-   | webinar | Webinar registration | 7 days |
-   | custom | User-defined | Variable |
-
-2. **Gather Context**
-   - Inject brand context:
-     ```bash
-     node .opencode/skills/brand/scripts/inject-brand-context.cjs --json
-     ```
-   - Determine:
-     - Product/service being promoted
-     - Target audience
-     - Desired conversion action
-     - Available personalization data
-
-3. **Generate Sequence Structure**
-   - Number of emails
-   - Timing/delays between emails
-   - Decision branches (opened/clicked/purchased)
-   - Exit conditions
-
-4. **Create Email Content**
-   - Activate `copywriting` skill for formulas
-   - Load `references/subject-line-formulas.md`
-   - For each email:
-     - Subject line (with A/B variant)
-     - Preview text
-     - Body copy (using PAS, AIDA, etc.)
-     - CTA
-
-5. **Output**
-   - Complete sequence → `assets/emails/flows/{flow-type}-{date}.md`
-   - Visual flow diagram (ASCII art)
-   - Implementation notes for email platform
-
-## Skills Used
-
-- `email` - Flow templates, best practices
-- `copywriting` - Subject lines, body copy
-- `brand` - Voice consistency
-- `assets-organizing` - Standardized output paths
-
-## Agents Used
-
-- `email-wizard` - Email sequence generation
-- `copywriter` - Conversion copy
-
-## Flow Types
-
-### welcome
-New subscriber welcome sequence (5 emails, 14 days)
-
-### cart
-Abandoned cart recovery (4 emails, 7 days)
-
-### onboarding
-New customer onboarding (7 emails, 30 days)
-
-### nurture
-Lead nurturing after download (5 emails, 21 days)
-
-### re-engagement
-Win-back inactive subscribers (4 emails, 21 days)
-
-### upsell
-Cross-sell after purchase (3 emails, 30 days)
-
-### renewal
-Subscription renewal sequence (4 emails, 30 days)
-
-### webinar
-Webinar registration to follow-up (5 emails, 7 days)
-
-### custom
-Describe your custom trigger and goal
-
-## Output Format
-
-```markdown
-# Email Flow: [Flow Name]
-
-**Trigger:** [What starts this flow]
-**Goal:** [Desired conversion]
-**Duration:** [X days]
-**Emails:** [X emails]
-
----
-
-## Flow Diagram
-
-```
-Trigger → Email 1 → Wait → [Condition?]
-                           ├─ Yes → Email 2A
-                           └─ No → Email 2B
-```
-
----
-
-## Email 1: [Name]
-
-**Send:** Immediately / Day X
-**Subject A:** [Subject line]
-**Subject B:** [A/B variant]
-**Preview:** [Preheader text]
-
-### Body
-
-[Email copy using copywriting formulas]
-
-**CTA:** [Button text]
-
----
-
-## Email 2: [Name]
-
-...
-
----
-
-## Implementation Notes
-
-- **Platform:** [Mailchimp/ConvertKit/etc.]
-- **Segments:** [Required segments]
-- **Tags:** [Tags to apply]
-- **Exit conditions:** [When to stop flow]
-```
-
-## Examples
-
-```bash
-# Pre-built flows
-/email:flow welcome
-/email:flow cart
-/email:flow onboarding
-/email:flow re-engagement
-
-# With goal context
-/email:flow nurture "convert to paid plan"
-/email:flow upsell "sell annual upgrade"
-
-# Custom flows
-/email:flow custom "trial expiring, convert to paid"
-/email:flow custom "course launch sequence for webinar attendees"
-```

package/.opencode/skills/email/references/sequence.md

@@ -1,166 +0,0 @@
-# Email Sequence Generator
-
-Generate a complete email sequence with full copy, subject lines, and timing.
-
-<sequence_input>$ARGUMENTS</sequence_input>
-
-## Sequence Types
-
-| Type | Emails | Duration | Purpose |
-|------|--------|----------|---------|
-| `welcome` | 5 | 14 days | Build relationship, introduce offer |
-| `onboarding` | 7 | 21 days | Product activation, feature discovery |
-| `nurture` | 6 | 30 days | Educate, build trust, soft sell |
-| `abandon` | 3 | 3 days | Recover cart/signup abandonment |
-| `winback` | 4 | 14 days | Re-engage inactive users |
-| `launch` | 5 | 7 days | Product launch countdown |
-
-## Workflow
-
-### Step 1: Parse Input
-
-Extract sequence type and context:
-- `welcome` → New subscriber welcome series
-- `onboarding "SaaS tool"` → Product-specific onboarding
-- `launch "Black Friday"` → Campaign-specific launch
-
-### Step 2: Inject Brand Context
-
-```bash
-node .opencode/skills/brand/scripts/inject-brand-context.cjs --json
-```
-
-Extract: brand voice, tone, prohibited words, CTA style.
-
-### Step 3: Load Email Templates
-
-Activate `email` skill and read:
-- `.opencode/skills/email/references/automation-flows.md`
-- `.opencode/skills/email/references/subject-line-formulas.md`
-- `.opencode/skills/email/references/email-templates.md`
-
-### Step 4: Generate Sequence Plan
-
-Create sequence architecture:
-
-```
-SEQUENCE: {type}
-TRIGGER: {event}
-DURATION: {days}
-GOAL: {conversion goal}
-
-EMAIL 1 (Day 0)
-├── Purpose: {purpose}
-├── Subject: {subject line}
-├── Hook: {opening line}
-├── Body: {main content}
-├── CTA: {call to action}
-└── Next: Wait {n} days
-
-EMAIL 2 (Day {n})
-...
-```
-
-### Step 5: Write Full Email Copy
-
-For each email, generate:
-1. **Subject line** (3 variants using formulas)
-2. **Preview text** (40-90 chars)
-3. **Opening hook** (pattern interrupt)
-4. **Body copy** (using PAS/AIDA)
-5. **CTA button** (action-oriented)
-6. **P.S. line** (urgency/social proof)
-
-### Step 6: Add Automation Logic
-
-Include branching conditions:
-- Opened? → Engaged path
-- Clicked? → Interest path
-- Purchased? → Exit flow
-- No action? → Reminder path
-
-### Step 7: Save Output
-
-```
-assets/copy/emails/{date}-{type}-sequence/
-├── 00-sequence-plan.md
-├── 01-{purpose}.md
-├── 02-{purpose}.md
-├── 03-{purpose}.md
-├── 04-{purpose}.md
-└── 05-{purpose}.md
-```
-
-## Output Format
-
-### Sequence Plan (00-sequence-plan.md)
-
-```markdown
-# {Type} Email Sequence
-
-## Overview
-- **Trigger:** {trigger event}
-- **Emails:** {count}
-- **Duration:** {days}
-- **Goal:** {conversion goal}
-
-## Flow Diagram
-{ASCII flow diagram}
-
-## Timing
-| Email | Day | Subject | Purpose |
-|-------|-----|---------|---------|
-| 1 | 0 | ... | ... |
-| 2 | 1 | ... | ... |
-
-## Exit Conditions
-- {condition 1}
-- {condition 2}
-```
-
-### Individual Email (01-welcome.md)
-
-```markdown
-# Email 1: {Title}
-
-**Day:** 0 (Immediate)
-**Purpose:** {purpose}
-
-## Subject Lines (Pick One)
-1. {subject 1}
-2. {subject 2}
-3. {subject 3}
-
-## Preview Text
-{40-90 char preview}
-
-## Email Body
-
-{Full email copy with formatting}
-
-## CTA
-**Button:** {CTA text}
-**Link:** {destination}
-
-## P.S.
-{urgency or social proof}
-
----
-*Next email: Day {n} - {next purpose}*
-```
-
-## Examples
-
-```bash
-/email:sequence welcome
-/email:sequence onboarding "project management SaaS"
-/email:sequence launch "New Year sale 40% off"
-/email:sequence abandon "checkout"
-/email:sequence nurture "B2B lead magnet"
-```
-
-## Skills Used
-
-- `email` - Sequence templates, timing, automation
-- `copywriting` - Email copy formulas, subject lines
-- `brand` - Voice, tone, CTA style

package/.opencode/skills/email/references/subject-line-formulas.md

@@ -1,67 +0,0 @@
-# Subject Line Formulas
-
-## High-Converting Formulas
-
-### Curiosity Gap
-- "The [topic] secret nobody talks about"
-- "What [successful people] know that you don't"
-- "I was wrong about [topic]"
-
-### How-To
-- "How to [achieve result] in [timeframe]"
-- "How [name] went from [A] to [B]"
-- "How to [goal] without [pain point]"
-
-### List/Number
-- "[Number] ways to [achieve outcome]"
-- "[Number] mistakes killing your [metric]"
-- "The [number]-step system for [result]"
-
-### Question
-- "Are you making this [topic] mistake?"
-- "What if [dream scenario]?"
-- "Ready to [achieve goal]?"
-
-### Urgency/Scarcity
-- "[X hours] left: [offer]"
-- "Last chance: [benefit]"
-- "Ending tonight: [specific offer]"
-
-### Personal
-- "[First name], quick question"
-- "I noticed something about your [behavior]"
-- "A gift for you, [First name]"
-
-### Social Proof
-- "How [company] achieved [result]"
-- "[Number] people already [action]"
-- "Join [number]+ [audience] who [benefit]"
-
-## Subject Line Best Practices
-
-| Factor | Recommendation |
-|--------|----------------|
-| Length | 30-50 characters |
-| Personalization | Use when relevant |
-| Emoji | Test, 1 max |
-| Caps | Avoid ALL CAPS |
-| Spam words | Avoid "free", "act now" |
-
-## Preview Text (Preheader)
-
-- Extends subject line (don't repeat)
-- 40-90 characters
-- Include CTA or benefit
-- Create curiosity
-
-**Examples:**
-- Subject: "Your weekly marketing insights"
-- Preview: "Plus a free template to save 5 hours"
-
-## A/B Test Ideas
-
-1. Question vs. statement
-2. With vs. without emoji
-3. With vs. without numbers
-4. Short vs. medium length
-5. With vs. without personalization

package/.opencode/skills/find-skills/SKILL.md

@@ -1,137 +0,0 @@
----
-name: ck:find-skills
-description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
-argument-hint: "[capability or task description]"
-metadata:
-  author: claudekit
-  version: "1.0.0"
----
-
-# Find Skills
-
-This skill helps you discover and install skills from the open agent skills ecosystem.
-
-## When to Use This Skill
-
-Use this skill when the user:
-
-- Asks "how do I do X" where X might be a common task with an existing skill
-- Says "find a skill for X" or "is there a skill for X"
-- Asks "can you do X" where X is a specialized capability
-- Expresses interest in extending agent capabilities
-- Wants to search for tools, templates, or workflows
-- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
-
-## What is the Skills CLI?
-
-The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
-
-**Key commands:**
-
-- `npx skills find [query]` - Search for skills interactively or by keyword
-- `npx skills add <package>` - Install a skill from GitHub or other sources
-- `npx skills check` - Check for skill updates
-- `npx skills update` - Update all installed skills
-
-**Browse skills at:** https://skills.sh/
-
-## How to Help Users Find Skills
-
-### Step 1: Understand What They Need
-
-When a user asks for help with something, identify:
-
-1. The domain (e.g., React, testing, design, deployment)
-2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
-3. Whether this is a common enough task that a skill likely exists
-
-### Step 2: Search for Skills
-
-Run the find command with a relevant query:
-
-```bash
-npx skills find [query]
-```
-
-For example:
-
-- User asks "how do I make my React app faster?" → `npx skills find react performance`
-- User asks "can you help me with PR reviews?" → `npx skills find pr review`
-- User asks "I need to create a changelog" → `npx skills find changelog`
-
-The command will return results like:
-
-```
-Install with npx skills add <owner/repo@skill>
-
-vercel-labs/agent-skills@vercel-react-best-practices
-└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
-```
-
-### Step 3: Present Options to the User
-
-When you find relevant skills, present them to the user with:
-
-1. The skill name and what it does
-2. The install command they can run
-3. A link to learn more at skills.sh
-
-Example response:
-
-```
-I found a skill that might help! The "vercel-react-best-practices" skill provides
-React and Next.js performance optimization guidelines from Vercel Engineering.
-
-To install it:
-npx skills add vercel-labs/agent-skills@vercel-react-best-practices
-
-Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
-```
-
-### Step 4: Offer to Install
-
-If the user wants to proceed, you can install the skill for them:
-
-```bash
-npx skills add <owner/repo@skill> -g -y
-```
-
-The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
-
-## Common Skill Categories
-
-When searching, consider these common categories:
-
-| Category        | Example Queries                          |
-| --------------- | ---------------------------------------- |
-| Web Development | react, nextjs, typescript, css, tailwind |
-| Testing         | testing, jest, playwright, e2e           |
-| DevOps          | deploy, docker, kubernetes, ci-cd        |
-| Documentation   | docs, readme, changelog, api-docs        |
-| Code Quality    | review, lint, refactor, best-practices   |
-| Design          | ui, ux, design-system, accessibility     |
-| Productivity    | workflow, automation, git                |
-
-## Tips for Effective Searches
-
-1. **Use specific keywords**: "react testing" is better than just "testing"
-2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
-3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
-
-## When No Skills Are Found
-
-If no relevant skills exist:
-
-1. Acknowledge that no existing skill was found
-2. Offer to help with the task directly using your general capabilities
-3. Suggest the user could create their own skill with `npx skills init`
-
-Example:
-
-```
-I searched for skills related to "xyz" but didn't find any matches.
-I can still help you with this task directly! Would you like me to proceed?
-
-If this is something you do often, you could create your own skill:
-npx skills init my-xyz-skill
-```

package/.opencode/skills/fix/SKILL.md

@@ -1,75 +0,0 @@
----
-name: ck:fix
-description: Fix bugs, errors, test failures, CI/CD issues with intelligent routing. Use when reporting bugs, type errors, log errors, UI issues, code problems. Auto-classifies complexity and activates relevant skills.
-argument-hint: "[issue] --auto|--review|--quick|--parallel"
-metadata:
-  author: claudekit
-  version: "1.0.0"
----
-
-# Fixing
-
-Unified skill for fixing issues of any complexity with intelligent routing.
-
-## Step 0: Mode Selection
-
-**First action:** If there is no "auto" keyword in the request, use `AskUserQuestion` to determine workflow mode:
-
-| Option | Recommend When | Behavior |
-|--------|----------------|----------|
-| **Autonomous** | Simple/moderate issues | Auto-approve if score >= 9.5 & 0 critical |
-| **Human-in-the-loop** | Critical/production code | Pause for approval at each step |
-| **Quick** | Type errors, lint, trivial bugs | Fast debug → fix → review cycle |
-
-See `references/mode-selection.md` for AskUserQuestion format.
-
-## Step 1: Complexity Assessment
-
-Classify before routing. See `references/complexity-assessment.md`.
-
-| Level | Indicators | Workflow |
-|-------|------------|----------|
-| **Simple** | Single file, clear error, type/lint | `references/workflow-quick.md` |
-| **Moderate** | Multi-file, root cause unclear | `references/workflow-standard.md` |
-| **Complex** | System-wide, architecture impact | `references/workflow-deep.md` |
-| **Parallel** | 2+ independent issues | Parallel `fullstack-developer` agents |
-
-## Skill/Subagent Activation Matrix
-
-See `references/skill-activation-matrix.md` for complete matrix.
-
-**Always activate:** `debugging` (all workflows)
-**Conditional:** `problem-solving`, `sequential-thinking`, `brainstorming`, `context-engineering`
-**Subagents:** `debugger`, `researcher`, `planner`, `code-reviewer`, `tester`, `Bash`
-**Parallel:** Multiple `Explore` agents for scouting, `Bash` agents for verification
-
-## Output Format
-
-Unified step markers:
-```
-✓ Step 0: [Mode] selected - [Complexity] detected
-✓ Step 1: Root cause identified - [summary]
-✓ Step 2: Fix implemented - [N] files changed
-✓ Step 3: Tests [X/X passed]
-✓ Step 4: Review [score]/10 - [status]
-✓ Step 5: Complete - [action taken]
-```
-
-## References
-
-Load as needed:
-- `references/mode-selection.md` - AskUserQuestion format for mode
-- `references/complexity-assessment.md` - Classification criteria
-- `references/workflow-quick.md` - Quick: debug → fix → review
-- `references/workflow-standard.md` - Standard: full pipeline
-- `references/workflow-deep.md` - Deep: research + brainstorm + plan
-- `references/review-cycle.md` - Review logic (autonomous vs HITL)
-- `references/skill-activation-matrix.md` - When to activate each skill
-- `references/parallel-exploration.md` - Parallel Explore/Bash subagents patterns
-
-**Specialized Workflows:**
-- `references/workflow-ci.md` - GitHub Actions/CI failures
-- `references/workflow-logs.md` - Application log analysis
-- `references/workflow-test.md` - Test suite failures
-- `references/workflow-types.md` - TypeScript type errors
-- `references/workflow-ui.md` - Visual/UI issues (requires design skills)

package/.opencode/skills/fix/references/complexity-assessment.md

@@ -1,61 +0,0 @@
-# Complexity Assessment
-
-Classify issue complexity before routing to workflow.
-
-## Classification Criteria
-
-### Simple (→ workflow-quick.md)
-
-**Indicators:**
-- Single file affected
-- Clear error message (type error, syntax, lint)
-- Keywords: `type`, `typescript`, `tsc`, `lint`, `eslint`, `syntax`
-- Obvious fix location
-- No investigation needed
-
-**Examples:**
-- "Fix type error in auth.ts"
-- "ESLint errors after upgrade"
-- "Syntax error in config file"
-
-### Moderate (→ workflow-standard.md)
-
-**Indicators:**
-- 2-5 files affected
-- Root cause unclear but localized
-- Needs debugging investigation
-- Keywords: `bug`, `broken`, `not working`, `fails sometimes`
-- Test failures with unclear cause
-
-**Examples:**
-- "Login sometimes fails"
-- "API returns wrong data"
-- "Component not rendering correctly"
-
-### Complex (→ workflow-deep.md)
-
-**Indicators:**
-- System-wide impact (5+ files)
-- Architecture decision needed
-- Research required for solution
-- Keywords: `architecture`, `refactor`, `system-wide`, `design issue`
-- Performance/security vulnerabilities
-- Multiple interacting components
-
-**Examples:**
-- "Memory leak in production"
-- "Database deadlocks under load"
-- "Security vulnerability in auth flow"
-
-### Parallel (→ multiple fullstack-developer agents)
-
-**Indicators:**
-- 2+ independent issues mentioned
-- Issues in different areas (frontend + backend, auth + payments)
-- No dependencies between issues
-- Keywords: list of issues, "and", "also", multiple error types
-
-**Examples:**
-- "Fix type errors AND update UI styling"
-- "Auth bug + payment integration issue"
-- "3 different test failures in unrelated modules"