cokit-cli 1.0.3 → 1.0.5

package/templates/repo/.github/prompts/ck-worktree.prompt.md

@@ -0,0 +1,127 @@
+---
+agent: 'agent'
+description: 'Create isolated git worktree for parallel development'
+tools: ['search/codebase', 'read/terminalLastCommand']
+---
+
+Create an isolated git worktree for parallel feature development.
+
+## Workflow
+
+### Step 1: Get Repository Info
+
+```bash
+node  info --json
+```
+
+**Response fields:**
+- `repoType`: "monorepo" or "standalone"
+- `baseBranch`: detected base branch
+- `projects`: array of {name, path} for monorepo
+- `envFiles`: array of .env* files found
+- `dirtyState`: boolean
+
+### Step 2: Gather Info via AskUserQuestion
+
+**Detect branch prefix from user's description:**
+- Keywords "fix", "bug", "error", "issue" → prefix = `fix`
+- Keywords "refactor", "restructure", "rewrite" → prefix = `refactor`
+- Keywords "docs", "documentation", "readme" → prefix = `docs`
+- Keywords "test", "spec", "coverage" → prefix = `test`
+- Keywords "chore", "cleanup", "deps" → prefix = `chore`
+- Keywords "perf", "performance", "optimize" → prefix = `perf`
+- Everything else → prefix = `feat`
+
+**For MONOREPO:** Use AskUserQuestion if project not specified:
+```javascript
+// If user said "/worktree add auth" but multiple projects exist
+AskUserQuestion({
+  questions: [{
+    header: "Project",
+    question: "Which project should the worktree be created for?",
+    options: projects.map(p => ({ label: p.name, description: p.path })),
+    multiSelect: false
+  }]
+})
+```
+
+**For env files:** Always ask which to copy:
+```javascript
+AskUserQuestion({
+  questions: [{
+    header: "Env files",
+    question: "Which environment files should be copied to the worktree?",
+    options: envFiles.map(f => ({ label: f, description: "Copy to worktree" })),
+    multiSelect: true
+  }]
+})
+```
+
+### Step 3: Convert Description to Slug
+
+- "add authentication system" → `add-auth`
+- "fix login bug" → `login-bug`
+- Remove filler words, kebab-case, max 50 chars
+
+### Step 4: Execute Command
+
+**Monorepo:**
+```bash
+node  create "<PROJECT>" "<SLUG>" --prefix <TYPE> --env "<FILES>"
+```
+
+**Standalone:**
+```bash
+node  create "<SLUG>" --prefix <TYPE> --env "<FILES>"
+```
+
+**Options:**
+- `--prefix` - Branch type: feat|fix|refactor|docs|test|chore|perf
+- `--env` - Comma-separated .env files to copy
+- `--json` - Output JSON for parsing
+- `--dry-run` - Preview without executing
+
+## Commands
+
+| Command | Usage | Description |
+|---------|-------|-------------|
+| `create` | `create [project] <feature>` | Create new worktree |
+| `remove` | `remove <name-or-path>` | Remove worktree and branch |
+| `info` | `info` | Get repo info |
+| `list` | `list` | List existing worktrees |
+
+## Error Codes
+
+| Code | Meaning | Action |
+|------|---------|--------|
+| `MISSING_ARGS` | Missing project/feature for monorepo | Ask for both |
+| `MISSING_FEATURE` | No feature name (standalone) | Ask for feature |
+| `PROJECT_NOT_FOUND` | Project not in .gitmodules | Show available projects |
+| `MULTIPLE_PROJECTS_MATCH` | Ambiguous project name | Use AskUserQuestion |
+| `MULTIPLE_WORKTREES_MATCH` | Ambiguous worktree for remove | Use AskUserQuestion |
+| `BRANCH_CHECKED_OUT` | Branch in use elsewhere | Suggest different name |
+| `WORKTREE_EXISTS` | Path already exists | Suggest use or remove |
+| `WORKTREE_CREATE_FAILED` | Git command failed | Show git error |
+| `WORKTREE_REMOVE_FAILED` | Cannot remove worktree | Check uncommitted changes |
+
+## Example Session
+
+```
+User: /worktree fix the login validation bug
+
+Claude: [Runs: node  info --json]
+        [Detects: standalone repo, envFiles: [".env.example"]]
+        [Detects prefix from "fix" keyword: fix]
+        [Converts slug: "login-validation-bug"]
+
+Claude: [Uses AskUserQuestion for env files]
+        "Which environment files should be copied?"
+        Options: .env.example
+
+User: .env.example
+
+Claude: [Runs: node  create "login-validation-bug" --prefix fix --env ".env.example"]
+
+Output: Worktree created at ../worktrees/myrepo-login-validation-bug
+        Branch: fix/login-validation-bug
+```

