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

@coceresroman/agentify

v0.6.2

Published

CLI tool to auto-detect project stacks and generate Claude Code configuration files

Downloads

1,160

Readme

Agentify

Auto-detect your project's tech stack and generate Claude Code configuration files.

npm version License: GPL v2 Node.js

Agentify scans your project, detects the tech stack, and writes .claude/CLAUDE.md and .claude/skills/{stack}/SKILL.md so Claude has context about your architecture, best practices, and common commands. If CLAUDE.md already exists, it appends the skills section rather than overwriting.

Usage

npx @coceresroman/agentify init

| Flag | Description | Default | |------|-------------|---------| | --yes, -y | Skip confirmation prompts | false | | --no-interaction | Non-interactive mode (CI/CD) | false | | --output <path>, -o | Output directory | .claude | | --debug, -d | Verbose logging | false |

Supported stacks

| Ecosystem | Stacks | |-----------|--------| | Frontend | React, Vue, Angular, Next.js | | Node.js | NestJS, Express | | Python | Django, Flask, FastAPI | | Java | Spring Boot | | Infrastructure | Docker | | CI/CD | GitHub Actions |

Architecture

agentify/
├── src/
│   ├── cli.ts                   # CLI entry point
│   ├── commands/init.ts         # Init command
│   ├── detectors/               # Per-ecosystem detectors
│   │   ├── node.detector.ts
│   │   ├── python.detector.ts
│   │   ├── java.detector.ts
│   │   ├── go.detector.ts
│   │   ├── docker.detector.ts
│   │   ├── ci.detector.ts
│   │   └── index.ts             # Detector registry
│   ├── templates/
│   │   ├── claude-md/           # CLAUDE.md templates
│   │   └── skills/              # Per-stack SKILL.md templates
│   ├── analyzer.ts              # Confidence filtering (≥70% threshold)
│   ├── generator.ts             # Template rendering
│   ├── writer.ts                # File writing / appending
│   ├── prompts.ts               # Interactive prompts
│   └── utils/
├── tests/
│   ├── unit/
│   └── integration/
└── bin/

Detection pipeline: detectorsanalyzer (confidence filter) → generator (Handlebars templates) → writer (fs output).

Contributing

Adding a detector

  1. Create src/detectors/my-framework.detector.ts:
import { DetectorFunction } from '../types/index.js';

export const detect: DetectorFunction = async (projectRoot) => {
  const hasIndicator = await checkForIndicator(projectRoot);
  if (!hasIndicator) return null;

  return {
    stack: 'my-framework',
    confidence: 0.8,
    evidence: ['Found indicator X', 'Found indicator Y'],
    metadata: { version: '1.0.0' }
  };
};
  1. Register in src/detectors/index.ts
  2. Add a skill template at src/templates/skills/my-framework/SKILL.md.hbs
  3. Add tests in tests/unit/detectors/my-framework.detector.test.ts

Development setup

git clone https://github.com/coceresroman/agentify.git
cd agentify
npm install
npm run build
npm test

Guidelines

  • Write tests for every new detector
  • Keep confidence scoring consistent with existing detectors
  • Skill templates should include best practices, common commands, and patterns

License

GPL-2.0