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

claude-code-autoconfig

v1.0.81

Published

Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.

Readme

Claude Code Autoconfig

Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.

Quick Install

macOS / Linux / WSL:

curl -fsSL https://raw.githubusercontent.com/design-and-deliver/claude-code-autoconfig/main/install.sh | bash

Windows (PowerShell):

irm https://raw.githubusercontent.com/design-and-deliver/claude-code-autoconfig/main/install.ps1 | iex

After Install

  1. /autoconfig — Claude analyzes your project and configures itself
  2. /show-docs — Opens an interactive guide showing what got set up

That's it. Your Claude Code environment is configured and ready.

What Gets Installed

your-project/
├── CLAUDE.md                          # Project context (auto-populated)
└── .claude/
    ├── commands/                      # Slash commands
    │   ├── autoconfig.md              #   /autoconfig - self-configures
    │   ├── commit-and-push.md         #   /commit-and-push - git workflow
    │   ├── enable-retro.md            #   /enable-retro - opt-in tech debt tracking
    │   ├── show-docs.md              #   /show-docs - interactive walkthrough
    │   ├── sync-claude-md.md          #   /sync-claude-md - update CLAUDE.md
    │   └── test.md                    #   /test - run tests
    ├── feedback/                      # Team corrections for Claude
    │   └── FEEDBACK.md                #   Add entries when Claude errs
    ├── docs/                          # Interactive documentation
    │   └── autoconfig.docs.html       #   Open with /show-docs
    ├── rules/                         # Path-scoped context (empty)
    ├── .mcp.json                      # MCP server configs (empty placeholder)
    └── settings.json                  # Permissions & security

How It Works

Self-Configuration

Most templates are static — copy, paste, manually fill in.

This one is self-configuring. Run /autoconfig and Claude:

  1. Detects your environment — Windows vs macOS/Linux for correct command syntax
  2. Scans your project — Package files, framework indicators, test setup
  3. Populates CLAUDE.md — Project name, tech stack, commands, conventions
  4. Configures settings.json — Permissions tuned to your ecosystem

You get a custom-fit configuration without the manual work.

Slash Commands

| Command | Description | |---------|-------------| | /autoconfig | Analyzes project and populates configuration | | /sync-claude-md | Re-analyzes project and updates CLAUDE.md | | /show-docs | Opens interactive docs in browser | | /test | Runs your test suite (auto-detects framework) | | /commit-and-push | Stages, commits with good message, and pushes | | /enable-retro | (Experimental) Enable tech debt tracking |

Team Feedback

When Claude makes a mistake, add an entry to .claude/feedback/FEEDBACK.md:

## 2026-01-07: Don't use deprecated API
Claude used `oldFunction()` instead of `newFunction()`.
Always use the v2 API for user endpoints.

Claude reads this directory and learns for next time. Persists across /autoconfig runs.

Retro Items (Experimental)

Opt-in feature for tracking tech debt. Run /enable-retro to activate.

When enabled, Claude logs improvement opportunities as structured story files in .claude/retro/:

  • Problem description
  • Acceptance criteria
  • Suggested approach
  • Priority & effort sizing
  • Files involved

Work through items anytime: "Hey Claude, fix retro #001"

Rules

The rules/ directory is intentionally empty. Effective rules require understanding your codebase patterns, team conventions, and quality standards.

Want optimized rules for your project? Reach out: [email protected]

Permissions & Security

The included settings.json provides sensible defaults that balance productivity with safety:

  • allow — Auto-approved operations (file edits, tests, git commands)
  • deny — Always blocked (secrets, destructive commands, network calls)

Review and adjust these for your team's needs. Run /permissions in Claude Code to inspect your current configuration.

See Claude Code Security Docs for best practices.

Links


Built by ADAC 1001