open-index/open-npm huggingface dataset:
npm package: @kylewadegrove/shiftydig-cli-staging
Description: First-class Shiftydig CLI with dedicated onboarding and MCP config, powered by Cutline components.
Latest version: 0.2.0

# Shiftydig CLI

`shiftydig` is a first-class CLI for Shiftydig with dedicated onboarding and MCP config, while reusing Cutline's auth/runtime components under the hood.

## Install

```bash
npm i -g @vibekiln/shiftydig-cli
```

For staging:

```bash
npm i -g @kylewadegrove/shiftydig-cli-staging
```

## Commands

- `shiftydig setup [--staging]`  
  Writes MCP config entries for only the `shiftydig` server, saves channel preference in `~/.shiftydig/config.json`, and installs `.cursor/rules/shiftydig-intents.mdc` so natural-language prompts route to Shiftydig MCP tools.
- `shiftydig login [--staging]`
- `shiftydig status [--staging]`
- `shiftydig logout [--staging]`
- `shiftydig serve [--staging] [--http --host --port --path]`
- `shiftydig bootstrap` (prints recommended first-run MCP tool sequence)
- `shiftydig event <level-up|game-over>` (renders local terminal banners)

## How it works

- `setup` writes `shiftydig` MCP entries separately from `cutline-*` entries.
- `serve` delegates to Cutline MCP components via:
  - production: `@vibekiln/cutline-mcp-cli`
  - staging: `@kylewadegrove/cutline-mcp-cli-staging`

This keeps Shiftydig onboarding/config independent while still leveraging shared Cutline internals.

## Natural-language start prompts

After `shiftydig setup`, you can say these directly in your AI chat:

- `start shiftydig and create my first run`
- `take a turn in shiftydig for this feature idea`
- `roll tests as the dungeon check for my run`
- `show my spellbook and equip the best offered spell`
npm package: @kylewadegrove/slopburn-cli-staging
Description: First-class SlopBurn CLI with dedicated onboarding and MCP config, powered by Cutline components.
Latest version: 0.2.1

# SlopBurn CLI

`slopburn` is a first-class CLI for SlopBurn with dedicated onboarding and MCP config, while reusing Cutline's auth/runtime components under the hood.

## Install

```bash
npm i -g @vibekiln/slopburn-cli
```

For staging:

```bash
npm i -g @kylewadegrove/slopburn-cli-staging
```

## Commands

- `slopburn setup [--staging]`  
  Writes MCP config entries for only the `slopburn` server, saves channel preference in `~/.slopburn/config.json`, and installs `.cursor/rules/slopburn-intents.mdc` so natural-language prompts route to SlopBurn MCP tools.
- `slopburn login [--staging]`
- `slopburn status [--staging]`
- `slopburn logout [--staging]`
- `slopburn serve [--staging] [--http --host --port --path]`
- `slopburn bootstrap` (prints recommended first-run MCP tool sequence)
- `slopburn event <level-up|game-over>` (renders local terminal banners)

## How it works

- `setup` writes `slopburn` MCP entries separately from `cutline-*` entries.
- `serve` delegates to Cutline MCP components via:
  - production: `@vibekiln/cutline-mcp-cli`
  - staging: `@kylewadegrove/cutline-mcp-cli-staging`

This keeps SlopBurn onboarding/config independent while still leveraging shared Cutline internals.

## Natural-language start prompts

After `slopburn setup`, you can say these directly in your AI chat:

- `start slopburn and create my first run`
- `take a turn in slopburn for this feature idea`
- `roll tests as the dungeon check for my run`
- `show my spellbook and equip the best offered spell`