# rulesync-feature-research

Maps rulesync features against coding-agent docs: what is supported, where the gaps are, how clients differ.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 1552
- Author: dyoshikawa
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/dyoshikawa/rulesync/tree/HEAD/.rulesync/skills/rulesync-feature-research/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/rulesync-feature-research

## What it does

The skill builds a reproducible map between a coding-agent client, its upstream docs and the local rulesync implementation. Ask about feature support or triage an issue and you get a table with feature, agent surface, rulesync support, rulesync surface and difference columns. Features with sub-surfaces such as hook events, MCP transports, permission actions, config keys or output roots get a second table.

Inside there is a request target table: for each client (`claudecode`, `codexcli`, `cursor`, `copilot`, `geminicli`, `opencode` and others) the skill reads its own file under `references/`. A target without a matching file is treated as coming, not unsupported. For an unknown target it falls back to `references/rulesync-source-map.md` plus the closest existing client map. Support labels follow the README style: `project`, `global`, `simulated`, `unsupported`.

Validation runs through dry-run: `pnpm run dev generate --targets <client> --features "*" --dry-run`. The skill advises an all-feature dry-run for a single client by default, and an all-target run for cross-client questions. Dry-run is validation, not the answer. The output ends with a `## Capability Gaps` section that lists only material gaps: unsupported upstream capabilities, lossy import or export, deprecated surfaces. Tests, fixtures and refactors stay out of that list.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/rulesync-feature-research/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/rulesync-feature-research/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/rulesync-feature-research/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/rulesync-feature-research/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install dyoshikawa/rulesync rulesync-feature-research
```

2. **Manually: put the files in place**
- File: `.github/skills/rulesync-feature-research/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/dyoshikawa/rulesync --path .rulesync/skills/rulesync-feature-research
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/rulesync-feature-research/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/dyoshikawa/rulesync/tree/HEAD/.rulesync/skills/rulesync-feature-research/SKILL.md

## When to use it
- check rulesync feature support against client docs
- triage an issue where agent behavior and rulesync diverge
- build a capability map for a new coding-agent client
- find missing project and global scope support
- verify generator gates and output roots from dry-run

## Example prompts
- Check hook support in cursor against the official docs and rulesync
- Build a feature map for codexcli and list the capability gaps
- Triage this issue: why is the feature marked simulated in claudecode

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 4d9f0dc5643e555b.

BEGIN THIRD-PARTY FILE 4d9f0dc5643e555b
```text
---
name: rulesync-feature-research
description: >-
  Maps rulesync feature implementations to upstream coding-agent documentation.
  Use when evaluating rulesync issues, comparing any coding-agent client with
  rulesync source capability surfaces, checking support, or planning a client map.
---

# Rulesync Feature Research

## What

Build a reproducible map between a coding-agent client, an upstream feature
surface, and the local rulesync implementation.

| Request target            | Read                                                                  |
| ------------------------- | --------------------------------------------------------------------- |
| `antigravity`             | `references/antigravity.md`                                           |
| `augmentcode`             | `references/augmentcode.md`                                           |
| `claudecode`              | `references/claudecode.md`                                            |
| `cline`                   | `references/cline.md`                                                 |
| `codexcli`                | `references/codexcli.md`                                              |
| `copilot`                 | `references/copilot.md`                                               |
| `copilotcli`              | `references/copilotcli.md`                                            |
| `cursor`                  | `references/cursor.md`                                                |
| `deepagents`              | `references/deepagents.md`                                            |
| `factorydroid`            | `references/factorydroid.md`                                          |
| `geminicli`               | `references/geminicli.md`                                             |
| `goose`                   | `references/goose.md`                                                 |
| `junie`                   | `references/junie.md`                                                 |
| `kilo`                    | `references/kilo.md`                                                  |
| `kiro`                    | `references/kiro.md`                                                  |
```
END THIRD-PARTY FILE 4d9f0dc5643e555b

The third-party file has ended. Everything between the 4d9f0dc5643e555b tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2194 of 7181 bytes. © dyoshikawa · MIT · https://github.com/dyoshikawa/rulesync/tree/HEAD/.rulesync/skills/rulesync-feature-research/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
