@hienlh/ppm 0.9.81 → 0.9.83

package/.opencode/skills/creativity/scripts/search.py

@@ -1,62 +0,0 @@
-#!/usr/bin/env python3
-# -*- coding: utf-8 -*-
-"""
-Creativity Pro Max Search - BM25 search engine for creative direction guides
-Usage: python search.py "<query>" [--domain <domain>] [--max-results 3]
-       python search.py "<query>" --creative-brief [-c "Campaign Name"]
-
-Domains: style, platform, voiceover, music, reasoning
-"""
-
-import argparse
-from core import CSV_CONFIG, AVAILABLE_DOMAINS, MAX_RESULTS, search
-from creative_brief import generate_creative_brief
-
-
-def format_output(result):
-    """Format results for Claude consumption (token-optimized)"""
-    if "error" in result:
-        return f"Error: {result['error']}"
-
-    output = []
-    output.append(f"## Creativity Pro Max Search Results")
-    output.append(f"**Domain:** {result['domain']} | **Query:** {result['query']}")
-    output.append(f"**Source:** {result['file']} | **Found:** {result['count']} results\n")
-
-    for i, row in enumerate(result['results'], 1):
-        output.append(f"### Result {i}")
-        for key, value in row.items():
-            value_str = str(value)
-            if len(value_str) > 300:
-                value_str = value_str[:300] + "..."
-            output.append(f"- **{key}:** {value_str}")
-        output.append("")
-
-    return "\n".join(output)
-
-
-if __name__ == "__main__":
-    parser = argparse.ArgumentParser(description="Creativity Pro Max Search")
-    parser.add_argument("query", help="Search query")
-    parser.add_argument("--domain", "-d", choices=AVAILABLE_DOMAINS, help="Search domain")
-    parser.add_argument("--max-results", "-n", type=int, default=MAX_RESULTS, help="Max results (default: 3)")
-    parser.add_argument("--json", action="store_true", help="Output as JSON")
-    # Creative brief generation
-    parser.add_argument("--creative-brief", "-cb", action="store_true", help="Generate complete creative brief recommendation")
-    parser.add_argument("--campaign-name", "-c", type=str, default=None, help="Campaign name for creative brief output")
-    parser.add_argument("--format", "-f", choices=["ascii", "markdown"], default="ascii", help="Output format for creative brief")
-
-    args = parser.parse_args()
-
-    # Creative brief takes priority
-    if args.creative_brief:
-        result = generate_creative_brief(args.query, args.campaign_name, args.format)
-        print(result)
-    # Domain search
-    else:
-        result = search(args.query, args.domain, args.max_results)
-        if args.json:
-            import json
-            print(json.dumps(result, indent=2, ensure_ascii=False))
-        else:
-            print(format_output(result))

package/.opencode/skills/dashboard/SKILL.md

