Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion ai.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,9 @@
{
"$schema": "https://x.a1st.dev/schemas/v1/ai.json",
"extends": "github:yokuze/aix-config",
"skills": {},
"skills": {
"aix-cli": "./skills/aix-cli"
},
"mcp": {},
"rules": {},
"prompts": {
Expand Down
105 changes: 105 additions & 0 deletions skills/aix-cli/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,105 @@
---
name: aix-cli
description: Use the aix CLI to manage AI agent configurations, skills, MCP servers, and rules across multiple editors.
---

# aix CLI Skill

The `aix` CLI is a unified tool for managing AI agent configurations. It allows you to define your skills, prompts, rules, and MCP server configurations in a single `ai.json` file and install them into various AI-powered editors like Claude Code, Cursor, Windsurf, and more.

## Core Commands

### Initialization

Initialize a new `ai.json` configuration file in your project:

```bash
aix init
```

Options:

- `--force`, `-f`: Overwrite existing `ai.json`.
- `--from <editor>`: Import existing configuration from a specific editor (e.g., `cursor`, `windsurf`, `claude-code`).

### Discovery

Search for available MCP servers and skills:

```bash
aix search [query]
```

### Adding Components

Add new components to your `ai.json` configuration.

#### Adding Skills

```bash
aix add skill <source>
```

Source can be a local path, a GitHub/GitLab URL, or an npm package name.

#### Adding MCP Servers

```bash
aix add mcp <name>
```

Adds an MCP server from the official registry. You can also specify `--command` for manual configuration.

#### Adding Rules and Prompts

```bash
aix add rule <source>
aix add prompt <source>
```

### Installation

Install your configured components to one or more AI editors:

```bash
aix install
```

Options:

- `--target <editor>`: Install to a specific editor (can be used multiple times).
- `--scope <scope>`: Install only specific types of components (`mcp`, `skills`, `rules`, `prompts`).
- `--save`: Save remote configurations locally.

### Management

List your configured components:

```bash
aix list skills
aix list mcp
aix list rules
aix list prompts
aix list editors
```

Remove a component:

```bash
aix remove <type> <name>
```

### Validation

Validate your `ai.json` configuration or a specific skill/rule file:

```bash
aix validate [path]
```

## Best Practices

1. **One Source of Truth**: Always modify your `ai.json` or use `aix add` instead of manually configuring each editor.
2. **Version Control**: Check your `ai.json` into your project's version control (e.g., Git).
3. **Local Overrides**: Use `ai.local.json` for machine-specific configurations (like API keys or local paths) that shouldn't be committed. Many `aix add` commands support a `--local` flag.
4. **Regular Sync**: Run `aix install` after adding or updating configurations to ensure all editors are in sync.
Loading