@hienlh/ppm 0.9.81 → 0.9.82

package/.opencode/skills/bootstrap/references/workflow-auto.md

@@ -1,52 +0,0 @@
-# Auto Workflow (`--auto`) — Default
-
-**Thinking level:** Ultrathink
-**User gates:** Design approval only. All other phases proceed automatically.
-
-## Step 1: Research
-
-Spawn multiple `researcher` subagents in parallel:
-- Explore request, idea validation, challenges, best solutions
-- Keep every report ≤150 lines
-
-No user gate — proceed automatically.
-
-## Step 2: Tech Stack
-
-1. Use `planner` + multiple `researcher` subagents in parallel for best-fit stack
-2. Write tech stack to `./docs` directory
-
-No user gate — auto-select best option.
-
-## Step 3: Wireframe & Design
-
-1. Use `ui-ux-designer` + `researcher` subagents in parallel:
-   - Research style, trends, fonts (predict Google Fonts name, NOT just Inter/Poppins), colors, spacing, positions
-   - Describe assets for `ck:ai-multimodal` skill generation
-2. `ui-ux-designer` creates:
-   - Design guidelines at `./docs/design-guidelines.md`
-   - Wireframes in HTML at `./docs/wireframe/`
-3. If no logo provided: generate with `ck:ai-multimodal` skill
-4. Screenshot wireframes with `ck:chrome-devtools` → save to `./docs/wireframes/`
-
-**Gate:** Ask user to approve design. Repeat if rejected.
-
-**Image tools:** `ck:ai-multimodal` for generation/analysis, `imagemagick` for crop/resize, background removal tool as needed.
-
-## Step 4: Planning
-
-Activate **ck:plan** skill: `/ck:plan --auto <requirements>`
-- Planning skill auto-detects complexity and picks appropriate mode
-- Creates plan directory using `## Naming` pattern
-- Overview at `plan.md` (<80 lines) + `phase-XX-*.md` files
-
-No user gate — proceed to implementation.
-
-## Step 5: Implementation → Final Report
-
-Load `references/shared-phases.md` for remaining phases.
-
-Activate **ck:cook** skill: `/ck:cook --auto <plan-path>`
-- Skips all review gates
-- Auto-approves if score≥9.5 and 0 critical issues
-- Continues through all phases without stopping

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

@@ -1,50 +0,0 @@
-# Fast Workflow (`--fast`)
-
-**Thinking level:** Think hard
-**User gates:** None. Fully autonomous from start to finish.
-
-## Step 1: Combined Research & Planning
-
-All research happens in parallel, then feeds into planning:
-
-**Parallel research batch** (spawn these simultaneously):
-- 2 `researcher` subagents (max 5 sources each): explore request, validate idea, find solutions
-- 2 `researcher` subagents (max 5 sources each): find best-fit tech stack
-- 2 `researcher` subagents (max 5 sources each): research design style, trends, fonts, colors, spacing, positions
-  - Predict Google Fonts name (NOT just Inter/Poppins)
-  - Describe assets for `ck:ai-multimodal` generation
-
-Keep all reports ≤150 lines.
-
-## Step 2: Design
-
-1. `ui-ux-designer` subagent analyzes research, creates:
-   - Design guidelines at `./docs/design-guidelines.md`
-   - Wireframes in HTML at `./docs/wireframe/`
-2. If no logo provided: generate with `ck:ai-multimodal` skill
-3. Screenshot wireframes with `ck:chrome-devtools` → save to `./docs/wireframes/`
-
-**Image tools:** `ck:ai-multimodal` for generation/analysis, `imagemagick` for crop/resize, background removal tool as needed.
-
-No user gate — proceed directly.
-
-## Step 3: Planning
-
-Activate **ck:plan** skill: `/ck:plan --fast <requirements>`
-- Skip research (already done above)
-- Read codebase docs → create plan directly
-- Plan directory using `## Naming` pattern
-- Overview at `plan.md` (<80 lines) + `phase-XX-*.md` files
-
-No user gate — proceed to implementation.
-
-## Step 4: Implementation → Final Report
-
-Load `references/shared-phases.md` for remaining phases.
-
-Activate **ck:cook** skill: `/ck:cook --auto <plan-path>`
-- Skips all review gates (fast planning pairs with fast execution)
-- Auto-approves if score≥9.5 and 0 critical issues
-- Continues through all phases without stopping
-
-**Note:** Fast mode uses `git-manager` to auto-commit (no push) at the end.

package/.opencode/skills/bootstrap/references/workflow-full.md

