my-ai-tools

Welcome to my-ai-tools 👋

Portable, source-controlled configuration for AI coding assistants.

my-ai-tools installs one consistent set of agent guidelines, skills, commands, hooks, MCP servers, and tool settings across supported AI coding assistants. It can also export local configuration changes back into this repository.

📖 Documentation website · 🎬 Setup video

✨ Features

• Configures Claude Code, OpenCode, Amp, Codex, Cursor, Pi, Antigravity, and many other assistants.
• Shares reusable skills, agent guidance, commands, hooks, and MCP server definitions.
• Supports macOS, Linux, Windows 11 with PowerShell and Git Bash, and WSL.
• Provides side-effect-free dry runs and optional backups before installation.
• Exports installed configurations back to the repository for bidirectional sync.
• Validates JSON and other supported configuration files before installation.

📋 Requirements

macOS, Linux, and WSL

• Bash 3.0 or later
• Git
• curl for the one-line installer
• Bun or Node.js LTS for JavaScript-based tools

Windows 11

• Windows PowerShell 5.1 or PowerShell 7
• winget (App Installer) for automatic prerequisite setup

The installer handles Git for Windows (including Git Bash), jq, and Node.js LTS with npm. You do not need to install them separately or open Git Bash first. WSL users can use the Linux instructions.

🚀 Installation

The installer can replace existing configuration files. Run a dry run first and use --backup or -Backup when you want a restorable copy.

macOS, Linux, and WSL

Review the installer, then run it:

curl -fsSL https://ai-tools.itman.fyi/install.sh -o install.sh
less install.sh
bash install.sh --dry-run
bash install.sh --backup

For a direct one-line installation:

curl -fsSL https://ai-tools.itman.fyi/install.sh | bash

Windows 11

Open PowerShell and run the canonical installer:

Invoke-RestMethod https://ai-tools.itman.fyi/install.ps1 | Invoke-Expression

This downloads and executes a remote script. Review install.ps1 before trusting it. It installs missing prerequisites through winget, reuses existing tools, refreshes PATH for the current process, and starts the shared installer in Git Bash. Windows may request administrator approval for Git or Node.js installation. Package installation uses --source winget, not the Microsoft Store. Node and npm are discovered again after installation and passed to Git Bash in the same process; no separate prerequisite command or terminal restart is needed after a successful install. The wrapper skips Git Bash login profiles so an older shell PATH cannot hide these tools. Approve only the package installer's elevation prompt; the wrapper does not relaunch the full configuration installer as administrator. If approval is denied, setup stops and can be rerun safely. Native Windows uses Node/npm, not Bun, for package installation; Linux, macOS, and WSL keep Bun-first behavior.

The one-line command and -y / --yes use these default categories:

• Default tools: Amp, Pi, Codex, OpenCode, Claude Code, Grok, qmd, rtk, ctx, open-cursor, ai-switcher, open_code_review, and Plannotator.
• Shared skills: bundled local skills, installed for the selected agents.
• Applicable MCP/plugin configuration: bundled configuration for the selected agents. The three memory MCP choices (qmd, codebase-memory-mcp, agentmemory) remain available; user-memory stays opt-in.
• Optional standalone catalog: remaining CLIs, formatters, and tools need selection. Interactive runs prompt for them; automation can use --with-tools.

qmd, ctx, and Plannotator are also logged as integration dependencies of the core agent templates. ctx installation in -y mode does not import history, start its daemon, install upstream skills, or change persistent Windows PATH. Other MCP commands keep their existing external prerequisites. No unrelated agent's plugin or skill directory is configured in yes mode.

From a reviewed checkout, select extra tools without enabling integrations:

./cli.sh --yes --without-integrations --with-tools=fx,cursor --dry-run
./cli.sh --yes --without-integrations --with-tools=fx,cursor
# Default configuration, plugins, shared skills and MCPs (can replace existing config):
./cli.sh --yes --backup

Windows equivalents are -WithoutIntegrations -WithTools 'fx,cursor' and -Yes -Backup on a saved install.ps1. Tool names are comma-separated; ./cli.sh --help lists the catalog. --without-integrations (-WithoutIntegrations) installs standalone CLIs only and leaves existing configuration unchanged. --with-integrations remains accepted but is now the default. Selecting an extra tool does not select another agent's configuration. Noninteractive/CI runs use the same default categories as --yes.

The installer can replace existing configuration. To inspect the script, preview changes, and request a backup, use the saved-script path instead:

Invoke-RestMethod https://ai-tools.itman.fyi/install.ps1 -OutFile install.ps1
Get-Content .\install.ps1
powershell -NoProfile -ExecutionPolicy Bypass -File .\install.ps1 -DryRun
powershell -NoProfile -ExecutionPolicy Bypass -File .\install.ps1 -Backup

Execution-policy bypass applies only to that process. -DryRun does not install prerequisites; install them first if the preview reports they are missing. The one-line command is non-interactive and automatically uses --yes.