package/templates/repo/.github/skills/ck-ai-artist/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: 'ck-ai-artist'
+description: 'Write and optimize prompts for AI-generated outcomes across text and image models. Use when crafting prompts for LLMs (Claude, GPT, Gemini), image generators (Midjourney, DALL-E, Stable Diffusion, Imagen, Flux), or video generators (Veo, Runway). Covers prompt structure, style keywords, negative prompts, chain-of-thought, few-shot examples, iterative refinement, and domain-specific patterns for marketing, code, and creative writing.'
+---
+
+# AI Artist - Prompt Engineering
+
+Craft effective prompts for AI text and image generation models.
+
+## Core Principles
+
+1. **Clarity** - Be specific, avoid ambiguity
+2. **Context** - Set scene, role, constraints upfront
+3. **Structure** - Use consistent formatting (markdown, XML tags, delimiters)
+4. **Iteration** - Refine based on outputs, A/B test variations
+
+## Quick Patterns
+
+### LLM Prompts (Claude/GPT/Gemini)
+
+```
+[Role] You are a {expert type} specializing in {domain}.
+[Context] {Background information and constraints}
+[Task] {Specific action to perform}
+[Format] {Output structure - JSON, markdown, list, etc.}
+[Examples] {1-3 few-shot examples if needed}
+```
+
+### Image Generation (Midjourney/DALL-E/Stable Diffusion)
+
+```
+[Subject] {main subject with details}
+[Style] {artistic style, medium, artist reference}
+[Composition] {framing, angle, lighting}
+[Quality] {resolution modifiers, rendering quality}
+[Negative] {what to avoid - only if supported}
+```
+
+**Example**: `Portrait of a cyberpunk hacker, neon lighting, cinematic composition, detailed face, 8k, artstation quality --ar 16:9 --style raw`
+
+## References
+
+Load for detailed guidance:
+
+| Topic | File | Description |
+|-------|------|-------------|
+| LLM | `references/llm-prompting.md` | System prompts, few-shot, CoT, output formatting |
+| Image | `references/image-prompting.md` | Style keywords, model syntax, negative prompts |
+| Nano Banana | `references/nano-banana.md` | Gemini image prompting, narrative style, multi-image input |
+| Advanced | `references/advanced-techniques.md` | Meta-prompting, chaining, A/B testing |
+| Domain Index | `references/domain-patterns.md` | Universal pattern, links to domain files |
+| Marketing | `references/domain-marketing.md` | Headlines, product copy, emails, ads |
+| Code | `references/domain-code.md` | Functions, review, refactoring, debugging |
+| Writing | `references/domain-writing.md` | Stories, characters, dialogue, editing |
+| Data | `references/domain-data.md` | Extraction, analysis, comparison |
+
+## Model-Specific Tips
+
+| Model | Key Syntax |
+|-------|------------|
+| Midjourney | `--ar`, `--style`, `--chaos`, `--weird`, `--v 6.1` |
+| DALL-E 3 | Natural language, no parameters, HD quality option |
+| Stable Diffusion | Weighted tokens `(word:1.2)`, LoRA, negative prompt |
+| Flux | Natural prompts, style mixing, `--guidance` |
+| Imagen/Veo | Descriptive text, aspect ratio, style references |
+
+## Anti-Patterns
+
+- Vague instructions ("make it better")
+- Conflicting constraints
+- Missing context for domain tasks
+- Over-prompting with redundant details
+- Ignoring model-specific strengths/limits

