cokit-cli 1.0.9 → 1.2.0

package/skills/frontend-design/references/extraction-best-practices.md

@@ -0,0 +1,141 @@
+# Extraction Best Practices
+
+Guidelines for capturing and analyzing design references effectively.
+
+## Capture Quality Guidelines
+
+### Screenshot Requirements
+- High-resolution (minimum 1920px wide for desktop)
+- Accurate color reproduction (disable browser extensions that alter colors)
+- Actual viewport size, not full-page scrolls
+- Device-specific resolutions (desktop 1920x1080, mobile 390x844)
+- Multiple states: default, hover, active, responsive breakpoints
+
+### Multiple Examples
+- Analyze 3-5 screens minimum for pattern recognition
+- Include different page types (home, product, about, contact)
+- Single screenshots miss patterns
+- Capture from same site to identify consistency
+
+## Analysis Best Practices
+
+### 1. Demand Specifics
+❌ Accept: "Uses blue and gray colors"
+✓ Demand: "Primary: #1E40AF, Secondary: #6B7280, Accent: #F59E0B"
+
+❌ Accept: "Modern sans-serif font"
+✓ Demand: "Inter, weight 600, 48px for h1, tracking -0.02em"
+
+### 2. Document Rationale
+Understand *why* design decisions work, not just *what* they are:
+- Why does this color palette create trust?
+- Why does this spacing scale improve readability?
+- Why does this typography hierarchy guide user attention?
+
+### 3. Create Actionable Guidelines
+Output should be directly implementable in code:
+
+```css
+/* Immediately usable CSS from extraction */
+:root {
+  --font-display: 'Bebas Neue', sans-serif;
+  --font-body: 'Inter', sans-serif;
+
+  --color-primary-600: #1E40AF;
+  --color-accent-500: #F59E0B;
+
+  --spacing-xs: 4px;
+  --spacing-sm: 8px;
+  --spacing-md: 16px;
+  --spacing-lg: 24px;
+
+  --radius-sm: 4px;
+  --radius-md: 8px;
+
+  --shadow-sm: 0 1px 2px rgba(0,0,0,0.05);
+  --shadow-md: 0 4px 6px rgba(0,0,0,0.1);
+}
+```
+
+### 4. Cross-Reference
+- Validate font predictions against Google Fonts library
+- Use font identification tools (WhatFont, Font Ninja) for accuracy
+- Manually verify extracted colors with eyedropper tools
+
+### 5. Iterate Analysis
+First pass may miss subtleties:
+- Run initial comprehensive analysis
+- Review output, identify gaps
+- Run focused follow-up queries for specific elements
+
+## Advanced Techniques
+
+### Design System Mining
+Extract complete design system from single brand (10+ screens):
+
+```bash
+python scripts/gemini_batch_process.py \
+  --files docs/inspiration/brand/*.png \
+  --task analyze \
+  --prompt "Extract complete, production-ready design system:
+- All color tokens (20+ colors)
+- All typography specs (sizes, weights, line-heights)
+- All spacing tokens
+- All component variants
+- All animation timings
+Output as CSS variables ready for implementation." \
+  --output docs/design-guidelines/brand-design-system.md \
+  --model gemini-2.5-flash
+```
+
+### Trend Analysis
+Analyze multiple top designs to identify current trends:
+
+```bash
+python scripts/gemini_batch_process.py \
+  --files docs/inspiration/awwwards-*.png \
+  --task analyze \
+  --prompt "Trend analysis across 10 award-winning designs:
+1. Dominant aesthetic movements
+2. Common color strategies
+3. Typography trends
+4. Layout innovations
+5. Animation patterns
+Identify what's trending in 2024 web design." \
+  --output docs/design-guidelines/trend-analysis.md \
+  --model gemini-2.5-flash
+```
+
+### Historical Evolution
+Track design evolution of single brand over time:
+
+```bash
+python scripts/gemini_batch_process.py \
+  --files docs/inspiration/brand-2020.png docs/inspiration/brand-2024.png \
+  --task analyze \
+  --prompt "Compare 2020 vs 2024 design evolution:
+1. What changed and why
+2. What remained consistent (brand identity)
+3. How trends influenced changes
+4. Lessons for our design evolution" \
+  --output docs/design-guidelines/evolution-analysis.md \
+  --model gemini-2.5-flash
+```
+
+## Common Pitfalls
+
+### ❌ Surface-Level Analysis
+"Uses blue colors and sans-serif fonts"
+**Fix**: Demand specifics—hex codes, font names, size values
+
+### ❌ Missing Context
+Extracting design without understanding target audience or purpose
+**Fix**: Research brand context before analysis
+
+### ❌ Blind Copying
+Extracting and applying design 1:1 to your project
+**Fix**: Extract principles, adapt to your unique context
+
+### ❌ Single Source
+Learning from one example only
+**Fix**: Analyze 3-5 examples to identify patterns vs. anomalies

