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

nimis

v1.1.0

Published

Agentic skills framework for AI coding agents — orchestrated workflows with adaptive routing, quality gates, and 17 composable skills.

Downloads

21

Readme


Nimis is a complete software development workflow for your coding agents, built on top of a set of composable skills. It doesn't just write code — it steps back, understands what you're building, plans the work, breaks it into slices, and executes each slice with built-in quality gates. And because the skills trigger automatically, you don't need to do anything special. Your coding agent just has Nimis.

How it works

It starts from the moment you give your agent a task. The orchestrator skill activates and:

  1. Senses context — Detects project type (new project, new feature, bug fix, or refactoring) via project-context
  2. Scores difficulty — Rates the task 1-10 via task-difficulty, selecting a variant (lite / standard / plus)
  3. Clarifies requirements — For ambiguous or complex tasks, uses requirement-qa and brainstorm to nail down scope before coding
  4. Slices scope — Breaks large tasks into ordered slices (by module dependency), each independently deliverable
  5. Routes — Picks one of four routes (A: new project, B: new feature, C: bug fix, D: refactoring) with route-specific skill chains
  6. Executes per slice — Each slice goes through Plan → Execute → Validate → Deliver with quality gates at each transition

If validation fails, work reflows to the right level — code-level issues go back to Execute, design-level back to Plan, requirement-level back to scope. No blind retries.

The Workflow

User Request
    │
    ▼
  Context Sensing → Difficulty Scoring → Clarify (if needed) → Scope Slicing
    │
    ▼
  ┌──────────────────────────────────┐
  │  Per-Slice Loop                  │
  │                                  │
  │  Route Selection (A/B/C/D)      │
  │       │                          │
  │       ▼                          │
  │  Plan ──── Gate ──── Execute     │
  │                        │         │
  │                      Gate        │
  │                        │         │
  │                    Validate      │
  │                        │         │
  │                    Deliver       │
  └──────────────────────────────────┘
    │
    ▼
  Done (or next slice)

Three Variants

| Difficulty | Variant | What changes | |-----------|---------|-------------| | L1-L2 (easy) | lite | Skip optional skills, quick self-review, no mandatory TDD | | L3 (medium) | standard | Full skill chain, mandatory TDD, standard review | | L4-L5 (hard) | plus | SubAgent isolation per task, strict TDD, two-stage review, parallel strategy |

What's Inside

Skills Library

Orchestration

  • orchestrator — Full-lifecycle flow orchestrator (routes, quality gates, reflow, slice iteration)

Requirements & Design

  • requirement-qa — Multi-round Q&A to elicit and refine requirements
  • brainstorm — Multi-perspective brainstorming with expert SubAgents
  • spec-writing — Structured feature specification documents
  • tech-stack — Full-stack technology selection & decision docs

Architecture & Engineering

  • engineering-principles — Context-aware principles matcher (SOLID, DDD, TDD, design patterns)
  • api-contract-design — RESTful/GraphQL API contracts, DTOs, OpenAPI specs
  • error-handling-strategy — Exception hierarchy, error codes, retry, circuit-breaker, fallback
  • performance-arch-design — Cache layering, async processing, indexing, rate limiting
  • observability-design — Distributed tracing, structured logging, metrics, alerting

Implementation

  • code-scaffold — Project scaffolding from domain model + design docs
  • implementation-complexity-analysis — Technical risk identification, complexity decomposition
  • integration-test-design — TestContainers, contract testing, mock strategy

Meta

  • task-difficulty — Multi-dimensional difficulty scoring (1-10)
  • project-context — Project structure awareness & cross-session persistence
  • docs-output — Document output management (modular docs/ organization)

Installation

Via npm

# Install all skills + all agent configs (Chinese, default)
npx nimis@latest init

# Install English skills
npx nimis@latest init --lang en

# Install for a specific editor only
npx nimis@latest init --agent cursor
npx nimis@latest init --agent trae
npx nimis@latest init --agent windsurf

# Only copy skills, skip agent config files
npx nimis@latest init --skills-only

# Overwrite existing files
npx nimis@latest init --force

# List all available skills
npx nimis@latest list

Available agents: claude, copilot, cursor, windsurf, cline, trae, codebuddy, codex, gemini, all (default).

Conflict handling: Existing files are preserved by default. Nimis adds its config alongside your existing rules. Use --force to overwrite.

Skills location: When targeting a single directory-based editor (e.g., --agent trae), skills are installed inside the editor directory (e.g., .trae/skills/). With --agent all (default), skills go to the project root skills/.

Via skills.sh

# Install to a specific editor (recommended)
npx skills add YuluoY/nimis --skill '*' -a cursor -y
npx skills add YuluoY/nimis --skill '*' -a trae -y
npx skills add YuluoY/nimis --skill '*' -a claude-code -y

# Install to multiple editors
npx skills add YuluoY/nimis --skill '*' -a cursor -a windsurf -y

