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

@weloin/claude-skills

v0.2.6

Published

Weloin's Claude Code skills library + cross-platform installer (symlinks skills into ~/.claude/skills)

Readme

@weloin/claude-skills

Weloin's Claude Code skills library — install with one command, updates via symlink. macOS · Linux · Windows.


weloin:project-setup

A phase-machine for agent-driven development. Instead of ad-hoc prompting, it runs your project through structured phases — from first interview to shipped code — with every decision recorded and resumable.

What you get

  • An interview that produces your brief, requirements, architecture, and ADRs.
  • A custom agent roster with model tags matched to each role.
  • Phased plans executed at your chosen AUTO / GUIDED / MANUAL autonomy.
  • A docs/project/STATE.md single source of truth — close a session mid-phase, resume days later without re-explaining anything.
  • Works on fresh directories or aligns an existing codebase to the same structure.

Why it holds up

  • Durable state. Agent sessions lose context; this makes project state survive across them.
  • Maturity axis (prototype → mvp → production) sets the quality bar independent of scale — prototypes skip ceremony but log every shortcut to a debt ledger; promote later upgrades by re-asking skipped questions and building a hardening plan from that ledger.
  • Evidence-based gates. Opt-in quality gates mean work isn't "done" until it passes review with proof — not when the agent says so.
  • Strategy that fits. A 15-strategy catalog with a project-kind recommendation matrix, not one-size-fits-all.
  • Configurable Git workflow. Commit strategy (style · detail · AI-signature) and worktree policy (per-phase / per-feature / ask / none) set once, applied automatically.
  • Never frozen. Every config field has a subcommand to re-set it later; changes apply going forward, never restructuring existing work.

Full subcommand reference & opt-in features → docs/project-setup.md.

Quick install

npm install -g @weloin/claude-skills   # then:
weloin-skills                          # pick skills interactively

Full install, update, and CLI reference → docs/installation.md.

What execution looks like (per feature / fix)

Once set up, every substantial change runs the same loop — 🧑 = you decide, 🤖 = Claude acts. Config (worktrees, autonomy, gitflow, commit_strategy) steers the branches without re-asking.

flowchart TD
    Start([🧑 Request: feature or fix]) --> Trivial{🤖 Substantial change?}
    Trivial -->|no, one-liner| CurCheckout[🤖 Work on current checkout]
    Trivial -->|yes| Policy{🤖 worktrees policy?}

    Policy -->|per-feature| MkWT[🤖 Auto-create worktree + branch]
    Policy -->|per-phase| Resolved[🤖 Already isolated at macro-plan]
    Policy -->|none| CurCheckout
    Policy -->|ask| AskIso[🧑 Choose: current branch / new branch / worktree]
    AskIso --> MkWT

    MkWT --> Plan
    Resolved --> Plan
    CurCheckout --> Plan

    Plan[🤖 Write plan: goal, files, tasks, DoD] --> MacroAsk[🧑 Macro-plan ask: gitflow branch? autonomy mode?]
    MacroAsk --> Gate1{🧑 Approve plan?}
    Gate1 -->|revise| Plan
    Gate1 -->|approve| Loop

    subgraph Loop [Task loop — per task]
        direction TB
        Dispatch[🤖 Builder subagent: task + spec + rules] --> Verify[🤖 Verify vs maturity DoD]
        Verify --> Review[🤖 Reviewer subagent]
        Review --> Gates{🤖 Quality gates at group boundary?}
        Gates -->|FAIL| Fix[🤖 Fix loop] --> Dispatch
        Gates -->|PASS / CONCERNS| Commit[🤖 Commit per commit_strategy + progress + STATE.md, same commit]
    end

    Commit --> Mode{🧑🤖 Autonomy mode?}
    Mode -->|AUTO| More
    Mode -->|GUIDED, group done| PauseG[🧑 Review report → go]
    Mode -->|MANUAL| PauseM[🧑 Approve next task]
    PauseG --> More
    PauseM --> More

    More{🤖 More tasks?} -->|yes| Dispatch
    More -->|no| Merge[🤖 Merge per gitflow + clean up worktree]
    Merge --> Done([🤖 Update STATE.md next: → resume-ready])

Deeper walk-through → docs/execution-flow.md.


Docs

License

MIT © Weloin