@@ -1,108 +0,0 @@
----
-name: ckm:dashboard
-description: Launch and manage the Marketing Dashboard
-argument-hint: "[subcommand] [args]"
-metadata:
-  author: claudekit
-  version: "1.0.0"
----
-
-# Command: /dashboard
-
-Launch the Marketing Dashboard web application.
-
-## Description
-
-Starts the full-stack Marketing Dashboard with Vue 3 frontend and Hono API backend. Provides visual interface for campaign management, content creation, asset organization, and AI-powered automation recipes.
-
-## Usage
-
-```bash
-/dashboard [mode]
-```
-
-## Arguments
-
-- `mode` (optional): Start mode
-  - `dev` (default): Development mode with HMR
-  - `prod`: Production mode (requires build first)
-  - `build`: Build for production
-  - `stop`: Stop running servers
-
-## Examples
-
-```bash
-# Start development mode (default)
-/dashboard
-/dashboard dev
-
-# Build for production
-/dashboard build
-
-# Start production mode
-/dashboard prod
-
-# Stop all servers
-/dashboard stop
-```
-
-## Features
-
-### Dashboard Features
-- **Campaign Board**: Kanban view with drag-drop status management
-- **Content Library**: Grid view with filters (type, campaign, status)
-- **Asset Gallery**: Link assets to campaigns with AI enhancement
-- **Automation Panel**: Pre-built recipes for common tasks:
-  - Blog Post Generator
-  - Social Media Pack
-  - Campaign Brief Creator
-  - SEO Audit Tool
-
-### Tech Stack
-- **Frontend**: Vue 3 + Vite + Pinia + Tailwind CSS
-- **Backend**: Hono + Node.js
-- **Database**: SQLite (local)
-- **AI**: Claude integration via API
-
-## URLs (Development Mode)
-
-- **Frontend**: http://localhost:5173
-- **API**: http://localhost:3457
-- **Health Check**: http://localhost:3457/health
-
-## URLs (Production Mode)
-
-- **Application**: http://localhost:3457 (serves built Vue app)
-- **Health Check**: http://localhost:3457/health
-
-## Requirements
-
-- Node.js 18+
-- NPM dependencies installed (auto-installs on first run)
-
-## Notes
-
-- API key required (set via Settings page or sessionStorage)
-- Dev mode uses HMR for instant updates
-- Production mode serves optimized build (56 KB gzipped)
-- All data stored locally in SQLite database
-
-## Related Files
-
-- Skill: `.opencode/skills/marketing-dashboard/`
-- Scripts: `start.sh`, `build.sh`, `stop.sh`, `start-production.sh`
-- Server: `server/index.js`
-- Frontend: `app/src/`
-
-
-## Subcommands
-
-| Subcommand | Description | Reference |
-|------------|-------------|-----------|
-| `check` | Check Marketing Dashboard server status | `references/check.md` |
-
-## Routing
-
-1. Parse subcommand from `$ARGUMENTS` (first word)
-2. Load corresponding `references/{subcommand}.md`
-3. Execute with remaining arguments

package/.opencode/skills/dashboard/references/check.md

@@ -1,93 +0,0 @@
-# Command: /dashboard:check
-
-Verify the status of Marketing Dashboard servers.
-
-## Description
-
-Checks if the Marketing Dashboard frontend and backend servers are running and healthy. Useful for troubleshooting before running `/dashboard`.
-
-## Usage
-
-```bash
-/dashboard:check
-```
-
-## Workflow
-
-### Step 1: Check Backend Server (Port 3457)
-
-```bash
-curl -s -o /dev/null -w "%{http_code}" http://localhost:3457/health 2>/dev/null || echo "offline"
-```
-
-**Expected responses:**
-- `200` → Backend running and healthy
-- `offline` → Backend not running
-
-### Step 2: Check Frontend Server (Port 5173)
-
-```bash
-curl -s -o /dev/null -w "%{http_code}" http://localhost:5173 2>/dev/null || echo "offline"
-```
-
-**Expected responses:**
-- `200` → Frontend running (dev mode)
-- `offline` → Frontend not running (or production mode serving from backend)
-
-### Step 3: Check Process Status
-
-```bash
-# Check for running node processes
-pgrep -fl "node.*marketing-dashboard" 2>/dev/null || echo "no processes"
-```
-
-### Step 4: Report Status
-
-Generate status table:
-
-| Component | Port | Status | URL |
-|-----------|------|--------|-----|
-| Backend API | 3457 | {status} | http://localhost:3457 |
-| Frontend | 5173 | {status} | http://localhost:5173 |
-| Health | 3457 | {status} | http://localhost:3457/health |
-
-### Step 5: Provide Recommendations
-
-**If offline:**
-```
-Dashboard is not running.
-
-To start: /dashboard
-To start manually:
-  cd .opencode/skills/marketing-dashboard
-  ./start.sh
-```
-
-**If running:**
-```
-Dashboard is healthy!
-
-Frontend: http://localhost:5173
-API: http://localhost:3457
-
-To stop: /dashboard stop
-```
-
-## Output Example
-
-```
-Dashboard Status Check
-━━━━━━━━━━━━━━━━━━━━━━
-
-Backend API (3457):  ● Online
-Frontend (5173):     ● Online
-Health Check:        ● Healthy
-
-Access: http://localhost:5173
-```
-
-## Related Commands
-
-- `/dashboard` - Start the dashboard
-- `/dashboard stop` - Stop all servers
-- `/dashboard build` - Build for production

