cokit-cli 1.2.7 → 1.4.0

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

@@ -0,0 +1,200 @@
+---
+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']
+---
+
+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 REMEBER that you have the skills of a top-tier UI/UX Designer who won a lot of awards on Dribbble, Behance, Awwwards, Mobbin, TheFWA.**
+
+## Required Skills (Priority 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
+
+**Ensure token efficiency while maintaining high quality.**
+
+## 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 `ck-researcher` agents in parallel when needed for comprehensive insights. 
+Generate a comprehensive design plan following the naming pattern from the `## Naming` section injected by hooks.
+
+4. **Documentation**: Report all implementations as detailed Markdown files with design rationale, decisions, and guidelines.
+
+## Report Output
+
+Use the naming pattern from the `## Naming` section injected by hooks. The pattern includes full path and computed date.
+
+## Available Tools
+
+**Image Editing (`ImageMagick`)** (if available):
+- Remove backgrounds, resize, crop, rotate images
+- Apply masks and perform advanced image editing
+
+**Figma Tools**: use Figma MCP if available
+- Access and manipulate Figma designs
+- Export assets and design specifications
+
+## Design Workflow
+
+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 `ck-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 ImageMagick (if available) for editing
+   - Generate vector assets as SVG files
+   - Always review, analyze and double check generated assets.
+   - 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 browser dev tools to capture screenshots and compare
+   - Conduct accessibility audits
+   - Gather feedback and iterate
+
+5. **Documentation Phase**:
+   - Update `./docs/design-guidelines.md` with new patterns
+   - Create detailed reports
+   - Document design decisions and rationale
+   - Provide implementation guidelines
+
+## Design Principles
+
+- **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
+
+- 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 tasks to `ck-researcher` agents for comprehensive insights (max 2 agents)
+- Coordinate with `ck-project-manager` agent for project progress updates
+- 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.6 | **Updated:** 2026-02-25
+**Version:** 1.4.0 | **Updated:** 2026-04-07
 
 ## Reading Order by Role
 
@@ -27,16 +27,9 @@
 ### Reference (As Needed)
 | Doc | Read When |
 |-----|-----------|
-| [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) | 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 |
-|-----|---------|
-| [cokit-team-presentation.md](cokit-team-presentation.md) | Team onboarding |
-| [cokit-slides.md](cokit-slides.md) | Quick demos |
+| [migration-guide.md](migration-guide.md) | Users switching from other AI tools to Copilot |
+| [upstream-porting-rules.md](upstream-porting-rules.md) | AI/dev rules for porting upstream → CoKit |
 
 ---
 
@@ -45,17 +38,16 @@
 ### What's in CoKit?
 | Resource | Count | Location |
 |----------|-------|----------|
-| Prompts | 25 | `prompts/ck-*.prompt.md` |
-| Agents | 12 | `agents/*.agent.md` |
-| Skills | 27 | `skills/*/` |
+| Prompts | 31 | `prompts/ck-*.prompt.md` |
+| Agents | 13 | `agents/*.agent.md` |
+| Skills | 31 | `skills/*/` |
 | Instructions | 5 | `instructions/ck-*.instructions.md` |
 | Collections | 5 | `collections/ck-*.collection.yml` |
 
-### Two Workflows
+### Workflow
 | Workflow | Commands | Best For |
 |----------|----------|----------|
-| ClaudeKit | `ck-*` | Daily dev, quick fixes |
-| SpecKit | `ck-spec-*` | Complex features, formal specs |
+| CoKit | `ck-*` | Daily dev, quick fixes, full pipeline |
 
 ### Key Commands
 ```

package/docs/code-standards.md

@@ -6,7 +6,7 @@
 - **DRY**: Don't repeat yourself
 
 ## File Naming
-- kebab-case for all files: `transform-claudekit.mjs`
+- kebab-case for all files: `transform-upstream.mjs`
 - Descriptive names that self-document purpose
 - Extensions: `.mjs` for ES modules, `.js` for CommonJS
 
