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

@loworbitstudio/lo-playbook

v0.2.0

Published

Low Orbit Playbook CLI — `npx @loworbitstudio/lo-playbook init` bootstraps a project with the playbook substrate (parallel surface to the /lo-install-playbook Claude skill).

Readme

@loworbitstudio/lo-playbook

CLI surface for the Low Orbit Playbook — a parallel entry point to the /lo-install-playbook Claude skill.

Both surfaces share the same wizard runner, option modules, and Zod-backed manifest accessor (@loworbitstudio/lo-project). The CLI is the right choice when you need to bootstrap a project from outside Claude — CI scripts, fleet operations, onboarding flows where Claude isn't open yet.

Quick start

# Full interactive install — same flow as /lo-install-playbook
npx @loworbitstudio/lo-playbook init

# Headless — accept defaults
npx @loworbitstudio/lo-playbook init --yes --name veronica-home --org veronica

# Seed answers from a partial manifest
npx @loworbitstudio/lo-playbook init --yes \
  --name veronica-home --org veronica \
  --config ./base.yaml

# Clear the cached "Reuse previous" pointer
npx @loworbitstudio/lo-playbook init --reset-preferences

Three-way fork

Every interactive run starts with a create-next-app-style choice:

| Choice | What happens | |--------|--------------| | Use defaults | Stack-detected defaults are applied; you only answer the four unfindable questions (name, org, description, brand color). | | Reuse previous | The most recently touched manifest across .projects.json-tracked repos pre-fills every answer. Cached at ${env-paths('lo-playbook').cache}/last-reuse.json for instant lookup. | | Customize | Full prompt flow — every option visible. Matches the legacy Claude-skill behavior. |

Flags

| Flag | What it does | |------|--------------| | --yes | Skip prompts. Requires --name and --org. | | --config <path> | Seed answers from a partial manifest YAML. Schema matches .lo/project.yaml. | | --reset-preferences | Delete the cached "Reuse previous" pointer. | | --name <slug> | Project name. Required in --yes mode unless project.name is in --config. | | --org <dir> | Org directory under ~/Code/{org}/. Required in --yes mode unless project.org is in --config. | | --target-dir <path> | Override the cwd (mostly used by tests). | | --playbook-root <path> | Override the playbook checkout. Defaults to $LO_PLAYBOOK_ROOT or ~/Code/low-orbit/low-orbit-playbook. |

See docs/setup/cli.md for headless / CI usage and a sample base.yaml.

How it fits with the Claude skill

The CLI does not re-implement any option logic. It:

  1. Renders the three-way fork.
  2. Resolves the playbook checkout.
  3. Spawns scripts/wizard.mjs run --target-dir <path> — the same runner the Claude skill invokes.

Adding a new playbook option (a new file under scripts/options/) requires zero CLI changes.

Cache + reuse details

The cache pointer lives at the platform-native cache directory returned by env-paths:

| Platform | Cache dir | |----------|-----------| | macOS | ~/Library/Caches/lo-playbook | | Linux | ~/.cache/lo-playbook (or $XDG_CACHE_HOME/lo-playbook) | | Windows | %LOCALAPPDATA%\lo-playbook\Cache |

If the cached pointer is stale (the manifest no longer exists on disk), the CLI falls back to a live scan over .projects.json.

Versioning

Pre-1.0 (0.x) — breaking changes can land in minor versions while the prompt module and accessor library stabilize. The package is published from CI via Changesets every time a .changeset/*.md file lands on main.

License

MIT