@@ -1,60 +0,0 @@
-# Full Interactive Workflow (`--full`)
-
-**Thinking level:** Ultrathink
-**User gates:** Every major phase requires user approval before proceeding.
-
-## Step 1: Clarify Requirements
-
-Use `AskUserQuestion` to probe user's request, constraints, true objectives.
-- Ask 1 question at a time, wait for answer before next
-- Question everything — don't assume
-- Challenge assumptions — best solution often differs from initial vision
-- Continue until 100% certain about requirements
-
-## Step 2: Research
-
-Spawn multiple `researcher` subagents in parallel:
-- Explore request validity, challenges, best solutions
-- Keep every report ≤150 lines
-
-**Gate:** Present findings to user. Proceed only with approval.
-
-## Step 3: Tech Stack
-
-1. Ask user for preferred tech stack. If provided, skip to step 4.
-2. Use `planner` + multiple `researcher` subagents in parallel to find best-fit stack
-3. Present 2-3 options with pros/cons via `AskUserQuestion`
-4. Write approved tech stack to `./docs` directory
-
-**Gate:** User approves tech stack before continuing.
-
-## Step 4: Wireframe & Design
-
-1. Ask user if they want wireframes/design. If no → skip to Step 5.
-2. Use `ui-ux-designer` + `researcher` subagents in parallel:
-   - Research style, trends, fonts (predict Google Fonts name, NOT just Inter/Poppins), colors, spacing, positions
-   - Describe assets for `ck:ai-multimodal` skill generation
-3. `ui-ux-designer` creates:
-   - Design guidelines at `./docs/design-guidelines.md`
-   - Wireframes in HTML at `./docs/wireframe/`
-4. If no logo provided: generate with `ck:ai-multimodal` skill
-5. Screenshot wireframes with `ck:chrome-devtools` → save to `./docs/wireframes/`
-
-**Gate:** User approves design. Repeat if rejected.
-
-**Image tools:** `ck:ai-multimodal` for generation/analysis, `imagemagick` for crop/resize, background removal tool as needed.
-
-## Step 5: Planning
-
-Activate **ck:plan** skill: `/ck:plan --hard <requirements>`
-- Planner creates directory using `## Naming` pattern
-- Overview at `plan.md` (<80 lines) + `phase-XX-*.md` files
-- Present pros/cons of plan
-
-**Gate:** User approves plan. DO NOT start implementing without approval.
-
-## Step 6: Implementation → Final Report
-
-Load `references/shared-phases.md` for remaining phases.
-
-Activate **ck:cook** skill: `/ck:cook <plan-path>` (interactive mode — review gates at each step)

package/.opencode/skills/bootstrap/references/workflow-parallel.md

@@ -1,59 +0,0 @@
-# Parallel Workflow (`--parallel`)
-
-**Thinking level:** Ultrathink parallel
-**User gates:** Design approval only. Implementation uses multi-agent parallel execution.
-
-## Step 1: Research
-
-Spawn max 2 `researcher` agents in parallel:
-- Explore requirements, validation, challenges, solutions
-- Keep reports ≤150 lines
-
-No user gate — proceed automatically.
-
-## Step 2: Tech Stack
-
-Use `planner` + multiple `researcher` agents in parallel for best-fit stack.
-Write to `./docs` directory (≤150 lines).
-
-No user gate — proceed automatically.
-
-## Step 3: Wireframe & Design
-
-1. Use `ui-ux-designer` + `researcher` agents in parallel:
-   - Research style, trends, fonts, colors, spacing, positions
-   - Predict Google Fonts name (NOT just Inter/Poppins)
-   - Describe assets for `ck:ai-multimodal` generation
-2. `ui-ux-designer` creates:
-   - Design guidelines at `./docs/design-guidelines.md`
-   - Wireframes in HTML at `./docs/wireframe/`
-3. If no logo: generate with `ck:ai-multimodal` skill
-4. Screenshot with `ck:chrome-devtools` → save to `./docs/wireframes/`
-
-**Gate:** Ask user to approve design. Repeat if rejected.
-
-**Image tools:** `ck:ai-multimodal` for generation/analysis, `imagemagick` for crop/resize, background removal tool as needed.
-
-## Step 4: Parallel Planning
-
-Activate **ck:plan** skill: `/ck:plan --parallel <requirements>`
-- Creates phases with **exclusive file ownership** per phase (no overlap)
-- **Dependency matrix**: which phases run concurrently vs sequentially
-- `plan.md` includes dependency graph, execution strategy, file ownership matrix
-- Task hydration with `addBlockedBy` for sequential deps, no blockers for parallel groups
-
-No user gate — proceed to implementation.
-
-## Step 5: Parallel Implementation → Final Report
-
-Load `references/shared-phases.md` for remaining phases.
-
-Activate **ck:cook** skill: `/ck:cook --parallel <plan-path>`
-- Read `plan.md` for dependency graph and execution strategy
-- Launch multiple `fullstack-developer` agents in PARALLEL for concurrent phases
-  - Pass: phase file path, environment info
-- Use `ui-ux-designer` for frontend (generate/analyze assets with `ck:ai-multimodal`, edit with `imagemagick`)
-- Respect file ownership boundaries
-- Run type checking after implementation
-
-Cook handles testing, review, docs, onboarding, final report per `shared-phases.md`.

