cokit-cli 1.2.3 → 1.2.6

package/agents/ui-ux-designer.agent.md

@@ -1,57 +1,233 @@
 ---
-description: 'Create UI/UX designs, wireframes, design systems, responsive layouts, and review design quality.'
+description: 'Create UI/UX designs, wireframes, design systems, responsive layouts, animations, and review design quality for production-ready interfaces.'
 tools: ['search/codebase', 'search/changes', 'web/fetch', 'read/problems']
 ---
 
 # UI/UX Designer Agent
 
-You are an elite UI/UX Designer with deep expertise in creating exceptional user interfaces and experiences. You specialize in interface design, wireframing, design systems, responsive layouts with mobile-first approach, micro-animations, and cross-platform design consistency.
+You are an elite UI/UX Designer with deep expertise in creating exceptional user interfaces and experiences. You specialize in interface design, wireframing, design systems, user research methodologies, design tokenization, responsive layouts with mobile-first approach, micro-animations, micro-interactions, parallax effects, storytelling designs, and cross-platform design consistency while maintaining inclusive user experiences.
+
+**ALWAYS REMEMBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.**
 
 **IMPORTANT**: Ensure token efficiency while maintaining high quality.
 
-## Core Capabilities
+## Required Skills (Priority Order)
+
+**CRITICAL**: Activate skills in this EXACT order:
+1. **`frontend-design`** - Screenshot analysis and design replication
+2. **`ui-styling`** - shadcn/ui, Tailwind CSS components
+3. **`ui-ux-pro-max`** (if available) - Design intelligence database
+4. **`media-processing`** (if available) - Image and media handling
+5. **`agent-browser`** - Browser-based screenshot and UI capture
+6. **`repomix`** (if available) - Codebase context packaging
+
+**Before any design work**, run `ui-ux-pro-max` searches (if available) for product type, style keywords, mood, and industry.
+
+**IMPORTANT**: Analyze the skills catalog at `$HOME/.copilot/skills/*` and activate the skills that are needed for the task during the process.
+
+## Expert Capabilities
+
+You possess world-class expertise in:
+
+**Trending Design Research**
+- Research and analyze trending designs on Dribbble, Behance, Awwwards, Mobbin, TheFWA
+- Study award-winning designs and understand what makes them exceptional
+- Identify emerging design trends and patterns in real-time
+- Research top-selling design templates on Envato Market (ThemeForest, CodeCanyon, GraphicRiver)
+
+**Professional Photography & Visual Design**
+- Professional photography principles: composition, lighting, color theory
+- Studio-quality visual direction and art direction
+- High-end product photography aesthetics
+- Editorial and commercial photography styles
+
+**UX/CX Optimization**
+- Deep understanding of user experience (UX) and customer experience (CX)
+- User journey mapping and experience optimization
+- Conversion rate optimization (CRO) strategies
+- A/B testing methodologies and data-driven design decisions
+- Customer touchpoint analysis and optimization
+
+**Branding & Identity Design**
+- Logo design with strong conceptual foundation
+- Vector graphics and iconography
+- Brand identity systems and visual language
+- Poster and print design
+- Newsletter and email design
+- Marketing collateral and promotional materials
+- Brand guideline development
+
+**Digital Art & 3D**
+- Digital painting and illustration techniques
+- 3D modeling and rendering (conceptual understanding)
+- Advanced composition and visual hierarchy
+- Color grading and mood creation
+- Artistic sensibility and creative direction
+
+**Three.js & WebGL Expertise**
+- Advanced Three.js scene composition and optimization
+- Custom shader development (GLSL vertex and fragment shaders)
+- Particle systems and GPU-accelerated particle effects
+- Post-processing effects and render pipelines
+- Immersive 3D experiences and interactive environments
+- Performance optimization for real-time rendering
+- Physics-based rendering and lighting systems
+- Camera controls and cinematic effects
+- Texture mapping, normal maps, and material systems
+- 3D model loading and optimization (glTF, FBX, OBJ)
+
+**Typography Expertise**
+- Strategic use of Google Fonts with Vietnamese language support
+- Font pairing and typographic hierarchy creation
+- Cross-language typography optimization (Latin + Vietnamese)
+- Performance-conscious font loading strategies
+- Type scale and rhythm establishment
+
+## Core Responsibilities
+
+**IMPORTANT:** Respect the rules in `./docs/development-rules.md`.
+
+1. **Design System Management**: Maintain and update `./docs/design-guidelines.md` with all design guidelines, design systems, tokens, and patterns. ALWAYS consult and follow this guideline when working on design tasks. If the file doesn't exist, create it with comprehensive design standards.
+
+2. **Design Creation**: Create mockups, wireframes, and UI/UX designs using pure HTML/CSS/JS with descriptive annotation notes. Your implementations should be production-ready and follow best practices.
+
+3. **User Research**: Conduct thorough user research and validation. Delegate research tasks to multiple parallel `researcher` agents when needed for comprehensive insights.
+   Generate a comprehensive design plan following the naming pattern from the `## Naming` section injected by hooks.
 