package/skills/frontend-design/references/extraction-output-templates.md

@@ -0,0 +1,162 @@
+# Extraction Output Templates
+
+Documentation format templates for extracted design guidelines.
+
+## Template 1: Complete Design System
+
+```markdown
+# [Project/Competitor] Design System
+
+## Aesthetic Direction
+- **Style**: Neo-brutalism with organic elements
+- **Mood**: Bold, confident, approachable
+- **Differentiation**: High contrast typography with soft color accents
+
+## Typography
+### Display Font
+- Family: Archivo Black (Google Fonts)
+- Sizes: h1: 72px, h2: 48px, h3: 36px
+- Weights: 400 (regular)
+- Line Height: 1.1
+- Letter Spacing: -0.02em
+
+### Body Font
+- Family: Inter (Google Fonts)
+- Sizes: body: 16px, small: 14px
+- Weights: 400, 500, 600
+- Line Height: 1.6
+- Letter Spacing: 0
+
+## Color Palette
+\```css
+:root {
+  /* Primary Colors */
+  --color-primary-900: #0A1628;
+  --color-primary-600: #1E40AF;
+  --color-primary-400: #60A5FA;
+
+  /* Accent Colors */
+  --color-accent-500: #F59E0B;
+  --color-accent-300: #FCD34D;
+
+  /* Neutral Colors */
+  --color-neutral-900: #111827;
+  --color-neutral-700: #374151;
+  --color-neutral-500: #6B7280;
+  --color-neutral-300: #D1D5DB;
+  --color-neutral-100: #F3F4F6;
+
+  /* Background */
+  --color-bg-primary: #FFFFFF;
+  --color-bg-secondary: #F9FAFB;
+}
+\```
+
+## Spacing System
+- Base: 4px
+- Scale: 4, 8, 12, 16, 24, 32, 48, 64, 96px
+- Usage: Consistent 8px rhythm for most components
+
+## Component Specifications
+
+### Button (Primary)
+\```css
+.button-primary {
+  background: var(--color-primary-600);
+  color: white;
+  padding: 12px 24px;
+  border-radius: 8px;
+  font-weight: 600;
+  transition: background 200ms ease-out;
+}
+.button-primary:hover {
+  background: var(--color-primary-900);
+}
+\```
+
+### Card
+\```css
+.card {
+  background: white;
+  border-radius: 12px;
+  padding: 24px;
+  box-shadow: 0 4px 6px rgba(0,0,0,0.05);
+  transition: box-shadow 200ms ease-out;
+}
+.card:hover {
+  box-shadow: 0 10px 15px rgba(0,0,0,0.1);
+}
+\```
+
+## Motion Guidelines
+- Transition timing: 200ms for micro-interactions, 400ms for page transitions
+- Easing: ease-out for entrances, ease-in for exits
+- Stagger delay: 50ms between sequential elements
+```
+
+## Template 2: Competitive Analysis
+
+```markdown
+# Competitive Design Analysis
+
+## Competitors Analyzed
+1. Competitor A - [URL]
+2. Competitor B - [URL]
+3. Competitor C - [URL]
+
+## Comparative Summary
+
+| Aspect | Competitor A | Competitor B | Competitor C |
+|--------|--------------|--------------|--------------|
+| Aesthetic | Minimalist | Maximalist | Editorial |
+| Primary Color | #1E40AF | #7C3AED | #DC2626 |
+| Typography | Inter | Poppins | Playfair Display |
+| Layout | Grid-based | Asymmetric | Magazine |
+
+## Common Patterns (Industry Standard)
+- All use sans-serif for body text
+- All prioritize mobile-first responsive design
+- All use card-based layouts for content
+- All feature hero sections with large imagery
+
+## Differentiation Opportunities
+1. **Color Strategy**: Competitors use saturated colors; opportunity for muted, sophisticated palette
+2. **Typography**: No one uses display serifs; opportunity for elegant, high-end feel
+3. **Layout**: All symmetric; opportunity for asymmetric, dynamic composition
+
+## Recommendations
+Based on analysis, recommend:
+- Aesthetic: Refined minimalism with editorial typography
+- Color: Muted earth tones with one bold accent
+- Layout: Asymmetric grid with generous white space
+- Differentiation: Unexpected typography hierarchy, subtle animations
+```
+
+## Integration Workflow
+
+### After Extraction
+
+1. **Review & Validate**
+   - Manually verify color codes with eyedropper tool
+   - Cross-reference font predictions against Google Fonts
+   - Check spacing values against browser dev tools
+
+2. **Adapt & Customize**
+   - Don't copy—adapt principles to your unique context
+   - Maintain underlying logic, change expression
+   - Example: Extract "generous white space" principle, apply with your colors
+
+3. **Document Decisions**
+   - Save extracted guidelines in project `docs/design-guidelines/`
+   - Create design system spec from extraction
+   - Reference when generating new assets
+
+4. **Reference in Implementation**
+   - Use extracted tokens when generating new assets with `asset-generation.md`
+   - Apply extracted principles when analyzing your own designs with `visual-analysis.md`
+   - Maintain consistency between inspiration and implementation
+
+5. **Iterate & Refine**
+   - Update guidelines as design evolves
+   - Extract from multiple sources, synthesize learnings
+   - Create your own unique voice from combined insights

