@haposoft/cafekit 0.8.15 → 0.8.17

package/src/antigravity/workflows/spec-tasks.md

@@ -1,156 +0,0 @@
----
-description: Generate implementation tasks for a specification
-allowed-tools: Glob, Grep, Read, Write, Edit, WebSearch, WebFetch
-argument-hint: <feature-name> [-y] [--sequential]
----
-
-# Implementation Tasks Generator
-
-<background_information>
-- **Mission**: Generate detailed, actionable implementation tasks that translate technical design into executable work items
-- **Success Criteria**:
-  - All requirements mapped to specific tasks
-  - Tasks properly sized (1-3 hours each)
-  - Clear task progression with proper hierarchy
-  - Natural language descriptions focused on capabilities
-</background_information>
-
-<instructions>
-## Core Task
-Generate implementation tasks for feature **$ARGUMENTS** based on approved requirements and design.
-
-## Execution Steps
-
-### Step 0: Validate Phase State (Plan-Style Gate)
-
-- Read `.specs/$ARGUMENTS/spec.json` first
-- If feature directory or `spec.json` is missing: stop and instruct user to run `/spec-init <project-description>`, `/spec-requirements <feature-name>`, and `/spec-design <feature-name>` first
-- If design has not been generated yet (phase before design): stop and instruct user to run `/spec-design $ARGUMENTS`
-- If `phase` is already `tasks-generated`: explain tasks phase already exists and only continue for explicit regeneration/merge intent
-
-### Step 1: Load Context
-
-**Read all necessary context**:
-- `.specs/$ARGUMENTS/spec.json`, `requirements.md`, `design.md`
-- `.specs/$ARGUMENTS/tasks.md` (if exists, for merge mode)
-- `.specs/$ARGUMENTS/research.md` (if exists, includes validation log)
-- **Entire `.specs/steering/` directory** for complete project memory (if exists)
-- **Load project docs context (Plan-style quality gate)** when available:
-  - `docs/codebase-summary.md`
-  - `docs/code-standards.md`
-  - `docs/system-architecture.md`
-  - `docs/project-overview-pdr.md`
-- If any docs file is missing, continue and mention missing context in execution output (do not block generation)
-
-**Validate approvals**:
-- If `-y` flag provided: Auto-approve requirements and design in spec.json
-- Otherwise: Verify both approved (stop if not, see Safety & Fallback)
-- **Backward compatibility fallback (older specs):**
-  - If `validation` object is missing, treat validation status as `not-run`
-  - If `design_context` object is missing, treat `validation_recommended` as `false`
-- If `spec.json.validation.status == "completed"`, treat validation as satisfied
-- If validation is missing and `design_context.validation_recommended == true`, warn user to run `/spec-validate $ARGUMENTS` before continuing (do not hard-block)
-- Determine sequential mode based on presence of `--sequential`
-
-### Step 2: Generate Implementation Tasks
-
-**Load generation rules and template**:
-- Read `{{SKILLS_DIR}}/specs/rules/tasks-generation.md` for principles
-- If `sequential` is **false**: Read `{{SKILLS_DIR}}/specs/rules/tasks-parallel-analysis.md` for parallel judgement criteria
-- Read `{{SKILLS_DIR}}/specs/templates/tasks.md` for format (supports `(P)` markers)
-
-**Generate task list following all rules**:
-- Use language specified in spec.json
-- Map all requirements to tasks
-- When documenting requirement coverage, list numeric requirement IDs only (comma-separated) without descriptive suffixes, parentheses, translations, or free-form labels
-- Ensure all design components included
-- Verify task progression is logical and incremental
-- Collapse single-subtask structures by promoting them to major tasks and avoid duplicating details on container-only major tasks (use template patterns accordingly)
-- Apply `(P)` markers to tasks that satisfy parallel criteria (omit markers in sequential mode)
-- Mark optional test coverage subtasks with `- [ ]*` only when they strictly cover acceptance criteria already satisfied by core implementation and can be deferred post-MVP
-- If existing tasks.md found, merge with new content
-
-### Step 3: Finalize
-
-**Write and update**:
-- Create/update `.specs/$ARGUMENTS/tasks.md`
-- Update spec.json metadata:
-  - Set `phase: "tasks-generated"`
-  - Set `approvals.tasks.generated: true, approved: false`
-  - Set `approvals.requirements.approved: true`
-  - Set `approvals.design.approved: true`
-  - Update `updated_at` timestamp
-
-## Critical Constraints
-- **Follow rules strictly**: All principles in tasks-generation.md are mandatory
-- **Natural Language**: Describe what to do, not code structure details
-- **Complete Coverage**: ALL requirements must map to tasks
-- **Maximum 2 Levels**: Major tasks and sub-tasks only (no deeper nesting)
-- **Sequential Numbering**: Major tasks increment (1, 2, 3...), never repeat
-- **Task Integration**: Every task must connect to the system (no orphaned work)
-</instructions>
-
-## Tool Guidance
-- **Read first**: Load all context, rules, and templates before generation
-- **Write last**: Generate tasks.md only after complete analysis and verification
-
-## Output Description
-
-Provide brief summary in the language specified in spec.json:
-
-1. **Status**: Confirm tasks generated at `.specs/$ARGUMENTS/tasks.md`
-2. **Task Summary**: 
-   - Total: X major tasks, Y sub-tasks
-   - All Z requirements covered
-   - Average task size: 1-3 hours per sub-task
-3. **Quality Validation**:
-   - ✅ All requirements mapped to tasks
-   - ✅ Task dependencies verified
-   - ✅ Testing tasks included
-4. **Next Action**: Review tasks and proceed when ready
-
-**Format**: Concise (under 200 words)
-
-## Safety & Fallback
-
-### Error Scenarios
-
-**Requirements or Design Not Approved**:
-- **Stop Execution**: Cannot proceed without approved requirements and design
-- **User Message**: "Requirements and design must be approved before task generation"
-- **Suggested Action**: "Run `/spec-tasks $ARGUMENTS -y` to auto-approve both and proceed"
-
-**Missing Requirements or Design**:
-- **Stop Execution**: Both documents must exist
-- **User Message**: "Missing requirements.md or design.md at `.specs/$ARGUMENTS/`"
-- **Suggested Action**: "Complete requirements and design phases first"
-
-**Incomplete Requirements Coverage**:
-- **Warning**: "Not all requirements mapped to tasks. Review coverage."
-- **User Action Required**: Confirm intentional gaps or regenerate tasks
-
-**Template/Rules Missing**:
-- **User Message**: "Template or rules files missing in `{{SKILLS_DIR}}/specs/`"
-- **Fallback**: Use inline basic structure with warning
-- **Suggested Action**: "Check repository setup or restore template files"
-
-**Missing Numeric Requirement IDs**:
-- **Stop Execution**: All requirements in requirements.md MUST have numeric IDs. If any requirement lacks a numeric ID, stop and request that requirements.md be fixed before generating tasks.
-
-### Next Phase: Implementation
-
-**Before Starting Implementation**:
-- **IMPORTANT**: Clear conversation history and free up context before running `/code`
-- This applies when starting first task OR switching between tasks
-- Fresh context ensures clean state and proper task focus
-
-**If Tasks Approved**:
-- Execute coding pass from approved spec tasks: `/code $ARGUMENTS`
-- After coding, run `/test` then `/review`
-- Repeat in small passes and clear context between iterations when needed
-
-**If Modifications Needed**:
-- Provide feedback and re-run `/spec-tasks $ARGUMENTS`
-- Existing tasks used as reference (merge mode)
-
-**Note**: Continue with `/test` then `/review` after `/code` to complete the workflow.

