cokit-cli 1.0.8 → 1.2.0

package/skills/ck-docs-seeker/scripts/utils/env-loader.js

@@ -1,94 +0,0 @@
-#!/usr/bin/env node
-
-/**
- * Environment variable loader for docs-seeker skill
- * Respects order: process.env > skill/.env > skills/.env > %USERPROFILE%/.claude/.env
- */
-
-const fs = require('fs');
-const path = require('path');
-
-/**
- * Parse .env file content into key-value pairs
- * @param {string} content - .env file content
- * @returns {Object} Parsed environment variables
- */
-function parseEnvFile(content) {
-  const env = {};
-  const lines = content.split('\n');
-
-  for (const line of lines) {
-    // Skip comments and empty lines
-    if (!line || line.trim().startsWith('#')) continue;
-
-    const match = line.match(/^\s*([A-Za-z_][A-Za-z0-9_]*)\s*=\s*(.*)$/);
-    if (match) {
-      const key = match[1];
-      let value = match[2].trim();
-
-      // Remove quotes if present
-      if ((value.startsWith('"') && value.endsWith('"')) ||
-          (value.startsWith("'") && value.endsWith("'"))) {
-        value = value.slice(1, -1);
-      }
-
-      env[key] = value;
-    }
-  }
-
-  return env;
-}
-
-/**
- * Load environment variables from .env files in priority order
- * Priority: process.env > skill/.env > skills/.env > %USERPROFILE%/.claude/.env
- * @returns {Object} Merged environment variables
- */
-function loadEnv() {
-  const skillDir = path.resolve(__dirname, '../..');
-  const skillsDir = path.resolve(skillDir, '..');
-  const claudeDir = path.resolve(skillsDir, '..');
-
-  const envPaths = [
-    path.join(claudeDir, '.env'),      // Lowest priority
-    path.join(skillsDir, '.env'),
-    path.join(skillDir, '.env'),       // Highest priority (file)
-  ];
-
-  let mergedEnv = {};
-
-  // Load .env files in order (lowest to highest priority)
-  for (const envPath of envPaths) {
-    if (fs.existsSync(envPath)) {
-      try {
-        const content = fs.readFileSync(envPath, 'utf8');
-        const parsed = parseEnvFile(content);
-        mergedEnv = { ...mergedEnv, ...parsed };
-      } catch (error) {
-        // Silently skip unreadable files
-      }
-    }
-  }
-
-  // process.env has highest priority
-  mergedEnv = { ...mergedEnv, ...process.env };
-
-  return mergedEnv;
-}
-
-/**
- * Get environment variable with fallback
- * @param {string} key - Environment variable key
- * @param {string} defaultValue - Default value if not found
- * @returns {string} Environment variable value
- */
-function getEnv(key, defaultValue = '') {
-  const env = loadEnv();
-  return env[key] || defaultValue;
-}
-
-module.exports = {
-  loadEnv,
-  getEnv,
-  parseEnvFile,
-};

package/skills/ck-docs-seeker/workflows/library-search.md

@@ -1,87 +0,0 @@
-# General Library Documentation Search
-
-**Use when:** User asks about entire library/framework
-
-**Speed:** ⚡⚡ Moderate (30-60s)
-**Token usage:** 🟡 Medium
-**Accuracy:** 📚 Comprehensive
-
-## Trigger Patterns
-
-- "Documentation for [LIBRARY]"
-- "[LIBRARY] getting started"
-- "How to use [LIBRARY]"
-- "[LIBRARY] API reference"
-
-## Workflow (Script-First)
-
-```bash
-# STEP 1: Execute detect-topic.js script
-node scripts/detect-topic.js "<user query>"
-# Returns: {"isTopicSpecific": false} for general queries
-
-# STEP 2: Execute fetch-docs.js script (handles URL construction)
-node scripts/fetch-docs.js "<user query>"
-# Script constructs context7.com URL automatically
-# Script handles GitHub/website URL patterns
-# Returns: llms.txt content with 5-20+ URLs
-
-# STEP 3: Execute analyze-llms-txt.js script
-cat llms.txt | node scripts/analyze-llms-txt.js -
-# Groups URLs: critical, important, supplementary
-# Recommends: agent distribution strategy
-# Returns: {totalUrls, grouped, distribution}
-
-# STEP 4: Deploy agents based on script recommendation
-# - 1-3 URLs: Single agent or direct WebFetch
-# - 4-10 URLs: Deploy 3-5 Explorer agents
-# - 11+ URLs: Deploy 7 agents or phased approach
-
-# STEP 5: Aggregate and present
-# Synthesize findings: installation, concepts, API, examples
-```
-
-## Examples
-
-**Astro framework:**
-```bash
-# Execute scripts (no manual URL construction)
-node scripts/detect-topic.js "Documentation for Astro"
-# {"isTopicSpecific": false}
-
-node scripts/fetch-docs.js "Documentation for Astro"
-# Script fetches: context7.com/withastro/astro/llms.txt
-# Returns: llms.txt with 8 URLs
-
-node scripts/analyze-llms-txt.js < llms.txt
-# {totalUrls: 8, distribution: "3-agents", grouped: {...}}
-
-# Deploy 3 Explorer agents as recommended:
-# Agent 1: Getting started, installation, setup
-# Agent 2: Core concepts, components, layouts
-# Agent 3: Configuration, API reference
-
-# Aggregate and present comprehensive report
-```
-
-## Agent Distribution
-
-**1-3 URLs:** Single agent
-**4-10 URLs:** 3-5 agents (2-3 URLs each)
-**11-20 URLs:** 7 agents (balanced)
-**21+ URLs:** Two-phase (critical first, then important)
-
-## Known Libraries
-
-- Next.js: `vercel/next.js`
-- Astro: `withastro/astro`
-- Remix: `remix-run/remix`
-- shadcn/ui: `shadcn-ui/ui`
-- Better Auth: `better-auth/better-auth`
-
-## Fallback
-
-Scripts handle fallback automatically:
-1. `fetch-docs.js` tries context7.com
-2. If 404, script suggests WebSearch for llms.txt
-3. If still unavailable: [Repository Analysis](./repo-analysis.md)