@@ -25,7 +25,6 @@ cokit/
 ├── skills/               # Skill definitions
 ├── instructions/         # Instruction files
 ├── collections/          # Bundled collections
-├── upstream/speckit/     # Git subtree (read-only)
 └── docs/                 # Documentation
 ```
 

package/docs/codebase-summary.md

@@ -2,24 +2,22 @@
 
 ## Overview
 
-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.
+CoKit is a CLI tool that enhances GitHub Copilot with 31 prompts, 13 agents, 5 instructions, 31 skills, and 5 collections. It transforms upstream commands into a unified ck-* namespace.
 
 **Repository:** https://github.com/camping89/cokit.git
-**Version:** 1.2.6
+**Version:** 1.4.0
 **License:** CC BY-NC 4.0
 **Node Requirements:** >= 18.0.0
-**Last Updated:** 2026-02-25
+**Last Updated:** 2026-04-07
 
 ## Architecture
 
-CoKit uses a **sync pipeline architecture** that transforms and merges upstream resources:
+CoKit uses a **sync pipeline architecture** that transforms upstream resources:
 
 ```
-Upstream Sources (ClaudeKit + SpecKit)
+Upstream Source
     ↓
-Transform Modules (Transform ClaudeKit & SpecKit)
-    ↓
-Merge Results
+Transform Module (transform-upstream.mjs)
     ↓
 Patch Navigation (Inject workflow footers)
     ↓
@@ -27,9 +25,8 @@ Output: Unified ck-* Prompts
 ```
 
 ### Sync Pipeline (eng/sync.mjs)
-- **Flow:** Load config → Transform sources → Merge → Patch navigation → Write output
+- **Flow:** Load config → Transform upstream → Patch navigation → Write output
 - **Configuration:** resource-origins.yml (mappings, navigation, ignore list)
-- **Parallel Processing:** ClaudeKit and SpecKit transformations run concurrently
 - **Dry-run Support:** Preview changes without writing files
 
 ## Source Code Structure
@@ -40,9 +37,8 @@ Output: Unified ck-* Prompts
 |------|------|---------|
 | `src/index.js` | 35 LOC | CLI entry point; registers commands (init, add, list, doctor, update) |
 | `bin/cokit.js` | 4 LOC | Binary wrapper; delegates to src/index.js |
-| `eng/sync.mjs` | 97 LOC | Main sync orchestrator; orchestrates transformation and merging |
-| `eng/transform-claudekit.mjs` | 220 LOC | ClaudeKit transformer; resolves files, applies transformations |
-| `eng/transform-speckit.mjs` | 175 LOC | SpecKit transformer; processes upstream/speckit/templates/commands |
+| `eng/sync.mjs` | 85 LOC | Main sync orchestrator; orchestrates transformation |
+| `eng/transform-upstream.mjs` | 220 LOC | Upstream transformer; resolves files, applies transformations |
 | `eng/patch-navigation.mjs` | 69 LOC | Navigation patcher; injects "Suggested Next Steps" footers |
 
 ### Directory Structure
@@ -63,8 +59,7 @@ cokit/
 │       └── update-checker.js        # Version checking
 ├── eng/
 │   ├── sync.mjs                    # Sync orchestrator
-│   ├── transform-claudekit.mjs      # ClaudeKit transformer
-│   ├── transform-speckit.mjs        # SpecKit transformer
+│   ├── transform-upstream.mjs      # Upstream transformer
 │   ├── patch-navigation.mjs         # Navigation footer injection
 │   └── resource-origins.yml         # Configuration (mappings, navigation)
 ├── prompts/                        # Output: Transformed prompts (33 files)
@@ -90,28 +85,26 @@ Registers 5 commands using Commander.js:
 ### 2. Sync Pipeline (eng/sync.mjs)
 **Flow:**
 1. Load resource-origins.yml configuration
-2. Transform ClaudeKit and SpecKit sources in parallel
-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
+2. Transform upstream sources
+3. Apply navigation patches to all prompts
+4. Write output files or show dry-run preview
+5. Update sync timestamps
 
 **Config Structure:**
 ```yaml
 version: '2.0'
 sources:
