Kotlin Tuple Utility Generation Skill

Generates type-safe Tuple utilities for Kotlin/KMP projects by copying pre-built example files and adjusting package names.

Usage

Before generating code, confirm the following with the user in a single message.

Confirmation Items

1. Target module (for multi-module projects, which module to generate into)
   • Analyze the project structure and suggest a candidate module
   • Ask the user to confirm or specify a different module
2. Package name and output directory
   • Infer from the module's existing package structure and suggest a candidate
   • Ask the user to confirm or specify a different package name
3. Maximum Tuple size (default: 20)
   • Ask: "Generate Tuple0–TupleN (default: 20)? Enter a different number to change."
4. File types to generate (default: all)
   • Let the user select (multiple choice):
     • Tuple.kt + TupleFactory.kt — Tuple data classes and tupleOf factories (required, always generated)
     • TupleToList.kt — toList() extension functions
     • AbstractTupleSerializer.kt + TupleSerializer.kt — KSerializer for kotlinx.serialization
     • AwaitAll.kt — Type-safe awaitAll
     • AllNotNullOrNull.kt — allNotNullOrNull utility

Skipping Confirmation

When the user's intent is clear, skip the confirmation and proceed directly with default settings:

• "デフォルトで" / "デフォルト設定で" / "with default settings"
• "全部入りで" / "全部生成して" / "generate all"
• Arguments explicitly specify target module, package, and options

ARGUMENTS の処理

スキルが ARGUMENTS パラメータを受け取った場合：

• ARGUMENTS の値は デフォルト値 として扱う（対象モジュール、パッケージ名、オプション等の推定に使用）
• ユーザメッセージで明示的に指定された値がある場合は、ユーザメッセージを優先 する
• ARGUMENTS とユーザメッセージが矛盾する場合は、ユーザメッセージの指定に従う

Output Directory Detection

Detect the source set directory based on the module type:

Module type	Source directory pattern
Kotlin Multiplatform (commonMain)	<module>/src/commonMain/kotlin/
JVM / Android (main)	<module>/src/main/kotlin/ or <module>/src/main/java/
Single-module project	src/main/kotlin/ or src/main/java/

Detection steps:

1. Check build.gradle.kts / build.gradle for KMP plugin (kotlin("multiplatform")) or JVM/Android plugin
2. Look for existing src/commonMain/kotlin, src/main/kotlin, or src/main/java directories
3. Append the package path (e.g., com.example.tuple → com/example/tuple/)

Example Confirmation Message

I'll generate Tuple utilities. Let me confirm the following:

1. Target module: **shared** (detected)
   → Enter a different module name if needed

2. Package: `com.example.tuple` (detected)
   Output: `shared/src/commonMain/kotlin/com/example/tuple/`
   → Enter a different package name if needed

3. Max Tuple size: **20** (default)
   → Enter a number to change

4. Files to generate:
   - [x] Tuple.kt + TupleFactory.kt (required)
   - [x] TupleToList.kt (toList() conversion)
   - [x] AbstractTupleSerializer.kt + TupleSerializer.kt (kotlinx.serialization support)
   - [x] AwaitAll.kt (type-safe awaitAll)
   - [x] AllNotNullOrNull.kt (null-safety utility)
   → Uncheck any you don't need

OK to proceed?

Generation Method: Copy from Example

This skill ships pre-built example files under example/src/commonMain/kotlin/com/example/tuple/. Do NOT generate code from scratch. Instead, copy example files and adjust them.

Step-by-step

1. Determine the absolute path of the example directory relative to this skill's location:
   • Example files: <skill_dir>/example/src/commonMain/kotlin/com/example/tuple/
2. Check for existing Tuple definitions in the target module:
   • Search for data class Tuple in <module>/src/
   • Additionally, search for Tuple-related directories: find <module>/src -type d -name "tuple*" でパッケージディレクトリを列挙
   • If found, ask the user whether to: overwrite, use a different package, or cancel
   • 検出結果は Step 10 の完了メッセージで使用するため保持しておくこと
3. Create the target output directory (if not exists)
4. Copy selected files from the example directory to the target output directory using Bash cp
   • Always copy: Tuple.kt, TupleFactory.kt
   • Copy if selected: TupleToList.kt, AbstractTupleSerializer.kt + TupleSerializer.kt, AwaitAll.kt, AllNotNullOrNull.kt
   • 全ファイル選択時: cp <EXAMPLE_DIR>/*.kt <TARGET_DIR>/ でまとめてコピーしてよい
   • 一部選択時: 選択されたファイルのみ個別にコピーする（cp *.kt は未選択ファイルも含むため使わない）
5. Replace package name in all copied files using Bash sed:

   sed -i '' 's/package com\.example\.tuple/package <USER_PACKAGE>/g' <TARGET_DIR>/*.kt
   

   Also replace import statements if the package is used in imports:

   sed -i '' 's/import com\.example\.tuple\./import <USER_PACKAGE>./g' <TARGET_DIR>/*.kt
   

6. If max Tuple size < 20: Read each copied file and remove Tuple definitions beyond N.
   • Each file has clearly separated blocks per Tuple size — remove lines for Tuple(N+1) through Tuple20
7. If max Tuple size > 20: Read the reference .md files to understand the pattern, then extend the copied files.
   • Reference files: tuple-to-list.md, tuple-serializer.md, await-all.md, all-not-null-or-null.md
8. Verify and add dependencies in build.gradle.kts: 依存関係を確認し、不足している場合は追加する。追加した場合はユーザに通知すること。
   • If TupleSerializer.kt is included:
     • kotlinx-serialization plugin が未設定 → build.gradle.kts に追加（公式ドキュメントを参照して正しい設定方法で追加）
     • kotlinx-serialization-json dependency が未設定 → commonMain.dependencies（KMP）または dependencies（JVM/Android）に追加
   • If AwaitAll.kt is included:
     • kotlinx-coroutines-core dependency が未設定 → 同様に追加
9. Build verification: Run a compile check to ensure the generated files have no errors:
   • KMP: ./gradlew :<module>:compileKotlinJvm
   • Android: ./gradlew :<module>:compileDebugKotlin
   • If errors occur, fix them before completing
10. Completion message — 以下のテンプレートに従って出力する:

    ## 生成完了
    
    **パッケージ**: `<package>`
    **出力先**: `<output_dir>`
    
    ### 生成ファイル
    - Tuple.kt
    - TupleFactory.kt
    - ...
    
    ### 依存関係
    - [変更なし / 追加: kotlinx-serialization plugin, kotlinx-serialization-json, ...]
    
    ### 既存 Tuple パッケージ
    - [なし / `<package1>`, `<package2>`, ... — 不要であれば削除を検討してください]
    
    ### ビルド結果
    - [SUCCESS / FAILED — エラー内容]
    

    • Step 2 で検出した既存 Tuple パッケージ（テキスト検索・ディレクトリ検索の両方の結果）を 必ず 報告する

Why This Approach

• The example files contain ~2,600 lines of repetitive Kotlin code
• Copying and sed-replacing is far more efficient than generating from scratch
• Minimizes context consumption and eliminates generation errors