npm - cokit-cli - Versions diffs - 1.2.7 → 1.4.0 - Mend

cokit-cli 1.2.7 → 1.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1206) hide show

package/templates/repo/.github/skills/frontend-design/references/asset-generation.md DELETED Viewed

@@ -1,161 +0,0 @@
-# Asset Processing Workflow
-Complete workflow for processing design assets using CLI tools (ImageMagick, FFmpeg, RMBG).
-## Processing Workflow
-### Step 1: Define Design Context
-Before processing, extract from the design brief:
-- **Aesthetic direction**: Minimalist? Maximalist? Brutalist? Organic?
-- **Color palette**: Primary colors, accent colors, mood
-- **Visual tone**: Professional? Playful? Luxury? Raw?
-- **Output requirements**: Formats, sizes, optimization targets
-### Step 2: Source Assets
-Get assets from:
-- Client-provided images/videos
-- Stock photo services (Unsplash, Pexels)
-- Design tools exports (Figma, Sketch)
-- Screenshots or captured frames
-### Step 3: Process Assets with CLI Tools
-Use these CLI tools:
-**Image Processing (ImageMagick)**:
-```bash
-# Resize for web
-convert input.png -resize 1920x1080 output.png
-# Convert format
-convert input.png output.webp
-# Apply color adjustments
-convert input.png -modulate 100,110,100 output.png
-# Add border/padding
-convert input.png -bordercolor white -border 20 output.png
-# Create thumbnail
-convert input.png -thumbnail 300x200 thumbnail.png
-```
-**Background Removal (RMBG CLI)**:
-```bash
-# Remove background from image
-rmbg input.png output.png
-# Batch process directory
-rmbg -i ./input/ -o ./output/
-```
-**Video Processing (FFmpeg)**:
-```bash
-# Extract frame from video
-ffmpeg -i video.mp4 -ss 00:00:05 -frames:v 1 frame.png
-# Create thumbnail grid
-ffmpeg -i video.mp4 -frames 1 -vf "select=not(mod(n\,100)),scale=200:120,tile=5x3" grid.png
-# Convert to web format
-ffmpeg -i input.mp4 -c:v libx264 -crf 23 output.mp4
-# Create animated GIF
-ffmpeg -i video.mp4 -vf "fps=10,scale=480:-1" output.gif
-```
-### Step 4: Optimize for Web
-**Image Optimization**:
-```bash
-# PNG optimization
-pngquant --quality=65-80 input.png -o output.png
-# JPEG optimization
-convert input.jpg -quality 85 output.jpg
-# WebP conversion (smaller file size)
-convert input.png -quality 80 output.webp
-```
-**Responsive Variants**:
-```bash
-# Create multiple sizes
-convert hero.png -resize 1920x output/hero-lg.png
-convert hero.png -resize 1280x output/hero-md.png
-convert hero.png -resize 768x output/hero-sm.png
-convert hero.png -resize 480x output/hero-xs.png
-```
-### Step 5: Verify Quality
-After processing, verify:
-- File sizes are optimized (target < 200KB for images)
-- Colors match design palette
-- Resolution appropriate for use case
-- No compression artifacts visible
-- Transparent backgrounds work correctly
-## Common Asset Tasks
-### Background Removal for Product Images
-```bash
-# Single image
-rmbg product.jpg product-nobg.png
-# Batch process
-for f in products/*.jpg; do rmbg "$f" "output/$(basename "$f" .jpg).png"; done
-```
-### Hero Image Optimization
-```bash
-# Full workflow
-convert original.png -resize 1920x1080^ -gravity center -extent 1920x1080 hero-lg.png
-convert hero-lg.png -quality 85 hero-lg.webp
-convert original.png -resize 768x -quality 85 hero-sm.webp
-```
-### Sprite Sheet Creation
-```bash
-# Combine multiple images into sprite
-convert icon-*.png +append sprite.png
-# With grid layout
-montage icon-*.png -tile 4x -geometry +0+0 sprite.png
-```
-### Video Thumbnail
-```bash
-# Extract best frame (usually around 25% in)
-ffmpeg -i video.mp4 -ss 00:00:03 -frames:v 1 thumbnail.jpg
-```
-## File Format Guidelines
-| Format | Use Case | Notes |
-|--------|----------|-------|
-| WebP | Web images (default) | Best compression, wide support |
-| PNG | Images with transparency | Use for icons, logos |
-| JPEG | Photos without transparency | Good for large images |
-| SVG | Icons, simple graphics | Scalable, smallest for simple shapes |
-| MP4 (H.264) | Web video | Universal support |
-| WebM | Modern browsers | Better compression than MP4 |
-| GIF | Simple animations | Limited colors, larger files |
-## Quality vs Size Targets
-| Asset Type | Target Size | Quality Setting |
-|------------|-------------|-----------------|
-| Hero image | < 200KB | 80-85% |
-| Thumbnails | < 50KB | 75-80% |
-| Icons | < 10KB | PNG or SVG |
-| Product images | < 150KB | 80-85% |
-| Background patterns | < 100KB | 70-80% |
-## Next Steps
-- **Verify visual quality**: Compare processed assets to originals
-- **Test across devices**: Ensure responsive variants work
-- **Document assets**: Keep track of source files and processing steps

