open-index/open-npm huggingface dataset:
npm package: @leonardocrdso/clean-code-mcp
Description: MCP server with 63 Clean Code principles — search, browse, and review code against best practices
Author: leonardocrdso
Latest version: 1.1.0

# @leonardocrdso/clean-code-mcp

An MCP (Model Context Protocol) server that provides 63 Clean Code principles for AI-assisted code review and development. Search, browse, and review code against best practices from Robert C. Martin's Clean Code.

## Installation

### Using npx (recommended)

```bash
npx @leonardocrdso/clean-code-mcp
```

### Adding to Claude Code

```bash
claude mcp add clean-code-mcp -- npx @leonardocrdso/clean-code-mcp
```

### Manual configuration

Add to your MCP client settings:

```json
{
  "mcpServers": {
    "clean-code-mcp": {
      "command": "npx",
      "args": ["@leonardocrdso/clean-code-mcp"]
    }
  }
}
```

## Tools

### `search-principle`

Search principles by name, keyword, or ID. Returns detailed results for top matches and a summary for additional matches.

```
query: "srp"
query: "naming"
query: "keep-functions-small"
```

### `search-by-context`

Find relevant principles for a given situation. Describe your problem in natural language.

```
context: "my function has too many parameters and is hard to test"
context: "I have deeply nested if statements"
```

### `list-principles`

List all principles or filter by category.

```
category: "solid"
category: "error-handling"
```

## Resources

- **`cleancode://catalog`** — Full catalog of all 63 principles grouped by category
- **`cleancode://principle/{id}`** — Individual principle by ID

## Prompts

### `clean-code-review`

Generates a structured code review prompt with relevant Clean Code principles embedded as context.

Parameters:
- `code` (required) — The source code to review
- `language` (optional) — Programming language (e.g. `typescript`, `python`)
- `focus_categories` (optional) — Comma-separated categories to focus on

## Categories

13 categories covering 63 principles:

| Category | Description |
|---|---|
| `naming` | Meaningful Names |
| `functions` | Functions |
| `comments` | Comments |
| `formatting` | Formatting |
| `error-handling` | Error Handling |
| `unit-testing` | Unit Testing |
| `classes` | Classes |
| `solid` | SOLID Principles |
| `code-smells` | Code Smells |
| `objects-and-data-structures` | Objects and Data Structures |
| `concurrency` | Concurrency |
| `systems` | Systems |
| `emergence` | Emergence |

## Development

```bash
# Install dependencies
bun install

# Run in development mode
bun run dev

# Build
bun run build
```

## License

MIT
npm package: @leonardodino/firebase-on-rest
Description: Firebase API base on REST
Author: Leonardo Dino
Latest version: 2.0.1

## FirebaseOnRest
- new FirebaseOnRest(uri)
- key()
- root()
- parent()
- toString()
- child(path)
- set(data)
- push(data)
- setAuth(auth) // auth token form generator
- unauth()

## Query
- once(event)
- remove()
- orderByKey()
- orderByChild(path)
- orderByValue()
- limitToFirst(num)
- limitToLast(num)
- startAt(value)
- endAt(value)
- equalTo(value)

## DataSnapshot
- key()
- ref()
- val()
- numChildren()