package/templates/repo/.github/skills/ck-ai-artist/references/advanced-techniques.md

@@ -0,0 +1,184 @@
+# Advanced Prompt Engineering
+
+## Prompt Optimization
+
+### DSPy Framework
+Automatic prompt optimization through:
+1. Define task with input/output signatures
+2. Compile with optimizer (BootstrapFewShot, MIPRO)
+3. Model learns optimal prompting strategy
+4. Export optimized prompts for production
+
+### Meta-Prompting
+```
+You are a prompt engineer. Create 5 variations for [task]:
+1. Direct instruction approach
+2. Role-based approach
+3. Few-shot example approach
+4. Chain of thought approach
+5. Constraint-focused approach
+
+Evaluate each, select best.
+```
+
+### Self-Refinement Loop
+```
+Generate: [Initial response]
+Critique: "What's wrong? Score 1-10."
+Refine: "Fix issues, improve score."
+Repeat until score ≥ 8.
+```
+
+## Prompt Chaining
+
+### Sequential Chain
+```
+Chain 1: [Input] → Extract key points
+Chain 2: Key points → Create outline
+Chain 3: Outline → Write draft
+Chain 4: Draft → Edit and polish
+```
+
+### Parallel Chain
+Run independent subtasks simultaneously, merge results.
+
+### Conditional Chain
+```
+If [condition A]: Execute prompt variant 1
+If [condition B]: Execute prompt variant 2
+Else: Execute default prompt
+```
+
+### Loop Pattern
+```
+While not [success condition]:
+    Generate attempt
+    Evaluate against criteria
+    If pass: break
+    Else: refine with feedback
+```
+
+## Evaluation Methods
+
+### LLM-as-Judge
+```
+Rate this [output] on:
+1. Accuracy (1-10)
+2. Completeness (1-10)
+3. Clarity (1-10)
+4. Relevance (1-10)
+
+Provide reasoning for each score.
+Final: Pass/Fail threshold = 7 average.
+```
+
+### A/B Testing Protocol
+1. Single variable per test
+2. 20+ samples minimum
+3. Score on defined criteria
+4. Statistical significance check (p < 0.05)
+5. Document winner, roll out
+
+### Regression Testing
+- Maintain test set of critical examples
+- Run before deploying prompt changes
+- Compare scores to baseline
+- Block deployment if regression detected
+
+## Agent Prompting
+
+### Tool Use Design
+```
+You have access to these tools:
+- search(query): Search the web
+- calculate(expression): Math operations
+- code(language, code): Execute code
+
+To use: <tool_name>arguments</tool_name>
+Wait for result before continuing.
+```
+
+### Planning Prompt
+```
+Task: [Complex goal]
+
+Before acting:
+1. Break into subtasks
+2. Identify dependencies
+3. Plan execution order
+4. Note potential blockers
+
+Then execute step by step.
+```
+
+### Reflection Pattern
+```
+After each step:
+- What worked?
+- What didn't?
+- Adjust approach for next step.
+```
+
+## Parameter Tuning
+
+| Parameter | Low | High | Use Case |
+|-----------|-----|------|----------|
+| Temperature | 0.0-0.3 | 0.7-1.0 | Factual vs Creative |
+| Top-P | 0.8 | 0.95 | Focused vs Diverse |
+| Top-K | 10 | 100 | Conservative vs Exploratory |
+
+**Rule**: Tune temperature first. Only adjust top-p if needed. Never both at once.
+
+## Safety Patterns
+
+### Output Filtering
+```
+Before responding, check:
+- No PII exposure
+- No harmful content
+- No policy violations
+- Aligned with guidelines
+
+If any fail: "I can't help with that."
+```
+
+### Jailbreak Prevention
+- Clear system boundaries upfront
+- Repeat constraints at end
+- "Ignore previous" pattern detection
+- Role-lock: "You are ONLY [role], never anything else"
+
+### Confidence Calibration
+```
+For each claim, provide:
+- Confidence: High/Medium/Low
+- Source: [citation if available]
+- Caveat: [limitations]
+```
+
+## Production Patterns
+
+### Version Control
+- Git for prompt files
+- Semantic versioning (1.0.0, 1.1.0)
+- Changelog per version
+- Rollback capability
+
+### Caching
+- Cache common queries
+- TTL based on content freshness
+- Invalidate on prompt update
+
+### Fallbacks
+```
+Try: Primary prompt
+If fail: Simplified fallback prompt
+If still fail: Human escalation
+Log all failures for analysis.
+```
+
+### Cost Optimization
+- Shorter prompts = fewer tokens
+- Remove redundant examples
+- Use smaller model for simple tasks
+- Batch similar requests