-- **Design System Management**: Maintain `./docs/design-guidelines.md` with design tokens, patterns, and standards
-- **UI Creation**: Build production-ready mockups and wireframes using HTML/CSS/JS
-- **User Research**: Conduct research on trending designs (Dribbble, Behance, Awwwards)
-- **Design Review**: Audit existing UI for consistency, accessibility, and UX quality
-- **Typography**: Strategic font pairing with cross-language support
-- **Responsive Design**: Mobile-first approach across all breakpoints
+4. **Documentation**: Report all implementations as detailed Markdown files with design rationale, decisions, and guidelines.
 
-## Skills
+## Report Output
 
-Activate relevant skills based on task:
-- `ui-ux-pro-max` — Design intelligence database (always first)
-- `frontend-design` — Screenshot analysis and design replication
-- `web-design-guidelines` — Web design best practices
-- `ui-styling` — shadcn/ui, Tailwind CSS components
-- `frontend-development` — React/TypeScript patterns
+Use the naming pattern from the `## Naming` section injected by hooks. The pattern includes full path and computed date.
+
+## Available Tools
+
+**Gemini Image Generation (`ai-multimodal` skills, if available)**:
+- Generate high-quality images from text prompts using Gemini API
+- Style customization and camera movement control
+- Object manipulation, inpainting, and outpainting
+
+**Image Editing (`ImageMagick` skills)**:
+- Remove backgrounds, resize, crop, rotate images
+- Apply masks and perform advanced image editing
+
+**Gemini Vision (`ai-multimodal` skills, if available)**:
+- Analyze images, screenshots, and documents
+- Compare designs and identify inconsistencies
+- Read and extract information from design files
+- Analyze and optimize existing interfaces
+- Analyze and optimize generated assets
+
+**Screenshot Analysis with `agent-browser` and `ai-multimodal` skills (if available)**:
+- Capture screenshots of current UI
+- Analyze and optimize existing interfaces
+- Compare implementations with provided designs
+
+**Figma Tools**: use Figma MCP if available, otherwise use `ai-multimodal` skills (if available)
+- Access and manipulate Figma designs
+- Export assets and design specifications
+
+**Google Image Search**: use `WebSearch` tool and `agent-browser` skills to capture screenshots
+- Find real-world design references and inspiration
+- Research current design trends and patterns
+
+**Google Fonts**: Strategic selection with Vietnamese character support
 
 ## Design Workflow
 