package/src/antigravity/workflows/spec-validate.md

@@ -1,106 +0,0 @@
----
-description: Validate design decisions with interview questions before task generation
-allowed-tools: Read, Write, Edit, Glob, AskUserQuestion
-argument-hint: <feature-name>
----
-
-# Specification Validation Interview
-
-<background_information>
-- **Mission**: Validate critical design decisions, assumptions, and trade-offs before generating implementation tasks.
-- **Success Criteria**:
-  - Ask targeted, concrete questions about high-impact decisions
-  - Record answers in spec artifacts for future traceability
-  - Update spec metadata to reflect validation status
-</background_information>
-
-<instructions>
-## Core Task
-Run a structured interview for feature **$ARGUMENTS** and persist decisions.
-
-## Execution Steps
-
-### Step 0: Resolve & Validate State
-- Require `$ARGUMENTS` as feature name
-- Read `.specs/$ARGUMENTS/spec.json`
-- Stop with guidance if spec does not exist
-- Ensure `requirements.md` and `design.md` exist before validation
-
-### Step 1: Load Validation Context
-Read:
-- `.specs/$ARGUMENTS/spec.json`
-- `.specs/$ARGUMENTS/requirements.md`
-- `.specs/$ARGUMENTS/design.md`
-- `.specs/$ARGUMENTS/research.md` (if exists)
-
-Extract decision points around:
-- architecture and boundaries
-- assumptions and defaults
-- integration risks
-- scope and sequencing
-- testing/security/performance trade-offs
-
-### Step 2: Determine Question Budget
-Use injected session validation settings when available (`Validation: mode=X, questions=MIN-MAX`).
-- If unavailable, use 3-6 questions
-- Ask only meaningful questions that can change implementation
-- Each question must have 2-4 concrete options
-
-### Step 3: Interview User
-Use `AskUserQuestion` in batches (max 4 questions per call).
-Rules:
-- Include one recommended option when a safe default exists
-- Keep options mutually exclusive
-- Do not ask redundant questions
-
-### Step 4: Persist Validation Log
-Append to `.specs/$ARGUMENTS/research.md` under `## Validation Log`.
-If section missing, create it.
-
-Session format:
-```markdown
-## Validation Log
-
-### Session N — YYYY-MM-DD
-- Questions asked: X
-
-1. [Category] Question text
-   - Options: A | B | C
-   - Answer: ...
-   - Rationale: why this decision matters
-
-#### Confirmed Decisions
-- ...
-
-#### Follow-up Actions
-- [ ] ...
-```
-
-### Step 5: Update Metadata
-Update `.specs/$ARGUMENTS/spec.json`:
-- `approvals.requirements.approved: true`
-- `approvals.design.approved: true`
-- `validation.last_validated_at: <ISO timestamp>`
-- `validation.questions_asked: <number>`
-- `validation.status: "completed"`
-- increment `validation.session_count` (initialize to 1 if absent)
-- update `updated_at`
-
-## Constraints
-- Keep input/output contract of existing `spec-*` commands unchanged
-- Validation must be traceable and append-only (never overwrite old sessions)
-- Ask fewer questions when artifact is simple; quality over quantity
-</instructions>
-
-## Output Description
-Provide concise summary:
-1. Validation status and files updated
-2. Number of questions asked
-3. Top confirmed decisions
-4. Recommended next command:
-   - `/spec-tasks $ARGUMENTS` when ready
-
-## Safety & Fallback
-- Missing spec/design artifacts: stop and instruct the exact preceding command
-- Empty decision surface: ask only 1-2 high-value confirmation questions
-- Write failure: report exact path and retry guidance

