@takuma-hirai/hirai-method 0.1.0

package/.claude/skills/file-organizer/SKILL.md

@@ -0,0 +1,433 @@
+---
+name: file-organizer
+description: Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
+---
+
+# File Organizer
+
+This skill acts as your personal organization assistant, helping you maintain a clean, logical file structure across your computer without the mental overhead of constant manual organization.
+
+## When to Use This Skill
+
+- Your Downloads folder is a chaotic mess
+- You can't find files because they're scattered everywhere
+- You have duplicate files taking up space
+- Your folder structure doesn't make sense anymore
+- You want to establish better organization habits
+- You're starting a new project and need a good structure
+- You're cleaning up before archiving old projects
+
+## What This Skill Does
+
+1. **Analyzes Current Structure**: Reviews your folders and files to understand what you have
+2. **Finds Duplicates**: Identifies duplicate files across your system
+3. **Suggests Organization**: Proposes logical folder structures based on your content
+4. **Automates Cleanup**: Moves, renames, and organizes files with your approval
+5. **Maintains Context**: Makes smart decisions based on file types, dates, and content
+6. **Reduces Clutter**: Identifies old files you probably don't need anymore
+
+## How to Use
+
+### From Your Home Directory
+
+```
+cd ~
+```
+
+Then run Claude Code and ask for help:
+
+```
+Help me organize my Downloads folder
+```
+
+```
+Find duplicate files in my Documents folder
+```
+
+```
+Review my project directories and suggest improvements
+```
+
+### Specific Organization Tasks
+
+```
+Organize these downloads into proper folders based on what they are
+```
+
+```
+Find duplicate files and help me decide which to keep
+```
+
+```
+Clean up old files I haven't touched in 6+ months
+```
+
+```
+Create a better folder structure for my [work/projects/photos/etc]
+```
+
+## Instructions
+
+When a user requests file organization help:
+
+1. **Understand the Scope**
+   
+   Ask clarifying questions:
+   - Which directory needs organization? (Downloads, Documents, entire home folder?)
+   - What's the main problem? (Can't find things, duplicates, too messy, no structure?)
+   - Any files or folders to avoid? (Current projects, sensitive data?)
+   - How aggressively to organize? (Conservative vs. comprehensive cleanup)
+
+2. **Analyze Current State**
+   
+   Review the target directory:
+   ```bash
+   # Get overview of current structure
+   ls -la [target_directory]
+   
+   # Check file types and sizes
+   find [target_directory] -type f -exec file {} \; | head -20
+   
+   # Identify largest files
+   du -sh [target_directory]/* | sort -rh | head -20
+   
+   # Count file types
+   find [target_directory] -type f | sed 's/.*\.//' | sort | uniq -c | sort -rn
+   ```
+   
+   Summarize findings:
+   - Total files and folders
+   - File type breakdown
+   - Size distribution
+   - Date ranges
+   - Obvious organization issues
+
+3. **Identify Organization Patterns**
+   
+   Based on the files, determine logical groupings:
+   
+   **By Type**:
+   - Documents (PDFs, DOCX, TXT)
+   - Images (JPG, PNG, SVG)
+   - Videos (MP4, MOV)
+   - Archives (ZIP, TAR, DMG)
+   - Code/Projects (directories with code)
+   - Spreadsheets (XLSX, CSV)
+   - Presentations (PPTX, KEY)
+   
+   **By Purpose**:
+   - Work vs. Personal
+   - Active vs. Archive
+   - Project-specific
+   - Reference materials
+   - Temporary/scratch files
+   
+   **By Date**:
+   - Current year/month
+   - Previous years
+   - Very old (archive candidates)
+
+4. **Find Duplicates**
+   
+   When requested, search for duplicates:
+   ```bash
+   # Find exact duplicates by hash
+   find [directory] -type f -exec md5 {} \; | sort | uniq -d
+   
+   # Find files with same name
+   find [directory] -type f -printf '%f\n' | sort | uniq -d
+   
+   # Find similar-sized files
+   find [directory] -type f -printf '%s %p\n' | sort -n
+   ```
+   
+   For each set of duplicates:
+   - Show all file paths
+   - Display sizes and modification dates
+   - Recommend which to keep (usually newest or best-named)
+   - **Important**: Always ask for confirmation before deleting
+
+5. **Propose Organization Plan**
+   
+   Present a clear plan before making changes:
+   
+   ```markdown
+   # Organization Plan for [Directory]
+   
+   ## Current State
+   - X files across Y folders
+   - [Size] total
+   - File types: [breakdown]
+   - Issues: [list problems]
+   
+   ## Proposed Structure
+   
+   ```
+   [Directory]/
+   ├── Work/
+   │   ├── Projects/
+   │   ├── Documents/
+   │   └── Archive/
+   ├── Personal/
+   │   ├── Photos/
+   │   ├── Documents/
+   │   └── Media/
+   └── Downloads/
+       ├── To-Sort/
+       └── Archive/
+   ```
+   
+   ## Changes I'll Make
+   
+   1. **Create new folders**: [list]
+   2. **Move files**:
+      - X PDFs → Work/Documents/
+      - Y images → Personal/Photos/
+      - Z old files → Archive/
+   3. **Rename files**: [any renaming patterns]
+   4. **Delete**: [duplicates or trash files]
+   
+   ## Files Needing Your Decision
+   
+   - [List any files you're unsure about]
+   
+   Ready to proceed? (yes/no/modify)
+   ```
+
+6. **Execute Organization**
+   
+   After approval, organize systematically:
+   
+   ```bash
+   # Create folder structure
+   mkdir -p "path/to/new/folders"
+   
+   # Move files with clear logging
+   mv "old/path/file.pdf" "new/path/file.pdf"
+   
+   # Rename files with consistent patterns
+   # Example: "YYYY-MM-DD - Description.ext"
+   ```
+   
+   **Important Rules**:
+   - Always confirm before deleting anything
+   - Log all moves for potential undo
+   - Preserve original modification dates
+   - Handle filename conflicts gracefully
+   - Stop and ask if you encounter unexpected situations
+
+7. **Provide Summary and Maintenance Tips**
+   
+   After organizing:
+   
+   ```markdown
+   # Organization Complete! ✨
+   
+   ## What Changed
+   
+   - Created [X] new folders
+   - Organized [Y] files
+   - Freed [Z] GB by removing duplicates
+   - Archived [W] old files
+   
+   ## New Structure
+   
+   [Show the new folder tree]
+   
+   ## Maintenance Tips
+   
+   To keep this organized:
+   
+   1. **Weekly**: Sort new downloads
+   2. **Monthly**: Review and archive completed projects
+   3. **Quarterly**: Check for new duplicates
+   4. **Yearly**: Archive old files
+   
+   ## Quick Commands for You
+   
+   ```bash
+   # Find files modified this week
+   find . -type f -mtime -7
+   
+   # Sort downloads by type
+   [custom command for their setup]
+   
+   # Find duplicates
+   [custom command]
+   ```
+   
+   Want to organize another folder?
+   ```
+
+## Examples
+
+### Example 1: Organizing Downloads (From Justin Dielmann)
+
+**User**: "My Downloads folder is a mess with 500+ files. Help me organize it."
+
+**Process**:
+1. Analyzes Downloads folder
+2. Finds patterns: work docs, personal photos, installers, random PDFs
+3. Proposes structure:
+   - Downloads/
+     - Work/
+     - Personal/
+     - Installers/ (DMG, PKG files)
+     - Archive/
+     - ToSort/ (things needing decisions)
+4. Asks for confirmation
+5. Moves files intelligently based on content and names
+6. Results: 500 files → 5 organized folders
+
+### Example 2: Finding and Removing Duplicates
+
+**User**: "Find duplicate files in my Documents and help me decide which to keep."
+
+**Output**:
+```markdown
+# Found 23 Sets of Duplicates (156 MB total)
+
+## Duplicate Set 1: "proposal.pdf"
+- `/Documents/proposal.pdf` (2.3 MB, modified: 2024-03-15)
+- `/Documents/old/proposal.pdf` (2.3 MB, modified: 2024-03-15)
+- `/Desktop/proposal.pdf` (2.3 MB, modified: 2024-03-10)
+
+**Recommendation**: Keep `/Documents/proposal.pdf` (most recent in correct location)
+Delete the other 2 copies?
+
+[Continue for all duplicates...]
+```
+
+### Example 3: Restructuring Projects Folder
+
+**User**: "Review my ~/Projects directory and suggest improvements."
+
+**Output**:
+```markdown
+# Analysis of ~/Projects
+
+## Current Structure Issues
+- Mix of active and archived projects (3+ years old)
+- No consistent naming convention
+- Some projects at root, others in random subfolders
+- Duplicate folders (project-name, project-name-old, project-name-v2)
+
+## Proposed Structure
+
+```
+Projects/
+├── Active/
+│   ├── client-work/
+│   ├── side-projects/
+│   └── learning/
+├── Archive/
+│   ├── 2022/
+│   ├── 2023/
+│   └── 2024/
+└── Templates/
+```
+
+## Specific Changes
+1. Move 12 projects not touched since 2022 → Archive/
+2. Consolidate 4 duplicate project folders
+3. Rename projects to consistent format: "client-name-project-name"
+4. Create Archive for old work
+
+Want me to implement this?
+```
+
+### Example 4: Organizing Photos by Date
+
+**User**: "Organize my photo folders by year and month."
+
+**Output**: Creates structure like:
+```
+Photos/
+├── 2023/
+│   ├── 01-January/
+│   ├── 02-February/
+│   └── ...
+├── 2024/
+│   ├── 01-January/
+│   └── ...
+└── Unsorted/
+```
+
+Then moves photos based on EXIF data or file modification dates.
+
+## Common Organization Tasks
+
+### Downloads Cleanup
+```
+Organize my Downloads folder - move documents to Documents, 
+images to Pictures, keep installers separate, and archive files 
+older than 3 months.
+```
+
+### Project Organization
+```
+Review my Projects folder structure and help me separate active 
+projects from old ones I should archive.
+```
+
+### Duplicate Removal
+```
+Find all duplicate files in my Documents folder and help me 
+decide which ones to keep.
+```
+
+### Desktop Cleanup
+```
+My Desktop is covered in files. Help me organize everything into 
+my Documents folder properly.
+```
+
+### Photo Organization
+```
+Organize all photos in this folder by date (year/month) based 
+on when they were taken.
+```
+
+### Work/Personal Separation
+```
+Help me separate my work files from personal files across my 
+Documents folder.
+```
+
+## Pro Tips
+
+1. **Start Small**: Begin with one messy folder (like Downloads) to build trust
+2. **Regular Maintenance**: Run weekly cleanup on Downloads
+3. **Consistent Naming**: Use "YYYY-MM-DD - Description" format for important files
+4. **Archive Aggressively**: Move old projects to Archive instead of deleting
+5. **Keep Active Separate**: Maintain clear boundaries between active and archived work
+6. **Trust the Process**: Let Claude handle the cognitive load of where things go
+
+## Best Practices
+
+### Folder Naming
+- Use clear, descriptive names
+- Avoid spaces (use hyphens or underscores)
+- Be specific: "client-proposals" not "docs"
+- Use prefixes for ordering: "01-current", "02-archive"
+
+### File Naming
+- Include dates: "2024-10-17-meeting-notes.md"
+- Be descriptive: "q3-financial-report.xlsx"
+- Avoid version numbers in names (use version control instead)
+- Remove download artifacts: "document-final-v2 (1).pdf" → "document.pdf"
+
+### When to Archive
+- Projects not touched in 6+ months
+- Completed work that might be referenced later
+- Old versions after migration to new systems
+- Files you're hesitant to delete (archive first)
+
+## Related Use Cases
+
+- Setting up organization for a new computer
+- Preparing files for backup/archiving
+- Cleaning up before storage cleanup
+- Organizing shared team folders
+- Structuring new project directories
+