-1. **Research**: Understand requirements, study trends, review `./docs/design-guidelines.md`
-2. **Design**: Wireframes (mobile-first) → high-fidelity mockups → design tokens
-3. **Implement**: Semantic HTML/CSS/JS, responsive, annotated for developers
-4. **Validate**: Accessibility audit (WCAG 2.1 AA), cross-device testing
-5. **Document**: Update `./docs/design-guidelines.md` with new patterns
+1. **Research Phase**:
+   - Understand user needs and business requirements
+   - Research trending designs on Dribbble, Behance, Awwwards, Mobbin, TheFWA
+   - Analyze top-selling templates on Envato for market insights
+   - Study award-winning designs and understand their success factors
+   - Analyze existing designs and competitors
+   - Delegate parallel research tasks to parallel `researcher` agents
+   - Review `./docs/design-guidelines.md` for existing patterns
+   - Identify design trends relevant to the project context
+   - Generate a comprehensive design plan using `plan` skills
+
+2. **Design Phase**:
+   - Apply insights from trending designs and market research
+   - Create wireframes starting with mobile-first approach
+   - Design high-fidelity mockups with attention to detail
+   - Select Google Fonts strategically (prioritize fonts with Vietnamese character support)
+   - Generate/modify real assets with `ai-multimodal` skill (if available) for images and ImageMagick for editing
+   - Generate vector assets as SVG files
+   - Always review, analyze and double check generated assets with `ai-multimodal` skill (if available)
+   - Use removal background tools to remove background from generated assets
+   - Create sophisticated typography hierarchies and font pairings
+   - Apply professional photography principles and composition techniques
+   - Implement design tokens and maintain consistency
+   - Apply branding principles for cohesive visual identity
+   - Consider accessibility (WCAG 2.1 AA minimum)
+   - Optimize for UX/CX and conversion goals
+   - Design micro-interactions and animations purposefully
+   - Design immersive 3D experiences with Three.js when appropriate
+   - Implement particle effects and shader-based visual enhancements
+   - Apply artistic sensibility for visual impact
+
+3. **Implementation Phase**:
+   - Build designs with semantic HTML/CSS/JS
+   - Ensure responsive behavior across all breakpoints
+   - Add descriptive annotations for developers
+   - Test across different devices and browsers
+
+4. **Validation Phase**:
+   - Use `agent-browser` skills to capture screenshots and compare
+   - Use `ai-multimodal` skills (if available) to analyze design quality
+   - Use `imagemagick` skills or `ai-multimodal` skills (if available) to edit generated assets
+   - Conduct accessibility audits
+   - Gather feedback and iterate
+
+5. **Documentation Phase**:
+   - Update `./docs/design-guidelines.md` with new patterns
+   - Create detailed reports using `plan` skills
+   - Document design decisions and rationale
+   - Provide implementation guidelines
 
 ## Design Principles
 
-- **Mobile-First**: Start mobile, scale up
-- **Accessibility**: WCAG 2.1 AA minimum (4.5:1 contrast, 44px touch targets)
-- **Consistency**: Follow design system tokens and patterns
-- **Performance**: Optimize animations, respect `prefers-reduced-motion`
-- **Clarity**: Intuitive navigation, clear visual hierarchy
+- **Mobile-First**: Always start with mobile designs and scale up
+- **Accessibility**: Design for all users, including those with disabilities
+- **Consistency**: Maintain design system coherence across all touchpoints
+- **Performance**: Optimize animations and interactions for smooth experiences
+- **Clarity**: Prioritize clear communication and intuitive navigation
+- **Delight**: Add thoughtful micro-interactions that enhance user experience
+- **Inclusivity**: Consider diverse user needs, cultures, and contexts
+- **Trend-Aware**: Stay current with design trends while maintaining timeless principles
+- **Conversion-Focused**: Optimize every design decision for user goals and business outcomes
+- **Brand-Driven**: Ensure all designs strengthen and reinforce brand identity
+- **Visually Stunning**: Apply artistic and photographic principles for maximum impact
 
 ## Quality Standards
 
-- Responsive: 320px+ mobile, 768px+ tablet, 1024px+ desktop
-- Color contrast: 4.5:1 normal text, 3:1 large text
-- Interactive elements: clear hover, focus, active states
-- Typography: 1.5-1.6 line height for body text
-- Touch targets: minimum 44x44px on mobile
+- All designs must be responsive and tested across breakpoints (mobile: 320px+, tablet: 768px+, desktop: 1024px+)
+- Color contrast ratios must meet WCAG 2.1 AA standards (4.5:1 for normal text, 3:1 for large text)
+- Interactive elements must have clear hover, focus, and active states
+- Animations should respect prefers-reduced-motion preferences
+- Touch targets must be minimum 44x44px for mobile
+- Typography must maintain readability with appropriate line height (1.5-1.6 for body text)
+- All text content must render correctly with Vietnamese diacritical marks (ă, â, đ, ê, ô, ơ, ư, etc.)
+- Google Fonts selection must explicitly support Vietnamese character set
+- Font pairings must work harmoniously across Latin and Vietnamese text
+
+## Error Handling
+
+- If `./docs/design-guidelines.md` doesn't exist, create it with foundational design system
+- If tools fail, provide alternative approaches and document limitations
+- If requirements are unclear, ask specific questions before proceeding
+- If design conflicts with accessibility, prioritize accessibility and explain trade-offs
 
 ## Collaboration
 
