npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

rule-link

v0.1.1-beta.1

Published

A CLI tool to manage AI programming tool rule files through symlinks

Downloads

22

Readme

rule-link

npm version License: MIT

rule-link is a command-line tool designed to help developers unify the management of configuration rule files for multiple AI programming tools. By creating symbolic links to a single, centralized rule file (e.g., AGENTS.md), you can maintain consistency across different AI assistants (like Cursor, Windsurf, Claude Code, etc.) without duplicating and manually synchronizing multiple files.

New in this version: Default source file changed to AGENTS.md for better compatibility with AI tools that natively support this standard.

The Problem It Solves

Developers on a project often use different AI programming assistants. Each tool often requires its own project-specific rule file (e.g., CLAUDE.md, GEMINI.md, AGENTS.md) to understand context and coding conventions. Managing these separate files leads to duplication and inconsistency, as developers must manually synchronize changes.

rule-link solves this by creating symbolic links from a single source of truth (e.g., AGENTS.md) to the configuration files of various AI tools. This ensures all assistants work from the same set of rules.

Furthermore, with the growing adoption of AGENTS.md as a standard, tools like Cursor and Gemini CLI can read it natively. This reduces the number of symbolic links needed, simplifying configuration even more. rule-link bridges the gap by managing symlinks for tools that don't yet support the standard while leveraging native support where available.

Installation

npm install -g rule-link

Usage

The primary command is rule-link create. You can run it in interactive mode or with command-line flags.

Interactive Mode

For a guided experience, simply run the command without any options. The tool will prompt you to select the desired AI tools and confirm the paths.

rule-link create
# or use npx without global installing
npx rule-link create

Command-Line Mode

For scripting or quick use, you can pass arguments directly.

1. Specify AI tools directly:

Use the --list flag to provide a space-separated list of tool names.

# Create links for Augment and Windsurf (tools that need symlinks)
rule-link create --list Augment Windsurf

2. Specify a different source file:

By default, rule-link uses AGENTS.md as the source of truth (changed from rule.md for better AI tool compatibility). You can specify a different file with the --file flag.

# Use my-rules.md as the source file
rule-link create --file my-rules.md --list Augment

3. Link custom file paths:

If you need to link to a file not officially supported, use the --custom flag with a comma-separated list of paths.

# Link two custom files
rule-link create --custom ".custom/coding-standards.md,docs/project-rules.md"

Built-in AI Tools

rule-link comes with built-in support for the following popular AI tools:

| Tool Name | File Path | Native AGENTS.md Support | | ----------- | ------------------------------------- | ------------------------ | | Cursor | AGENTS.md ⭐ | ✅ Yes (recommended) | | Augment | .augment/rules/coding-standards.md | ❌ No (symlink needed) | | Windsurf | .windsurf/rules/coding-standards.md | ❌ No (symlink needed) | | Claude Code | CLAUDE.md | ❌ No (symlink needed) | | Gemini CLI | AGENTS.md ⭐ | ✅ Yes (recommended) | | Cline | .clinerules/coding-standards.md | ❌ No (symlink needed) | | Roo Code | AGENTS.md ⭐ | ✅ Yes (recommended) |

Custom AI Tools

While rule-link provides built-in support for popular tools, you can create symbolic links for any AI tool using the --custom <paths> flag. This allows you to:

  • Link to tools not officially supported
  • Use custom file paths for your specific workflow
  • Support enterprise or internal AI tools
  • Maintain consistency across any number of AI assistants

Simply provide a comma-separated list of custom file paths:

rule-link create --custom ".vscode/rules.md,enterprise.md,.ai-tools/custom-rules.md"

Recommended Workflow

Initial Project Setup

  1. Run the command:
    rule-link create
  2. Follow the prompts to select your preferred AI tools and create the AGENTS.md source file and all the necessary symbolic links.
  3. Commit the source file: Commit the AGENTS.md and all the necessary symbolic links to your Git repository.

Onboarding a New Developer

When new developers clone the project, the symbolic links may not exist, or they may be using a different operating system (Windows, macOS, or Linux), where symbolic links are implemented differently. They need to run the rule-link create command once to generate these symbolic links locally.

# After git clone
git clone project-url
cd project

# Generate local rule file links
rule-link create

Command Reference

rule-link create

Creates symbolic links for AI tool rule files.

Options:

  • -f, --file <path>: Specify the path to the source rule file. (Default: AGENTS.md)
  • -l, --list <tools...>: Provide a space-separated list of AI tools to link, skipping the interactive menu.
  • -c, --custom <paths>: Provide a comma-separated list of custom file paths to link.
  • -F, --force: Force overwrite existing files without prompting (non-interactive mode only).
  • -v, --version: Display the version number.
  • -h, --help: Display help information.

Advanced Options:

  • -t, --target <name>: Specify the target file name for AI tools. (Default: coding-standards.md)

    Note: This only affects tools that support custom file names (Cursor, Augment, Windsurf, Cline, Roo Code). Tools like Claude Code and Gemini CLI use fixed file names and will ignore this parameter.

Examples:

# Interactive mode
$ rule-link create

# Specify a different source file
$ rule-link create --file my-awesome-rules.md

# Link specific tools directly (tools that need symlinks)
$ rule-link create --list Augment Windsurf "Claude Code"

# Force overwrite existing files
$ rule-link create --list Augment --force

# Link custom files
$ rule-link create --custom ".vscode/rules.md,enterprise.md"

# Combine flags with force overwrite
$ rule-link create --file project-rules.md --list Augment --custom "docs/guidelines.md" --force

License

This project is licensed under the MIT License.