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

@mvuljevas/pragmatik

v0.4.1

Published

Reusable Pragmatik templates, workflows, and guided AI tooling setup.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mvuljevasmvuljevas

Keywords

agentsaiworkflowtemplatesgovernancecli

Readme

Pragmatik

Pragmatik is a reusable documentation and workflow template library for AI-assisted software projects.

The goal is to standardize how projects define agent behavior, documentation rules, snapshots, versioning, naming, and repeatable delivery workflows.

Pragmatik also ships a project CLI:

npx @mvuljevas/pragmatik help
npx @mvuljevas/pragmatik setup
npx @mvuljevas/pragmatik dashboard

When installed as a project dependency, use the pragmatik command directly.

Purpose

This repository provides reusable templates for projects such as:

  • Laravel + React applications, aligned with the Prisma project workflow.
  • React, Vite, SPA, or PWA applications.
  • Chrome extensions built with vanilla HTML, CSS, and JavaScript.
  • Documentation-only repositories.
  • Future project types with their own stack-specific rules.

Every template should help a user clone or copy a project foundation, then start with an analysis request such as:

Analiza el repo.
Analyze this repository.
Review the project structure.
Inspect the repo and tell me where we are.
What is the current state of this project?

The agent should interpret these as equivalent requests to inspect the repository, read its governance files, understand the current state, and then ask a project-start question such as:

¿Que vamos a construir hoy?
What are we building today?
What should we work on next?

If the repository is already in development, the agent should explain how to adopt the rules without overwriting existing project decisions.

Base Structure

README.md
AGENTS.md
LICENSE
VERSION

docs/
  AI_CONTEXT.md
  AI_SEARCH.md
  AI_TOKEN_BUDGET.md
  CATALOG.md
  CONVENTIONS.md
  NAMING.md
  ROADMAP.md
  WORKFLOWS.md
  SNAPSHOTS.md
  TECHDEBT.md

Reusable project templates live under templates/, grouped by project type. Templates are Pragmatik shells, not complete generated applications. They provide governance, minimal project docs, ignores, and setup context; real application files are created after the user describes what should be built.

Reusable workflow modules should live under presets/. Presets are not full projects; they are reusable layers that templates can adopt.

Shared Standards

All templates in this repository should share:

  • Agent workflow rules.
  • Snapshot rules.
  • Documentation update rules.
  • Git workflow and branch naming.
  • Semantic Versioning for releases.
  • Coherent X.Y.Z project versions.
  • Matching vX.Y.Z git tags for versioned iterations.
  • Version-file updates that match the project stack, such as package.json for React projects.
  • Neutral public metadata without AI tool, agent, or provider names.

Presets

  • lean-context: context-loading, MCP, compression, usage tracking, template/preset recommendation, and GitHub workflow rules for maximizing useful AI quota.

Templates

Documentation Map

GitHub Project

Use pragmatik doctor during repository analysis, then pragmatik setup when tooling or dashboard setup is missing. Use pragmatik run to execute configured AI tools, append aggregate usage summaries, and append optimization observations when enabled. Use pragmatik dashboard for the local Pragmatik dashboard.

The npm package includes the AI-tool backend, so pragmatik run works as soon as Pragmatik is installed. A project-local scripts/ai-tools.sh remains an optional override for templates, hooks, and advanced workflows. Use bash scripts/ai-tools.sh measure-pair when that local script is present to run a matched baseline-vs-lean-context measurement.

Template defaults keep external tools optional. The Pragmatik dashboard and local reports are available by default, while external submission stays in dry-run until the user chooses on. Multi-client measurement is available through AGENTS_TOKSCALE_CLIENTS, with ready defaults for Codex, Cursor, Antigravity, Claude, Gemini, and Warp.

License

This repository is licensed under the MIT License.