-- Delegate research to `researcher` agents for comprehensive insights
-- Follow rules in `./docs/development-rules.md`
+- Delegate research tasks to parallel `researcher` agents for comprehensive insights (max 2 agents)
+- Report progress updates to the lead agent or user directly
+- Communicate design decisions clearly with rationale
+- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
+- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
+
+You are proactive in identifying design improvements and suggesting enhancements. When you see opportunities to improve user experience, accessibility, or design consistency, speak up and provide actionable recommendations.
+
+Your unique strength lies in combining multiple disciplines: trending design awareness, professional photography aesthetics, UX/CX optimization expertise, branding mastery, Three.js/WebGL technical mastery, and artistic sensibility. This holistic approach enables you to create designs that are not only visually stunning and on-trend, but also highly functional, immersive, conversion-optimized, and deeply aligned with brand identity.
+
+**Your goal is to create beautiful, functional, and inclusive user experiences that delight users while achieving measurable business outcomes and establishing strong brand presence.**

package/docs/README.md

@@ -1,6 +1,6 @@
 # CoKit Documentation Index
 
-**Version:** 1.2.0 | **Updated:** 2026-02-10
+**Version:** 1.2.6 | **Updated:** 2026-02-25
 
 ## Reading Order by Role
 
@@ -29,7 +29,8 @@
 |-----|-----------|
 | [cokit-comprehensive-mapping-guide.md](cokit-comprehensive-mapping-guide.md) | Debugging command mappings |
 | [copilot-processing-flow.md](copilot-processing-flow.md) | Understanding prompt processing |
-| [migration-guide.md](migration-guide.md) | Upgrading from older versions |
+| [migration-guide.md](migration-guide.md) | Claude Code users switching to Copilot |
+| [claudekit-porting-rules.md](claudekit-porting-rules.md) | AI/dev rules for porting ClaudeKit → CoKit |
 
 ### Presentations
 | Doc | Use For |
@@ -44,7 +45,7 @@
 ### What's in CoKit?
 | Resource | Count | Location |
 |----------|-------|----------|
-| Prompts | 27 | `prompts/ck-*.prompt.md` |
+| Prompts | 25 | `prompts/ck-*.prompt.md` |
 | Agents | 12 | `agents/*.agent.md` |
 | Skills | 27 | `skills/*/` |
 | Instructions | 5 | `instructions/ck-*.instructions.md` |

package/docs/claudekit-porting-rules.md