# Install to ALL editors (installs many agent directories)
npx skills add YuluoY/nimis --all

# Interactive: select skills and editors
npx skills add YuluoY/nimis

# List available skills
npx skills add YuluoY/nimis --list

Agent names for skills.sh: claude-code, github-copilot, cursor, windsurf, cline, trae, codebuddy, codex, gemini-cli.

Note: skills.sh does not support --lang. For English skills, use npx nimis@latest init --lang en.

Per-Agent Manual Installation

Nimis ships with CLAUDE.md at the project root — Claude Code reads this automatically.

git clone https://github.com/YuluoY/nimis.git

Nimis ships with .github/copilot-instructions.md pre-configured.

git clone https://github.com/YuluoY/nimis.git

Nimis ships with .cursor/rules/nimis.mdc (alwaysApply: true) for auto-discovery.

git clone https://github.com/YuluoY/nimis.git

Nimis ships with .windsurf/rules/nimis.md (trigger: always_on) for auto-discovery.

git clone https://github.com/YuluoY/nimis.git

Nimis ships with .clinerules/nimis.md for auto-discovery.

git clone https://github.com/YuluoY/nimis.git

Nimis ships with .trae/rules/nimis.md for auto-discovery.

git clone https://github.com/YuluoY/nimis.git

Nimis ships with .codebuddy/rules/nimis/RULE.mdc (alwaysApply: true) for auto-discovery.

git clone https://github.com/YuluoY/nimis.git

Nimis ships with AGENTS.md at the project root — Codex reads this automatically.

git clone https://github.com/YuluoY/nimis.git

Nimis ships with GEMINI.md at the project root — Gemini CLI reads this automatically.

git clone https://github.com/YuluoY/nimis.git

Project Structure

nimis/
├── skills/                            # Skills (Chinese)
│   ├── orchestrator/                # Flow orchestrator
│   │   ├── SKILL.md                # Orchestrator logic
│   │   └── references/             # Methodology docs
│   ├── brainstorm/
│   ├── spec-writing/
│   ├── code-scaffold/
│   ├── ...                          # 16 skills total
│   └── docs-output/
├── skills-en/                         # Skills (English)
├── CLAUDE.md                        # Claude Code
├── AGENTS.md                        # Codex / cross-agent compat
├── GEMINI.md                        # Gemini CLI
├── .github/copilot-instructions.md    # VS Code Copilot
├── .cursor/rules/nimis.mdc        # Cursor
├── .windsurf/rules/nimis.md       # Windsurf
├── .clinerules/nimis.md           # Cline
├── .trae/rules/nimis.md           # Trae
├── .codebuddy/rules/nimis/RULE.mdc  # CodeBuddy
├── README.md
├── README_CN.md
├── CONTRIBUTING.md
├── LICENSE
└── package.json

Philosophy

Core Principles

Document-Driven Development — Specs precede code. Every feature starts as a structured document (specs/), becoming the single source of truth for requirements, tech decisions, and API contracts. Code implements specs; specs don't retroactively describe code.

Full Traceability — Every technical decision records why it was chosen and what alternatives were considered. Progress is persistently tracked (docs/). Cross-session context is preserved in SQLite. Nothing relies on memory alone.

Counter AI Cognitive Weaknesses — AI agents systematically underestimate complexity, skip validation, lose context across sessions, and forget plans. Nimis's mechanisms directly target these weaknesses: path lock prevents skipping, difficulty throttle counters underestimation, file persistence defeats context loss, mechanical reconciliation catches omissions.

Human Authority, Machine Execution — The system provides defaults and recommendations, but humans have unconditional override. Tech choices are recommended, not mandatory. Difficulty scores can be overridden with natural language. AI executes the workflow; humans own the decisions.

Adaptive Overhead — Process weight must match problem weight. Simple tasks (lite) skip optional skills for speed. Medium tasks (standard) get the full chain. Hard tasks (plus) add extra review stages and parallel strategies. No one-size-fits-all.

Design Mechanisms

  • Path Lock — Route flowcharts are mandatory execution paths, not references. Every node runs in arrow order, no skipping.
  • Throttle Valve — Built-in upward bias in difficulty scoring. AI tends to underestimate, so scores nudge up unless clearly trivial.
  • Persist Then Forget — Each skill writes output to files. Subsequent steps read from files, not from context window. Counters attention decay.
  • Precision Reflow — Validation failures route back to the exact broken level (code → Execute, design → Plan, requirement → scope), not full restart.
  • Mechanical Reconciliation — Delivery compares Plan checklist vs. actual files. Trust the filesystem, not the model's recall.
  • Recommended ≠ Mandatory — Tech reference tables have defaults, but any technology is valid if the reasoning is documented.

Contributing

See CONTRIBUTING.md. Skills live directly in this repository.

License

MIT © Nimis Contributors