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

nuxt-dev-skills

v1.0.0

Published

Reusable Claude Code skills for Nuxt/Vue development — coding conventions, architecture, bug fixing, and more.

Readme

nuxt-dev-skills

Reusable Claude Code skills for Nuxt / Vue development.

Install once, use across all your projects — coding conventions, architecture, bug fixing, and anti-patterns as structured AI skills.

中文文档


Install

# Install to current project (.claude/skills/)
npx nuxt-dev-skills add JieHaoCai/nuxt-dev-skills

# Install globally (~/.claude/skills/)
npx nuxt-dev-skills add JieHaoCai/nuxt-dev-skills -g

# Install specific skills only
npx nuxt-dev-skills add JieHaoCai/nuxt-dev-skills --only=bug-fix,bug-hunt

# Overwrite existing files
npx nuxt-dev-skills add JieHaoCai/nuxt-dev-skills --force

# List available skills in a repo
npx nuxt-dev-skills list JieHaoCai/nuxt-dev-skills

# Specify a branch
npx nuxt-dev-skills add JieHaoCai/nuxt-dev-skills --branch=dev

Install from any GitHub repo

The CLI can install skills from any GitHub repository that has a skills/ directory:

npx nuxt-dev-skills add other-user/their-skill-repo

Where are skills installed?

| Flag | Location | Scope | |------|----------|-------| | (default) | .claude/skills/ | Current project only | | --global / -g | ~/.claude/skills/ | All projects |

Skills

| Skill | File | Description | |-------|------|-------------| | Code Conventions | code-conventions.md | Import order, CSS variables, BEM naming, component patterns, constants | | Architecture | architecture.md | Directory structure, layer separation, state management, type system | | Bug Hunt | bug-hunt.md | Systematic investigation — reproduce, trace data flow, identify root cause | | Bug Fix | bug-fix.md | Minimal safe fixing — smallest change, verify, regression test | | Feature Dev Flow | feature-dev-flow.md | End-to-end development — requirements → types → API → components → page | | Anti-patterns | anti-patterns.md | Comprehensive "never do this" reference, organized by severity (P0/P1/P2) | | UI from Screenshot | ui-from-screenshot.md | Analyze screenshot, ask clarifying questions, confirm scope before coding |

How It Works

Each skill is a Markdown file with frontmatter that Claude Code reads as context:

---
description: When this skill should be activated
---

## When to Apply
## Core Principles
## Anti-patterns (NEVER do these)
## Checklist

When you ask Claude Code to fix a bug, build a feature, or review code, the relevant skill provides structured guidance — including what NOT to do.

Skill Structure

Every skill follows a consistent format:

  • When to Apply — Trigger conditions
  • Core Principles — 3-5 key rules with examples
  • Anti-patterns — Things that must never be done (the most effective part)
  • Procedure / Steps — How to execute
  • Checklist — Verification before done

Create Your Own Skill Repo

Any GitHub repository with a skills/ directory containing .md files can be used as a skill source:

your-skill-repo/
├── skills/
│   ├── your-skill-a.md
│   └── your-skill-b.md
└── README.md

Each .md file should have frontmatter with a description field for the list command to display.

Customization

After installation, edit the .md files directly to match your team's conventions. The skills are yours — adapt them to your stack and preferences.

Tech Stack

These skills are designed for but not limited to:

  • Nuxt 3 + Vue 3 + TypeScript
  • Pinia (state management)
  • Tailwind CSS / SCSS + BEM
  • Biome (linting)
  • shadcn-vue (UI components)

The architecture and bug-fixing principles apply to any frontend project.

License

MIT