package/.opencode/skills/brainstorm/SKILL.md

@@ -1,79 +0,0 @@
----
-name: ck:brainstorm
-description: Brainstorm solutions with trade-off analysis and brutal honesty. Use for ideation, architecture decisions, technical debates, feature exploration, feasibility assessment, design discussions.
-argument-hint: "[topic or problem]"
-license: MIT
-metadata:
-  author: claudekit
-  version: "2.0.0"
----
-
-# Brainstorming Skill
-
-You are a Solution Brainstormer, an elite software engineering expert who specializes in system architecture design and technical decision-making. Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs.
-
-## Communication Style
-If coding level guidelines were injected at session start (levels 0-5), follow those guidelines for response structure and explanation depth. The guidelines define what to explain, what not to explain, and required response format.
-
-## Core Principles
-You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
-
-## Your Expertise
-- System architecture design and scalability patterns
-- Risk assessment and mitigation strategies
-- Development time optimization and resource allocation
-- User Experience (UX) and Developer Experience (DX) optimization
-- Technical debt management and maintainability
-- Performance optimization and bottleneck identification
-
-## Your Approach
-1. **Question Everything**: Use `AskUserQuestion` tool to ask probing questions to fully understand the user's request, constraints, and true objectives. Don't assume - clarify until you're 100% certain.
-2. **Brutal Honesty**: Use `AskUserQuestion` tool to provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
-3. **Explore Alternatives**: Always consider multiple approaches. Present 2-3 viable solutions with clear pros/cons, explaining why one might be superior.
-4. **Challenge Assumptions**: Use `AskUserQuestion` tool to question the user's initial approach. Often the best solution is different from what was originally envisioned.
-5. **Consider All Stakeholders**: Use `AskUserQuestion` tool to evaluate impact on end users, developers, operations team, and business objectives.
-
-## Collaboration Tools
-- Consult the `planner` agent to research industry best practices and find proven solutions
-- Engage the `docs-manager` agent to understand existing project implementation and constraints
-- Use `WebSearch` tool to find efficient approaches and learn from others' experiences
-- Use `docs-seeker` skill to read latest documentation of external plugins/packages
-- Leverage `ai-multimodal` skill to analyze visual materials and mockups
-- Query `psql` command to understand current database structure and existing data
-- Employ `sequential-thinking` skill for complex problem-solving that requires structured analysis
-
-## Your Process
-1. **Scout Phase**: Use `scout` skill to discover relevant files and code patterns, read relevant docs in `<project-dir>/docs` directory, to understand the current state of the project
-2. **Discovery Phase**: Use `AskUserQuestion` tool to ask clarifying questions about requirements, constraints, timeline, and success criteria
-3. **Research Phase**: Gather information from other agents and external sources
-4. **Analysis Phase**: Evaluate multiple approaches using your expertise and principles
-5. **Debate Phase**: Use `AskUserQuestion` tool to Present options, challenge user preferences, and work toward the optimal solution
-6. **Consensus Phase**: Ensure alignment on the chosen approach and document decisions
-7. **Documentation Phase**: Create a comprehensive markdown summary report with the final agreed solution
-8. **Finalize Phase**: Use `AskUserQuestion` tool to ask if user wants to create a detailed implementation plan.
-   - If `Yes`: Run `/plan` command with the brainstorm summary context as the argument to ensure plan continuity.
-     **CRITICAL:** The invoked plan command will create `plan.md` with YAML frontmatter including `status: pending`.
-   - If `No`: End the session.
-
-## Report Output
-Use the naming pattern from the `## Naming` section in the injected context. The pattern includes the full path and computed date.
-
-## Output Requirements
-When brainstorming concludes with agreement, create a detailed markdown summary report including:
-- Problem statement and requirements
-- Evaluated approaches with pros/cons
-- Final recommended solution with rationale
-- Implementation considerations and risks
-- Success metrics and validation criteria
-- Next steps and dependencies
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-## Critical Constraints
-- You DO NOT implement solutions yourself - you only brainstorm and advise
-- You must validate feasibility before endorsing any approach
-- You prioritize long-term maintainability over short-term convenience
-- You consider both technical excellence and business pragmatism
-
-**Remember:** Your role is to be the user's most trusted technical advisor - someone who will tell them hard truths to ensure they build something great, maintainable, and successful.
-
-**IMPORTANT:** **DO NOT** implement anything, just brainstorm, answer questions and advise.

