open-index/open-npm huggingface dataset:
npm package: @redradix/design-system
Description: Design system for redradix's projects
Author: redradix
Latest version: 0.0.8

# @redradix/design-system

## Install

```bash
npm i -D @redradix/design-system
```

or

```bash
yarn add -D @redradix/design-system
```

## Usage

Create a `.design-system` directory with an `index.js` file in it.

Its content of the `index.js` should be similar to this:

```jsx
import React from "react";
import ReactDOM from "react-dom";
import DesignSystem from "@redradix/design-system";

const config = {
  logoSrc: "https://example-image.com/1.png",
  faviconSrc: "https://example-image.com/favicon.ico",
  projectName: "Example",
  keyResources: {
    repoUrl: "https://example-repo.com",
    designUrl: "https://example-design.com"
  }
};

ReactDOM.render(
  <DesignSystem {...{ config }} />,
  document.getElementById("root")
);
```

To easily run it and build it add the following scripts to your `package.json`:

```
  "design-system": "redradix-design-system start",
  "build-design-system": "redradix-design-system build",
```

### Props

- config
  - logoSrc: `string`
  - projectName: `string`
  - repoUrl: `string`
  - designUrl: `string`
  
### Styles overrides

The css variables are in [`src/styles/globals/_settings.scss`](https://bitbucket.org/redradix/components-library-storybook/src/master/src/styles/globals/_settings.scss)

## Development

Run the app in the `example` directory which has a link to the package in the package.json so it can require and use it.
The problem is that package links (in this case yarn links) do not require `peerDependencies` so the `example` app will throw an error that `@redradix/design-system` can't require react.

So in the root run `npm link ../example/node_modules/{react,react-dom}` so it uses `example`'s react packages.

Then, run `yarn start` in the root directory to build the package in watch mode.

And finally, as with other cra project, go inside the `example` directory and run `yarn run design-system` which will serve the design system in the port 3000.
Maybe you need to add `SKIP_PREFLIGHT_CHECK=true` before the command if it yells at you.

**Important note**

The `redradix-design-system` binaries are a fork of `react-scripts` located in the `cra` dir.

In case it needs to be updated in the future, the only differences with the original are located in the `paths` file (`cra/packages/react-scripts/config/paths`):

- appBuild
- appIndexJs
- appDesignSystem (all old references to appSrc must be an array containing appSrc and this appDesignSystem)
- ownPackageJson

Steps to update `react-scrips`:

1. Clone `facebook/create-react-app` into `cra2` for example
2. Point `package.json` bin to the updated dir
3. Change the above paths so they work with out approach
4. When working remove cra and rename cra2 to cra

## Deployment (npm publishing)

In the root dir:

- Bump `package.json` version by running `npm version {major|minor|patch}` according to semver.

- Run `npm publish`.

# Future improvements

Nothing to do, it's perfect.

## License

MIT � [redradix](https://github.com/redradix)
npm package: @redredchen01/code-quality
Description: Code quality analysis CLI tool — lint, format, complexity, coverage
Latest version: 1.0.0

# @redredchen01/code-quality

CLI toolkit for code quality analysis — lint, format, complexity, duplication, and test coverage.

## Install

```bash
npm install -g @redredchen01/code-quality
```

## Usage

```bash
code-quality lint
code-quality format --check
code-quality complexity --threshold 5
code-quality duplication --min-lines 10
code-quality coverage
code-quality report
code-quality fix --dry-run
```

See `code-quality --help` or `code-quality <command> --help` for full options.

## Supported Languages

| Language | lint | format | complexity | fix |
|----------|------|--------|------------|-----|
| JS / TS  | eslint | prettier | eslint (complexity rule) | eslint --fix |
| Python   | pylint | black | radon cc | autopep8 |
| Shell    | shellcheck | shfmt | built-in heuristic | shfmt -w |

Duplication (`jscpd`) and coverage (lcov / JSON) are language-agnostic.
npm package: @redredchen01/dep-audit
Description: CLI toolkit for npm dependency auditing — outdated, vulnerabilities, licenses, updates
Latest version: 1.0.0

# @foundry/dep-audit

> CLI toolkit for npm dependency auditing — outdated, vulnerabilities, licenses, updates

[![npm version](https://img.shields.io/npm/v/@foundry/dep-audit.svg)](https://www.npmjs.com/package/@foundry/dep-audit)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## Install

```bash
npm install -g @foundry/dep-audit
```

## Quick Start

```bash
dep-audit outdated              # check for updates
dep-audit vulnerabilities       # security scan
dep-audit licenses --prod       # license compliance
dep-audit tree --depth 1        # dependency tree
dep-audit why lodash            # why is it installed?
```

## Commands

| Command | Description |
|---------|-------------|
| `outdated` | Outdated deps with severity coloring |
| `vulnerabilities` | Security vulnerability scan |
| `licenses` | License compliance check |
| `update` | Safe dependency updates (dry-run default) |
| `tree` | Dependency tree visualization |
| `why` | Dependency chain explanation |

## License

MIT
npm package: @redredchen01/docker-mgmt
Description: CLI toolkit for Docker container/image lifecycle management
Latest version: 1.0.0

# @foundry/docker-mgmt

> CLI toolkit for Docker container/image lifecycle management

[![npm version](https://img.shields.io/npm/v/@foundry/docker-mgmt.svg)](https://www.npmjs.com/package/@foundry/docker-mgmt)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## Install

```bash
npm install -g @foundry/docker-mgmt
```

## Quick Start

```bash
docker-mgmt ps                    # what's running?
docker-mgmt build -t myapp        # build image
docker-mgmt run myapp -p 8080:80  # run container
docker-mgmt logs myapp -f         # follow logs
docker-mgmt clean                 # see reclaimable space
docker-mgmt compose up            # start compose stack
```

## Commands

| Command | Description |
|---------|-------------|
| `ps` | List containers with readable status overview |
| `build` | Build image (auto-detect Dockerfile, auto-tag) |
| `run` | Run container with sensible defaults |
| `stop` | Stop containers by name/ID or --all |
| `logs` | View logs with tail, follow, since |
| `clean` | Clean Docker resources (dry-run default) |
| `compose` | Docker Compose shortcuts (up/down/restart/status/rebuild) |

## As Claude Skill

> "What Docker containers are running?"
> "Build the Dockerfile in this directory"
> "Clean up Docker and free disk space"
> "Start my docker-compose services"

## License

MIT
npm package: @redredchen01/env-manager
Description: CLI toolkit for .env file management — diff, validate, sync, encrypt/decrypt
Latest version: 1.0.0

# @foundry/env-manager

> CLI toolkit for .env file management — diff, validate, sync, encrypt/decrypt

[![npm version](https://img.shields.io/npm/v/@foundry/env-manager.svg)](https://www.npmjs.com/package/@foundry/env-manager)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## Install

```bash
npm install -g @foundry/env-manager
```

## Quick Start

```bash
env-manager show                    # view vars (secrets masked)
env-manager validate                # check for missing vars
env-manager diff .env .env.prod     # compare environments
env-manager sync                    # update .env.example
env-manager encrypt                 # encrypt .env → .env.enc
```

## Commands

| Command | Description |
|---------|-------------|
| `show` | Display .env with secret masking |
| `diff` | Compare two .env files |
| `validate` | Check against .env.example |
| `sync` | Generate .env.example from .env |
| `encrypt` | Encrypt .env (AES-256-CBC) |
| `decrypt` | Decrypt .env.enc |
| `init` | Create .env from template |

## As Claude Skill

> "Show me the env vars in this project"
> "Am I missing any environment variables?"
> "What's different between staging and production env?"
> "Encrypt the .env file for safe storage"

## License

MIT
npm package: @redredchen01/foundry-cli
Description: Unified CLI entry point for Skill Foundry — developer toolkit
Author: redredchen01
Latest version: 1.2.0

# @redredchen01/foundry-cli

> Unified CLI entry point for Skill Foundry v2 — developer toolkit

[![npm version](https://img.shields.io/npm/v/@redredchen01/foundry-cli.svg)](https://www.npmjs.com/package/@redredchen01/foundry-cli)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## Install

```bash
npm install -g @redredchen01/foundry-cli
```

## Quick Start

```bash
foundry list                         # list all installed skills
foundry help                         # show full help
foundry version                      # show version
foundry dep-audit outdated           # dispatch to dep-audit skill
foundry git-workflow branches        # dispatch to git-workflow skill
```

## Commands

| Command | Description |
|---------|-------------|
| `list` | List installed skills with versions and command counts |
| `version` | Show Foundry CLI version |
| `help` | Show help with all discovered skills |
| `<skill> <command>` | Dispatch to a specific skill's command |

## Plugin Discovery

Skills are discovered by scanning sibling packages for a `SKILL.md` marker file. No manual registration is needed — install a new skill package and `foundry` detects it automatically.

## Options

| Option | Description |
|--------|-------------|
| `--json` | JSON output (pipe protocol) |
| `--verbose` | Verbose logging |
| `--quiet` | Suppress info messages |

## Architecture

`foundry-cli` is the top-level dispatcher in Skill Foundry v2. It:

1. Scans `../*/SKILL.md` for installed skills (excluding `cli-core` and `foundry-cli` itself)
2. Routes `foundry <skill> <args>` to `../<skill>/bin/<skill>.sh`
3. Built-in commands (`list`, `version`, `help`) are handled directly

## License

MIT
npm package: @redredchen01/foundry-dashboard
Description: Local web dashboard for Skill Foundry — monitor and execute all CLI skills from browser
Author: redredchen01
Latest version: 1.0.0

# @redredchen01/foundry-dashboard

Local web dashboard for Skill Foundry — monitor, browse, and execute all 103 CLI commands from your browser.

## Quick Start

```bash
# Via foundry CLI
foundry dashboard

# Or directly
npx @redredchen01/foundry-dashboard

# Custom port
foundry dashboard --port 8080
```

Then open http://localhost:3170 in your browser.

## Features

- **Skill Grid**: Visual overview of all 15+ installed skills with version and command count
- **Command Browser**: Click a skill to see all commands with descriptions
- **One-Click Execute**: Run any command with arguments from the browser
- **Output Display**: Monospace terminal-style output with JSON highlighting
- **Activity Log**: Recent command history with timestamps and status
- **Auto-Refresh**: Skills status updates every 30 seconds
- **Dark Theme**: Professional dark UI with responsive layout
- **Zero Dependencies**: Pure Node.js HTTP server, no npm dependencies

## API

The dashboard exposes a REST API:

| Endpoint | Method | Description |
|----------|--------|-------------|
| `/api/skills` | GET | List all skills and commands (JSON) |
| `/api/skill/:name` | GET | Detailed info for one skill |
| `/api/run` | POST | Execute a command: `{"skill":"...","command":"...","args":"..."}` |
| `/api/health` | GET | Server health check |

## Screenshots

Open http://localhost:3170 after starting the server to see the dashboard.
npm package: @redredchen01/foundry-mcp
Description: MCP server for Skill Foundry — exposes 103 CLI commands as AI agent tools
Author: redredchen01
Latest version: 1.0.0

# @redredchen01/foundry-mcp

MCP (Model Context Protocol) server for Skill Foundry — exposes 103 CLI commands as AI agent tools.

## Setup

### Claude Desktop / Claude Code

Add to your MCP config (`~/.claude/claude_desktop_config.json`):

```json
{
  "mcpServers": {
    "foundry": {
      "command": "npx",
      "args": ["@redredchen01/foundry-mcp"]
    }
  }
}
```

### Cursor

Add to `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "foundry": {
      "command": "npx",
      "args": ["@redredchen01/foundry-mcp"]
    }
  }
}
```

## Available Tools

The server automatically discovers all installed Foundry skills and exposes each command as an MCP tool.

Tool naming convention: `foundry_{skill}_{command}`

Examples:
- `foundry_dep_audit_vulnerabilities` — Scan npm vulnerabilities
- `foundry_db_tools_migrate` — Run database migrations
- `foundry_monitoring_tools_healthcheck` — HTTP health check
- `foundry_secret_mgmt_generate` — Generate random secrets
- `foundry_k8s_tools_pods` — List Kubernetes pods

### Meta Tools
- `foundry_list` — List all installed skills
- `foundry_agent_info` — Get machine-readable schema for all tools

## Agent Mode

When invoked via MCP, all commands automatically run in agent mode:
- JSON output (no human-readable text)
- Structured error codes (E1-E7)
- No ANSI colors
npm package: @redredchen01/git-workflow
Description: CLI toolkit for git branch management, rebasing, cherry-picking, and workflow automation
Latest version: 1.0.0

# @foundry/git-workflow

> CLI toolkit for git branch management, rebasing, cherry-picking, and workflow automation

[![npm version](https://img.shields.io/npm/v/@foundry/git-workflow.svg)](https://www.npmjs.com/package/@foundry/git-workflow)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## Install

### CLI Tool

```bash
npm install -g @foundry/git-workflow
```

### Claude Code Skill

Download `.skill` file from [GitHub Releases](https://github.com/redredchen01/skill-foundry/releases):

```bash
claude skill install git-workflow.skill
```

## Quick Start

```bash
git-workflow --help
git-workflow branches
git-workflow clean --dry-run
git-workflow log --graph
```

## Commands

| Command | Description |
|---------|-------------|
| `branches` | List branches with status markers (current, merged, stale) |
| `clean` | Delete merged/stale branches safely (dry-run by default) |
| `rebase` | Guided interactive rebase with commit preview |
| `pick` | Cherry-pick commits with conflict guidance |
| `merge-check` | Check if branches can merge without conflicts |
| `stash` | Manage stash entries (list, save, pop, drop, show) |
| `log` | Pretty-formatted git log with graph support |

## As Claude Skill

After installing, use natural language in Claude Code:

> "Show me all my branches and which ones are merged"
> "Clean up old branches that are already merged"
> "I want to rebase my last 5 commits"
> "Can I merge feature/login into main without conflicts?"
> "Stash my current changes"

## License

MIT
npm package: @redredchen01/project-init
Description: Project scaffolding and initialization CLI tool
Latest version: 1.0.0

# @redredchen01/project-init

> Project scaffolding and initialization CLI tool

[![npm version](https://img.shields.io/npm/v/@redredchen01/project-init.svg)](https://www.npmjs.com/package/@redredchen01/project-init)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## Install

```bash
npm install -g @redredchen01/project-init
```

## Quick Start

```bash
project-init init --type node --name my-app   # scaffold new node project
project-init config                            # generate config files
project-init readme                            # create README.md
project-init license                           # create MIT LICENSE
project-init gitsetup                          # init git + initial commit
project-init deps                              # install dev dependencies
project-init check                             # verify project structure
```

## Commands

| Command | Description |
|---------|-------------|
| `init` | Scaffold new project from template (node, python, shell) |
| `config` | Generate .editorconfig, .gitignore, .nvmrc, .prettierrc |
| `readme` | Generate README.md with standard sections |
| `license` | Generate LICENSE (MIT, Apache-2.0, GPL-3.0) |
| `gitsetup` | Initialize git repo and make initial commit |
| `deps` | Install recommended dev dependencies |
| `check` | Verify project structure and required files |

## License

MIT