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

guideline-manage

v0.21.0

Published

Keep shared coding-agent guidelines on a guideline server and pick them into ruler projects

Downloads

1,757

Readme

guideline-manage

English · 한국어

A tool for keeping a team's shared coding-agent guidelines (per-stack rules, skills, subagents, MCP settings) on a guideline server and picking them into projects with the guideline CLI. Projects receive them as ruler sources (.ruler/).

guideline server (source DB) ── admin web: view, edit, history, proposal review, tokens
        │  ▲
        │  │ guideline propose (proposal → accepted by an admin)
        ▼  │
project: guideline pick / status / update → copies in .ruler/ + guideline.json + guideline-lock.json

Install

You need Node 24 or later.

npm install -g guideline-manage   # provides the guideline command

The server runs with Docker Compose from this repository (docs/manual/server.md).

Usage

guideline login --server <URL>   # once per machine
guideline pick                   # choose in the server form; submitting applies right away
guideline status                 # are we up to date?
guideline update                 # same choices, latest version
guideline propose --dry-run      # propose edited copies upstream (preview without sending)
  • New here? Start with docs/manual/guide.md — installation, running a server, receiving guidelines, overrides and troubleshooting, in order.
  • Point agents at the server's /llms.txt ("Usage" at the top of the admin web).
  • Command reference: docs/manual/usage.md. Running the server: docs/manual/server.md. Language packs: docs/manual/locales.md.
  • Projects must use ruler (.ruler/). Subdirectories of a monorepo receive guidelines separately.
  • A project can receive from several guideline servers (--source). Name clashes are resolved with aliases in guideline.json.
  • The source changes through proposals: edited copies with guideline propose, new guidelines with guideline source + guideline propose --from. An admin accepts them under "Proposals" on the web; with an admin scope token, propose applies them directly (--review proposes instead).

Language

English is the default. With GUIDELINE_LANG=ko, CLI messages, the admin web, the management guideline and index written into projects, and the seed of an empty server are in Korean. For the CLI you can instead put { "lang": "ko" } in ~/.config/guideline/config.json; the environment variable wins. Set it for the CLI and the server separately. Other languages come as language pack folders you drop in (docs/manual/locales.md).

Coming from 0.14 or earlier: the default language is now English. To keep Korean, set GUIDELINE_LANG=ko in your shell and in the server environment; otherwise the next update rewrites the management guideline and index in English. The 0.10 docs-repository commands (init, pick/update inside a guideline repository, and its management skills) are gone — see "Moving to 0.15" in docs/manual/usage.md.

Development

pnpm test                                # node --test. Tests run with GUIDELINE_LANG=ko
node cli/bin/guideline.js help
ADMIN_TOKEN=$(openssl rand -base64 48) PUBLIC_URL=http://localhost:3000 DATA_DIR=./.data node server/bin/guideline-server.js   # server

Releases

GitHub Actions publishes to npm. Do not run pnpm publish locally.

pnpm version minor            # or patch, major. Creates the commit and the v<version> tag
git push --follow-tags        # the tag starts the release workflow

A v<SemVer> tag runs .github/workflows/release.yml: it checks that the tag matches package.json, runs pnpm test, and publishes with provenance. It uses npm Trusted Publishing, so no token is stored: the npm package trusts jang2162/guideline-manage and release.yml. Pull requests and pushes to main run only the tests (ci.yml).

Versioning

  • Command behavior or skill procedures change: minor
  • Anything else: patch

Until 1.0.0, breaking changes also bump the minor version.

Layout

| Path | Contents | | --- | --- | | cli/ | The guideline command. cli/src/i18n.js reads the language setting and language packs | | locales/ | Language packs: en (canonical) and ko. messages.json strings and templates/ long texts (management guideline, authoring rules, seed skills, llms.txt, new-file templates) | | server/ | The guideline server. server/src/ server code (web/ admin pages), server/static/ page CSS and JS, server/Dockerfile. Not part of the npm package | | compose.yaml | Guideline server deployment with Docker Compose. Environment variables in .env.example | | .github/workflows/ | CI (tests) and release (npm publish) | | docs/manual/ | Documentation for people (English). Korean in docs/manual/ko/ |

License

MIT