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

@stupidur/vibe-coding-opencode

v0.1.4

Published

Personal OpenCode plugin template for commands, skills, and rules.

Downloads

582

Readme

@stupidur/vibe-coding-opencode

Minimal OpenCode plugin template for personal maintenance of commands, skills, and rules.

Local usage

  1. Add this plugin path to .opencode/opencode.json:
{
  "plugin": ["./plugins/vibe-coding-opencode"]
}
  1. Optional validation:
node plugins/vibe-coding-opencode/src/index.js --validate

Install helper

Project install:

bash plugins/vibe-coding-opencode/scripts/install-opencode.sh --target project

Global install:

bash plugins/vibe-coding-opencode/scripts/install-opencode.sh --target global

Dry run:

bash plugins/vibe-coding-opencode/scripts/install-opencode.sh --dry-run

Clean install (remove old target files first):

bash plugins/vibe-coding-opencode/scripts/install-opencode.sh --target project --clean

Publish to npm

  1. Confirm package metadata in package.json:
    • name should be your scoped package, for example @stupidur/vibe-coding-opencode.
    • repository, homepage, and bugs should point to your real GitHub repo.
  2. Run release checks:
cd plugins/vibe-coding-opencode
npm run release:check
  1. Login and publish:
npm login
npm publish --access public
  1. Use published plugin in .opencode/opencode.json:
{
  "plugin": ["@stupidur/vibe-coding-opencode"]
}

OpenCode npm install example

# In your project
npm install -D @stupidur/vibe-coding-opencode

Then point .opencode/opencode.json to package name:

{
  "plugin": ["@stupidur/vibe-coding-opencode"]
}

With this plugin config, commands under commands/, skills under skills/, and rules under rules/ are auto-registered at startup. You do not need to manually add command, skills.paths, or instructions.

Shopify theme init

When you start or take over a Shopify theme repo, run /init-shopify-project once. It drives generation or update of root AGENTS.md (project survey + full team guidelines). Former always-on rules/shopify/project-rules.md is now only reached through this command, so it is not injected into every session.

For a quick reminder of which rule file applies (git vs new/reuse/modify section), run /shopify-rules.