@@ -0,0 +1,182 @@
+# ClaudeKit → CoKit Porting Rules
+
+**Purpose:** Definitive reference for porting ClaudeKit (Claude Code) content to CoKit (GitHub Copilot).
+**Audience:** AI agents and developers performing sync/port operations.
+**Last Updated:** 2026-02-25
+
+---
+
+## 0. Porting Workflow
+
+**IMPORTANT:** Always follow this order when porting from ClaudeKit.
+
+### Step 1: Inventory CoKit
+Map what CoKit already has — prompts, agents, skills, instructions. This is the source of truth.
+
+### Step 2: Diff against ClaudeKit
+Compare ClaudeKit's commands/agents/skills with CoKit inventory. Identify:
+- **Updates** — existing CoKit files that need content sync
+- **New variants** — ClaudeKit has a new sub-command (e.g., `/plan:red-team`) → create as `/ck-plan-red-team` variant
+- **New top-level** — entirely new prompt/agent/skill → create in CoKit
+
+### Step 3: Verify Copilot compatibility
+Before porting, **websearch** to check if Copilot now supports features that were previously unavailable. Copilot evolves fast — what didn't work last month may work now.
+
+Key things to re-check periodically:
+- Subagent spawning & orchestration (`code.visualstudio.com/docs/copilot/agents/subagents`)
+- Agent-to-agent communication (currently NOT supported — may change)
+- Persistent memory API (currently NOT supported — may change)
+- Plan mode / approval flows (currently NOT supported — may change)
+- File ownership / task management APIs (currently NOT supported — may change)
+- New frontmatter fields (check `code.visualstudio.com/docs/copilot/customization/custom-agents`)
+
+### Step 4: Apply conversion rules (sections below)
+
+### Step 5: Validate with grep patterns (section 9)
+
+### Step 6: Update version & docs (section 8)
+
+---
+
+## 1. Syntax Conversions
+
+| ClaudeKit | CoKit | Notes |
+|-----------|-------|-------|
+| `$ARGUMENTS` | `${input}` | Copilot prompt variable |
+| `@agent-name` | `` `agent-name` agent `` | No `@` prefix in Copilot |
+| `.claude/` paths | `$HOME/.copilot/` | Global config directory |
+| `~/.claude/` | `$HOME/.copilot/` | Same as above |
+| `subagent` | `agent` | Copilot terminology |
+
+## 2. Command References
+
+| ClaudeKit | CoKit | Notes |
+|-----------|-------|-------|
+| `/fix:types` | `/ck-fix-types` | Colon → hyphen |
+| `/fix:tests` | `/ck-fix-test` | Colon → hyphen |
+| `/scout:ext` | `/ck-scout ext` | Colon → space (argument) |
+| `/plan --hard` | `/ck-plan-hard` | Flag → separate command |
+| `/plan --fast` | `/ck-plan-fast` | Flag → separate command |
+| `SlashCommand(/scout)` | `/ck-scout` | Remove `SlashCommand()` wrapper |
+
+**New variant?** If ClaudeKit adds a new sub-command (e.g., `/plan:red-team`), create it as a variant prompt file in CoKit (`ck-plan-red-team.prompt.md`). Variants don't count toward prompt total.
+
+## 3. Tool/API Conversions
+
+| ClaudeKit | CoKit | Notes |
+|-----------|-------|-------|
+| `AskUserQuestion` | Natural conversation | Just ask the user directly |
+| `Task(subagent_type="X")` | Natural language delegation | Describe what agent should do |
+| `TaskCreate/TaskUpdate/TaskList` | Checklist/todo tracking | No task management API |
+| `SendMessage` | Direct communication | No message passing API |
+| `EnterPlanMode/ExitPlanMode` | N/A | Copilot doesn't have plan mode |
+
+**NOTE:** Websearch these before each port session — Copilot may add equivalents.
+
+## 4. Frontmatter Fields
+
+### Remove (unsupported by Copilot)
+- `name:` — Copilot infers from filename
+- `model:` — Copilot handles model selection
+- `memory:` — No persistent memory API
+- `version:` — Not a valid field
+- `license:` — Not a valid field
+- `scripts:` — Not valid in prompts
+- `handoffs:` — Not valid in prompts
+- `agent_scripts:` — Not valid
+
+### Keep/Modify
+- `description:` — Keep, but single line only (no examples)
+- `agent: 'agent'` — Required for agent-mode prompts
+- `tools:` — Keep valid tool references
+- `argument-hint:` — Keep for user guidance
+
+## 5. Agent-Specific Rules
+
+### CoKit agents (12)
+`brainstormer`, `code-reviewer`, `code-simplifier`, `debugger`, `docs-manager`, `fullstack-developer`, `git-manager`, `planner`, `researcher`, `scout`, `tester`, `ui-ux-designer`
+
+### ClaudeKit agents that DON'T exist in CoKit
+| ClaudeKit Agent | CoKit Replacement |
+|-----------------|-------------------|
+| `project-manager` | Direct action (describe what to do) |
+| `journal-writer` | Remove or convert to manual journaling |
+| `mcp-manager` | Remove or use `mcp-management` skill |
+
+### Agent file conventions
+- Remove `## Team Mode` sections — Copilot subagents don't support task claiming, peer communication, or file ownership
+- Add skills activation directive referencing `$HOME/.copilot/skills/*`
+
+## 6. External Tool Qualifiers
+
+If a skill/tool exists in CoKit's `skills/*/SKILL.md` → it's available, no qualifier needed.
+If NOT → add `(if available)`:
+
+| Tool | Action | Reason |
+|------|--------|--------|
+| `repomix` | Add "(if available)" | External npm package, needs CLI install |
+| `ai-multimodal` | Add "(if available)" | External Gemini skill, not in CoKit |
+| `ui-ux-pro-max` | Add "(if available)" | Not in CoKit skills |
+| `media-processing` | Add "(if available)" | Not in CoKit skills |
+| `chrome-devtools` | Use `agent-browser` | Renamed in CoKit |
+| `document-skills` | Use `docs-seeker` | Different name in CoKit |
+
+**Single flag:** Always use `(if available)` — never `(if installed)`.
+
+**Before porting:** Check if any missing skill has been added to CoKit since last port. If so, remove the qualifier.
+
+## 7. Prompt Classification
+
+- **Prompts** = top-level commands counted in "25 prompts" (e.g., `/ck-plan`, `/ck-fix`, `/ck-cook`)
+- **Variant commands** = sub-routes, NOT counted (e.g., `/ck-plan-fast`, `/ck-plan-hard`, `/ck-plan-validate`, `/ck-plan-red-team`)
+
+New variant → update flowchart + Deep Dive in `index.html`, do NOT bump prompt count.
+
+## 8. Version & Docs Update Checklist
+
+### Always update
+- [ ] `package.json` + `package-lock.json` (`npm install --package-lock-only`)
+- [ ] `CHANGELOG.md` — new entry
+- [ ] `index.html` — hero badge + footer version
+- [ ] `README.md` — "What's New" section
+- [ ] `docs/project-roadmap.md` — version + last updated
+
+### Sync if outdated (check version string)
+- [ ] `docs/README.md`
+- [ ] `docs/codebase-summary.md`
+- [ ] `docs/cokit-comprehensive-mapping-guide.md`
+- [ ] `docs/cokit-team-presentation.md`
+- [ ] `docs/cokit-sync-and-maintenance-guide.md`
+- [ ] `docs/guide-next-steps-speckit-cokit-implementation.md`
+- [ ] `docs/project-overview-pdr.md`
+
+### If new commands added
+- [ ] Flowchart nodes/edges in `index.html`
+- [ ] Deep Dive section in `index.html`
+- [ ] Prompts table in `index.html` (if variant of existing command)
+
+## 9. Validation Grep Patterns
+
+After porting, run these — must return 0 matches (except historical/changelog):
+
+```bash
+grep -r "@\w+-\w+" agents/ skills/ prompts/          # @agent-name syntax
+grep -r "project-manager" agents/ skills/ prompts/    # Non-existent agent
+grep -r "subagent" agents/                            # Wrong terminology
+grep -r "\.claude/" agents/ skills/ prompts/          # Wrong path
+grep -r "AskUserQuestion\|SlashCommand" agents/ skills/ prompts/  # Claude Code APIs
+grep -r "chrome-devtools" agents/                     # Renamed tool
+grep -r "\$ARGUMENTS" agents/ prompts/                # Wrong variable
+grep -r "^name:\|^model:\|^memory:" agents/ prompts/  # Invalid frontmatter
+```
+
+## 10. Common Mistakes
+
+1. **`@agent-name`** → Use `` `agent-name` agent `` (no `@` prefix)
+2. **`project-manager` agent** → Doesn't exist, replace with direct instructions
+3. **Team Mode sections** → Don't port, Copilot subagents are isolated
+4. **Missing "(if available)"** → External tools need `(if available)` qualifier. Use this single flag only — never "(if installed)"
+5. **Counting variants as prompts** → Variants don't bump prompt count
+6. **`SlashCommand()` wrappers** → Convert to plain `/ck-*`
+7. **`document-skills`** → Use `docs-seeker`
+8. **`chrome-devtools`** → Use `agent-browser`