package/templates/repo/.github/skills/ck-ai-artist/references/domain-code.md

@@ -0,0 +1,66 @@
+# Code Generation Patterns
+
+## Function Implementation
+```
+Write a [language] function:
+- Input: [params with types]
+- Output: [return type]
+- Behavior: [logic]
+
+Requirements:
+- Edge cases: [list]
+- Error handling: [approach]
+- Performance: O([complexity])
+```
+
+## Code Review
+```
+Review for:
+1. Bugs/logic errors
+2. Security vulnerabilities
+3. Performance issues
+4. Style violations
+5. Missing edge cases
+
+Format: Issue, line number, severity, fix.
+```
+
+## Refactoring
+```
+Refactor to:
+- [Improvement goal]
+- Maintain backward compatibility
+- Keep public API
+- Add comments for complex logic
+Show before/after.
+```
+
+## Debugging
+```
+<error>[Error message/behavior]</error>
+<code>[Relevant code]</code>
+<context>[When it occurs]</context>
+
+Analyze:
+1. Root cause
+2. Why it happens
+3. Fix with explanation
+4. Prevention strategy
+```
+
+## Test Generation
+```
+Generate tests for [function/class]:
+- Framework: [jest/pytest/etc]
+- Coverage: happy path, edge cases, errors
+- Include: setup, assertion, cleanup
+- Mock: [external dependencies]
+```
+
+## Documentation
+```
+Document this [function/class/API]:
+- Format: [JSDoc/docstring/OpenAPI]
+- Include: description, params, returns, examples
+- Note: edge cases, errors, deprecations
+```

package/templates/repo/.github/skills/ck-ai-artist/references/domain-data.md

@@ -0,0 +1,72 @@
+# Data & Analysis Patterns
+
+## Structured Extraction
+```
+Extract from text:
+<text>[content]</text>
+
+Return JSON:
+{
+  "field1": "value or null",
+  "field2": ["array"]
+}
+
+Rules:
+- Exact matches only
+- Confidence score if uncertain
+- null for missing
+```
+
+## Document Analysis
+```
+Analyze [document type]:
+1. Summary (2-3 sentences)
+2. Key entities (people, orgs, dates)
+3. Main topics (ranked)
+4. Sentiment: positive/neutral/negative
+5. Action items
+```
+
+## Comparison
+```
+Compare [A] and [B]:
+| Criterion | A | B |
+|-----------|---|---|
+| [Factor 1] | | |
+| [Factor 2] | | |
+
+Recommendation: [choice] for [use case]
+```
+
+## Problem Solving
+```
+Problem: [description]
+
+Analyze:
+1. Root cause (5 whys)
+2. Contributing factors
+3. Options (pros/cons)
+4. Recommendation
+5. Implementation steps
+6. Risk mitigation
+```
+
+## Data Transformation
+```
+Transform data:
+- Input format: [CSV/JSON/etc]
+- Output format: [target]
+- Rules: [mapping logic]
+- Validation: [constraints]
+
+Handle: missing values, type mismatches.
+```
+
+## Summarization
+```
+Summarize [content]:
+- Length: [sentences/words]
+- Focus: [key themes]
+- Audience: [technical/general]
+- Preserve: [critical details]
+```

package/templates/repo/.github/skills/ck-ai-artist/references/domain-marketing.md