package/src/antigravity/workflows/test.md

@@ -1,13 +0,0 @@
----
-description: Run project tests and report failures concisely.
-allowed-tools: Bash, Read, Grep
-argument-hint: [scope]
----
-
-# /test
-
-Run the project's test command and report:
-- total passed/failed
-- failing test names
-- root cause hints
-- next fix action

package/src/claude/hooks/lib/skill-router-routes.cjs

@@ -1,196 +0,0 @@
-const MIN_SCORE = 4;
-const WEIGHTS = { strong: 6, medium: 3, weak: 1, negative: -5 };
-
-const ROUTES = [
-  route('hapo:hotfix', 'urgent fix or production regression', 100, {
-    strong: ['hotfix', 'fix bug', 'fix lỗi', 'fix loi', 'sửa lỗi', 'sua loi', 'production bug', 'prod bug', 'regression', 'lỗi production', 'loi production', 'sửa gấp', 'sua gap', 'バグ修正', '不具合修正', '本番障害', '本番バグ', '緊急修正', '至急修正', 'リグレッション'],
-    medium: ['khẩn cấp', 'khan cap', 'production', 'critical bug', 'rollback', '修正して', '直して', '緊急', '本番', '重大バグ', 'ロールバック', '障害対応'],
-    weak: ['fix', 'fixing', 'sửa', 'sua', 'urgent', 'emergency', 'release is broken', '修正', '直す', '至急', 'リリースが壊れた'],
-    negative: ['slide', 'pptx', 'spec', 'brainstorm'],
-  }),
-  route('hapo:debug', 'bug investigation or failure diagnosis', 90, {
-    strong: ['debug', 'root cause', 'diagnose', 'stack trace', 'không chạy', 'khong chay', 'デバッグ', '原因調査', '根本原因', 'スタックトレース', '動かない'],
-    medium: ['bug', 'error', 'exception', 'failing', 'failed', 'failure', 'broken', 'lỗi', 'loi', 'tại sao', 'tai sao', 'vì sao', 'vi sao', 'nguyên nhân', 'nguyen nhan', 'ci fail', 'build fail', 'バグ', 'エラー', '例外', '失敗', '壊れている', 'なぜ', '原因', 'ci失敗', 'ビルド失敗'],
-    weak: ['sai', 'fail', 'issue', 'problem', '問題', '不具合'],
-    negative: ['commit', 'push', 'slide', 'pptx'],
-  }),
-  route('hapo:specs', 'specification, requirements, design, tasks, or spec validation', 80, {
-    strong: ['spec', 'specs', 'requirements', 'acceptance criteria', 'task breakdown', 'đặc tả', 'dac ta', '仕様', '仕様書', '要件', '受け入れ条件', 'タスク分解', '仕様を作って', '仕様を作成'],
-    medium: ['requirement', 'ears', 'design doc', 'scope', '--validate', 'yêu cầu', 'yeu cau', 'phạm vi', 'pham vi', 'validate spec', 'kiểm tra spec', 'kiem tra spec', '要求', '設計書', 'スコープ', '検証', '仕様を確認'],
-    weak: ['tính năng mới', 'tinh nang moi', 'feature idea', 'user story', 'criteria', 'task list', '新機能', 'ユーザーストーリー', '基準', 'タスクリスト'],
-    negative: ['commit', 'push', 'bug', 'error', 'production', 'pptx', 'pdf', 'reconstruct requirements', 'as-is requirements', 'legacy system documentation', 'documentation from source code', 'docs from source code', 'ソースコードから'],
-  }),
-  route('hapo:develop', 'implementation from an approved spec or task list', 75, {
-    strong: ['develop', 'implement', 'implementation', 'theo spec', 'theo specs', 'approved spec', 'làm theo spec', 'lam theo spec', '実装', '開発', '仕様に沿って', '仕様どおり', '承認済み仕様'],
-    medium: ['build this', 'code this', 'start task', 'run task', 'thực hiện task', 'thuc hien task', 'phát triển', 'phat trien', 'bắt đầu implement', 'bat dau implement', 'vào code', 'vao code', '作って', 'コードを書いて', 'タスクを開始', 'タスクを実行', '開発して', '実装して'],
-    weak: ['triển khai', 'trien khai', 'đưa vào code', 'dua vao code', 'code feature', 'コード化', '機能を作る'],
-    negative: ['bug', 'debug', 'review', 'test only', 'commit'],
-  }),
-  route('hapo:test', 'test, verification, QA, or runtime validation', 70, {
-    strong: ['unit test', 'integration test', 'e2e', 'playwright', 'coverage', 'test all', 'run all tests', 'test toàn bộ', 'test toan bo', 'kiểm thử', 'kiem thu', 'kiểm tra toàn bộ', 'kiem tra toan bo', '単体テスト', '結合テスト', '全体テスト', 'カバレッジ', 'テストして'],
-    medium: ['test', 'tests', 'testing', 'qa', 'verify', 'verification', 'kiểm tra chạy', 'kiem tra chay', 'xác minh', 'xac minh', 'テスト', '検証', '確認', '動作確認', '全体確認'],
-    weak: ['assert', 'runtime proof', 'manual qa', 'end to end', 'smoke test', 'アサート', 'スモークテスト'],
-    negative: ['spec', 'requirements', 'commit', 'push'],
-  }),
-  route('hapo:code-review', 'code review, audit, security, or quality assessment', 68, {
-    strong: ['code review', 'security review', 'performance review', 'đánh giá code', 'danh gia code', 'コードレビュー', 'セキュリティレビュー', '性能レビュー'],
-    medium: ['review', 'audit', 'quality', 'đánh giá', 'danh gia', 'kiểm tra chất lượng', 'kiem tra chat luong', 'レビュー', '監査', '品質', '品質確認'],
-    weak: ['risk', 'maintainability', 'readability', 'vulnerability', 'lỗ hổng', 'lo hong', 'リスク', '保守性', '可読性', '脆弱性'],
-    negative: ['slide', 'pptx', 'commit and push'],
-  }),
-  route('hapo:git', 'git, commit, push, branch, tag, or pull request workflow', 65, {
-    strong: ['commit', 'push', 'pull request', 'git', 'đẩy lên', 'day len', 'コミット', 'プッシュ', 'プルリク', 'リリースして'],
-    medium: ['pr ', 'branch', 'tag', 'release', 'publish', 'merge', 'rebase', 'ブランチ', 'タグ', 'リリース', '公開', 'マージ', 'リベース'],
-    weak: ['origin', 'remote', 'checkout', 'stash', 'version bump', 'リモート', 'チェックアウト', 'スタッシュ', 'バージョン更新'],
-    negative: ['deploy', 'test', 'review only'],
-  }),
-  route('hapo:inspect', 'codebase discovery, file search, structure scan, or locating implementation areas', 64, {
-    strong: ['inspect', 'codebase scan', 'scan codebase', 'scan source', 'file discovery', 'find files', 'locate files', 'xem source', 'xem codebase', 'kiểm tra source', 'kiem tra source', 'kiểm tra source code', 'kiem tra source code', 'quét source', 'quet source', 'quét codebase', 'quet codebase', 'kiểm tra cấu trúc', 'kiem tra cau truc', 'コード構造', 'ソース確認', 'コードベース確認', 'ファイル探索', '構造を確認'],
-    medium: ['search files', 'find where', 'where is', 'project structure', 'code structure', 'repo structure', 'source code', 'tìm file', 'tim file', 'tìm trong source', 'tim trong source', 'cấu trúc project', 'cau truc project', 'ở đâu', 'o dau', 'nằm đâu', 'nam dau', '関連ファイル', 'どこにある', 'プロジェクト構造', 'リポジトリ構造', '探して'],
-    weak: ['scan', 'inspect code', 'explore code', 'xem qua', 'xem giúp', '調べて', '確認して'],
-    negative: ['bug', 'error', 'lỗi', 'loi', 'fail', 'failure', 'production', 'hotfix', 'fix', 'sửa', 'sua', 'debug', 'develop', 'implement', 'test', 'commit', 'push', 'slide', 'pptx'],
-  }),
-  route('hapo:impact-analysis', 'impact analysis before changing existing behavior', 64, {
-    strong: ['impact analysis', 'blast radius', 'ảnh hưởng', 'anh huong', 'tác động', 'tac dong', '影響分析', '影響範囲', '影響', '副作用'],
-    medium: ['impact', 'liên quan những đâu', 'lien quan nhung dau', 'affected files', 'dependency impact', '関連箇所', '影響ファイル', '依存関係'],
-    weak: ['before changing', 'risk area', 'downstream', 'upstream', 'side effect', '変更前', 'リスク範囲', '下流', '上流'],
-    negative: ['slide', 'pptx'],
-  }),
-  route('hapo:frontend-design', 'UI/UX design, visual style, layout, or color system', 62, {
-    strong: ['ui design', 'visual style', 'color system', 'thiết kế giao diện', 'thiet ke giao dien', 'màu sắc', 'mau sac', 'uiデザイン', '画面デザイン', 'ビジュアルスタイル', '配色'],
-    medium: ['ux', 'layout', 'style', 'theme', 'responsive design', 'giao diện', 'giao dien', 'wireframe', 'レイアウト', 'スタイル', 'テーマ', 'レスポンシブデザイン', '画面', 'ワイヤーフレーム', '色'],
-    weak: ['palette', 'typography', 'spacing', 'polish ui', 'mockup', 'prototype', 'パレット', 'タイポグラフィ', '余白', 'モックアップ', 'プロトタイプ'],
-    negative: ['backend', 'api', 'database'],
-  }),
-  route('hapo:react-best-practices', 'React and Next.js performance patterns, rerender optimization, and Vercel best practices', 60, {
-    strong: ['react best practices', 'next.js best practices', 'vercel react best practices', 'react performance', 'next.js performance', 'optimize react', 'optimize next.js', 'rerender nhiều', 'rerender nhieu', 'nhiều rerender', 'nhieu rerender', 'tối ưu react', 'toi uu react', 'tối ưu next.js', 'toi uu next.js', 'reactベストプラクティス', 'next.jsベストプラクティス', 'react最適化', 'next.js最適化', 'react性能'],
-    medium: ['bundle optimization', 'bundle size', 'rerender optimization', 're-render optimization', 'data fetching', 'server component', 'client component', 'suspense', 'hydration', 'waterfall', 'usememo', 'usecallback', 'react cache', 'optimize', 'optimization', 'tối ưu', 'toi uu', 'tối ưu rerender', 'toi uu rerender', 'tối ưu bundle', 'toi uu bundle', 'バンドル最適化', '再レンダー最適化', '最適化', 'データ取得', 'サーバーコンポーネント', 'クライアントコンポーネント', 'ハイドレーション'],
-    weak: ['react', 'next.js', 'memo', 'rerender', 're-render', 'render performance', 'component performance', 'waterfalls', 'lazy state', 'dynamic import', 'react pattern', 'next.js pattern', 'レンダー性能', 'コンポーネント性能', '動的インポート'],
-    negative: ['backend', 'api', 'database', 'slide', 'pptx', 'commit', 'push'],
-  }),
-  route('hapo:frontend-development', 'frontend implementation work', 58, {
-    strong: ['react', 'next.js', 'vite', 'frontend', 'tailwind', 'web app', 'フロントエンド', 'webアプリ'],
-    medium: ['component', 'css', 'html', 'browser ui', 'client side', 'giao diện react', 'コンポーネント', 'ブラウザui', 'クライアント側', 'react画面'],
-    weak: ['state management', 'hook', 'form', 'table', 'dashboard ui', '状態管理', 'フック', 'フォーム', 'テーブル', 'ダッシュボードui'],
-    negative: ['best practices', 'performance', 'optimize', 'optimization', 'rerender', 're-render', 'tối ưu', 'toi uu', '再レンダー', '最適化', '性能', 'backend only', 'database only', 'slide', 'pptx'],
-  }),
-  route('hapo:backend-development', 'backend, API, database, or service implementation', 58, {
-    strong: ['backend', 'api', 'database', 'endpoint', 'server', 'service', 'バックエンド', 'データベース', 'エンドポイント', 'サーバー', 'サービス'],
-    medium: ['db', 'sql', 'postgres', 'mysql', 'migration', 'schema', 'worker', 'queue', 'マイグレーション', 'スキーマ', 'ワーカー', 'キュー'],
-    weak: ['controller', 'route handler', 'repository', 'model', 'auth service', 'コントローラ', 'ルートハンドラ', 'リポジトリ', 'モデル', '認証サービス'],
-    negative: ['frontend only', 'slide', 'pptx'],
-  }),
-  route('hapo:mobile-development', 'mobile app implementation', 56, {
-    strong: ['mobile', 'ios', 'android', 'react native', 'flutter', 'モバイル'],
-    medium: ['app store', 'play store', 'native app', 'mobile screen', 'アプリストア', 'playストア', 'ネイティブアプリ', 'モバイル画面'],
-    weak: ['gesture', 'push notification', 'offline sync', 'ジェスチャー', 'プッシュ通知', 'オフライン同期'],
-    negative: ['web only', 'desktop only'],
-  }),
-  route('hapo:devops', 'deployment, infrastructure, CI/CD, or operations work', 54, {
-    strong: ['deploy', 'deployment', 'docker', 'kubernetes', 'ci/cd', 'github actions', 'デプロイ', 'デプロイメント'],
-    medium: ['vercel', 'infra', 'infrastructure', 'devops', 'pipeline', 'environment variable', 'インフラ', 'パイプライン', '環境変数'],
-    weak: ['build server', 'container', 'helm', 'terraform', 'monitoring', 'ビルドサーバー', 'コンテナ', '監視'],
-    negative: ['slide', 'pptx', 'spec only'],
-  }),
-  route('hapo:generate-graph', 'diagram, graph, architecture map, or flow visualization', 52, {
-    strong: ['diagram', 'graph', 'mermaid', 'flowchart', 'architecture diagram', 'sơ đồ', 'so do', '図', '図解', 'ダイアグラム', 'グラフ', 'フローチャート', '構成図'],
-    medium: ['biểu đồ', 'bieu do', 'visualize', 'sequence diagram', 'data flow', '可視化', 'シーケンス図', 'データフロー'],
-    weak: ['mind map', 'dependency map', 'system map', 'マインドマップ', '依存関係図', 'システム図'],
-    negative: ['pptx', 'slide deck'],
-  }),
-  route('hapo:docs', 'project documentation, codebase docs, or source-backed as-is reconstruction', 51, {
-    strong: ['hapo:docs', 'project docs', 'system docs', 'codebase docs', 'codebase documentation', 'documentation from source code', 'docs from source code', 'generate docs from codebase', 'dựng tài liệu từ source code', 'dung tai lieu tu source code', 'tài liệu hệ thống', 'tai lieu he thong', 'tài liệu hiện trạng', 'tai lieu hien trang', 'tạo tài liệu project', 'tao tai lieu project', 'legacy documentation', 'legacy system documentation', 'as-is documentation', 'as-is requirements', 'requirement reconstruction', 'reconstruct requirements', 'reconstruct requirements from legacy system', 'ソースコードから仕様書', 'ソースコードから仕様書を作成', 'ソースコードからドキュメント', '既存システムのドキュメント', '現行仕様書', 'as-isドキュメント'],
-    medium: ['create docs', 'update docs', 'refresh docs', 'summarize codebase', 'system documentation', 'source to docs', 'reverse documentation', 'current-state docs', 'existing system docs', 'legacy docs', 'legacy system', 'dựng docs', 'dung docs', 'tạo docs', 'tao docs', 'cập nhật docs', 'cap nhat docs', 'tóm tắt codebase', 'tom tat codebase', 'dựng lại tài liệu', 'dung lai tai lieu', '仕様書を作成', 'ドキュメント作成', 'ドキュメント更新', 'コードベース要約', '既存システム', 'レガシーシステム'],
-    weak: ['docs', 'documentation', 'document project', 'document codebase', 'as-is', 'reconstruct', 'hiện trạng', 'hien trang', 'tài liệu', 'tai lieu', 'ドキュメント', '資料化', '仕様化', '現状'],
-    negative: ['official docs', 'latest docs', 'library docs', 'framework docs', 'api docs lookup', 'context7', 'best practice', 'research', 'pptx', 'slide'],
-  }),
-  route('hapo:brainstorm', 'early ideation or unclear solution direction', 50, {
-    strong: ['brainstorm', 'ý tưởng', 'y tuong', 'phương án', 'phuong an', 'gợi ý', 'goi y', 'ブレスト', 'アイデア', '案', '提案して', '相談'],
-    medium: ['idea', 'ideas', 'approach', 'options', 'tradeoff', 'chủ đề', 'chu de', 'cần làm gì', 'can lam gi', 'アプローチ', '選択肢', 'トレードオフ', 'テーマ', '何をすれば'],
-    weak: ['proposal', 'strategy', 'plan options', 'explore', 'direction', 'seminar topic', '提案', '戦略', '方向性', '検討'],
-    negative: ['commit', 'push', 'bug', 'error'],
-  }),
-  route('hapo:research', 'technical research or best-practice lookup', 48, {
-    strong: ['research', 'best practice', 'tìm hiểu', 'tim hieu', 'nghiên cứu', 'nghien cuu', '調査', 'リサーチ', 'ベストプラクティス'],
-    medium: ['documentation', 'docs', 'compare tools', 'latest docs', 'official docs', 'ドキュメント', '比較', '最新ドキュメント', '公式ドキュメント'],
-    weak: ['investigate options', 'market scan', 'reference', 'source material', '選択肢を調べる', '参考資料', '資料'],
-    negative: ['commit', 'push'],
-  }),
-  route('hapo:pptx', 'presentation or PowerPoint work', 46, {
-    strong: ['pptx', 'powerpoint', 'slide deck', 'presentation deck', 'スライド資料', 'プレゼン資料'],
-    medium: ['slide', 'slides', 'deck', 'presentation', 'seminar slides', 'スライド', 'プレゼン', 'セミナー資料'],
-    weak: ['speaker notes', 'appendix', 'mục lục slide', 'muc luc slide', '発表ノート', '付録', '目次'],
-    negative: ['source code', 'api', 'database'],
-  }),
-  route('hapo:agent-browser', 'browser automation with snapshot refs, web interaction, recording, or Browserbase cloud browser workflows', 45, {
-    strong: ['agent-browser', 'browser automation', 'web automation', 'browserbase', 'cloud browser', 'snapshot refs', 'browser snapshot', 'automate browser', 'tự động trình duyệt', 'tu dong trinh duyet', 'tự động thao tác trình duyệt', 'tu dong thao tac trinh duyet', 'ブラウザ自動化', 'クラウドブラウザ', 'ブラウザ操作', 'ブラウザスナップショット'],
-    medium: ['open url', 'navigate site', 'click in browser', 'fill form in browser', 'record browser', 'browser session', 'multi tab', 'browser test session', 'mở website', 'mo website', 'truy cập website', 'truy cap website', 'click trên web', 'click tren web', 'điền form web', 'dien form web', 'サイトを開く', 'ブラウザで開く', 'ブラウザで', 'フォーム入力', 'フォーム入力を自動化', '自動化して', 'クリック操作', '録画'],
-    weak: ['click button', 'fill form', 'open site', 'web session', 'browser ref', 'viewport', 'cookies', 'localstorage', 'ボタンをクリック', 'ビューポート', 'クッキー'],
-    negative: ['attached screenshot', 'ảnh đính kèm', 'anh dinh kem', '画像添付', 'source code', 'codebase', 'commit', 'push', 'pptx', 'pdf'],
-  }),
-  route('hapo:pdf', 'PDF reading, extraction, or generation', 44, {
-    strong: ['pdf'], medium: ['export pdf', 'read pdf', 'extract pdf', 'pdf出力', 'pdfを読む', 'pdf抽出'], weak: ['page render', 'ページレンダー'], negative: [],
-  }),
-  route('hapo:docx', 'Word document work', 42, {
-    strong: ['docx', 'word document', 'word file', 'word文書', 'wordファイル'], medium: ['word'], weak: ['tracked changes', 'document file', '変更履歴', '文書ファイル'], negative: [],
-  }),
-  route('hapo:xlsx', 'spreadsheet or Excel work', 42, {
-    strong: ['xlsx', 'excel', 'spreadsheet', 'スプレッドシート'], medium: ['csv', 'sheet', 'workbook', 'シート', 'ワークブック'], weak: ['formula', 'pivot table', '数式', 'ピボットテーブル'], negative: [],
-  }),
-  route('hapo:ai-multimodal', 'image, video, audio, or multimodal artifact analysis', 40, {
-    strong: ['screenshot', 'video', 'audio', 'multimodal', 'ảnh', 'anh', 'hình', 'hinh', 'スクリーンショット', '動画', '音声', '画像', '写真'],
-    medium: ['image', 'screen capture', 'recording', 'file attached', 'イメージ', '画面キャプチャ', '録画', '添付ファイル'],
-    weak: ['visual', 'describe image', 'ocr', 'ビジュアル', '画像説明'],
-    negative: ['pptx', 'pdf export'],
-  }),
-];
-
-function route(skill, reason, priority, signals) {
-  return { skill, reason, priority, signals };
-}
-
-function normalize(value) {
-  return String(value || '')
-    .normalize('NFKC')
-    .normalize('NFD')
-    .replace(/[\u0300-\u036f]/g, '')
-    .normalize('NFC')
-    .toLowerCase();
-}
-
-function scoreRoute(prompt, routeItem) {
-  const normalized = normalize(prompt);
-  const matched = [];
-  let score = 0;
-  for (const [bucket, weight] of Object.entries(WEIGHTS)) {
-    for (const term of routeItem.signals[bucket] || []) {
-      if (!normalized.includes(normalize(term))) continue;
-      score += weight;
-      matched.push({ bucket, term, weight });
-    }
-  }
-  return { ...routeItem, score, matched, confidence: confidence(score) };
-}
-
-function confidence(score) {
-  if (score >= 12) return 'high';
-  if (score >= 7) return 'medium';
-  if (score >= MIN_SCORE) return 'low';
-  return 'none';
-}
-
-function findRoute(prompt) {
-  const candidates = ROUTES
-    .map((routeItem, index) => ({ ...scoreRoute(prompt, routeItem), index }))
-    .filter((routeItem) => routeItem.score >= MIN_SCORE)
-    .sort((a, b) => b.score - a.score || b.priority - a.priority || a.index - b.index);
-  return candidates[0] || null;
-}
-
-module.exports = {
-  MIN_SCORE,
-  ROUTES,
-  findRoute,
-  normalize,
-  scoreRoute,
-};