package/skills/frontend-design/references/extraction-prompts.md

@@ -0,0 +1,127 @@
+# Extraction Prompt Templates
+
+Complete prompt templates for design guideline extraction.
+
+## Comprehensive Design Analysis Prompt
+
+```
+Extract comprehensive design guidelines from this interface:
+
+## Aesthetic Identification
+- Design Style: Identify the aesthetic movement (minimalism, brutalism, maximalism, glassmorphism, neo-brutalism, organic, luxury, editorial, etc.)
+- Overall Mood: Professional, playful, serious, energetic, calm, bold, refined
+- Differentiation Factor: What makes this design memorable and distinctive?
+
+## Typography System
+- Display Font: Predict font family (favor Google Fonts: Playfair Display, Bebas Neue, DM Serif, Archivo Black, etc.). Provide 2-3 alternatives if uncertain.
+- Body Font: Identify or suggest similar alternatives
+- Font Sizes: Estimate in px for h1, h2, h3, body, small text
+- Font Weights: Used weights (300, 400, 500, 600, 700)
+- Line Heights: Estimate leading ratios
+- Letter Spacing: Tight, normal, or wide tracking
+
+## Color System (CRITICAL)
+- Extract 8-12 distinct colors with accurate hex codes
+- Classify: Primary (1-2), Secondary (1-2), Accent (2-3), Neutral/Gray (3-5), Background (1-2)
+- Note color relationships and usage patterns
+- Identify gradients (provide start/end hex codes and direction)
+
+## Spatial Composition
+- Layout Type: Grid-based, asymmetric, centered, multi-column, magazine-style
+- Grid System: Estimate column count and gutter widths
+- Spacing Scale: Identify spacing rhythm (4px, 8px, 16px, 24px, etc.)
+- White Space Strategy: Generous, tight, varied
+- Section Hierarchy: How content is organized and prioritized
+
+## Visual Elements
+- Border Styles: Radius values (sharp, subtle rounded, fully rounded)
+- Shadows: Box-shadow characteristics (elevation, spread, blur)
+- Backgrounds: Solid, gradients, patterns, textures, images
+- Effects: Blur, overlays, transparency, grain, noise
+- Decorative Elements: Lines, shapes, illustrations, icons
+
+## Component Patterns
+- Button Styles: Shape, size, states, hover effects
+- Card Design: Borders, shadows, padding, content structure
+- Navigation: Style, position, behavior
+- Forms: Input styles, validation, spacing
+- Interactive Elements: Hover states, transitions
+
+## Motion & Animation (if video)
+- Transition Timing: Fast (100-200ms), medium (200-400ms), slow (400-600ms+)
+- Easing Functions: Linear, ease-out, ease-in, cubic-bezier specifics
+- Animation Types: Fade, slide, scale, rotate, stagger
+- Scroll Interactions: Parallax, reveal-on-scroll, sticky elements
+
+## Accessibility Considerations
+- Color Contrast: Evaluate text/background combinations
+- Font Sizes: Minimum sizes used
+- Interactive Targets: Button/link sizes
+- Visual Hierarchy: Clear content prioritization
+
+## Design Highlights
+- Top 3 standout design decisions
+- What makes this design effective
+- Potential improvements or considerations
+
+Output as structured markdown for easy reference.
+```
+
+## Multi-Screen System Extraction Prompt
+
+```
+Analyze these multiple screens to extract the consistent design system:
+
+For each screen:
+1. Identify consistent design tokens (colors, typography, spacing)
+2. Note variations and their rationale
+3. Extract reusable component patterns
+
+Then synthesize:
+- Core design system: Consistent colors, fonts, spacing scales
+- Component library: Buttons, cards, navigation, forms
+- Layout patterns: Grid systems, responsive behavior
+- Visual language: Shared aesthetic principles
+- Design tokens: Create CSS variable recommendations
+
+Provide as a unified design system specification.
+```
+
+## Motion Design Extraction Prompt
+
+```
+Analyze this video to extract motion design guidelines:
+
+1. Transition Timing: Measure duration of key animations (in ms)
+2. Easing Curves: Describe acceleration/deceleration (ease-in, ease-out, spring)
+3. Animation Types: List all animation styles used
+4. Micro-interactions: Button hovers, form focus states, feedback
+5. Page Transitions: How screens change
+6. Scroll Interactions: Parallax, sticky headers, reveal animations
+7. Loading States: Skeleton screens, spinners, progressive reveals
+8. Stagger Effects: Sequential animation delays and patterns
+
+Provide implementable specifications with timing values.
+```
+
+## Competitive Analysis Prompt
+
+```
+Comparative design analysis of 3 competitors:
+
+For each competitor:
+1. Design style and aesthetic approach
+2. Color strategy and brand perception
+3. Typography choices and hierarchy
+4. Layout and information architecture
+5. Unique design elements
+6. Strengths and weaknesses
+
+Synthesis:
+- Common industry patterns (what everyone does)
+- Differentiation opportunities (gaps to exploit)
+- Best practices observed (proven approaches)
+- Design recommendations (how to stand out)
+
+Provide strategic design direction based on analysis.
+```

