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

pi-karpathy-guidelines

v1.0.0

Published

Enforces Andrej Karpathy's coding guidelines to reduce common LLM mistakes: think before coding, simplicity first, surgical changes, goal-driven execution.

Downloads

144

Readme

pi-karpathy-guidelines

A Pi extension that enforces Andrej Karpathy's coding guidelines to reduce common LLM coding mistakes.

Install

pi install npm:pi-karpathy-guidelines

Or from git:

pi install git:github.com/parkiyong/pi-karpathy-guidelines

Guidelines

The extension injects four behavioral rules into every LLM turn:

  1. Think Before Coding — State assumptions. Ask when uncertain. Surface tradeoffs.
  2. Simplicity First — Minimum code that solves the problem. No speculative features or abstractions.
  3. Surgical Changes — Touch only what's needed. Match existing style. Don't refactor what isn't broken.
  4. Goal-Driven Execution — Define verifiable success criteria. State a plan with checks.

Derived from Karpathy's observations on LLM coding pitfalls.

Active Enforcement

Beyond prompt injection, the extension actively gates tool calls that violate the guidelines:

| Gate | Trigger | Guideline | |------|---------|-----------| | Large write | write tool > 200 lines | #2 Simplicity First | | Broad edit | edit tool > 5 blocks | #3 Surgical Changes |

Both gates prompt for confirmation before allowing the operation through. The LLM receives the guideline-specific reason if blocked.

Commands

| Command | Description | |---------|-------------| | /karpathy | Toggle on/off — shows 🧠 in footer when active | | /karpathy-check | Ask the LLM to self-critique its last response against all 4 guidelines |

The extension is enabled by default. Use /karpathy to turn it off for trivial tasks where the caution bias isn't useful.

How it works

  • before_agent_start — Appends the full guidelines to the system prompt each turn.
  • tool_call — Intercepts write and edit calls, checks thresholds, prompts for confirmation.
  • /karpathy-check — Sends a self-review prompt referencing the last assistant message.

License

MIT