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

@kweiza/harness

v1.1.0

Published

Kweiza Harness — Claude Code project setup CLI

Readme

@kweiza/harness

Claude Code harness setup CLI for Kweiza projects. Automates project initialization with company-wide standards, stack-specific presets, and Anthropic's recommended harness engineering practices.

Quick Start

npx @kweiza/harness init my-project

Features

  • One-command setup — Interactive CLI generates CLAUDE.md, .claude/rules/, hooks, and more
  • 9 stack presets — Next.js, Vite, FastAPI, Express, Figma Plugin, AI Agent, ComfyUI, Fullstack Platform, Docker
  • Composable presets — Combine multiple presets (e.g., nextjs + docker)
  • Anthropic best practices — Follows official harness engineering recommendations:
    • CLAUDE.md for project overview (< 200 lines)
    • .claude/rules/ for modular, path-scoped rules
    • .claude/settings.json for hooks (100% enforcement)
  • Company standards — Git workflow, code quality, testing, security, documentation rules baked in
  • Updatable — Sync projects with latest standards via harness update

Installation

# Use directly with npx (no install needed)
npx @kweiza/harness init

# Or install globally
npm install -g @kweiza/harness

Commands

harness init [path]

Initialize a new project with Kweiza harness standards.

npx @kweiza/harness init my-app

Interactive prompts will ask for:

  • Project name
  • Presets to apply (multi-select)
  • Whether to initialize git

harness add <preset>

Add a preset to an existing project. Merges into existing CLAUDE.md, settings, and rules.

cd my-existing-project
npx @kweiza/harness add fastapi

harness update

Sync your project with the latest harness standards. Only updates CLAUDE.md, settings, and rules — never touches your scaffold files.

npx @kweiza/harness update

harness list

Show all available presets.

npx @kweiza/harness list

Available Presets

| Preset | Stack | Language | |--------|-------|----------| | nextjs | Next.js web app | TypeScript | | vite | Vite web app | TypeScript | | fastapi | FastAPI backend | Python | | express | Express backend | TypeScript | | figma-plugin | Figma plugin | TypeScript | | ai-agent | Background AI agent | Python | | comfyui | ComfyUI custom nodes | Python | | fullstack-platform | Node-based generative AI platform | TS + Python | | docker | Docker containerization | — |

What Gets Generated

When you run harness init, the following structure is created in your project:

your-project/
├── CLAUDE.md                      # Project overview + build commands
├── .claude/
│   ├── settings.json              # Hooks (lint, format — enforced on every commit)
│   └── rules/
│       ├── git-workflow.md        # Branch naming, conventional commits
│       ├── code-quality.md        # Type safety, SRP, no magic numbers
│       ├── testing.md             # TDD, regression tests, CI gates
│       ├── security.md            # Secrets, OWASP, input validation
│       ├── documentation.md       # README, API docs
│       └── <preset>.md            # Stack-specific rules (path-scoped)
└── .gitignore

How It Works

Merge Strategy

Presets are composable. When you select multiple presets:

  • CLAUDE.md — Base content at top, each preset appended as a section
  • settings.json — Hooks merged into a single array (duplicates removed)
  • rules/ — All rule files copied (base + each preset). Warns if > 20 files (Anthropic limit)
  • scaffold files — Copied without overwriting existing files

Version Tracking

Harness writes version info to .claude/settings.local.json (gitignored). This lets harness update know which presets were applied and when.

Contributing

See CONTRIBUTING.md for development setup and contribution guidelines.

License

MIT