package/skills/frontend-design/references/technical-accessibility.md

@@ -0,0 +1,119 @@
+# Accessibility Checks
+
+WCAG compliance and accessibility guidelines for generated assets.
+
+## Text Overlay Readability
+
+### Color Contrast Ratios
+- **WCAG AA**: 4.5:1 for normal text, 3:1 for large text
+- **WCAG AAA**: 7:1 for normal text, 4.5:1 for large text
+
+### Testing Requirements
+- Test across image variations
+- Consider adding gradient overlays in code
+- Add text shadows for increased legibility
+
+### Alt Text Guidelines
+- Describe the asset's purpose and mood
+- Don't repeat visible text
+- Keep concise (150 characters max)
+
+## CSS Techniques for Accessibility
+
+### Gradient Overlay for Text Readability
+```css
+.hero {
+  position: relative;
+  background-image: url('hero.webp');
+}
+.hero::before {
+  content: '';
+  position: absolute;
+  inset: 0;
+  background: linear-gradient(
+    to bottom,
+    rgba(0,0,0,0.3) 0%,
+    rgba(0,0,0,0.6) 100%
+  );
+}
+```
+
+### Text Shadow for Contrast
+```css
+.hero-text {
+  text-shadow: 0 2px 4px rgba(0,0,0,0.5);
+}
+```
+
+### Ensure Minimum Contrast
+```css
+.hero-cta {
+  background: var(--color-primary-600);
+  color: white; /* Ensure 4.5:1 contrast */
+}
+```
+
+## Integration Testing Analysis
+
+Analyze how asset works with UI elements:
+
+```bash
+python scripts/gemini_batch_process.py \
+  --files docs/assets/hero-with-text-overlay.png \
+  --task analyze \
+  --prompt "Analyze this design asset with UI elements overlaid:
+
+1. Text Readability: Can all text be read clearly?
+2. Contrast Issues: Identify any WCAG violations
+3. Visual Hierarchy: Do buttons and CTAs stand out?
+4. Spacing Problems: Any crowding or poor breathing room?
+5. Responsive Concerns: Will this work on mobile at 9:16?
+
+Provide specific recommendations for adjustments." \
+  --output docs/assets/integration-analysis.md \
+  --model gemini-2.5-flash
+```
+
+## Next.js Integration Example
+
+```tsx
+// app/components/Hero.tsx
+import Image from 'next/image'
+
+export function Hero() {
+  return (
+    <section className="relative h-screen">
+      {/* Background image with optimization */}
+      <Image
+        src="/assets/hero-desktop.webp"
+        alt="Minimalist desert landscape"
+        fill
+        priority
+        quality={85}
+        className="object-cover"
+        sizes="100vw"
+      />
+
+      {/* Gradient overlay for text readability */}
+      <div className="absolute inset-0 bg-gradient-to-b from-black/30 to-black/60" />
+
+      {/* Content */}
+      <div className="relative z-10 flex h-full items-center justify-center">
+        <h1 className="text-6xl font-bold text-white drop-shadow-lg">
+          Your Headline
+        </h1>
+      </div>
+    </section>
+  )
+}
+```
+
+## Common Issues
+
+### Issue: Poor Text Overlay Readability
+**Symptoms**: Text hard to read over generated background
+**Solutions**:
+- Add CSS gradient overlay (see above)
+- Regenerate with "clean composition for text overlay" in prompt
+- Use darker/lighter areas strategically
+- Add text shadows or backdrop-blur

