Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Maps rulesync feature implementations to upstream coding-agent documentation.
Install Rulesync Feature Research
$ npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dyoshikawa/rulesync rulesync-feature-research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.rulesync/skills/rulesync-feature-research .claude/skills/rulesync-feature-research && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "rulesync-feature-research" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/rulesync-feature-research into .claude/skills/rulesync-feature-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rulesync-feature-research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/rulesync-feature-researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dyoshikawa/rulesync rulesync-feature-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.rulesync/skills/rulesync-feature-research .agents/skills/rulesync-feature-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rulesync-feature-research" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/rulesync-feature-research into .agents/skills/rulesync-feature-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rulesync-feature-research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dyoshikawa/rulesync rulesync-feature-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.rulesync/skills/rulesync-feature-research .cursor/skills/rulesync-feature-research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rulesync-feature-research" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/rulesync-feature-research into .cursor/skills/rulesync-feature-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rulesync-feature-research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dyoshikawa/rulesync.git --path .rulesync/skills/rulesync-feature-research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dyoshikawa/rulesync rulesync-feature-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.rulesync/skills/rulesync-feature-research .gemini/skills/rulesync-feature-research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rulesync-feature-research" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/rulesync-feature-research into .gemini/skills/rulesync-feature-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rulesync-feature-research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dyoshikawa/rulesync rulesync-feature-researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .github/skills && cp -r skills-src/.rulesync/skills/rulesync-feature-research .github/skills/rulesync-feature-research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rulesync-feature-research" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/rulesync-feature-research into .github/skills/rulesync-feature-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rulesync-feature-research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dyoshikawa/rulesync rulesync-feature-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.rulesync/skills/rulesync-feature-research .opencode/skills/rulesync-feature-research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rulesync-feature-research" agent skill from https://github.com/dyoshikawa/rulesync/tree/main/.rulesync/skills/rulesync-feature-research into .opencode/skills/rulesync-feature-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rulesync-feature-research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
rulesync-feature-research- GitHub stars
- 1.5k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 544 words
- Files
- 29 (incl. references)
- Skills in repo
- 40
- Repo updated
- First seen
- Licence
- MIT
At a glance
Maps rulesync feature implementations to upstream coding-agent documentation.
- Works in 4 steps: Create references/.md from the closest… → Fill Official Docs with the client's… → Add Client Anchors only for behavior not… → …
- Evaluating rulesync issues
- SKILL.md covers What and Contract
- Calls pnpm
What it does
Rulesync Feature Research is an agent skill from dyoshikawa/rulesync. 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.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 29 other files, including reference files (for example `references/antigravity.md`, `references/augmentcode.md` and `references/claudecode.md`).
It sits in Development. The repository describes itself as: A Utility CLI for AI Coding Agents. The licence is MIT.
When your agent uses it
- Evaluating rulesync issues
- Comparing any coding-agent client with rulesync source capability surfaces
- Checking support
- Planning a client map
Example prompts
- “/rulesync-feature-research”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Create references/.md from the closest existing map.
- Fill Official Docs with the client's docs URLs and feature surfaces.
- Add Client Anchors only for behavior not obvious from rulesync-source-map.md.
- Add the client to the request target table.
What it can do on your machine
Read from SKILL.md and the folder at commit 85bcaf6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Rulesync Feature Research loads about 1.8k tokens when it runs, and up to ~43k if it reads all its reference files. Until then it costs about 65 tokens; SKILL.md has 544 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dyoshikawa/rulesync at commit 85bcaf6, republished under its MIT licence (© dyoshikawa). 544 words, ~1,794 tokens.
Download SKILL.mdSave it as
.claude/skills/rulesync-feature-research/SKILL.md (or your agent's skills folder). This skill also uses 28 other files; get the full folder from GitHub.- 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 |
opencode | references/opencode.md |
pi | references/pi.md |
qwencode | references/qwencode.md |
replit | references/replit.md |
roo | references/roo.md |
rovodev | references/rovodev.md |
takt | references/takt.md |
warp | references/warp.md |
windsurf | references/windsurf.md |
zed | references/zed.md |
| Any other rulesync target | references/rulesync-source-map.md + the closest existing client map |
A target without references/<client>.md is To be coming, not unsupported.
To add a client map:
- Create
references/<client>.mdfrom the closest existing map. - Fill
Official Docswith the client's docs URLs and feature surfaces. - Add
Client Anchorsonly for behavior not obvious fromrulesync-source-map.md. - Add the client to the request target table.
Contract
Input:
| Field | Source |
|---|---|
| Client | User prompt or issue text; validate with the rulesync target list |
| Question | Support check, diff, capability surface, issue triage, or new map work |
Reproducibility boundary: same question, official docs, local source tree, and dry-run command/config.
Collect:
- Canonical target and feature lists from
references/rulesync-source-map.md. - Rulesync support labels from README, source, processor gates, and dry-run.
- Official docs from the selected client map.
- Re-check sentinel rows through official docs/site, then web search if needed;
confirm candidate URLs with Curl or Fetch. Recognized sentinel phrases:
No dedicated upstream <feature> surface in map— upstream has no dedicated docs surface that this row could point at.No Rulesync-supported <feature> target in map— no Rulesync adapter is known to target this feature.Rulesync maps <surface>; verify upstream before expanding behavior— Rulesync ships an adapter, but the upstream docs surface is thin or missing; treat as low confidence until re-verified.
- Client anchors for surfaces not obvious from naming rules.
- Dry-run output for generator gates and output roots.
Scope:
- Inspect every rulesync feature for each requested client.
- Do not narrow the investigation by feature or surface.
- Do not explain scope normalization in the final answer.
Show full SKILL.md (208 more words)Show less
Dry-run commands:
pnpm run dev generate --targets <client> --features "*" --dry-run
pnpm run dev generate --targets <client> --features "*" --global --dry-run
pnpm run dev generate --targets "*" --features "*" --dry-runUse client all-feature dry-runs by default. Use the all-target dry-run for cross-client questions. Dry-run is validation, not the answer.
Output:
- Start with the result table.
| Feature | Agent surface | Rulesync support | Rulesync surface | Difference |
|---|
Use README-style support labels for Rulesync: project, global, simulated,
unsupported.
- Add a surface table when the feature has sub-surfaces such as hook events, MCP transports, permission actions, config keys, metadata fields, or output roots.
| Surface | Agent surface | Rulesync map | Difference |
|---|
- End with capability gaps.
Use this section title:
## Capability GapsList only material feature gaps: unsupported upstream capabilities, missing
project/global scope, missing event/config surfaces, lossy import/export, or
deprecated surfaces that should be replaced. Each bullet should name the
feature and user-visible missing capability. Write None only when every
observed difference is an intentional mapping or already covered behavior.
For gaps based on any of the sentinel phrases listed in Collect step 4, re-check during the current run before claiming absence or low confidence.
Do not list tests, fixtures, refactors, source locations, or implementation chores unless they are necessary to explain the capability gap. Do not write "implementation change is not needed"; it is ambiguous.
Skip separate sections for canonicalization, map status, dry-run logs, and source lists unless the user asks for them.
© dyoshikawa, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 28 other files (references) in .rulesync/skills/rulesync-feature-research of dyoshikawa/rulesync.
- SKILL.md
- references/antigravity.md
- references/augmentcode.md
- references/claudecode.md
- references/cline.md
- references/codexcli.md
- references/copilot.md
- references/copilotcli.md
- references/cursor.md
- references/deepagents.md
- references/devin.md
- references/factorydroid.md
- references/geminicli.md
- references/goose.md
- references/junie.md
- references/kilo.md
- references/kiro.md
- references/new-target-watchlist.md
- references/opencode.md
- references/pi.md
- … and 9 more
Open the folder on GitHubat commit 85bcaf6
Compare with similar skills
Rulesync Feature Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Rulesync Feature Research this skilldyoshikawa/rulesync | 1.5k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 59 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from dyoshikawa/rulesync
All 40 skills in this repoBabysit Dependabot PR
dyoshikawa/rulesync
Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed)…
Commit Push PR
dyoshikawa/rulesync
Commit current changes, push to remote, and create or update a pull request.
Git Worktree Runner
dyoshikawa/rulesync
Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.
Goal PR
dyoshikawa/rulesync
Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge.
Goal Release
dyoshikawa/rulesync
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the…
PRs Awaiting Author
dyoshikawa/rulesync
List open pull requests where the ball is in the author's court: CI is failing, review comments are unaddressed, or a maintainer question is awaiting the author's reply.
Related
Categories
Questions about Rulesync Feature Research
What does Rulesync Feature Research do?
Maps rulesync feature implementations to upstream coding-agent documentation. Rulesync Feature Research is an agent skill from dyoshikawa/rulesync. Maps rulesync feature implementations to upstream coding-agent documentation.
When should I use Rulesync Feature Research?
Rulesync Feature Research fits situations like: evaluating rulesync issues; comparing any coding-agent client with rulesync source capability surfaces; checking support; planning a client map.
How do I install Rulesync Feature Research in Claude Code?
Run `npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a claude-code`. Or copy the skill folder (.rulesync/skills/rulesync-feature-research in dyoshikawa/rulesync) into .claude/skills/rulesync-feature-research in your project. Claude Code loads it when a task matches its description.
How do I install Rulesync Feature Research in Codex?
Run `npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a codex`. Or copy the skill folder (.rulesync/skills/rulesync-feature-research in dyoshikawa/rulesync) into .agents/skills/rulesync-feature-research in your project. Codex loads it when a task matches its description.
Can I use Rulesync Feature Research in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dyoshikawa/rulesync --skill rulesync-feature-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rulesync-feature-research, .gemini/skills/rulesync-feature-research, .github/skills/rulesync-feature-research and .opencode/skills/rulesync-feature-research in your project.
What does Rulesync Feature Research need to run?
Going by SKILL.md and its folder, Rulesync Feature Research needs the command-line tools its instructions call (pnpm).
Does Rulesync Feature Research access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Rulesync Feature Research safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Rulesync Feature Research use?
Rulesync Feature Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Rulesync Feature Research use?
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 41k tokens, read only when the agent opens those files.
What are the alternatives to Rulesync Feature Research?
Skills that share tags, products or a category with Rulesync Feature Research: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rulesync Feature Research?
dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,507 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 8, 2026.
Source: dyoshikawa/rulesync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.