package/.opencode/skills/brand/SKILL.md

@@ -1,97 +0,0 @@
----
-name: ckm:brand
-description: Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.
-argument-hint: "[update|review|create] [args]"
-metadata:
-  author: claudekit
-  version: "1.0.0"
----
-
-# Brand
-
-Brand identity, voice, messaging, asset management, and consistency frameworks.
-
-## When to Use
-
-- Brand voice definition and content tone guidance
-- Visual identity standards and style guide development
-- Messaging framework creation
-- Brand consistency review and audit
-- Asset organization, naming, and approval
-- Color palette management and typography specs
-
-## Quick Start
-
-**Inject brand context into prompts:**
-```bash
-node scripts/inject-brand-context.cjs
-node scripts/inject-brand-context.cjs --json
-```
-
-**Validate an asset:**
-```bash
-node scripts/validate-asset.cjs <asset-path>
-```
-
-**Extract/compare colors:**
-```bash
-node scripts/extract-colors.cjs --palette
-node scripts/extract-colors.cjs <image-path>
-```
-
-## Brand Sync Workflow
-
-```bash
-# 1. Edit docs/brand-guidelines.md (or use /brand update)
-# 2. Sync to design tokens
-node scripts/sync-brand-to-tokens.cjs
-# 3. Verify
-node scripts/inject-brand-context.cjs --json | head -20
-```
-
-**Files synced:**
-- `docs/brand-guidelines.md` → Source of truth
-- `assets/design-tokens.json` → Token definitions
-- `assets/design-tokens.css` → CSS variables
-
-## Subcommands
-
-| Subcommand | Description | Reference |
-|------------|-------------|-----------|
-| `update` | Update brand identity and sync to all design systems | `references/update.md` |
-
-## References
-
-| Topic | File |
-|-------|------|
-| Voice Framework | `references/voice-framework.md` |
-| Visual Identity | `references/visual-identity.md` |
-| Messaging | `references/messaging-framework.md` |
-| Consistency | `references/consistency-checklist.md` |
-| Guidelines Template | `references/brand-guideline-template.md` |
-| Asset Organization | `references/asset-organization.md` |
-| Color Management | `references/color-palette-management.md` |
-| Typography | `references/typography-specifications.md` |
-| Logo Usage | `references/logo-usage-rules.md` |
-| Approval Checklist | `references/approval-checklist.md` |
-
-## Scripts
-
-| Script | Purpose |
-|--------|---------|
-| `scripts/inject-brand-context.cjs` | Extract brand context for prompt injection |
-| `scripts/sync-brand-to-tokens.cjs` | Sync brand-guidelines.md → design-tokens.json/css |
-| `scripts/validate-asset.cjs` | Validate asset naming, size, format |
-| `scripts/extract-colors.cjs` | Extract and compare colors against palette |
-
-## Templates
-
-| Template | Purpose |
-|----------|---------|
-| `templates/brand-guidelines-starter.md` | Complete starter template for new brands |
-
-## Routing
-
-1. Parse subcommand from `$ARGUMENTS` (first word)
-2. Load corresponding `references/{subcommand}.md`
-3. Execute with remaining arguments

package/.opencode/skills/brand/references/approval-checklist.md

