# get-started-stinger

The get-started-stinger skill brings a new or incomplete repository to a documented baseline with CI and project-health files. Use it during first-session setup or when wasp-nest.lock is missing.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 96 repo stars
- Author: Legion Code Inc.
- License: AGPL-3.0-or-later · policy=link-only · description only; the file stays with the author
- Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/wasp-nest-core/skills/get-started-stinger/SKILL.md
- Updated: 2026-10-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/get-started-stinger

## What it does

get-started-stinger inspects the repository root, then copies setup files in dependency order. Its templates cover `.gitignore`, `.editorconfig`, `.nvmrc`, `.env.example`, `.github/` workflows and templates, `README.md`, contributor and security files, a changelog, and `library/`. Placeholder values such as `{placeholder}` are resolved from repository signals like `package.json`, the git remote, `LICENSE`, and the lockfile.

The skill is safe to rerun. Missing files are created, matching files remain untouched, and differences are reported rather than overwritten. Each run ends with a report of existing files, files created during the run, and decisions that require a repository owner. It does not change GitHub Settings such as branch protection, push protection, CodeQL, or license selection. For repositories that already contain code, `knowledge-stinger` runs before `wasp-nest.lock` is written.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add legioncodeinc/vibe-coding-tools
```
In the agent chat (not a shell):
```text
/plugin install wasp-nest-core@wasp-nest
```
This installs the whole wasp-nest-core plugin with all its skills

2. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill get-started-stinger -a claude-code
```

3. **Manually: put the files in place**
- File: `~/.claude/skills/get-started-stinger/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/get-started-stinger/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill get-started-stinger -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/get-started-stinger/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill get-started-stinger -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/get-started-stinger/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install legioncodeinc/vibe-coding-tools plugins/wasp-nest-core/skills/get-started-stinger
```

2. **Manually: put the files in place**
- File: `.github/skills/get-started-stinger/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill get-started-stinger -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/wasp-nest-core/skills/get-started-stinger
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/get-started-stinger/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/wasp-nest-core/skills/get-started-stinger/SKILL.md

## When to use it
- bootstrap a new repository before feature work
- add starter GitHub CI and repository templates
- create baseline security and maintenance files
- report drift during repeated setup runs
- summarize files created in the current run

## Example prompts
- Set up this new repository with the starter baseline and report every file you create.
- Add the missing CI and repository-health files, but leave existing hand-edited files untouched.
- Run the repository checks, then create `wasp-nest.lock` only after the setup passes.

## Similar
- [repo-standardizer](https://affpapa.org/en/nevibecode/skills/repo-standardizer.md) — skill · 33 installs
- [sentry-get-started](https://affpapa.org/en/nevibecode/skills/sentry-get-started.md) — skill · 874 installs
- [agents-get-started](https://affpapa.org/en/nevibecode/skills/agents-get-started.md) — skill · 2100 installs
- [nemo-relay-get-started](https://affpapa.org/en/nevibecode/skills/nemo-relay-get-started.md) — skill · 163 installs
- [google-mobile-ads-get-started](https://affpapa.org/en/nevibecode/skills/google-mobile-ads-get-started.md) — skill · 5855 installs
- [help-me-get-started](https://affpapa.org/en/nevibecode/skills/help-me-get-started.md) — skill · ★ 1104 repo stars

From the same set: [legioncodeinc/vibe-coding-tools](https://affpapa.org/en/nevibecode/by/legioncodeinc/vibe-coding-tools.md) — 172 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