package/.claude/skills/gan-style-harness/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: gan-style-harness
+description: GAN-inspired three-agent harness (Planner / Generator / Evaluator) that iteratively converges to production-grade quality via numerical scoring rubric. Replicated from ECC.
+origin: ECC
+---
+
+# GAN-Style Harness — 自己改善 L2+
+
+GAN（Generative Adversarial Network）にインスパイアされた3エージェント構造。Planner が仕様を作り、Generator が実装し、Evaluator が live app をテストして数値スコアを返す。閾値到達まで反復。
+
+## When to Activate
+
+- 高品質なフロントエンド/フルスタック成果物が必要
+- 「単一エージェント実装」では届かない quality bar
+- 視覚品質・craft が要求される（デザイン、UI、ランディング）
+- 4-6 時間 / $125-200 のコストを許容できる案件
+
+## Three-Agent Loop
+
+```
+User 1行プロンプト
+       │
+       ▼
+   Planner (Opus)
+   仕様書 16機能・複数Sprint 化
+       │ 仕様書
+       ▼
+   Generator (Opus)  ←─────────────────┐
+   実装 + git管理                       │ feedback-N+1.md
+       │ live app deploy (port 3000)   │
+       ▼                                │
+   Evaluator (Opus + Playwright MCP)    │
+   実機テスト → 4基準スコア             │
+       └────────────────────────────────┘
+```
+
+## Scoring Rubric
+
+各 1-10、重み付き合計。
+
+| 基準 | 重み | 1-3 | 9-10 |
+|---|---:|---|---|
+| Design Quality | 0.30 | テンプレ的・ストック | プロデザイナー級 |
+| Originality | 0.20 | 既視感のある構成 | 独自ビジョン |
+| Craft | 0.30 | 雑（spacing/typography 不揃い） | 完璧（anim/responsive 含む） |
+| Functionality | 0.20 | 機能不全 | エッジケース対応 |
+
+## Convergence
+
+- Pass threshold: **7.0 / 10**（重み付き合計）
+- Max iterations: **15**（典型は 5-15 で十分）
+- Plateau detection: **3 反復連続** スコア改善なし → 人間レビューへ
+
+## State / File Layout
+
+```
+gan-session-<timestamp>/
+├── spec.md                    # Planner output
+├── feedback-001.md            # Evaluator output (1st)
+├── feedback-002.md
+├── ...
+├── feedback-NNN.md            # 最終
+├── live-app/                  # Generator が実装
+└── playwright-runs/           # Evaluator のスクリーンショット
+```
+
+Generator は **直前の feedback-NNN.md だけ読む**（コンテキスト爆発防止）。
+Evaluator は **live-app の最新版だけ実機評価**。
+
+## Resource Trade-offs
+
+| アプローチ | 時間 | コスト | 成果物 |
+|---|---:|---:|---|
+| 単一エージェント | 20分 | $9 | barely functional |
+| GAN harness | 4-6h | $125-200 | production-ready |
+
+## Slash Commands
+
+- `/gan-design <prompt>` — Planner phase（仕様生成）
+- `/gan-build <spec-file>` — Generator/Evaluator loop 起動
+
+## Sprint Contract
+
+Generator は実装前に Evaluator と「sprint contract」を交渉する:
+
+```markdown
+# Sprint Contract: <feature>
+- 実装範囲: <bullet list>
+- 完了条件: <eval が PASS と判定する観測可能な振る舞い>
+- 非ゴール: <今回やらないこと>
+- 推定時間: <hour>
+```
+
+これにより Evaluator が「想定外の角度」で減点する自体を抑制。
+
+## Failure Modes
+
+- スコア plateau → 人間レビュー、仕様書見直し、Tier 切り下げ
+- Evaluator が hallucinate（実機を見ずに採点） → Playwright MCP の screenshot を必須化
+- コスト爆発 → max-iterations / max-cost を必ず設定
+
+## Integration
+
+- **L1 eval-harness** をスコアリング rubric の単位テストとして併用
+- **L4 continuous-learning-v2** で Evaluator の指摘を instinct 化（次回以降の Planner に自動注入）
+- **L5 introspection-debugging** でスコア低下の根本原因を分析
+
+## References
+
+- Source: ECC `skills/gan-style-harness/`
+- 元アイデア: GANs (Goodfellow 2014) を agent harness に転写