---
- [Firebase Web Api](https://www.firebase.com/docs/web/api/firebase)
npm package: @leonardodino/gatsby-plugin-page-creator
Description: Gatsby plugin that automatically creates pages from React components in specified directories
Author: Kyle Mathews
Latest version: 0.0.2

# gatsby-plugin-page-creator

Gatsby plugin that automatically creates pages from React components in specified directories. Gatsby
includes this plugin automatically in all sites for creating pages from components in `src/pages`.

With this plugin, _any_ file that lives in the `src/pages` folder (or subfolders) will be expected to export a React Component to generate a Page. The following files are automatically excluded:

- `template-*`
- `__tests__/*`
- `*.test.jsx?`
- `*.spec.jsx?`
- `*.d.tsx?`
- `*.json`
- `*.yaml`
- `_*`
- `.*`

## Install

`npm install --save gatsby-plugin-page-creator`

## How to use

```javascript
// gatsby-config.js

module.exports = {
  plugins: [
    // You can have multiple instances of this plugin
    // to create pages from React components in different directories.
    //
    // The following sets up the pattern of having multiple
    // "pages" directories in your project
    {
      resolve: `gatsby-plugin-page-creator`,
      options: {
        path: `${__dirname}/src/account/pages`,
      },
    },
    {
      resolve: `gatsby-plugin-page-creator`,
      options: {
        path: `${__dirname}/src/settings/pages`,
      },
    },
    // You can also provide "createPath" and "validatePath" functions
    // to override default behaviour, if needed
    {
      resolve: `gatsby-plugin-page-creator`,
      options: {
        path: `${__dirname}/src/articles`,
        createPath: (basePath, filePath) => {
          // Creates a custom URL based on filename
          return `/articles/${slugify(basename(filePath))}/`
        },
        validatePath: (relativePath, isValid) => {
          // Filter page creation based on criteria,
          // the second argument is the default validatePath function
          if (!isValid(relativePath)) return false
          if (basename(relativePath).startsWith("draft-")) return false
          return true
        },
      },
    },
  ],
}
```
npm package: @leonardodino/hello-color
Description: Functional color palette generator
Author: Brent Jackson
Latest version: 1.0.3

# hello-color

Functional color palette generator

http://jxnblk.com/hello-color

[![Build Status](https://travis-ci.org/jxnblk/hello-color.svg?branch=master)](https://travis-ci.org/jxnblk/hello-color)

```sh
npm i hello-color
```

```js
import hello from 'hello-color'

const result = hello('#0fc')
// Returns an object with negated and adjusted color
// that meets a minimum contrast
// {
//   base: '#00ffcc',
//   color: '#f6002d',
//   contrast: 3.2636058745832304,
//   dark: false
// }
```

MIT License
npm package: @leonardodino/netlify-cms
Description: An extensible, open source, Git-based, React CMS for static sites.
Latest version: 2.3.2-alpha.1

# Netlify CMS
[![](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/netlify/netlifycms)

A CMS for static site generators. Give non-technical users a simple way to edit
and add content to any site built with a static site generator.

## How it works

Netlify CMS is a single-page app that you pull into the `/admin` part of your site.

It presents a clean UI for editing content stored in a Git repository.

You setup a YAML config to describe the content model of your site, and typically
tweak the main layout of the CMS a bit to fit your own site.

When a user navigates to `/admin/` they'll be prompted to login, and once authenticated
they'll be able to create new content or edit existing content.

Read more about Netlify CMS [Core Concepts](https://www.netlifycms.org/docs/intro/).

# Installation and Configuration

The Netlify CMS can be used in two different ways.

* A Quick and easy install, that just requires you to create a single HTML file and a configuration file. All the CMS Javascript and CSS are loaded from a CDN.
  To learn more about this installation method, refer to the [Quick Start Guide](https://www.netlifycms.org/docs/quick-start/)
* A complete, more complex install, that gives you more flexibility but requires that you use a static site builder with a build system that supports npm packages.

# Community

Netlify CMS has a [Gitter community](https://gitter.im/netlify/netlifycms) where members of the community hang out and share things about the project, as well as give and receive support.

# Contributing

New contributors are always welcome! Check out [CONTRIBUTING.md](https://github.com/netlify/netlify-cms/blob/master/CONTRIBUTING.md) to get involved.

# Change Log

This project adheres to [Semantic Versioning](http://semver.org/).
Every release is documented on the Github [Releases](https://github.com/netlify/netlify-cms/releases) page.

# License

Netlify CMS is released under the [MIT License](LICENSE).
Please make sure you understand its [implications and guarantees](https://writing.kemitchell.com/2016/09/21/MIT-License-Line-by-Line.html).

# Thanks

## Services
These services support Netlify CMS development by providing free infrastructure.
<p>
  <a href="https://www.travis-ci.org">
    <img src="https://raw.githubusercontent.com/netlify/netlify-cms/master/img/travis.png" height="38"/>
  </a>
  <img src="https://spacergif.org/spacer.gif" width="20"/>
  <a href="https://www.browserstack.com">
    <img src="https://raw.githubusercontent.com/netlify/netlify-cms/master/img/browserstack.png" height="38"/>
  </a>
</p>
npm package: @leonardodino/rifm
Description: Tiny react input formatter and mask
Author: istarkov
Latest version: 0.3.0

# RIFM - React Input Format & Mask

Is a tiny (≈ 650-750b) component to transform any input component
into formatted or masked input.

[Demo](https://istarkov.github.io/rifm/docs-readme)

## Highlights

- Dependency free
- Tiny (≈ 650b)
- Supports any [input](https://istarkov.github.io/rifm/docs-readme#material-ui).
- Can mask input and format

## Example

```javascript
import { Rifm } from 'rifm';
import { Value } from 'react-powerplug';
import TextField from '@material-ui/core/TextField';
import { css } from 'emotion';

const numberFormat = (str: string) => {
  const r = parseInt(str.replace(/[^\d]+/gi, ''), 10);
  return r ? r.toLocaleString('en') : '';
}

...

  <Value initial={''}>
    {text => (
      <Rifm
        value={text.value}
        onChange={text.set}
        format={numberFormat}
      >
        {({ value, onChange }) => (
          <TextField
            value={value}
            label={'Float'}
            onChange={onChange}
            className={css({input: {textAlign:"right"}})}
            type="tel"
          />
        )}
      </Rifm>
    )}
  </Value>

...
```

[Demo](https://istarkov.github.io/rifm/docs-readme)

[Demo source](https://github.com/istarkov/rifm/blob/master/docs/readme.mdx)

## Install

```shell
  yarn add rifm
```

```shell
  npm -i rifm
```

## Thanks

[@TrySound](https://github.com/TrySound) for incredible help and support on this
npm package: @leonardodino/vite-plugin-relay
Description: A vite plugin for relay
Author: Oscar Beaumont
Latest version: 0.0.0-alpha.0

<h1 align="center">Vite Plugin Relay</h1>

[![NPM](https://img.shields.io/npm/v/vite-plugin-relay)](https://www.npmjs.com/package/vite-plugin-relay)
[![CI workflow](https://github.com/oscartbeaumont/vite-plugin-relay/actions/workflows/ci.yml/badge.svg)](https://github.com/oscartbeaumont/vite-plugin-relay/actions)

Add relay support to your [Vite](https://vitejs.dev) projects.

❤️ Special thanks to:

- [@Brendonovich](https://github.com/Brendonovich) for general help
- [@kesne](https://github.com/kesne) for adding [pnpm](https://pnpm.io) support
- [@tobias-tengler](https://github.com/tobias-tengler) for adding Vite 3 support

Created with the help of [@Brendonovich](https://github.com/Brendonovich) and thanks to [@kesne](https://github.com/kesne) for adding [pnpm](https://pnpm.io) support.

## Usage

Follow Relay's guide on [how to add Relay to your project](https://relay.dev/docs/getting-started/installation-and-setup/).

> ⚠️ Note: Install `babel-plugin-relay` (>= 13.0.1) and `graphql` as devDependencies as instructed, but skip the configuration of the babel plugin. `vite-plugin-relay` will invoke it for you!

Add `vite-plugin-relay` to your `devDependencies`:

```bash
yarn add vite-plugin-relay -D
```

Add `vite-plugin-relay` to your Vite configuration (`vite.config.ts` or `vite.config.js`):

```typescript
import { defineConfig } from "vite";
import relay from "vite-plugin-relay";

export default defineConfig({
  plugins: [..., relay],
});
```

Now your project is setup to use Relay with Vite!

## How this plugin works

Under the hood we are inovking the official `babel-plugin-relay`. This ensures that our plugin and `babel-plugin-relay` do not get out of sync over time and also reduces the maintainance costs of this project.

Since v13 `babel-plugin-relay` automatically gets its configuration from either the `package.json`, `relay.config.js` or `relay.config.json`, so our plugin also doesn't have to expose a configuration API.

## Common Issues

### `Uncaught ReferenceError: global is not defined`

If you experience this error in your browser console when using the plugin add the following define to your `index.html` file before importing your Javascript:

```html
<script>
  let global = globalThis;
</script>
```

## Server Side Rendering

If you are planning to use this plugin with server side rendering you may need to define `window`. You could do this by putting the following snippet in your [`entry-server.js`](https://vitejs.dev/guide/ssr.html#source-structure) file.

```js
if (typeof (window as any).global === 'undefined') {
  (window as any).global = globalThis;
}
```
npm package: @leonardoferri/angular-design-system
Description: Design System Angular by Leonardo Ferri
Author: Leonardo Ferri
Latest version: 0.0.43

# AngularDesignSystem

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 18.2.0.

## Code scaffolding

Run `ng generate component component-name --project angular-design-system` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project angular-design-system`.
> Note: Don't forget to add `--project angular-design-system` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build angular-design-system` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build angular-design-system`, go to the dist folder `cd dist/angular-design-system` and run `npm publish`.

## Running unit tests

Run `ng test angular-design-system` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.