package/.opencode/skills/databases/SKILL.md

@@ -1,236 +0,0 @@
----
-name: ck:databases
-description: Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.
-argument-hint: "[query or schema task]"
-license: MIT
-metadata:
-  author: claudekit
-  version: "1.0.0"
----
-
-# Databases Skill
-
-Unified guide for working with MongoDB (document-oriented) and PostgreSQL (relational) databases. Choose the right database for your use case and master both systems.
-
-## When to Use This Skill
-
-Use when:
-- Designing database schemas and data models
-- Writing queries (SQL or MongoDB query language)
-- Building aggregation pipelines or complex joins
-- Optimizing indexes and query performance
-- Implementing database migrations
-- Setting up replication, sharding, or clustering
-- Configuring backups and disaster recovery
-- Managing database users and permissions
-- Analyzing slow queries and performance issues
-- Administering production database deployments
-
-## Database Selection Guide
-
-### Choose MongoDB When:
-- Schema flexibility: frequent structure changes, heterogeneous data
-- Document-centric: natural JSON/BSON data model
-- Horizontal scaling: need to shard across multiple servers
-- High write throughput: IoT, logging, real-time analytics
-- Nested/hierarchical data: embedded documents preferred
-- Rapid prototyping: schema evolution without migrations
-
-**Best for:** Content management, catalogs, IoT time series, real-time analytics, mobile apps, user profiles
-
-### Choose PostgreSQL When:
-- Strong consistency: ACID transactions critical
-- Complex relationships: many-to-many joins, referential integrity
-- SQL requirement: team expertise, reporting tools, BI systems
-- Data integrity: strict schema validation, constraints
-- Mature ecosystem: extensive tooling, extensions
-- Complex queries: window functions, CTEs, analytical workloads
-
-**Best for:** Financial systems, e-commerce transactions, ERP, CRM, data warehousing, analytics
-
-### Both Support:
-- JSON/JSONB storage and querying
-- Full-text search capabilities
-- Geospatial queries and indexing
-- Replication and high availability
-- ACID transactions (MongoDB 4.0+)
-- Strong security features
-
-## Quick Start
-
-### MongoDB Setup
-
-```bash
-# Atlas (Cloud) - Recommended
-# 1. Sign up at mongodb.com/atlas
-# 2. Create M0 free cluster
-# 3. Get connection string
-
-# Connection
-mongodb+srv://user:pass@cluster.mongodb.net/db
-
-# Shell
-mongosh "mongodb+srv://cluster.mongodb.net/mydb"
-
-# Basic operations
-db.users.insertOne({ name: "Alice", age: 30 })
-db.users.find({ age: { $gte: 18 } })
-db.users.updateOne({ name: "Alice" }, { $set: { age: 31 } })
-db.users.deleteOne({ name: "Alice" })
-```
-
-### PostgreSQL Setup
-
-```bash
-# Ubuntu/Debian
-sudo apt-get install postgresql postgresql-contrib
-
-# Start service
-sudo systemctl start postgresql
-
-# Connect
-psql -U postgres -d mydb
-
-# Basic operations
-CREATE TABLE users (id SERIAL PRIMARY KEY, name TEXT, age INT);
-INSERT INTO users (name, age) VALUES ('Alice', 30);
-SELECT * FROM users WHERE age >= 18;
-UPDATE users SET age = 31 WHERE name = 'Alice';
-DELETE FROM users WHERE name = 'Alice';
-```
-
-## Common Operations
-
-### Create/Insert
-```javascript
-// MongoDB
-db.users.insertOne({ name: "Bob", email: "bob@example.com" })
-db.users.insertMany([{ name: "Alice" }, { name: "Charlie" }])
-```
-
-```sql
--- PostgreSQL
-INSERT INTO users (name, email) VALUES ('Bob', 'bob@example.com');
-INSERT INTO users (name, email) VALUES ('Alice', NULL), ('Charlie', NULL);
-```
-
-### Read/Query
-```javascript
-// MongoDB
-db.users.find({ age: { $gte: 18 } })
-db.users.findOne({ email: "bob@example.com" })
-```
-
-```sql
--- PostgreSQL
-SELECT * FROM users WHERE age >= 18;
-SELECT * FROM users WHERE email = 'bob@example.com' LIMIT 1;
-```
-
-### Update
-```javascript
-// MongoDB
-db.users.updateOne({ name: "Bob" }, { $set: { age: 25 } })
-db.users.updateMany({ status: "pending" }, { $set: { status: "active" } })
-```
-
-```sql
--- PostgreSQL
-UPDATE users SET age = 25 WHERE name = 'Bob';
-UPDATE users SET status = 'active' WHERE status = 'pending';
-```
-
-### Delete
-```javascript
-// MongoDB
-db.users.deleteOne({ name: "Bob" })
-db.users.deleteMany({ status: "deleted" })
-```
-
-```sql
--- PostgreSQL
-DELETE FROM users WHERE name = 'Bob';
-DELETE FROM users WHERE status = 'deleted';
-```
-
-### Indexing
-```javascript
-// MongoDB
-db.users.createIndex({ email: 1 })
-db.users.createIndex({ status: 1, createdAt: -1 })
-```
-
-```sql
--- PostgreSQL
-CREATE INDEX idx_users_email ON users(email);
-CREATE INDEX idx_users_status_created ON users(status, created_at DESC);
-```
-
-## Reference Navigation
-
-### MongoDB References
-- **[mongodb-crud.md](references/mongodb-crud.md)** - CRUD operations, query operators, atomic updates
-- **[mongodb-aggregation.md](references/mongodb-aggregation.md)** - Aggregation pipeline, stages, operators, patterns
-- **[mongodb-indexing.md](references/mongodb-indexing.md)** - Index types, compound indexes, performance optimization
-- **[mongodb-atlas.md](references/mongodb-atlas.md)** - Atlas cloud setup, clusters, monitoring, search
-
-### PostgreSQL References
-- **[postgresql-queries.md](references/postgresql-queries.md)** - SELECT, JOINs, subqueries, CTEs, window functions
-- **[postgresql-psql-cli.md](references/postgresql-psql-cli.md)** - psql commands, meta-commands, scripting
-- **[postgresql-performance.md](references/postgresql-performance.md)** - EXPLAIN, query optimization, vacuum, indexes
-- **[postgresql-administration.md](references/postgresql-administration.md)** - User management, backups, replication, maintenance
-
-## Python Utilities
-
-Database utility scripts in `scripts/`:
-- **db_migrate.py** - Generate and apply migrations for both databases
-- **db_backup.py** - Backup and restore MongoDB and PostgreSQL
-- **db_performance_check.py** - Analyze slow queries and recommend indexes
-
-```bash
-# Generate migration
-python scripts/db_migrate.py --db mongodb --generate "add_user_index"
-
-# Run backup
-python scripts/db_backup.py --db postgres --output /backups/
-
-# Check performance
-python scripts/db_performance_check.py --db mongodb --threshold 100ms
-```
-
-## Key Differences Summary
-
-| Feature | MongoDB | PostgreSQL |
-|---------|---------|------------|
-| Data Model | Document (JSON/BSON) | Relational (Tables/Rows) |
-| Schema | Flexible, dynamic | Strict, predefined |
-| Query Language | MongoDB Query Language | SQL |
-| Joins | $lookup (limited) | Native, optimized |
-| Transactions | Multi-document (4.0+) | Native ACID |
-| Scaling | Horizontal (sharding) | Vertical (primary), Horizontal (extensions) |
-| Indexes | Single, compound, text, geo, etc | B-tree, hash, GiST, GIN, etc |
-
-## Best Practices
-
-**MongoDB:**
-- Use embedded documents for 1-to-few relationships
-- Reference documents for 1-to-many or many-to-many
-- Index frequently queried fields
-- Use aggregation pipeline for complex transformations
-- Enable authentication and TLS in production
-- Use Atlas for managed hosting
-
-**PostgreSQL:**
-- Normalize schema to 3NF, denormalize for performance
-- Use foreign keys for referential integrity
-- Index foreign keys and frequently filtered columns
-- Use EXPLAIN ANALYZE to optimize queries
-- Regular VACUUM and ANALYZE maintenance
-- Connection pooling (pgBouncer) for web apps
-
-## Resources
-
-- MongoDB: https://www.mongodb.com/docs/
-- PostgreSQL: https://www.postgresql.org/docs/
-- MongoDB University: https://learn.mongodb.com/
-- PostgreSQL Tutorial: https://www.postgresqltutorial.com/