package/.claude/skills/gateguard/.gateguard.yml

@@ -0,0 +1,47 @@
+# GateGuard 設定 - .gateguard.yml
+#
+# Edit/Write/Bash の事実検証ゲート対象を制御する。
+# このファイルが存在しなくても hook は動作する（既定値あり）。
+
+# Edit/Write の事前ブロックを有効化
+edit_gate: true
+write_gate: true
+
+# 破壊的 Bash の事前ブロックを有効化
+destructive_bash_gate: true
+
+# 破壊的とみなすコマンドの正規表現（| 区切り）
+destructive_bash_patterns: |
+  rm -rf
+  rm -fr
+  git reset --hard
+  git push --force
+  git push -f
+  git branch -D
+  drop table
+  DROP TABLE
+  truncate table
+  TRUNCATE TABLE
+  DELETE FROM .* WHERE
+  supabase db reset
+
+# Gate を恒久的に除外するパス（Glob 風）
+ignore_paths:
+  - .gitignore
+  - .dockerignore
+  - .env.example
+  - .gitmessage
+  - "**/CLAUDE.md"
+  - "**/README.md"
+  - "**/*.lock"
+  - "**/.claude/.agent-markers/**"
+  - "**/.claude/.gateguard-state/**"
+
+# State directory（cleared marker の保存先）
+state_dir: .claude/.gateguard-state
+
+# サブエージェント中は Gate を pass する
+pass_through_for_subagents: true
+
+# Bypass 用環境変数の名前
+bypass_env_var: ECC_GATEGUARD

