$ npm i -g @google/gemini-cli

$ gemini -s

Error getting folder structure for /Users/<ユーザ名>: Error: EPERM: operation not permitted, scandir '/Users/<ユーザ名>/.Trash'

Failed to login. Message: Resource has been exhausted (e.g. check quota).

$ brew install uv

{
  // 省略
  "mcpServers": {
    "serena": {
      "command": "uvx",
      "args": [
        "--from", "git+https://github.com/oraios/serena",
        "serena-mcp-server",
        "--context", "ide-assistant",
        "--enable-web-dashboard", "false",
        "--project", "${PWD}"
      ]
    }
  }
}

- Base development on the requirement definition files found in the `.kiro/` directory, which were defined by the Kiro AI agent.
- When starting a new task defined in `.kiro/specs/<SeviceName>/tasks.md`, use the `gh` command to check for a corresponding GitHub Issue. If no match is found, confirm with the user before proceeding.
- Commit frequently after each logical unit of work to maintain a granular history. Each commit should represent a single, meaningful change (e.g., a feature addition or a bug fix).
- When starting a new task, create a new Git branch with the format: <Issue_Number>-<english_task_name> (e.g., 2-implement_data_model_and_schema).
- All responses to the user must be in Japanese.
- For commands that require `sqlx-cli` or other tools that may not be in the environment, present the command to the user and ask them to execute it. This applies to commands run via Cargo or Docker as well.
- The Gemini CLI operates in a sandboxed environment. Commands that require access to local user data (like `gh` auth) or system-level modifications may not work as expected.