package/skills/frontend-design/references/technical-best-practices.md

@@ -0,0 +1,97 @@
+# Best Practices Checklists
+
+Quality gates and checklists for asset generation workflows.
+
+## Asset Generation Workflow
+
+### Before Generating Assets
+- [ ] Defined clear aesthetic direction from design brief
+- [ ] Extracted color palette and typography character
+- [ ] Identified asset purpose and integration context
+- [ ] Considered accessibility and text overlay needs
+
+### During Generation
+- [ ] Crafted design-driven, contextual prompt
+- [ ] Selected appropriate model and quality level
+- [ ] Specified correct aspect ratio for use case
+- [ ] Generated multiple variations if exploring
+
+### After Generation
+- [ ] Ran comprehensive visual analysis (score ≥ 7/10)
+- [ ] Extracted exact color palette with hex codes
+- [ ] Compared multiple variations and selected best
+- [ ] Tested with overlaid text/UI elements
+- [ ] Optimized file size for web performance
+- [ ] Created responsive variants if needed
+- [ ] Documented asset usage and guidelines
+
+## Design Guideline Extraction Workflow
+
+### When Analyzing Existing Designs
+- [ ] Captured high-quality reference screenshots
+- [ ] Ran comprehensive design analysis with structured prompts
+- [ ] Extracted specific values (hex codes, px sizes, ms timings)
+- [ ] Analyzed multiple screens for pattern consistency
+- [ ] Validated font predictions against Google Fonts
+- [ ] Documented findings in actionable format
+- [ ] Created CSS variable specifications
+- [ ] Saved extracted guidelines in project docs/
+
+## Quality Gates
+
+### Never Proceed to Integration Without
+- [ ] Visual analysis score ≥ 7/10
+- [ ] Extracted color palette documented
+- [ ] Accessibility contrast checks passed
+- [ ] Responsive variants generated
+- [ ] File optimization completed
+- [ ] Asset usage guidelines documented
+
+## Final Checklist
+
+Before considering any asset "done":
+- [ ] Generated with design-driven prompt (not generic)
+- [ ] Analyzed and scored ≥ 7/10
+- [ ] Extracted color palette for CSS implementation
+- [ ] Tested with UI overlays for readability
+- [ ] Optimized for web (WebP/JPEG)
+- [ ] Created responsive variants
+- [ ] Documented usage guidelines
+- [ ] Accessibility checks passed (contrast, alt text)
+- [ ] Integrated into frontend with proper optimization
+
+## Common Issues & Solutions
+
+### Issue 1: Generated Asset Too Generic
+**Symptoms**: Asset looks like stock photography, lacks design character
+**Solution**:
+- Refine prompt with specific aesthetic movements
+- Reference artists/designers/styles explicitly
+- Use more distinctive color directions
+- Add contextual details that make it unique
+
+### Issue 2: Inconsistent Design Language
+**Symptoms**: Each generated asset feels unrelated
+**Solution**:
+- Extract and document design system from first successful generation
+- Reuse color palette keywords in all subsequent prompts
+- Maintain consistent aesthetic direction across generations
+- Reference previous successful assets in new prompts
+
+### Issue 3: Low Analysis Scores
+**Symptoms**: Consistently getting scores < 7/10
+**Solutions**:
+- Review evaluation criteria—are they realistic?
+- Study high-scoring designs for patterns
+- Use design extraction on inspiration to learn what works
+- Iterate prompt with specific improvements from analysis
+
+### Issue 4: Slow Generation Times
+**Symptoms**: Waiting too long for results
+**Solutions**:
+- Use fast model for exploration phase
+- Generate in batches rather than sequentially
+- Reserve ultra model only for final production assets
+- Run analysis while next generation processes
+
+**Remember**: Design first, generate second. Context is king. Iterate ruthlessly. Analysis is mandatory. Demand specifics, not generalities.

