Porting: Optimize Kinderpowers ecosystem for Gemini CLI

[jw409]

Overview

Kinderpowers was originally designed for Claude/Claude Code. While many features (SKILL.md, MCP servers) are compatible with Gemini CLI, there are areas where optimization is needed for a first-class experience.

Resolution (2026-03-31)

PR: feat/issue-sweep-2026-03-31

Created: docs/gemini-compatibility.md

Comprehensive guide covering:

1. Tool Name Mapping Table — Claude Code names (Read, Bash, Grep, etc.) mapped to Gemini CLI equivalents (read_file, run_shell_command, etc.)
2. Agent Definition Adaptation — how frontmatter tool declarations translate, why prompts still work (intent-based)
3. Grep/Glob workarounds — Gemini lacks dedicated tools, use shell commands instead
4. Subagent spawning — Agent tool → gemini --prompt pattern
5. MCP server compatibility — kp-github and kp-sequential-thinking work identically (MCP is runtime-agnostic)
6. Skill compatibility matrix — high compat (analysis skills), needs adaptation (tool-referencing skills), Claude-only (plugin system skills)
7. Sequential thinking tuning — Gemini already has a pre-tuned profile in the MCP server (wider exploration, different thresholds)
8. Best practices for cross-runtime skills — describe intent not tools, absolute paths, verification commands

Updated: skills/dispatching-to-runtimes/SKILL.md

• Added tool name mapping quick reference in the Gemini section
• Cross-referenced the full compatibility guide

Remaining Work

• Add Gemini-specific examples to 3-4 high-use skills
• Test agent definitions with Gemini CLI and document failure modes
• Consider a tool-name translation layer in the plugin system (low priority — MCP handles this)