If setup fails, resolve the reported error and rerun the same command. If a newly installed prerequisite still cannot be found, close all terminal windows and reopen PowerShell. If winget is missing, install or update App Installer, or install Git for Windows, jq, and Node.js LTS with npm manually. In Git setup, select Git from the command line and also from 3rd-party software. Do not bypass package lifecycle errors with --ignore-scripts: native binaries can remain uninstalled.

Optional qmd requires Node.js >=22 on native Windows. Its installer prioritizes the real node.exe directory and npm's global prefix in the same Git Bash session, ahead of stale Bun launchers or extensionless Node copies in ~/.local/bin. Those old files are not deleted. In npm 11.19.1, unreviewed allowScripts entries warn but still run unless strict policy is enabled. The installer does not change npm script policy. Review actual build errors and approve only required packages if your policy requires it; do not enable all scripts globally. On Windows ARM64, qmd keyword indexing/search works, but sqlite-vec currently warns that vector search is unsupported.

Optional Plannotator installs only the official v0.28.23 Windows release binary (x64 or ARM64), with a pinned SHA-256 hash. It uses %LOCALAPPDATA%\plannotator and updates only the current Git Bash PATH. No remote PowerShell script, policy bypass, persistent PATH change, sidecar, skill, or agent-settings edit is used. The direct method avoids an upstream PowerShell $Minimal/$minimal variable collision. Failure output gives the release URL, expected hash, and destination for manual recovery. In a separate terminal, add that directory and npm's global prefix to your user PATH, or use full executable paths. Unix/WSL installation paths are unchanged.

If the wrapper says all prerequisites are met but Bash then reports missing Node/npm, check that the downloaded install.ps1 includes Find-Node and the OpenJS.NodeJS.LTS installation step. A stale web deployment can serve an older wrapper while cloning the latest Bash installer. Maintainers must check the Dokku Deploy workflow for ai-tools.itman.fyi; a successful Deploy GitHub Pages run does not update that domain. Until the domain is updated, use a reviewed repository checkout and run:

powershell -NoProfile -ExecutionPolicy Bypass -File .\install.ps1 -Yes

Repository checkout

git clone https://github.com/jellydn/my-ai-tools.git
cd my-ai-tools
./cli.sh --dry-run
./cli.sh --backup

On Windows PowerShell, use the native wrapper from the checkout:

git clone https://github.com/jellydn/my-ai-tools.git
Set-Location my-ai-tools
.\install.ps1 -DryRun
.\install.ps1 -Backup

⚙️ Installer options

Bash option	PowerShell option	Purpose
--dry-run	-DryRun	Show planned changes without applying them.
--backup	-Backup	Back up existing files before installation.
--no-backup	-NoBackup	Skip the interactive backup prompt.
--yes / -y	-Yes	Install the default tool set, shared skills, applicable MCP/plugin config and declared dependencies.
--with-tools=fx,cursor	-WithTools 'fx,cursor'	Add optional standalone catalog CLIs.
--with-integrations	-WithIntegrations	Install bundled config, plugins, skills and MCP dependencies (default).
--without-integrations	-WithoutIntegrations	Install standalone CLIs only; leave configuration unchanged.
--rollback	-Rollback	Restore the most recent backup.
--verbose / -v	-Verbose	Show detailed installer output.
--migrate-gemini	—	Migrate Gemini CLI configuration to Antigravity CLI.

Non-interactive Bash and PowerShell pipelines automatically add --yes. This mode uses the same default categories above; it is not a configuration-free install. Review cli.sh before using it in automation.

🤖 Supported tools

The repository currently contains configuration or integration support for:

Category	Tools
Primary assistants	Claude Code, OpenCode, Amp, Codex, Cursor, Pi, Oh My Pi, Antigravity, Kilo, Kimi Code, Muse Code
Additional CLIs	CommandCode, GitHub Copilot CLI, Gemini CLI, Grok CLI, MiMo-Code, Qoder CLI, DeepSeek Harness, Kiro CLI, Devin CLI, Factory Droid, Cline, Reasonix
Workflow and desktop tools	Conductor, Delta, Codiff, Hunk, ctx, herdr, Orca, AI Launcher, CCS, fx, Open Code Review

Some installers are platform-specific, and optional tools are skipped when they are not detected. Gemini CLI is deprecated for Google One and unpaid tiers; use the --migrate-gemini option to move its configuration to Antigravity CLI.

See configs/ for the source configuration of each tool and skills/ for shared skills.

For an opt-in VPS terminal accessed from a Mac over Tailscale, see the Pi Durable setup. It uses a pinned experimental TUI, private persistent storage, and a user service; the general installer does not enable it.

🔌 Shared configuration

The installer manages these common resources where the target tool supports them:

• Agent guidance and software-development practices
• Reusable skills and commands
• Lifecycle and safety hooks
• Tool-specific settings, themes, and provider configuration
• MCP servers from configs/mcp-registry.json

The MCP registry includes integrations such as Context7, sequential thinking, qmd, codebase memory, agent memory, fff, React Grab, logpilot, sem, and ctx. Installation depends on each server's runtime and credentials.