@@ -1,169 +0,0 @@
-# Asset Approval Checklist
-
-Comprehensive checklist for reviewing marketing assets before approval.
-
-## Quick Review
-
-Before detailed review, verify:
-- [ ] Asset serves stated purpose
-- [ ] Target audience appropriate
-- [ ] No obvious errors or issues
-- [ ] Aligns with campaign goals
-
-## Visual Elements
-
-### Logo Usage
-- [ ] Correct logo variant for context
-- [ ] Proper clear space maintained
-- [ ] Minimum size requirements met
-- [ ] Approved colors only
-- [ ] No unauthorized modifications
-- [ ] Appropriate for background
-
-### Color Compliance
-- [ ] Uses brand palette colors only
-- [ ] Primary/secondary ratio appropriate (60/30/10)
-- [ ] Semantic colors used correctly
-- [ ] No off-brand colors introduced
-- [ ] Consistent across all elements
-
-### Typography
-- [ ] Brand fonts used throughout
-- [ ] Correct font weights applied
-- [ ] Proper type hierarchy
-- [ ] Appropriate sizes for medium
-- [ ] Line heights adequate
-- [ ] No orphans/widows in body text
-
-### Imagery
-- [ ] Matches brand photography style
-- [ ] Appropriate subjects/content
-- [ ] Quality meets requirements
-- [ ] Properly licensed/credited
-- [ ] Optimized for intended use
-
-## Accessibility
-
-### Visual Accessibility
-- [ ] Text contrast ratio >= 4.5:1 (AA)
-- [ ] Large text contrast >= 3:1
-- [ ] Interactive elements have visible focus
-- [ ] Color not sole indicator of meaning
-- [ ] Alt text for all images
-
-### Content Accessibility
-- [ ] Clear and scannable layout
-- [ ] Readable font sizes
-- [ ] Logical reading order
-- [ ] Meaningful headings structure
-- [ ] Links describe destination
-
-## Content Quality
-
-### Copy Review
-- [ ] Matches brand voice
-- [ ] Appropriate tone for context
-- [ ] No prohibited terms used
-- [ ] Value proposition clear
-- [ ] CTA compelling and clear
-- [ ] Proofread for errors
-
-### Messaging
-- [ ] Aligns with key messages
-- [ ] Differentiators highlighted
-- [ ] Benefits over features
-- [ ] Target audience addressed
-- [ ] No conflicting claims
-
-## Technical Requirements
-
-### File Specifications
-- [ ] Correct file format
-- [ ] Appropriate resolution
-- [ ] File size optimized
-- [ ] Proper naming convention
-- [ ] Metadata included
-
-### Platform Requirements
-| Platform | Verified |
-|----------|----------|
-| Instagram | [ ] Correct dimensions |
-| Twitter/X | [ ] Meets requirements |
-| LinkedIn | [ ] Professional standards |
-| Facebook | [ ] Guidelines compliant |
-| Email | [ ] Size under 1MB |
-| Web | [ ] Optimized for web |
-
-## Legal & Compliance
-
-### Intellectual Property
-- [ ] Stock images licensed
-- [ ] Music/audio cleared
-- [ ] No trademark violations
-- [ ] User content authorized
-- [ ] Credits included where needed
-
-### Regulatory
-- [ ] Required disclosures present
-- [ ] No misleading claims
-- [ ] Pricing accurate
-- [ ] Terms linked where needed
-- [ ] Privacy compliant
-
-## Review Status
-
-### Reviewer Sign-off
-
-| Review Area | Reviewer | Date | Status |
-|-------------|----------|------|--------|
-| Visual Design | | | [ ] Pass / [ ] Revisions |
-| Copy/Content | | | [ ] Pass / [ ] Revisions |
-| Brand Compliance | | | [ ] Pass / [ ] Revisions |
-| Technical | | | [ ] Pass / [ ] Revisions |
-| Legal | | | [ ] Pass / [ ] Revisions |
-
-### Final Approval
-
-- [ ] All review areas passed
-- [ ] Revisions completed (if any)
-- [ ] Final version uploaded
-- [ ] Metadata updated
-- [ ] Ready for publish/use
-
-**Approved By:** _______________
-
-**Date:** _______________
-
-**Version:** _______________
-
-## Common Issues & Fixes
-
-| Issue | Fix |
-|-------|-----|
-| Logo too small | Increase to minimum size |
-| Wrong font | Replace with brand font |
-| Low contrast | Adjust colors for accessibility |
-| Off-brand color | Replace with palette color |
-| Blurry image | Use higher resolution source |
-| Missing alt text | Add descriptive alt text |
-| Weak CTA | Strengthen action-oriented copy |
-
-## Automation Support
-
-The `validate-asset.cjs` script can auto-check:
-- Color palette compliance
-- Minimum dimensions
-- File format/size
-- Naming convention
-- Basic metadata
-
-Run: `node .opencode/skills/brand/scripts/validate-asset.cjs <asset-path>`
-
-## Archival
-
-After approval:
-1. Update asset status in manifest.json
-2. Add approver and timestamp
-3. Move previous versions to archive
-4. Update campaign tracking
-5. Notify relevant teams