package/templates/repo/.github/skills/frontend-design/references/visual-analysis-overview.md DELETED Viewed

@@ -1,95 +0,0 @@
-# Visual Analysis Overview
-Use AI multimodal vision to analyze generated assets and verify design standards.
-## Purpose
-- Verify generated assets align with aesthetic direction
-- Ensure professional quality before integration
-- Identify specific improvements needed for iteration
-- Make objective design decisions based on analysis
-- Extract actionable data (hex codes, composition insights)
-## Quick Start
-### Comprehensive Analysis
-```bash
-python scripts/gemini_batch_process.py \
-  --files docs/assets/generated-hero.png \
-  --task analyze \
-  --prompt "[see analysis-prompts.md for detailed prompt]" \
-  --output docs/assets/analysis-report.md \
-  --model gemini-2.5-flash
-```
-### Compare Multiple Variations
-```bash
-python scripts/gemini_batch_process.py \
-  --files docs/assets/option-1.png docs/assets/option-2.png docs/assets/option-3.png \
-  --task analyze \
-  --prompt "[see analysis-prompts.md for comparison prompt]" \
-  --output docs/assets/comparison-analysis.md \
-  --model gemini-2.5-flash
-```
-### Extract Color Palette
-```bash
-python scripts/gemini_batch_process.py \
-  --files docs/assets/final-asset.png \
-  --task analyze \
-  --prompt "Extract 5-8 dominant colors with hex codes. Classify as primary/accent/neutral. Suggest CSS variable names." \
-  --output docs/assets/color-palette.md \
-  --model gemini-2.5-flash
-```
-## Decision Framework
-### Score ≥ 8/10: Proceed to Integration
-**Actions**:
-- Optimize for web delivery
-- Create responsive variants
-- Document implementation guidelines
-- Extract color palette for CSS variables
-### Score 6-7/10: Minor Refinements Needed
-**Actions**:
-- Use ImageMagick for adjustments (brightness/contrast/saturation)
-- Consider selective regeneration of problem areas
-- May proceed with caution if time-constrained
-### Score < 6/10: Major Iteration Required
-**Actions**:
-- Analyze specific failure points from report
-- Refine generation prompt substantially
-- Regenerate with corrected parameters
-- Consider alternative aesthetic approach
-## Detailed References
-- `analysis-prompts.md` - All analysis prompt templates
-- `analysis-techniques.md` - Advanced analysis strategies
-- `analysis-best-practices.md` - Quality guidelines and pitfalls
-## Example Color Extraction Output
-```css
-/* Extracted Color Palette */
-:root {
-  /* Primary Colors */
-  --color-primary-600: #2C5F7D;  /* Dark teal - headers, CTAs */
-  --color-primary-400: #4A90B8;  /* Medium teal - links, accents */
-  /* Accent Colors */
-  --color-accent-500: #E8B44F;   /* Warm gold - highlights */
-  /* Neutral Colors */
-  --color-neutral-900: #1A1A1A;  /* Near black - body text */
-  --color-neutral-100: #F5F5F5;  /* Light gray - backgrounds */
-  /* Semantic Usage */
-  --color-text-primary: var(--color-neutral-900);
-  --color-text-on-primary: #FFFFFF;
-  --color-background: var(--color-neutral-100);
-  --color-cta: var(--color-primary-600);
-}
-```

package/templates/repo/.github/skills/frontend-design/references/workflow-describe.md DELETED Viewed