@@ -0,0 +1,66 @@
+# Marketing Copy Patterns
+
+## Headlines
+```
+Write 5 headline variations for [product].
+Frameworks:
+1. How to [benefit]
+2. [Number] ways to [solve problem]
+3. The secret to [outcome]
+4. Why [audience] love [product]
+5. [Timeframe] to [transformation]
+```
+
+## Product Descriptions
+```
+<product>[Name, features]</product>
+<audience>[Demographics, pain points]</audience>
+
+Write description that:
+- Opens with benefit (not feature)
+- Addresses [main objection]
+- Social proof placeholder
+- Clear CTA
+- Tone: [brand voice]
+- Length: [word count]
+```
+
+## Email Subject Lines
+```
+Generate 10 subject lines for [campaign].
+Mix approaches:
+- Curiosity gap
+- Urgency/scarcity
+- Personalization
+- Question format
+- Number/list
+Under 50 chars. Test 2-3 with emojis.
+```
+
+## Ad Copy
+```
+Platform: [Google/Meta/LinkedIn]
+Objective: [awareness/conversion]
+Character limit: [limit]
+
+Create [N] variations with:
+- Hook (first 5 words critical)
+- Value proposition
+- Social proof element
+- CTA matching platform norms
+```
+
+## Landing Pages
+```
+<offer>[Product/service]</offer>
+<goal>[signup/purchase/download]</goal>
+
+Write sections:
+1. Hero headline + subhead
+2. Problem agitation
+3. Solution introduction
+4. 3-5 benefit bullets
+5. Social proof
+6. CTA with urgency
+7. FAQ (3 objections)
+```

package/templates/repo/.github/skills/ck-ai-artist/references/domain-patterns.md

@@ -0,0 +1,33 @@
+# Domain-Specific Prompt Patterns
+
+Quick reference index. Load specific domain file for detailed patterns.
+
+## Domains
+
+| Domain | File | Use Cases |
+|--------|------|-----------|
+| Marketing | `domain-marketing.md` | Headlines, product copy, emails, ads |
+| Code | `domain-code.md` | Functions, review, refactoring, debugging |
+| Writing | `domain-writing.md` | Stories, characters, dialogue, editing |
+| Data | `domain-data.md` | Extraction, analysis, comparison, reasoning |
+
+## Universal Pattern
+
+All domain prompts follow:
+```
+<context>
+[Domain-specific background]
+</context>
+
+<task>
+[Specific action]
+</task>
+
+<constraints>
+[Quality criteria, format, length, tone]
+</constraints>
+
+<output>
+[Expected structure]
+</output>
+```

package/templates/repo/.github/skills/ck-ai-artist/references/domain-writing.md

@@ -0,0 +1,68 @@
+# Creative Writing Patterns
+
+## Story Outline
+```
+Create [length] story outline:
+- Genre: [genre]
+- Protagonist: [brief]
+- Conflict: [type]
+- Setting: [time/place]
+
+Structure:
+1. Hook/Opening
+2. Inciting incident
+3. Rising action (3 beats)
+4. Climax
+5. Resolution
+```
+
+## Character Voice
+```
+Write as [character]:
+- Background: [history]
+- Speech: [patterns, vocab]
+- Emotion: [current state]
+- Goal: [scene objective]
+
+Maintain voice consistency.
+```
+
+## Dialogue
+```
+Write dialogue between [A] and [B]:
+- Scene: [context]
+- Tension: [conflict source]
+- Subtext: [what's unsaid]
+
+Each character distinct voice. Show don't tell.
+```
+
+## Scene Description
+```
+Describe [scene]:
+- POV: [character/omniscient]
+- Focus: [sensory details]
+- Mood: [atmosphere]
+- Pacing: [fast/slow/measured]
+
+Use active verbs, concrete details.
+```
+
+## Editing Pass
+```
+Edit this [content type]:
+Focus: [clarity/flow/voice/grammar]
+Preserve: [author's style]
+Flag: [major issues only]
+
+Provide tracked changes with rationale.
+```
+
+## Genre Adaptation
+```
+Rewrite [content] as [genre]:
+- Keep: core plot/message
+- Add: genre conventions
+- Tone: [genre-appropriate]
+- Tropes: [use/subvert specific tropes]
+```