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

@dotdotgod/claude-code

v0.1.15

Published

Claude Code adapter for dotdotgod project memory workflows.

Readme

@dotdotgod/claude-code

Change a file, know what else must be checked.

Claude Code adapter for dotdotgod's context curation workflow. It gives Claude Code /dd:load, /dd:plan, /dd:init, and skills that follow the same curated AGENTS.md, docs/spec, docs/test, docs/arch, docs/plan, and docs/archive contract used by the Pi and Codex adapters.

What Gets Better?

  • /dd:load starts from curated project memory.
  • Load guidance prefers dotdotgod load-snapshot <root> --json when the CLI is available, then falls back to README-index reads.
  • Claude Code can use docs structure as retrieval intent: specs for behavior, architecture for rationale, tests for verification, plans for current work, and archive indexes for past decisions.
  • Product intent, design rationale, and verification standards stay in durable docs.
  • /dd:plan writes or updates durable task intent in docs/plan/<task-slug>/README.md before implementation.
  • /dd:init bootstraps shared agent instructions and docs folders for future context curation.
  • Skills mirror the commands so natural-language requests can use the same workflows.

Included

  • Claude Code plugin manifest: .claude-plugin/plugin.json
  • Slash commands:
    • /dd:load: load project memory read-only.
    • /dd:plan: plan from docs before implementation.
    • /dd:init: initialize shared agent docs and docs folders, using dotdotgod init when available and the bundled fallback when not.
  • Skills:
    • project-load
    • doc-first-planning
    • project-initializer

Optional Hooks

Claude Code can run local lifecycle hooks from Claude settings. dotdotgod does not require hooks: /dd:load, /dd:plan, /dd:init, and the bundled skills work without them.

Use hooks only when you want opt-in reminders or validation around the same workflow. See hooks/README.md for advisory examples and stricter plan-safety patterns.

Local Development

Use the package as a local Claude Code plugin directory while developing:

claude --plugin-dir /Users/dotdot/Workspace/dotdotgod/packages/claude-code

Run package checks:

pnpm --filter @dotdotgod/claude-code run verify
pnpm --filter @dotdotgod/claude-code run pack:dry-run

Shared Contract

  • AGENTS.md remains canonical.
  • CLAUDE.md stays thin and imports or points to AGENTS.md.
  • Active plans use docs/plan/<task-slug>/README.md.
  • Completed plans move to docs/archive/plan/<task-slug>/.
  • Temporary reports move to docs/archive/report/<report-slug>/.
  • docs/archive/README.md is the archive map; archive bodies should be read only when targeted.

Compared with Graphify-Style Memory

This adapter is guidance-oriented. It asks Claude Code to prefer a bounded dotdotgod load snapshot when available, avoid broad archive scans, and follow README indexes before reading raw files.

The strength is structured retrieval: project docs declare which files are rules, specs, architecture, verification, active intent, or historical memory. That keeps the memory layer useful on small tasks where a large graph report would be overhead.