@@ -1,86 +0,0 @@
-# Design Description Workflow
-Create detailed design documentation from screenshot/video for developer implementation.
-## Prerequisites
-- Activate `ui-styling` skill first for design patterns
-## Workflow Steps
-### 1. Comprehensive Visual Analysis
-Analyze and describe exhaustively:
-**Layout & Structure**
-- Element positions (absolute coords or relative)
-- Container hierarchy
-- Grid/flexbox patterns
-- Responsive breakpoints visible
-**Visual Properties**
-- Design style and aesthetic trend
-- Every color with hex codes
-- Every border (width, style, radius)
-- Every icon (describe or identify)
-- Font names (predict Google Fonts), sizes, weights
-- Line heights, letter spacing
-**Spacing System**
-- Padding values
-- Margin values
-- Gap between elements
-- Section spacing
-**Visual Effects**
-- Shapes and geometry
-- Textures and materials
-- Lighting direction
-- Shadows (offset, blur, spread, color)
-- Reflections and refractions
-- Blur effects (backdrop, gaussian)
-- Glow effects
-- Background transparency
-- Image treatments
-**Interactions (if video)**
-- Animation sequences
-- Transition types and timing
-- Hover/focus states
-- Scroll behaviors
-**Font Prediction**: Match actual fonts, avoid Inter/Poppins defaults.
-### 2. Create Implementation Plan
-Use `ui-ux-designer` agent:
-- Create plan directory (use `## Naming` pattern)
-- Write `plan.md` overview (<80 lines)
-- Add detailed `phase-XX-name.md` files
-### 3. Report to User
-Provide implementation-ready documentation:
-- Summary of design system
-- Component breakdown
-- Technical specifications
-- Suggested implementation approach
-## Output Format
-```markdown
-# Design Analysis: [Name]
-## Design System
-- **Style**: [aesthetic direction]
-- **Colors**: [palette with hex]
-- **Typography**: [fonts, sizes, weights]
-- **Spacing Scale**: [values]
-## Component Breakdown
-1. [Component] - [specs]
-2. [Component] - [specs]
-## Implementation Notes
-- [Technical considerations]
-```
-## Related
-- `extraction-prompts.md` - Detailed prompts
-- `extraction-output-templates.md` - Output formats

package/templates/repo/.github/skills/frontend-design/references/workflow-quick.md DELETED Viewed

@@ -1,54 +0,0 @@
-# Quick Design Workflow
-Rapid design creation with minimal planning overhead.
-## Prerequisites
-- Activate `ui-styling` skill first for design patterns
-## Initial Research
-Quick reference from `ui-styling` skill:
-- shadcn/ui components for rapid development
-- Tailwind CSS utility classes
-- Color and typography defaults
-## Workflow Steps
-### 1. Start Design Process
-Use `ui-ux-designer` agent directly:
-- Skip extensive planning
-- Move to implementation quickly
-- Make design decisions on-the-fly
-### 2. Implement
-- Default to HTML/CSS/JS if unspecified
-- Focus on core functionality
-- Maintain quality despite speed
-### 3. Process Assets
-Use CLI tools:
-- Process images with ImageMagick
-- Optimize assets for web
-- Quick adjustments as needed
-### 4. Report & Approve
-- Summarize changes briefly
-- Request user approval
-- Update `./docs/design-guidelines.md` if approved
-## When to Use
-- Simple components
-- Prototypes and MVPs
-- Time-constrained projects
-- Iterative exploration
-- Single-page designs
-## Quality Shortcuts
-While moving fast, maintain:
-- Semantic HTML
-- CSS variables for consistency
-- Basic accessibility
-- Clean code structure
-## Related
-- `workflow-screenshot.md` - For exact replication
-- `technical-overview.md` - Quick reference

package/templates/repo/.github/skills/frontend-design/references/workflow-screenshot.md DELETED Viewed

