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

sisyo

v1.3.1

Published

Smart documentation system for vibe coding with Claude Code. Token-efficient MAP.md routing.

Readme

sisyo

Smart documentation system for vibe coding with Claude Code. Docs auto-update as you build. Token-efficient 3-level routing pattern.

Install

npx sisyo

Run it in your project root.

What it creates

your-project/
  SISYO.md                             # Project rules (imported by CLAUDE.md)
  CLAUDE.md                            # Auto-created or updated with @SISYO.md
  .claude/
    rules/docs.md                      # Doc rules (auto-loaded)
    skills/vibe-docs/SKILL.md          # Brain (loaded on trigger)
  docs/
    MAP.md                             # Level 1: routing table
    99_progress/todo.md                # Task backlog
    99_progress/handoff.md             # Session recovery
    99_progress/features.md            # Feature log

SISYO.md holds the project config. CLAUDE.md is untouched if it already exists — sisyo just appends @SISYO.md to it.

How it works

Problem: Loading all docs into context = 20K+ tokens = runs out fast.

Solution: 3-level routing -- load only what you need, when you need it.

Level 1: MAP.md              (~500 tokens)  Read ALWAYS
    |
Level 2: folder/_summary.md  (~200 tokens)  Compact table of all items
    |
Level 3: folder/[detail].md                 Full detail, ONLY when needed

Most tasks only need Level 1 + Level 2. Detail files load only when actively modifying.

Example flow

MAP.md
  "03_database -- 4 tables: users, posts, comments, categories"
    |
    v
03_database/_summary.md
  | Table    | Description              | Key relations |
  | users    | Accounts, auth, profile  | --            |
  | posts    | Blog posts, draft/publish| -> users      |
    |
    v  (only if modifying users table)
03_database/users.md
  Full column definitions, indexes, constraints

Auto-triggers

The vibe-docs skill triggers automatically when you:

  • Complete a feature -> logs to 99_progress/features.md
  • Design database tables -> updates 03_database/_summary.md + detail file
  • Add API endpoints -> updates 04_api/_summary.md + detail file
  • Plan features -> updates 01_requirements/_summary.md + detail file
  • Make architecture decisions -> updates 02_architecture/decisions.md
  • Set up auth/security -> creates 08_security/[topic].md
  • Integrate third-party service -> creates 09_integrations/[service].md
  • Complete any task -> updates 99_progress/todo.md
  • End a session -> writes 99_progress/handoff.md

Every change updates bottom-up: detail → _summary.md → MAP.md

Session recovery

After /clear or starting fresh:

Read handoff and continue

Claude reads MAP.md + handoff.md + todo.md (~3K tokens) and picks up where you left off.

Update

npx sisyo --update

Updates system files (SISYO.md, .claude/rules/docs.md, vibe-docs/SKILL.md) without touching your docs.

Doc folders

| Folder | Purpose | |---|---| | 00_schedule/ | Roadmap, milestones, sprint plans | | 01_requirements/ | Feature specs, user stories | | 02_architecture/ | System design, tech decisions (ADR) | | 03_database/ | Schema, ERD, migration log | | 04_api/ | API endpoint specs by module | | 05_frontend/ | Pages, components, routing | | 06_infra/ | Deploy, Docker, CI/CD, env vars | | 07_testing/ | Test plans, test cases, edge cases | | 08_security/ | Auth flows, permissions, API keys | | 09_integrations/ | Third-party services config & usage | | 99_progress/ | Feature log, TODO, session handoff |

Each folder with multiple items has a _summary.md (compact table) + detail files. Folders are created on-demand. No empty placeholders.

Skills

Optional best-practice guides that Claude loads on demand:

| Skill | Triggers on | |---|---| | vibe-docs | Doc updates, feature changes, session end | | fastapi-best-practices | FastAPI backends, REST APIs, Python web services | | react-page-oriented | React/Next.js pages, component structure |

After install

  1. Edit SISYO.md — replace [Project Name] with yours
  2. Open Claude Code and start building
  3. Docs update automatically as you work

Author

HoangThang - hoang.jp

License

MIT