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.2.3

Published

Claude Code adapter for dotdotgod project memory workflows.

Readme

@dotdotgod/claude-code

npm version GitHub License: Elastic 2.0

Claude Code adapter for dotdotgod's docs-first project-memory workflow.

Use this package when you want Claude Code to initialize shared project docs, load bounded repository context, plan from durable docs before implementation, and review changed files with graph-impact evidence before handoff.

Start Here

This package is a Claude Code plugin: a plugin manifest plus /dd:* commands and skills. Installing it from npm alone does not register the commands — Claude Code loads it through plugin registration or a local plugin directory.

Register the dotdotgod plugin marketplace inside Claude Code, then install the plugin:

/plugin marketplace add dotdotgod/dotdotgod-kit
/plugin install dotdotgod@dotdotgod

Then use the bundled /dd:* commands in your repository:

/dd:init
/dd:load
/dd:plan Update the API migration plan.
/dd:plan-goal Add the new export API to the auth module.
/dd:impact

For local development from a source checkout, load the plugin directory directly instead of installing:

claude --plugin-dir /path/to/dotdotgod/packages/claude-code

What It Adds to Claude Code

| Command or skill | Use it for | Result | | --- | --- | --- | | /dd:init | Start a repository with dotdotgod conventions. | Creates or normalizes AGENTS.md, thin agent entrypoints, docs indexes, active-plan space, and archive map. | | /dd:load | Load project memory read-only. | Prefers dotdotgod load-snapshot <root> --json, then falls back to README-index reads. | | /dd:plan | Plan before implementation. | Writes or updates durable task intent in docs/plan/<task-slug>/README.md. | | /dd:plan-goal | Run 5-stage structured planning before implementation. | Produces durable checkpoint files in docs/plan/<task>/.dotdotgod-plan/ and a plan README. | | /dd:impact | Review changed files before verification or handoff. | Uses dotdotgod graph impact to identify likely related docs, tests, commands, and source files. | | document-clarify | Improve docs wording without changing behavior contracts. | Clarifies README/spec/test/arch/plan/archive docs using memory-area roles. |

The package also includes matching skills for init, load, planning, plan-goal, and impact-review workflows.

Shared Project-Memory Contract

  • AGENTS.md remains canonical.
  • CLAUDE.md stays thin and imports or points to AGENTS.md.
  • Specs describe behavior and requirements.
  • Architecture docs explain rationale, boundaries, and conventions.
  • Test docs explain verification strategy, regression coverage, fixtures, and commands.
  • 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.

Memory Areas and Traceability

By default, docs/spec/** has two separate roles:

  • It is stable shared project memory for product behavior and requirements.
  • It is the traceability-enforced path for behavior specs.

Projects can customize memory roles with memory.areas, and can customize traceability requirements with traceability.required and traceability.exclude.

Optional Hooks

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

Use hooks only when you want opt-in reminders, validation, or local safety rails around the same loop: plan, implement, impact-review, verify, review, and archive. See hooks/README.md for current lifecycle notes and advisory examples.

Local Development

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

Learn More

See the root README, Context curation, Context mechanics, Memory area config, and Traceability config.

Compared with Graphify-Style Memory

This adapter is guidance-oriented. It asks Claude Code to prefer a bounded dotdotgod load snapshot, avoid broad archive scans, and follow README indexes before reading raw files. The strength is structured retrieval from explicit project-maintained links, not a giant graph report.