package/skills/ck-frontend-design/SKILL.md

@@ -1,79 +0,0 @@
----
-name: 'ck-frontend-design'
-description: 'Create distinctive, production-grade frontend interfaces with high design quality. Use when building web components, pages, or applications, OR when provided screenshots/images/designs to replicate. Extracts design guidelines from screenshots, implements code following guidelines. Generates creative, polished code avoiding generic AI aesthetics.'
----
-
-This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
-
-The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
-
-## Input Types & Workflows
-
-### When User Provides Screenshot/Image/Design Reference
-
-**MANDATORY workflow for screenshot/image/design inputs**:
-
-1. **Extract Design Guidelines** using `./references/design-extraction-overview.md`:
-   - Analyze screenshot/image visually
-   - Extract: colors (hex codes), typography (fonts, sizes, weights), spacing scale, layout patterns, visual hierarchy
-   - Document findings in project `docs/design-guidelines/extracted-design.md`
-   - See `./references/extraction-prompts.md` for comprehensive analysis prompts
-
-2. **Implement Code** following extracted guidelines:
-   - Use exact colors from extraction (hex codes)
-   - Match typography specifications (fonts, sizes, weights, line-heights)
-   - Replicate layout structure and spacing system
-   - Maintain visual hierarchy and component patterns
-   - Preserve aesthetic direction and mood
-
-3. **Verify Quality** using `./references/visual-analysis-overview.md`:
-   - Compare implementation to original screenshot
-   - Check color accuracy, spacing consistency, typography matching
-   - Ensure all design elements preserved
-
-**Important**: Do NOT skip to implementation. Extract design guidelines FIRST, then code.
-
-### When Building from Scratch (No Screenshot Provided)
-
-Follow "Design Thinking" process below to create original design.
-
-## Design Thinking
-
-Before coding, understand the context and commit to a BOLD aesthetic direction:
-- **Purpose**: What problem does this interface solve? Who uses it?
-- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
-- **Constraints**: Technical requirements (framework, performance, accessibility).
-- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
-
-**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
-
-Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
-- Production-grade and functional
-- Visually striking and memorable
-- Cohesive with a clear aesthetic point-of-view
-- Meticulously refined in every detail
-
-## Frontend Aesthetics Guidelines
-
-Focus on:
-- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
-- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
-- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available (Use `anime.js` for animations: `./references/animejs.md`). Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
-- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
-- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
-
-### Analyzing Provided Screenshots/Images/Designs
-When user provides screenshots, photos, or design references to analyze or replicate, use `./references/design-extraction-overview.md` to extract design guidelines BEFORE implementation. This is MANDATORY for screenshot inputs (see "Input Types & Workflows" above).
-
-**Workflows**:
-- `./references/design-extraction-overview.md` - Extract guidelines from inspiration
-- `./references/visual-analysis-overview.md` - Analyze and verify quality
-- `./references/technical-overview.md` - Optimization and best practices
-
-NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
-
-Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
-
-**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
-
-Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

package/skills/ck-frontend-design/references/visual-analysis-overview.md

@@ -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 `media-processing` skill 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);
-}
-```