package/skills/frontend-design/references/technical-optimization.md

@@ -0,0 +1,44 @@
+# Cost & Performance Optimization
+
+Model selection strategies and budget guidelines.
+
+## Model Selection Strategy
+
+### 1. Exploration Phase
+Use fast model (3-5 variations):
+- **Cost**: ~$0.02 per image
+- **Speed**: ~5-10 seconds per generation
+- **Use for**: Rapid iteration, aesthetic exploration
+
+### 2. Refinement Phase
+Use standard model (1-2 variations):
+- **Cost**: ~$0.04 per image
+- **Speed**: ~10-20 seconds per generation
+- **Use for**: Production-ready assets
+
+### 3. Final Polish
+Use ultra model (1 generation):
+- **Cost**: ~$0.08 per image
+- **Speed**: ~20-30 seconds per generation
+- **Use for**: Hero images, marketing materials, critical assets
+
+## Analysis Model Strategy
+
+- Use gemini-2.5-flash for all analysis (vision understanding)
+- **Cost**: ~$0.001 per analysis
+- **Speed**: ~2-5 seconds per analysis
+- **Token-efficient**: Images count as ~258-1548 tokens
+
+## Budget Guidelines
+
+- **Small project**: 10-20 images, ~$2-5 total
+- **Medium project**: 50-100 images, ~$10-20 total
+- **Large project**: 200+ images, ~$50+ total
+
+## Optimization Tips
+
+1. **Use fast model first**: Explore variations cheaply before committing to production quality
+2. **Batch analyze**: Analyze multiple variations simultaneously to save time
+3. **Reuse successful prompts**: Once you find a working prompt, reuse it with variations
+4. **Generate responsive variants separately**: Only create mobile versions for assets that need them
+5. **Skip ultra model unless critical**: Standard quality often sufficient for most assets