@@ -1,62 +0,0 @@
-# Screenshot Replication Workflow
-Replicate a design exactly from a provided screenshot.
-## Prerequisites
-- Activate `ui-styling` skill first for design patterns
-## Workflow Steps
-### 1. Analyze Screenshot Details
-Extract from screenshot:
-- Design style and visual trends
-- Font names (predict Google Fonts), sizes, weights
-- Color palette with exact hex codes
-- Border radius, spacing patterns
-- Element positions, sizes, shapes
-- Textures, materials, lighting
-- Shadows, reflections, blur, glow effects
-- Background transparency, transitions
-- Image treatments and effects
-**Font Prediction**: Avoid defaulting to Inter/Poppins. Match actual fonts visible.
-### 2. Create Implementation Plan
-Use `ui-ux-designer` agent:
-- Create plan directory (use `## Naming` pattern from hooks)
-- Write `plan.md` (<80 lines, generic overview)
-- Add `phase-XX-name.md` files with:
-  - Context links, Overview, Key Insights
-  - Requirements, Architecture, Related files
-  - Implementation Steps, Todo list
-  - Success Criteria, Risk Assessment
-### 3. Implement
-- Follow plan step by step
-- Default to HTML/CSS/JS if no framework specified
-- Match screenshot precisely
-### 4. Process Assets
-Use CLI tools:
-- Process images with ImageMagick
-- Remove backgrounds with RMBG CLI
-- Optimize assets for web
-### 5. Verify & Report
-- Compare implementation to screenshot
-- Report changes summary to user
-- Request approval
-### 6. Document
-If approved, update `./docs/design-guidelines.md`
-## Quality Standards
-- Match screenshot at pixel level where possible
-- Preserve all visual hierarchy
-- Maintain exact spacing and proportions
-- Replicate animations if visible in source
-## Related
-- `design-extraction-overview.md` - Extract design guidelines
-- `extraction-prompts.md` - Detailed analysis prompts
-- `visual-analysis-overview.md` - Verify quality

package/templates/repo/.github/skills/git/SKILL.md DELETED Viewed

@@ -1,99 +0,0 @@
----
-name: git
-description: Git operations with conventional commits. Use for staging, committing, pushing, PRs, merges. Auto-splits commits by type/scope. Security scans for secrets.
----
-# Git Operations
-Execute git workflows via `git-manager` agent to isolate verbose output.
-Activate `context-engineering` skill.
-**IMPORTANT:**
-- Sacrifice grammar for the sake of concision.
-- Ensure token efficiency while maintaining high quality.
-- Pass these rules to agents.
-## Arguments
-- `cm`: Stage files & create commits
-- `cp`: Stage files, create commits and push
-- `pr`: Create Pull Request [to-branch] [from-branch]
-  - `to-branch`: Target branch (default: main)
-  - `from-branch`: Source branch (default: current branch)
-- `merge`: Merge [to-branch] [from-branch]
-  - `to-branch`: Target branch (default: main)
-  - `from-branch`: Source branch (default: current branch)
-## Quick Reference
-| Task | Reference |
-|------|-----------|
-| Commit | `references/workflow-commit.md` |
-| Push | `references/workflow-push.md` |
-| Pull Request | `references/workflow-pr.md` |
-| Merge | `references/workflow-merge.md` |
-| Standards | `references/commit-standards.md` |
-| Safety | `references/safety-protocols.md` |
-| Branches | `references/branch-management.md` |
-| GitHub CLI | `references/gh-cli-guide.md` |
-## Core Workflow
-### Step 1: Stage + Analyze
-```bash
-git add -A && git diff --cached --stat && git diff --cached --name-only
-```
-### Step 2: Security Check
-Scan for secrets before commit:
-```bash
-git diff --cached | grep -iE "(api[_-]?key|token|password|secret|credential)"
-```
-**If secrets found:** STOP, warn user, suggest `.gitignore`.
-### Step 3: Split Decision
-**NOTE:**
-- Search for related issues on GitHub and add to body.
-- Only use `feat`, `fix`, or `perf` prefixes for files in `.copilot` directory (do not use `docs`).
-**Split commits if:**
-- Different types mixed (feat + fix, code + docs)
-- Multiple scopes (auth + payments)
-- Config/deps + code mixed
-- FILES > 10 unrelated
-**Single commit if:**
-- Same type/scope, FILES ≤ 3, LINES ≤ 50
-### Step 4: Commit
-```bash
-git commit -m "type(scope): description"
-```
-## Output Format
-```
-✓ staged: N files (+X/-Y lines)
-✓ security: passed
-✓ commit: HASH type(scope): description
-✓ pushed: yes/no
-```
-## Error Handling
-| Error | Action |
-|-------|--------|
-| Secrets detected | Block commit, show files |
-| No changes | Exit cleanly |
-| Push rejected | Suggest `git pull --rebase` |
-| Merge conflicts | Suggest manual resolution |
-## References
-- `references/workflow-commit.md` - Commit workflow with split logic
-- `references/workflow-push.md` - Push workflow with error handling
-- `references/workflow-pr.md` - PR creation with remote diff analysis
-- `references/workflow-merge.md` - Branch merge workflow
-- `references/commit-standards.md` - Conventional commit format rules
-- `references/safety-protocols.md` - Secret detection, branch protection
-- `references/branch-management.md` - Naming, lifecycle, strategies
-- `references/gh-cli-guide.md` - GitHub CLI commands reference