package/.claude/skills/gateguard/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: gateguard
+description: Fact-forcing PreToolUse gate that blocks Edit/Write/destructive Bash on first encounter and demands concrete evidence (importers, public APIs, data schema, verbatim user instruction) before allowing retry. Replicated from ECC. Measured +2.25 quality points vs ungated.
+origin: ECC
+---
+
+# GateGuard — Fact-Forcing Gate
+
+ECC の事実検証層の中核。Edit / Write / 破壊的 Bash を**初回遭遇時にブロック**し、具体的な事実調査を要求してから許可する PreToolUse hook。
+
+> 哲学: **self-evaluation（"are you sure?"）では達成できない awareness を、調査自体が生む**。
+> A/B 実測で **+2.25 / 10 ポイント** の品質改善（ungated 6.75 → gated 9.0）。
+
+## When to Activate
+
+- Edit / Write / 破壊的 Bash を伴うすべての作業
+- 特に複数ファイルへの影響が想定される変更
+- DB マイグレーション・データ削除・force push 等の不可逆操作
+- 信頼度の低い AI セッションでの安全網
+
+## What Gets Gated
+
+| Gate | 発火タイミング | 要求する事実 |
+|---|---|---|
+| **Edit / MultiEdit** | セッション中 ファイル F の **初回 Edit** | ① F を import/require している全ファイル（Grep）<br>② 影響を受ける public function/class<br>③ データ構造（フィールド名・date 形式、値は redact）<br>④ user 指示の **逐語引用** |
+| **Write**（新規） | セッション中 ファイル F の **初回 Write** | ① どのファイル/行が呼ぶか<br>② Glob で重複用途のファイルが無いことの確認<br>③ データ構造<br>④ user 指示の逐語引用 |
+| **Destructive Bash** | `rm -rf` / `git reset --hard` / `git push --force` / `git branch -D` / `drop table` / `truncate` 等 | ① 影響ファイル/データ全列挙<br>② 1 行 rollback 手順<br>③ user 指示の逐語引用 |
+
+## 3 段階ゲート
+
+```
+1. ❌ DENY    — block で具体的な事実要求を提示
+2. 🔍 INVESTIGATE — agent が Grep/Read/Glob で事実収集
+3. ✅ ALLOW   — 同ファイル/同コマンドの retry は通る（state file で記録）
+```
+
+## State Tracking
+
+`.claude/.gateguard-state/<file-hash>.cleared` を作成して再発火を抑止する。
+セッション間で永続するため、リセットは `/gate-clear` で行う。
+
+ファイルパスを SHA-256 12文字 hash 化することで、長いパスでもファイル名衝突を回避。
+
+## Bypass Mechanism
+
+| 方法 | 用途 |
+|---|---|
+| `ECC_GATEGUARD=off` env var | セッション全体で無効化 |
+| `/gate-bypass <file>` | 特定ファイルのみ pre-clear（事実収集済みと申告） |
+| `/gate-clear` / `/gate-clear all` | 状態をリセット |
+| `.gateguard.yml` の `ignore_paths` | 設定ファイル等を恒久除外 |
+
+## Subagent Pass-through
+
+サブエージェント（Agent tool 経由）実行中は GateGuard は通過する。理由:
+- サブエージェントは目的特化で動く
+- メインエージェントが Agent 起動時点で「この調査を委譲」と意図している
+- 二重ゲートで動作不能になるのを防ぐ
+
+検出方法: `delegation-guard.sh` と同じ多段検出（CLAUDE_HARNESS_ROLE / agent_type フィールド / `.claude/.agent-markers/*.lock`）。
+
+## Effectiveness（A/B 実測）
+
+| タスク | Gated | Ungated | 差 |
+|---|---:|---:|---:|
+| Analytics module | 8.0 | 6.5 | +1.5 |
+| Webhook validator | 10.0 | 7.0 | +3.0 |
+| **平均** | **9.0** | **6.75** | **+2.25** |
+
+## Files
+
+- `hooks/gateguard.sh`（このスキル外、`.claude/hooks/` に配置）
+- `.gateguard.yml`（このディレクトリ） — gate 対象 / 除外パス設定
+
+## Slash Commands
+
+- `/gate-status` — 現在の cleared 状態と pending を一覧
+- `/gate-clear [file|all]` — state リセット
+- `/gate-bypass <file>` — 1 ファイル分だけ pre-clear
+
+## Integration
+
+| 層 | 関係 |
+|---|---|
+| **L1** Eval Harness | gate を抜けた変更を最終検証 |
+| **L4** Continuous Learning | gate が要求した「事実型」を instinct DB に蓄積 |
+| **L5** Introspection | gate 発火履歴を debug 入力として使う |
+
+## Anti-Patterns
+
+- ❌ `ECC_GATEGUARD=off` を常用する（gate の意義を失う）
+- ❌ user 指示の逐語引用を捏造する
+- ❌ 1 ファイルに複数の独立変更を詰め込む（gate が 1 度しか発火せず、後続変更が無検証になる）
+
+## Related
+
+- ECC 元実装: `affaan-m/everything-claude-code/skills/gateguard/`
+- skill: `.claude/skills/verification-loop/SKILL.md`（事後検証側のペア）
+- rule: `.claude/rules/self-improvement.md`（事実性レイヤーの位置づけ）