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

@outsourced-br/sharp-pragma-skills

v3.0.6

Published

Pragmatic .NET review skill pack for agentic development

Readme

SharpPragma Skills

SharpPragma Skills is a pragmatic .NET review skill pack for agentic development with Codex, Antigravity, Claude Code, Gemini, and similar tools.

The pack focuses on Clean Architecture where useful, clean code, SOLID, DRY, YAGNI, KISS, repository hygiene, build conventions, NuGet dependency health, analyzer policy, testing, security hygiene, performance review, and allocation review.

It is intentionally DDD-neutral. It does not prescribe aggregates, repositories, domain events, shared kernels, or DDD project naming. Existing repositories may use names such as Domain, but these skills must not introduce DDD vocabulary or structure merely because the codebase is being reviewed.

Package version

Current package version: 3.0.6.

Individual skills may keep their own internal versions, but the package-level version is the source of truth for distribution.

Skills

| Order | Skill | Purpose | |---:|---|---| | 0 | sharp-full-solution-review | Optional orchestrator that runs the review lenses below in order. | | 1 | sharp-solution-audit | Solution audit. | | 2 | sharp-repo-structure | Repository structure review. | | 3 | sharp-build-conventions | Build conventions review. | | 4 | sharp-nuget-dependency-review | NuGet and dependency review. | | 5 | sharp-analyzer-policy-review | Analyzer policy review. | | 6 | sharp-architecture-pragmatic | Pragmatic architecture review. | | 7 | sharp-code-quality-review | Code quality review. | | 8 | sharp-design-principles-review | Design principles review. | | 9 | sharp-solid-deep-review | SOLID deep review. | | 10 | sharp-composition-over-inheritance | Composition over inheritance review. | | 11 | sharp-performance-review | Performance review. | | 12 | sharp-allocation-review | Allocation review. | | 13 | sharp-test-review | Test review. | | 14 | sharp-security-hygiene | Security hygiene review. | | 15 | sharp-code-review-reporting | Code review reporting. |

Routing model

There is one safe routing model:

  1. Start with sharp-full-solution-review when doing a broad review.
  2. The orchestrator calls review lenses in a directed, acyclic workflow.
  3. Companion skills are non-recursive references, not automatic routing instructions.
  4. Each skill may read upstream findings and hand off downstream findings, but it must not loop backward or re-run unrelated skills.

See:

  • docs/review-workflow.md
  • docs/companion-skills-graph.md
  • docs/shared-guardrails.md

Default review command for agents

Use sharp-full-solution-review. Review the repository using the workflow in docs/review-workflow.md. Produce findings using docs/severity-and-reporting-model.md. Do not introduce DDD terminology. Do not recommend performance or allocation rewrites without evidence.

Installation

The easiest way to install all skills into the current repository or folder is via npx:

npx @outsourced-br/sharp-pragma-skills@latest install

To install into a specific repository or folder from anywhere:

npx @outsourced-br/sharp-pragma-skills@latest install C:/git/draftbench

The repository/folder install writes the skills into local agent skill directories: .agents/skills, .codex/skills, .gemini/skills, and .claude/skills.

Use --target <path> only when you want to copy directly into one exact skills directory, for example .codex/skills. Use --profile only when you explicitly want a user-profile install.

See docs/installing-skills.md for alternative manual installation scripts. The npm package includes the docs and scripts referenced below; the same files are available in the GitHub repository.

Codex and other frontmatter-based loaders can consume the repository root sharp-* folders directly or copy them into their configured skills directory.

Codex:

bash scripts/install-codex-skills.sh

PowerShell:

pwsh ./scripts/install-codex-skills.ps1

Gemini:

bash scripts/install-gemini-skills.sh

PowerShell:

pwsh ./scripts/install-gemini-skills.ps1 -Copy

Claude Code:

bash scripts/install-claude-skills.sh

PowerShell:

pwsh ./scripts/install-claude-skills.ps1 -Copy

Eval runner:

bash scripts/run-evals.sh

PowerShell:

pwsh ./scripts/run-evals.ps1

Operating principles

  • Prefer simple corrections over architectural theatre.
  • Treat unsupported frameworks, vulnerable dependencies, leaking secrets, and broken test/build flows as serious.
  • Treat style disagreements and speculative abstractions as lower severity unless they create real delivery risk.
  • Never prescribe interfaces, layers, inheritance, analyzers, caching, Span<T>, ArrayPool<T>, ValueTask, or pooling without a concrete reason.
  • When evidence is missing, ask for evidence or produce a safe measurement plan rather than guessing.

License and citation

SharpPragma Skills is licensed under the GNU Affero General Public License v3.0 only. See LICENSE.

Citation metadata is available in CITATION.cff.