package/templates/repo/.github/skills/git/references/commit-standards.md DELETED Viewed

@@ -1,46 +0,0 @@
-# Commit Message Standards
-## Format
-```
-type(scope): description
-```
-## Types (priority order)
-- `feat`: New feature
-- `fix`: Bug fix
-- `docs`: Documentation only
-- `style`: Formatting (no logic change)
-- `refactor`: Restructure without behavior change
-- `test`: Tests
-- `chore`: Maintenance, deps, config
-- `perf`: Performance
-- `build`: Build system
-- `ci`: CI/CD
-## Rules
-- **<72 characters**
-- **Present tense, imperative** ("add" not "added")
-- **No period at end**
-- **Scope optional but recommended**
-- **Focus on WHAT, not HOW**
-- Only use `feat`, `fix`, or `perf` prefixes for files in `.copilot` directory (do not use `docs`).
-## NEVER Include AI Attribution
-- ❌ "Generated with AI"
-- ❌ "Co-Authored-By: AI"
-- ❌ Any AI reference
-## Good Examples
-- `feat(auth): add login validation`
-- `fix(api): resolve query timeout`
-- `docs(readme): update install guide`
-- `refactor(utils): simplify date logic`
-## Bad Examples
-- ❌ `Updated files` (not descriptive)
-- ❌ `feat(auth): added login using bcrypt with salt` (too long, describes HOW)
-- ❌ `Fix bug` (not specific)
-## Special Cases
-- `$HOME/.copilot/` skill updates: `perf(skill): improve token efficiency`
-- `$HOME/.copilot/` new skills: `feat(skill): add database-optimizer`

package/templates/repo/.github/skills/git/references/workflow-commit.md DELETED Viewed

@@ -1,58 +0,0 @@
-# Commit Workflow
-Execute via `git-manager` agent.
-## Tool 1: Stage + Analyze
-```bash
-git add -A && \
-echo "=== STAGED ===" && git diff --cached --stat && \
-echo "=== SECURITY ===" && \
-git diff --cached | grep -c -iE "(api[_-]?key|token|password|secret|credential)" | awk '{print "SECRETS:"$1}' && \
-echo "=== GROUPS ===" && \
-git diff --cached --name-only | awk -F'/' '{
-  if ($0 ~ /\.(md|txt)$/) print "docs:"$0
-  else if ($0 ~ /test|spec/) print "test:"$0
-  else if ($0 ~ /\.copilot/) print "config:"$0
-  else if ($0 ~ /package\.json|lock/) print "deps:"$0
-  else print "code:"$0
-}'
-```
-**If SECRETS > 0:** STOP, show matches, block commit.
-## Tool 2: Split Decision
-NOTE:
-- Search for related issues on GitHub and add to body.
-- Only use `feat`, `fix`, or `perf` prefixes for files in `.copilot` directory (do not use `docs`).
-**From groups, decide:**
-**A) Single commit:** Same type/scope, FILES ≤ 3, LINES ≤ 50
-**B) Multi commit:** Mixed types/scopes, group by:
-- Group 1: `config:` → `chore(config): ...`
-- Group 2: `deps:` → `chore(deps): ...`
-- Group 3: `test:` → `test: ...`
-- Group 4: `code:` → `feat|fix: ...`
-- Group 5: `docs:` → `docs: ...`
-## Tool 3: Commit
-**Single:**
-```bash
-git commit -m "type(scope): description"
-```
-**Multi (sequential):**
-```bash
-git reset && git add file1 file2 && git commit -m "type(scope): desc"
-```
-Repeat for each group.
-## Tool 4: Push (if requested)
-```bash
-git push && echo "✓ pushed: yes" || echo "✓ pushed: no"
-```
-**Only push if user explicitly requested** ("push", "commit and push").