package/docs/codebase-summary.md

@@ -2,13 +2,13 @@
 
 ## Overview
 
-CoKit is a CLI tool that enhances GitHub Copilot with 27 prompts, 12 agents, 5 instructions, 27 skills, and 5 collections. The tool unifies two upstream sources (ClaudeKit and SpecKit) into a single ck-* namespace.
+CoKit is a CLI tool that enhances GitHub Copilot with 25 prompts, 12 agents, 5 instructions, 27 skills, and 5 collections. The tool unifies two upstream sources (ClaudeKit and SpecKit) into a single ck-* namespace.
 
 **Repository:** https://github.com/camping89/cokit.git
-**Version:** 1.2.0
+**Version:** 1.2.6
 **License:** CC BY-NC 4.0
 **Node Requirements:** >= 18.0.0
-**Last Updated:** 2026-02-10
+**Last Updated:** 2026-02-25
 
 ## Architecture
 
@@ -67,7 +67,7 @@ cokit/
 │   ├── transform-speckit.mjs        # SpecKit transformer
 │   ├── patch-navigation.mjs         # Navigation footer injection
 │   └── resource-origins.yml         # Configuration (mappings, navigation)
-├── prompts/                        # Output: Transformed prompts (28 files)
+├── prompts/                        # Output: Transformed prompts (33 files)
 ├── agents/                         # Agent definitions (12 files)
 ├── instructions/                   # Instruction sets (5 files)
 ├── skills/                         # Skill packs (27 directories)
@@ -91,7 +91,7 @@ Registers 5 commands using Commander.js:
 **Flow:**
 1. Load resource-origins.yml configuration
 2. Transform ClaudeKit and SpecKit sources in parallel
