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

cad-workflow

v1.2.0

Published

Clean Agentic Dev - Workflow IA avec Clean Architecture Hexagonale et TDD

Readme

CAD Workflow - Clean Agentic Dev

Workflow Claude Code pour le developpement assiste par IA avec Clean Architecture Hexagonale et TDD.

Installation

npx cad-workflow install

L'installateur interactif vous pose quelques questions :

  1. Nom du projet
  2. Stack : Mobile (React Native Expo + NestJS), Web (Angular/React + NestJS), ou Backend-only (NestJS)
  3. Gestion des tickets : Jira (connexion automatique) ou Local (stories en markdown)

Fichiers installes dans votre projet :

  • CLAUDE.md - Instructions pour Claude Code
  • .claude/agents/ - Agents specialises selon votre stack
  • .claude/commands/ - 9 commandes de workflow (+ jira-setup si Jira)
  • .claude/skills/ - Skills (clean code, hexa, TDD, mutation testing)
  • .cad/config.yaml - Configuration du workflow
  • .cad/workflow-status.yaml - Etat du workflow
  • docs/ - Structure de documentation

Toujours genere :

  • .mcp.json - Configuration MCP (Context7 + Playwright, + Atlassian si Jira)

Mise a jour

npx cad-workflow update

Met a jour les fichiers CAD (agents, commands, skills) sans toucher a vos fichiers personnalises (CLAUDE.md, config, docs/).

Status

npx cad-workflow status

Affiche la version installee, la stack, le mode de tickets, et verifie les mises a jour.

Workflow

/cad [description de la feature]

Repondez OK apres chaque phase pour continuer. Si interrompu :

/cad continue

Commandes

| Commande | Phase | Description | |----------|-------|-------------| | /status | - | Afficher le status actuel | | /cad | 1-7 | Workflow complet orchestre | | /comprendre | 1 | Analyse et clarification du besoin | | /concevoir | 2 | Design et plan d'implementation | | /implementer | 3 | Implementation TDD | | /review | 4 | Review code + mutation tests | | /e2e | 5 | Tests end-to-end | | /documenter | 6 | Documentation | | /commit | 7 | Formatage, linting, commit |

Stacks

| Stack | Agents | Skills | |-------|--------|--------| | Mobile | backend-developer, backend-reviewer, mobile-developer, mobile-reviewer, orchestrator | clean-hexa-backend, clean-hexa-mobile, mutation-testing | | Web | backend-developer, backend-reviewer, frontend-developer, frontend-reviewer, orchestrator | clean-hexa-backend, clean-hexa-frontend, mutation-testing | | Backend-only | backend-developer, backend-reviewer, orchestrator | clean-hexa-backend, mutation-testing |

MCPs inclus

Les MCPs suivants sont automatiquement configures dans le .mcp.json genere :

  • context7 : Documentation a jour des frameworks (ajouter "use context7" dans vos prompts)
  • playwright : Automatisation tests E2E

Si Jira est selectionne, le MCP Atlassian est egalement ajoute.

Licence

MIT - Voir LICENSE