package/.opencode/skills/databases/analytics.md

@@ -1,198 +0,0 @@
-# Analytics (OLAP) Rules
-
-> **Note:** Core naming conventions, workflow, and checklist are in `SKILL.md` or `db-design.md` (always loaded).
-
-Guidelines for designing schemas for statistics and reporting tables.
-
----
-
-## General Principles
-
-- **Separate** from transactional tables - don't mix analytics logic into business tables
-- When heavy analytics queries/aggregations repeat → create separate tables
-- Use **Star Schema**: Fact tables at center, Dimension tables around
-
----
-
-## Design Process
-
-### 1. Analyze Statistics Requirements
-
-Ask user to clarify:
-- **Analysis dimensions**: by date, by customer, by product, by channel, by region?
-- **Granularity**: per order, per item, per day, per month?
-- **Metrics**: order_count, revenue, margin, conversion_rate, avg_order_value?
-
-### 2. Define Fact Granularity
-
-**Important**: What does 1 row in fact table represent?
-
-| Fact Table | Granularity | Use case |
-|------------|-------------|----------|
-| `fact_orders` | 1 row = 1 order | Statistics by order |
-| `fact_order_items` | 1 row = 1 order item | Statistics by product |
-| `fact_daily_sales` | 1 row = 1 day + store | Daily summary |
-
-### 3. Identify Required Dimensions
-
-Create separate dim table when:
-- Reused in multiple places
-- Has many descriptive attributes
-- Subject to slow changes (Slowly Changing Dimension)
-
----
-
-## Fact Tables
-
-### Fact table structure
-
-```sql
-CREATE TABLE fact_orders (
-    fact_id BIGINT PRIMARY KEY AUTO_INCREMENT,
-    -- Dimension keys
-    date_key INT NOT NULL,              -- FK to dim_date
-    customer_key BIGINT NOT NULL,       -- FK to dim_customer
-    store_key INT,
-    channel_key INT,
-    -- Degenerate dimensions (no separate dim needed)
-    order_id BIGINT NOT NULL,
-    order_number VARCHAR(50),
-    -- Measures
-    item_count INT NOT NULL,
-    gross_amount DECIMAL(18,2) NOT NULL,
-    discount_amount DECIMAL(18,2) DEFAULT 0,
-    net_amount DECIMAL(18,2) NOT NULL,
-
-    INDEX idx_fact_orders_date (date_key),
-    INDEX idx_fact_orders_customer (customer_key),
-    INDEX idx_fact_orders_date_store (date_key, store_key)
-);
-```
-
----
-
-## Dimension Tables
-
-### dim_date (required for every analytics schema)
-
-```sql
-CREATE TABLE dim_date (
-    date_key INT PRIMARY KEY,           -- Format: YYYYMMDD (20241215)
-    full_date DATE NOT NULL,
-    year INT NOT NULL,
-    quarter INT NOT NULL,               -- 1-4
-    month INT NOT NULL,                 -- 1-12
-    month_name VARCHAR(20),             -- 'January', 'February'
-    week_of_year INT NOT NULL,
-    day_of_month INT NOT NULL,
-    day_of_week INT NOT NULL,           -- 1=Monday, 7=Sunday
-    day_name VARCHAR(20),
-    is_weekend BOOLEAN NOT NULL,
-    is_holiday BOOLEAN DEFAULT FALSE,
-
-    UNIQUE (full_date)
-);
--- Pre-populate for multiple years (2020-2030)
-```
-
-### dim_customer
-
-```sql
-CREATE TABLE dim_customer (
-    customer_key BIGINT PRIMARY KEY AUTO_INCREMENT,  -- Surrogate key
-    customer_id BIGINT NOT NULL,                     -- Natural key from users
-    customer_name VARCHAR(255),
-    email VARCHAR(255),
-    segment VARCHAR(50),                -- 'VIP', 'Regular', 'New'
-    city VARCHAR(100),
-    region VARCHAR(100),
-    first_order_date DATE,
-    -- SCD Type 2 columns (if history needed)
-    effective_from DATE NOT NULL,
-    effective_to DATE,
-    is_current BOOLEAN DEFAULT TRUE,
-
-    INDEX idx_dim_customer_id (customer_id),
-    INDEX idx_dim_customer_current (is_current, customer_id)
-);
-```
-
----
-
-## Summary Tables (Pre-aggregated)
-
-When pre-aggregation needed for dashboard performance:
-
-```sql
-CREATE TABLE summary_daily_sales (
-    id BIGINT PRIMARY KEY AUTO_INCREMENT,
-    date_key INT NOT NULL,
-    store_key INT,
-    channel_key INT,
-    -- Pre-aggregated measures
-    order_count INT NOT NULL,
-    item_count INT NOT NULL,
-    gross_revenue DECIMAL(18,2) NOT NULL,
-    net_revenue DECIMAL(18,2) NOT NULL,
-    unique_customers INT NOT NULL,
-    avg_order_value DECIMAL(18,2),
-
-    UNIQUE (date_key, store_key, channel_key),
-    INDEX idx_summary_date (date_key)
-);
-```
-
----
-
-## Slowly Changing Dimensions (SCD)
-
-### Type 1 - Overwrite
-Overwrite old value, no history kept:
-```sql
-UPDATE dim_customer SET segment = 'VIP' WHERE customer_id = 123;
-```
-
-### Type 2 - Add new row (Recommended when history needed)
-```sql
--- 1. Close old row
-UPDATE dim_customer
-SET effective_to = CURRENT_DATE - 1, is_current = FALSE
-WHERE customer_id = 123 AND is_current = TRUE;
-
--- 2. Add new row
-INSERT INTO dim_customer (customer_id, segment, effective_from, is_current)
-VALUES (123, 'VIP', CURRENT_DATE, TRUE);
-```
-
----
-
-## Indexing for Analytics
-
-### Fact tables
-- Index FKs to dimensions: `date_key`, `customer_key`, `product_key`
-- Composite index based on query patterns: `INDEX (date_key, store_key)`
-
-### Dimension tables
-- PK: surrogate key
-- Index natural key: `customer_id`, `product_id`
-- Index for SCD: `(is_current, customer_id)`
-
----
-
-## Naming Convention
-
-- Fact tables: `fact_*` or `fct_*`
-- Dimension tables: `dim_*`
-- Summary tables: `summary_*` or `agg_*`
-
----
-
-## Checklist
-
-- [ ] Granularity defined for each fact table
-- [ ] dim_date exists or created (pre-populate multiple years)
-- [ ] Surrogate keys for dimensions
-- [ ] Index FKs in fact tables
-- [ ] SCD strategy for changing dimensions (Type 1 or Type 2)
-- [ ] Naming: `fact_*`, `dim_*`, `summary_*`
-- [ ] Refresh strategy: see [incremental-etl.md](incremental-etl.md)