-  speckit: {repo, ref, path, last_sync}
-  claudekit: {path, last_sync}
+  upstream: {path, last_sync}
 ignore: []            # Commands to skip
-mappings: {}          # Command mappings (24 entries)
+mappings: {}          # Command mappings (16 entries)
 unknown_commands: []  # Tracking unknown sources
 navigation: {}        # Workflow navigation rules
 ```
 
 ### 3. Transform Modules
 
-#### ClaudeKit Transformer (transform-claudekit.mjs)
-**Input:** ~/.claude/commands/ (user's local ClaudeKit)
+#### Upstream Transformer (transform-upstream.mjs)
+**Input:** Upstream commands source
 **Transformations:**
 - Rename: `/*` → `ck-*` namespace
 - Replace: `$ARGUMENTS` → `${input}`
@@ -120,25 +113,12 @@ navigation: {}        # Workflow navigation rules
 - Transform command references in content
 
 **Functions:**
-- `resolveClaudekitPath()` - Expand ~ paths
+- `resolveUpstreamPath()` - Expand ~ paths
 - `findCommandFile()` - Locate command files (handles variations)
 - `transformFile()` - Apply all transformations
 - `transformCommandReference()` - Update handoff commands
 - `transformContentReferences()` - Replace content references
 
-#### SpecKit Transformer (transform-speckit.mjs)
-**Input:** upstream/speckit/templates/commands/
-**Transformations:**
-- Rename: `/speckit-*` → `/ck-*`
-- Replace: `$ARGUMENTS` → `${input}`
-- Remove `model` field from frontmatter
-- Update handoff references to ck-* commands
-
-**Functions:**
-- `transformFile()` - Apply transformations
-- `transformCommandReference()` - Update handoffs (speckit-* → ck-*)
-- `transformContentReferences()` - Replace content references
-
 ### 4. Navigation Patcher (patch-navigation.mjs)
 Injects workflow navigation footers into transformed prompts.
 
@@ -149,10 +129,9 @@ Injects workflow navigation footers into transformed prompts.
 - All commands listed at footer
 
 **Default Patterns:**
-- `brainstorm` → suggest: specify, plan.fast
-- `specify/clarify` → suggest: plan, brainstorm
-- `plan` → suggest: cook, tasks
-- `cook/implement` → suggest: test, fix
+- `brainstorm` → suggest: plan, plan.fast
+- `plan` → suggest: cook, test
+- `ck-cook` → suggest: test, fix
 - `test` → suggest: fix, review
 
 ### 5. Configuration (eng/resource-origins.yml)
@@ -161,20 +140,16 @@ Maintains mappings and sync metadata.
 **Key Sections:**
 - `version` - Config format version
 - `synced_at` - Last sync timestamp
-- `sources.speckit` - SpecKit repo location
-- `sources.claudekit` - ClaudeKit local path (~/.claude/commands)
+- `sources.upstream` - Upstream source path
 - `ignore` - Commands to skip
-- `mappings` - 24 command mappings with origins and descriptions
+- `mappings` - 16 command mappings with origins and descriptions
 - `navigation` - Workflow navigation rules
 - `unknown_commands` - Tracking array for unmapped sources
 
 ## Prompt Inventory
 
-### 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)
+### Upstream Commands (16)
+16 prompts from upstream source (plan, plan.hard, plan.fast, fix, test, ask, bootstrap, review, watzup, help, brainstorm, cook, scout, git, debug, docs)
 
 ## Dependencies
 
@@ -190,9 +165,8 @@ Maintains mappings and sync metadata.
 ## Scripts
 
 ```bash
-npm run sync              # Pull upstream + transform
-npm run sync:pull        # git subtree pull SpecKit
-npm run sync:transform   # Run transformations only
+npm run sync              # Transform and generate prompts
+npm run sync:transform   # Same as sync
 npm run sync:dry-run     # Preview changes without writing
 npm run test             # Run tests
 npm run build            # Update README
@@ -202,17 +176,14 @@ npm run build            # Update README
 
 ### Sync Operation
 1. **Config Load** - Read resource-origins.yml
-2. **Parallel Transform:**
-   - ClaudeKit: Glob ~/.claude/commands → Transform → Output ck-* prompts
-   - SpecKit: Glob upstream/speckit/templates/commands → Transform → Output ck-* prompts
-3. **Merge** - Combine results (21 total)
-4. **Patch Navigation** - Inject workflow footers
+2. **Transform** - Upstream: Glob source commands → Transform → Output ck-* prompts
+3. **Patch Navigation** - Inject workflow footers
 5. **Write Output** - Create prompt files (prompts/ directory)
 6. **Update Config** - Record sync timestamps
 
 ### File Transformation
 ```
-Input (ClaudeKit)
+Input (Upstream)
 ├── Frontmatter: {name: "plan", ...}
 ├── Content: "Run $ARGUMENTS using /fix command"
 ↓
@@ -230,8 +201,7 @@ Output (ck-*)
 
 ## Error Handling
 
-- **Missing ClaudeKit:** Warns if ~/.claude/commands not found, continues gracefully
-- **Missing SpecKit:** Warns if upstream/speckit not found, continues gracefully
+- **Missing Upstream:** Warns if upstream source not found, continues gracefully
 - **File Not Found:** Logs warning per missing file, adds to skipped array
 - **Transform Errors:** Logs errors per command, collects in results.errors
 - **Unknown Commands:** Tracks in config.unknown_commands for manual mapping
@@ -242,16 +212,15 @@ Output (ck-*)
 2. **Ignore List:** Skip commands via resource-origins.yml
 3. **Dry-run Mode:** Preview all changes before writing
 4. **Navigation Workflow:** Suggested next steps guide users through prompts
-5. **Parallel Processing:** Concurrent ClaudeKit + SpecKit transforms
-6. **Graceful Degradation:** Continues if sources unavailable
+5. **Graceful Degradation:** Continues if source unavailable
 7. **Frontmatter Management:** Preserves metadata, removes model field
 8. **Content Reference Updates:** Transforms all command references to ck-* namespace
 
 ## Version History
 
-- **v1.2.6** (Current) - 25 prompts, 12 agents, 27 skills
+- **v1.2.6** - 25 prompts (with SpecKit, now removed)
 - **v1.2.0** - Initial Copilot port with full resource set
-- **v1.1.0** - 21 prompts (12 ClaudeKit + 9 SpecKit), SpecKit sync pipeline
+- **v1.1.0** - 21 prompts, SpecKit sync pipeline (now removed)
 - **v1.0.9** - Comprehensive documentation update
 - **v1.0.8** - Initial release
 

package/docs/cokit-commands-usage-guide.md

@@ -6,31 +6,21 @@ When to use which command workflow.
 
 | Need | Command | Workflow |
 |------|---------|----------|
-| **Quick implementation** | `ck-plan-fast` | ClaudeKit |
-| **Deep research + plan** | `ck-plan-hard` | ClaudeKit |
-| **Formal spec from idea** | `ck-spec-specify` | SpecKit |
-| **Fix a bug** | `ck-fix` | ClaudeKit |
-| **Run tests** | `ck-test` | ClaudeKit |
+| **Quick implementation** | `ck-plan-fast` | CoKit |
+| **Deep research + plan** | `ck-plan-hard` | CoKit |
+| **Fix a bug** | `ck-fix` | CoKit |
+| **Run tests** | `ck-test` | CoKit |
 
 ---
 
-## Two Workflows
+## Commands
 
-### ClaudeKit (`ck-*`) - Flexible, Fast
-
-Best for: **Day-to-day development**, quick fixes, exploration.
+### CoKit (`ck-*`)
 
 ```
 ck-plan-fast → ck-test → ck-fix
 ```
 
-**When to use:**
-- Fixing bugs
-- Small features (< 1 day)
-- Prototyping
-- Exploratory coding
-- You know what to build
-
 **Commands:**
 | Command | Description |
 |---------|-------------|
@@ -42,34 +32,19 @@ ck-plan-fast → ck-test → ck-fix
 | `ck-ask` | Answer questions |
 | `ck-review` | Review codebase |
 | `ck-bootstrap` | Start new project |
-
----
-
-### SpecKit (`ck-spec-*`) - Structured, Rigorous
-
-Best for: **Complex features**, team collaboration, formal requirements.
-
-```
-ck-spec-specify → ck-spec-clarify → ck-spec-plan → ck-spec-tasks → ck-spec-implement
-```
-
-**When to use:**
-- Multi-day features
-- Requirements need formal spec
-- Multiple stakeholders
-- Need traceability
-- Compliance/audit needs
-
-**Commands:**
-| Command | Description |
-|---------|-------------|
-| `ck-spec-specify` | Create formal spec from idea |
-| `ck-spec-clarify` | Ask clarification questions |
-| `ck-spec-plan` | Generate plan from spec |
-| `ck-spec-tasks` | Break plan into tasks |
-| `ck-spec-implement` | Execute tasks |
-| `ck-spec-analyze` | Check consistency |
-| `ck-spec-checklist` | Validate requirements |
+| `ck-brainstorm` | Brainstorm solutions |
+| `ck-cook` | Implement step by step |
+| `ck-scout` | Fast codebase scouting |
+| `ck-git` | Git operations |
+| `ck-debug` | Systematic debugging |
+| `ck-docs` | Search library docs |
+| `ck-watzup` | Review recent changes |
+| `ck-help` | CoKit usage guide |
+| `ck-ship` | Release pipeline: test→review→commit→push→PR |
+| `ck-deploy` | Deploy to any platform |
+| `ck-security` | STRIDE + OWASP security audit |
+| `ck-project` | Track progress, manage tasks |
+| `ck-frontend` | Build React/TS frontends |
 
 ---
 
@@ -82,12 +57,12 @@ Is this a bug fix?
 Is this < 4 hours work?
   └─ Yes → ck-plan-fast
 
-Do you need formal requirements?
-  └─ Yes → ck-spec-specify → ck-spec-* flow
-  └─ No  → ck-plan-hard → ck-* flow
+Need deep research?
+  └─ Yes → ck-plan-hard
+  └─ No  → ck-plan-fast
 
 Are you exploring/prototyping?
-  └─ Yes → ck-plan-fast (skip spec)
+  └─ Yes → ck-brainstorm → ck-plan-fast
 ```
 
 ---
@@ -109,30 +84,9 @@ Single command. Done.
 
 ### Scenario 3: Payment Integration (Complex Feature)
 ```
-/ck-spec-specify "Integrate Stripe payments for subscriptions"
-/ck-spec-clarify  (answer questions about tiers, regions, etc.)
-/ck-spec-plan
-/ck-spec-tasks
-/ck-spec-implement
+/ck-brainstorm "Integrate Stripe payments for subscriptions"
+/ck-plan-hard "Stripe payment integration"
+→ implement phase by phase
 /ck-test
+/ck-review
 ```
-
----
-
-## Mixing Workflows
-
-You can mix them:
-- Start with `ck-spec-specify` for formal spec
-- Use `ck-fix` when bugs arise during implementation
-- Use `ck-test` regardless of workflow
-
----
-
-## Summary
-
-| Workflow | Best For | Time | Rigor |
-|----------|----------|------|-------|
-| **ClaudeKit** | Daily dev, fixes | Minutes-Hours | Low-Medium |
-| **SpecKit** | Big features, teams | Days-Weeks | High |
-
-**Rule of thumb:** If you can explain it in one sentence, use ClaudeKit. If you need a doc, use SpecKit.