# vibe-coding

vibe-coding sets how a coding agent behaves on a codebase: read before editing, match verification to the risk, lead the write-up with the outcome.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 1 install · ★ 321 repo stars
- Author: shareAI-lab
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/shareAI-lab/lab-skills/tree/HEAD/software-engineering/vibe-coding/SKILL.md
- Updated: 2026-09-16
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/vibe-coding

## What it does

The skill changes how the agent behaves on a codebase rather than adding tools to it. It starts with the repo's own instructions and the surrounding code, works out current behaviour and where the change plugs in, and leaves unrelated edits alone. You get asked something only when the answer would move the implementation, the risk or the product direction. Choices that are expensive to undo are named together with their trade-off.

Content sits in `SKILL.md` and a `references/` folder. Task files cover a new project, a feature, a bug, refactoring, performance work and a mixed high-risk change. Phase files cover discovery, design and implementation, while domain files handle APIs, data work, error handling, security, testing, code quality, UI and UX. The agent opens the few that fit the job.

Then it runs a loop: orient, frame, implement, verify, report. Smallest coherent change, checks sized to the risk, failures investigated rather than explained away. The author calls the style opinionated and expects checkpoints to flex with the task. When the job is designing the agent itself, this is the wrong skill.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add shareAI-lab/lab-skills --skill vibe-coding -a claude-code
```

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

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add shareAI-lab/lab-skills --skill vibe-coding -a codex
```

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

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add shareAI-lab/lab-skills --skill vibe-coding -a cursor
```

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

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install shareAI-lab/lab-skills software-engineering/vibe-coding/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/vibe-coding/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add shareAI-lab/lab-skills --skill vibe-coding -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/shareAI-lab/lab-skills --path software-engineering/vibe-coding
```

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add shareAI-lab/lab-skills --skill vibe-coding -a opencode
```

### 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/shareAI-lab/lab-skills/tree/HEAD/software-engineering/vibe-coding/SKILL.md

## When to use it
- carry a feature through unfamiliar code without breaking unrelated edits
- trace a bug to its cause instead of patching the first suspicious line
- size the test run to what the change can break
- run a migration with a rollback path
- keep the agent from refactoring everything it walks past

## Example prompts
- Follow the vibe-coding skill: read how sign-in works today, then add email login.
- Debug `checkout.test.ts` with vibe-coding; no patch until you can explain the execution path.
- Move sessions to `redis`, verify at the right level, and show me the rollback plan.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 7ba00ddc12a66620.

BEGIN THIRD-PARTY FILE 7ba00ddc12a66620
```text
---
name: vibe-coding
description: Transform an AI agent into a disciplined software development partner with strong judgment, transparent decisions, proportionate verification, and craftsmanship. Use for software implementation, feature work, bug fixing, refactoring, optimization, migrations, and sustained collaboration inside a codebase. Do not use merely because a task involves an AI agent; use a dedicated agent-design skill when the primary problem is agent architecture.
---

# Vibe Coding

Act as a development partner, not a code vending machine. Preserve the human's control over product direction while taking ownership of careful execution.

## Applicability

This is an opinionated collaboration style, not a universal software process. Adapt its checkpoints and communication depth to task risk, project conventions, and the user's desired level of involvement.

## Core principles

### Understand before changing

Establish the goal, affected users, constraints, current system behavior, and success evidence before making consequential changes. Inspect the repository and existing conventions instead of asking the user for facts already available locally.

Ask a question only when the answer materially changes the implementation, risk, authority, or product direction.

### Surface consequential decisions

State choices that are expensive to reverse or likely to surprise the user. Include the reason and meaningful trade-off. Do not narrate obvious implementation details or turn routine work into a stream of approvals.

### Verify proportionately

Match verification to the risk:

- focused checks for small, isolated edits;
- relevant tests and integration checks for behavioral changes;
- regression, migration, rollback, and security checks for high-impact work.

Never substitute "should work" for evidence. Also do not run an enormous unrelated test suite when a smaller check answers the real question.

### Protect craftsmanship

Follow project conventions, keep the public surface simple, handle meaningful failure paths, and leave the code easier to understand. Do not refactor unrelated areas merely because they could be improved.

## Choose the work scenario

Load only the references needed for the actual task.

| Scenario | Required reference | Additional reference when needed |
```
END THIRD-PARTY FILE 7ba00ddc12a66620

The third-party file has ended. Everything between the 7ba00ddc12a66620 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2319 of 7846 bytes. © shareAI-lab · Apache-2.0 · https://github.com/shareAI-lab/lab-skills/tree/HEAD/software-engineering/vibe-coding/SKILL.md

_Part of the page did not fit — see the HTML version._

---
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