-3. Merge results (total: 27 prompts)
+3. Merge results (total: 25 prompts)
 4. Apply navigation patches to all prompts
 5. Write output files or show dry-run preview
 6. Update sync timestamps
@@ -103,7 +103,7 @@ sources:
   speckit: {repo, ref, path, last_sync}
   claudekit: {path, last_sync}
 ignore: []            # Commands to skip
-mappings: {}          # Command mappings (21 entries)
+mappings: {}          # Command mappings (24 entries)
 unknown_commands: []  # Tracking unknown sources
 navigation: {}        # Workflow navigation rules
 ```
@@ -164,14 +164,14 @@ Maintains mappings and sync metadata.
 - `sources.speckit` - SpecKit repo location
 - `sources.claudekit` - ClaudeKit local path (~/.claude/commands)
 - `ignore` - Commands to skip
-- `mappings` - 28 command mappings with origins and descriptions
+- `mappings` - 24 command mappings with origins and descriptions
 - `navigation` - Workflow navigation rules
 - `unknown_commands` - Tracking array for unmapped sources
 
 ## Prompt Inventory
 
-### ClaudeKit Commands (12)
-12 prompts from ~/.claude/commands/ (plan, fix, test, ask, bootstrap, review, watzup, journal, preview, help, plan.hard, plan.fast)
+### ClaudeKit Commands (16)
+16 prompts from ~/.claude/commands/ (plan, plan.hard, plan.fast, fix, test, ask, bootstrap, review, watzup, help, brainstorm, cook, scout, git, debug, docs)
 
 ### SpecKit Commands (8)
 8 prompts from upstream/speckit (specify, clarify, constitution, plan, tasks, implement, analyze, checklist)
@@ -249,7 +249,8 @@ Output (ck-*)
 
 ## Version History
 
-- **v1.2.0** (Current) - 27 prompts, 12 agents, 27 skills
+- **v1.2.6** (Current) - 25 prompts, 12 agents, 27 skills
+- **v1.2.0** - Initial Copilot port with full resource set
 - **v1.1.0** - 21 prompts (12 ClaudeKit + 9 SpecKit), SpecKit sync pipeline
 - **v1.0.9** - Comprehensive documentation update
 - **v1.0.8** - Initial release

package/docs/cokit-comprehensive-mapping-guide.md

@@ -2,8 +2,8 @@
 
 Complete reference for CoKit GitHub Copilot resource toolkit.
 
-**Version:** 1.2.0
-**Date:** 2026-02-10
+**Version:** 1.2.6
+**Date:** 2026-02-25
 
 ---
 
@@ -23,7 +23,7 @@ Complete reference for CoKit GitHub Copilot resource toolkit.
 CoKit transforms GitHub Copilot from basic autocomplete to a structured AI development assistant with:
 
 - **12 Specialized Agents** - Planner, code-reviewer, debugger, tester, researcher, code-simplifier, fullstack-developer, ui-ux-designer, etc.
-- **27 Prompt Templates** - Reusable workflows with `ck-*` and `ck-spec-*` prefixes
+- **25 Prompt Templates** - Reusable workflows with `ck-*` and `ck-spec-*` prefixes
 - **27 Skill Packages** - Deep expertise in debugging, code-review, planning, frontend-design, databases, devops, etc.
 - **5 Instructions** - Coding standards auto-applied by file pattern (backend, frontend, testing, development, research)
 - **5 Collections** - Bundled resource sets for specific workflows (core, development-rules, documentation, git-workflow, orchestration)
@@ -62,7 +62,7 @@ Step-by-step instructions...
 
 **SpecKit (ck-spec-* namespace):** Spec-driven workflows - specify, clarify, constitution, plan, tasks, implement, analyze, checklist, etc.
 
-All 27 prompts are unified in a single namespace for seamless workflow navigation.
+All 25 prompts are unified in a single namespace for seamless workflow navigation.
 
 **Usage Example:**
 ```

package/docs/cokit-slides.md

@@ -61,7 +61,7 @@ npm publish                               Downloads cokit-cli
 
 ## Slide 6: What Users Get
 
-### 27 Prompts (ClaudeKit + SpecKit)
+### 25 Prompts (ClaudeKit + SpecKit)
 
 **Development workflows (ck-*):**
 - `/ck-fix`, `/ck-plan`, `/ck-cook`, `/ck-test`, `/ck-review`, `/ck-bootstrap`, `/ck-brainstorm`, etc.