package/src/claude/hooks/skill-router.cjs

@@ -1,68 +0,0 @@
-#!/usr/bin/env node
-/**
- * Copyright (c) 2026 Haposoft. MIT License.
- *
- * UserPromptSubmit Hook - skill-router.cjs
- *
- * Adds a deterministic CafeKit skill suggestion for natural-language prompts.
- * It never overrides explicit slash commands; it only injects a short routing hint.
- *
- * Exit: 0 always (fail-open)
- */
-
-const fs = require('fs');
-const path = require('path');
-
-function logCrash(error) {
-  try {
-    const dir = path.join(__dirname, '.logs');
-    if (!fs.existsSync(dir)) fs.mkdirSync(dir, { recursive: true });
-    fs.appendFileSync(
-      path.join(dir, 'hook-log.jsonl'),
-      JSON.stringify({
-        ts: new Date().toISOString(),
-        hook: 'skill-router',
-        status: 'crash',
-        error: error.message,
-      }) + '\n'
-    );
-  } catch (_) {}
-}
-
-try {
-  const { isHookEnabled } = require('./lib/config.cjs');
-  const { findRoute } = require('./lib/skill-router-routes.cjs');
-
-  function isExplicitCommand(prompt) {
-    const trimmed = prompt.trim();
-    return trimmed.startsWith('/') || /^hapo:[a-z-]+/i.test(trimmed);
-  }
-
-  const stdin = fs.readFileSync(0, 'utf8').trim();
-  if (!stdin) process.exit(0);
-
-  const payload = JSON.parse(stdin);
-  const cwd = payload.cwd || process.cwd();
-  const prompt = payload.prompt || '';
-  if (!isHookEnabled('skill-router', { cwd })) process.exit(0);
-  if (!prompt || isExplicitCommand(prompt)) process.exit(0);
-
-  const route = findRoute(prompt);
-  if (!route) process.exit(0);
-
-  const skillDir = route.skill.replace(/^hapo:/, '');
-  const lines = [
-    '## CafeKit Skill Router',
-    `- Suggested skill: \`${route.skill}\``,
-    `- Why: ${route.reason}.`,
-    `- Confidence: ${route.confidence} (score ${route.score}).`,
-    `- Action: before acting, read \`.claude/skills/${skillDir}/SKILL.md\` and follow that workflow.`,
-    '- If the user explicitly names another workflow or asks for direct answering only, follow the user request.',
-  ];
-
-  console.log(lines.join('\n'));
-  process.exit(0);
-} catch (error) {
-  try { logCrash(error); } catch (_) {}
-  process.exit(0);
-}