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

phlight

v0.2.15

Published

Structured development workflow skills for AI coding agents

Downloads

205

Readme

phlight

A shitty little set of workflow skills that aspires to be a controlled, modular workflow for your AI coding agent. Built on Superpowers.

Every skill accepts --help (also -h, help) to print its usage screen and exit without running. That's the authoritative reference for args, flags, and prerequisites.

Skills

Pipeline (chain with --auto):

| Skill | Purpose | |---|---| | architect | Brainstorm and plan interactively, producing a plan file | | split | Break large plans into PR-sized chunks with dependency tracking | | implement | Execute a plan with subagent-driven development | | review | Opinionated PR fitness review focused on bloat and anti-patterns | | merge | Create PR, wait for checks, merge, cleanup |

Standalone:

| Skill | Purpose | |---|---| | fast | Full pipeline in one session for quick fixes and small features | | dispatch | Send a task or question to an agent in another tmux pane | | ask | Read-only Q&A - ideation, triage, architecture questions | | task | Create, view, and list tasks in your configured provider | | cleanup | Delete stale git branches locally and optionally on remote | | project-init | Detect and configure project context for all skills | | skill-build | Interactive workflow for building new phlight skills |

architect -> split (if needed) -> implement -> review -> merge
                                      |                    |
                                      +-- next split plan -+

dispatch -----> [another pane runs fast, implement, or ask]

Flags

--auto chains skills together. After each skill completes (and any human stop is cleared), it invokes the next in the pipeline. Attach at any entry point:

/phlight-architect my feature --auto
/phlight-implement path/to/plan.md --auto
/phlight-review --auto

--noconfirm skips the merge confirmation step. All other human stops (plan approval, manual testing) are always enforced.

Human Stops

Even in --auto mode, these always pause for you:

| When | You need to | |---|---| | architect completes | Read the plan, approve or request changes | | implement completes | Go to the worktree, test manually, confirm it works | | implement hits a project-specific intervention | Follow the documented procedure (migrations, etc.) | | merge is ready | Confirm you want to merge (skipped with --noconfirm) |

Everything else is autonomous.

Installation

Dependencies

Claude Code (via Plugin Marketplace)

/plugin marketplace add evansendra/phlight
/plugin install phlight@phlight-marketplace

Claude Code (local development)

claude --plugin-dir /path/to/phlight

OpenCode

Add phlight as an npm runtime plugin in your OpenCode config, either project-level opencode.json or global ~/.config/opencode/opencode.jsonc:

{
  "plugin": ["phlight"]
}

Restart OpenCode after changing config. This is the same runtime-plugin pattern Superpowers uses: the package registers skills/ from .opencode/plugins/phlight.js. It is not a TUI plugin, so do not install it through the TUI plugin installer.

OpenCode caches npm plugins under ~/.cache/opencode/packages/, not ~/.config/opencode/plugins/.

Verify

opencode debug config | rg 'phlight|plugin_origins|skills'
node -p 'require(process.env.HOME + "/.cache/opencode/packages/phlight@latest/node_modules/phlight/package.json").version'

In a new OpenCode session, use the skill tool to list skills and confirm the phlight-* skills are available.

Configuration

Config lives in your CLAUDE.md or rules files. Run /phlight-project-init for guided setup, or add manually:

## Task Management
- tool: github
- repo: owner/repo
- id-format: #xxx

Providers: clickup, linear, github, jira, none

## Quality Gates
- test: npm test
- lint: npm run lint
- format: npm run format
## Plans
- directory: docs/plans
- pr-target: 400

Plans config is optional; defaults to docs/plans/ and 400 lines per PR.

Config file locations

| Scope | Claude Code | OpenCode | |---|---|---| | Project (shared) | CLAUDE.md or .claude/CLAUDE.md | opencode.md or .opencode/opencode.md | | Per-user | .claude/rules/CLAUDE.local.md | .opencode/rules/*.local.md | | Global | ~/.claude/CLAUDE.md | ~/.config/opencode/opencode.md |

Quick Start

/phlight-fast fix the login redirect loop on the /callback route
/phlight-architect add CSV export to the reports dashboard --auto

License

MIT