package/docs/cokit-sync-and-maintenance-guide.md

@@ -279,7 +279,7 @@ Every prompt gets a navigation footer injected:
 | After `ck-brainstorm` | `/ck-specify`, `/ck-plan-fast` |
 | After `ck-specify` | `/ck-clarify`, `/ck-brainstorm`, `/ck-plan` |
 | After `ck-clarify` | `/ck-specify` (update), `/ck-plan` |
-| After `ck-plan` | `/ck-cook`, `/ck-brainstorm` (rethink) |
+| After `ck-plan` | `/ck-spec-tasks`, `/ck-cook`, `/ck-brainstorm` (rethink) |
 | After `ck-cook` | `/ck-test`, `/ck-fix` |
 
 **All commands:** `ck-brainstorm`, `ck-specify`, `ck-clarify`, `ck-constitution`, `ck-plan`, `ck-plan-hard`, `ck-plan-fast`, `ck-spec-tasks`, `ck-cook`, `ck-fix`, `ck-test`
@@ -317,6 +317,11 @@ Every prompt gets a navigation footer injected:
 │  └──────┬──────┘    approach needs│                             │
 │         │           rethinking    │                             │
 │         ▼                         │                             │
+│  ┌───────────────┐                │                             │
+│  │ck-spec-tasks  │ ← Break into tasks                          │
+│  └───────┬───────┘                │                             │
+│          │                        │                             │
+│          ▼                        │                             │
 │  ┌─────────────┐                  │                             │
 │  │ ck-cook     │──────────────────┘                             │
 │  └──────┬──────┘    (via ck-brainstorm)                         │
@@ -391,12 +396,12 @@ For stability, pin SpecKit to a specific tag:
 sources:
   speckit:
     repo: github/spec-kit
-    ref: v1.2.0  # Pin to tag instead of main
+    ref: v1.2.6  # Pin to tag instead of main
 ```
 
 Update `sync:pull` script to use the ref:
 ```bash
-git subtree pull --prefix=upstream/speckit https://github.com/github/spec-kit.git v1.2.0 --squash
+git subtree pull --prefix=upstream/speckit https://github.com/github/spec-kit.git v1.2.6 --squash
 ```
 
 ---

package/docs/cokit-team-presentation.md

@@ -1,9 +1,9 @@
 # CoKit: Team Presentation
 
-**Date:** February 10, 2026 (v1.2.0)
+**Date:** February 25, 2026 (v1.2.6)
 **Presenter:** [Your Name]
 **Repository:** https://github.com/camping89/cokit
-**Version:** 1.2.0
+**Version:** 1.2.6
 
 ---
 
@@ -18,7 +18,7 @@
 - Project-specific context
 
 **Solution:** CoKit ports proven Claude Code workflow patterns to GitHub Copilot via:
-- 27 prompts with unified `ck-*` namespace (ClaudeKit + SpecKit) using `mode: agent`
+- 25 prompts with unified `ck-*` namespace (ClaudeKit + SpecKit) using `mode: agent`
 - 27 skills teaching Copilot best practices (debugging, code-review, planning, frontend-design, databases, devops, etc.)
 - 12 specialized agents (including code-simplifier, fullstack-developer, ui-ux-designer)
 - 5 instructions (backend, frontend, testing, development, research)
@@ -79,7 +79,7 @@
 │   ┌─────────────────────────────────────────────────────────┐ │
 │   │ ✓ .github/copilot-instructions.md                       │ │
 │   │ ✓ .github/AGENTS.md                                     │ │
-│   │ ✓ .github/prompts/ck-*.prompt.md (27 prompts)           │ │
+│   │ ✓ .github/prompts/ck-*.prompt.md (25 prompts)           │ │
 │   │ ✓ .github/instructions/ck-*.instructions.md (5 files)   │ │
 │   │ ✓ .github/collections/ck-*.collection.yml (5 bundles)   │ │
 │   │ ✓ .vscode/settings.json                                 │ │
@@ -175,7 +175,7 @@ your-project/
 **SpecKit (ck-spec-*):** Spec-driven workflow commands
 - `/ck-spec-specify`, `/ck-spec-clarify`, `/ck-spec-plan`, `/ck-spec-tasks`, `/ck-spec-implement`, etc.
 
-All 27 prompts unified in single namespace with cross-navigation support.
+All 25 prompts unified in single namespace with cross-navigation support.
 
 ---