vibe-coding
/vibe-coding
Manage the full lifecycle of a Vibe Coding project — create, refine, brainstorm, initialize, plan, implement, review, test, deploy, update, and fix issues. Use when the user wants to start a new project from a prompt, evolve its requirements, plan or write code, validate or deploy it, or apply updates and bug fixes against an existing project.
- Author
- x-school-academy ↗
- Repository
- skill-pilot ↗
- Licence
- MIT
- Last repository change
- 07.06.2026
Assessment and security
- Files in this package
- 15
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Manage the full lifecycle of a Vibe Coding project — create, refine, brainstorm, initialize, plan, implement, review, test, deploy, update, and fix issues. Use when the user wants to start a new project from a prompt, evolve its requirements, plan or write code, validate or deploy it, or apply updates and bug fixes against an existing project.
Original author description
Manage the full lifecycle of a Vibe Coding project — create, refine, brainstorm, initialize, plan, implement, review, test, deploy, update, and fix issues. Use when the user wants to start a new project from a prompt, evolve its requirements, plan or write code, validate or deploy it, or apply updates and bug fixes against an existing project.
How it works
- Roles
- Project Boundary
- Project Layout
- File Lifecycle Rules
- Default Flows
- agent-workflow Context
- Stage Dispatch
- Instructions
- Key Principles
SKILL.md preview
---
name: vibe-coding
description: Manage the full lifecycle of a Vibe Coding project — create, refine, brainstorm, initialize, plan, implement, review, test, deploy, update, and fix issues. Use when the user wants to start a new project from a prompt, evolve its requirements, plan or write code, validate or deploy it, or apply updates and bug fixes against an existing project.
---
# Vibe Coding Skill
Drives every stage of a Vibe Coding project. Stage details live in `references/`. This file defines layout, lifecycle rules, and stage dispatch.
## Roles
Project Manager · Technical Writer · Backend Developer · DevOps Engineer · Code Reviewer · QA Engineer · Creative Strategist
Apply only the roles relevant to the chosen stage. Announce actions before performing them: `As a {Role}, I will {action}.`
## Project Boundary
Stay inside `workspace/vibe-coding/{project-name}/` unless the user explicitly asks otherwise.
## Project Layout
```
workspace/vibe-coding/{project-name}/
├── README.md # overview and usage guide
├── CHANGELOG.md # change log per update/fix cycle
├── AGENTS.md # AI-agent instructions for this project
├── requirements.md # living — scope and intent
├── plan.md # living — current implementation plan
├── implementation.md # living — current implementation summary
├── deployment.md # living — deployment record
├── initialized.md # write-once — init completed mark
├── design-archive/ # timestamped snapshots, created only when needed
└── (project source code)
```
`create` bootstraps the project folder, root design docs, and top-level files. It does not create `design-archive/`; archive stages create it when needed. `deploy` creates `assets/` when missing.
## File Lifecycle Rules
**Living docs** (overwrite in place, always current): `requirements.md`, `plan.md`, `implementation.md`, `deployment.md`. Refresh after any stage that changes scope, plan, or code.
**Top-level files** (maintain throughout lifecycle):
- `README.md` — update when purpose, usage, or setup changes
- `CHANGELOG.md` — append an entry each update/fix cycle
- `AGENTS.md` — update when AI-agent notes change
**Plan archiving** — before writing a new `plan.md`, archive the old one:
```bash
timestamp=$(date +"%Y-%m-%d-%H%M")
mkdir -p design-archive
mv plan.md "design-archive/plan.$timestamp.md"
```
**Intermediates** — archive after consumption using `{basename}.{YYYY-MM-DD-HHMM}.md`:
- `brainstorm.md`, `update.md`, `issues.md`, `reviewed.md`, `tested.md`
`initialized.md` is write-once — never refresh it.
## Default Flows
**New project:** `create → refine → initialize → plan → implement → test → review → deploy`
**Update/fix:** `update/fix → refine → plan → implement → test → review → deploy`
The `update/fix` stage only sets up the trigger doc. `plan` and `implement` then run the same as in the new project flow, but automatically read the trigger doc for context.
| Stage | Purpose |
|-------|---------|
| create | Create project folder, `requirements.md`, and top-level stubs |
| refine | Resolve ambiguities only; keep original meaning |
| initialize | Init git repo for a new project |
| plan | Archive old `plan.md`; write new plan |
| implement | Write code; update `implementation.md` |
| test | Test → fix → retest until all requirements pass |
| review | Review for cleanliness/correctness; fix all issues found |
| deploy | Deploy; update `deployment.md` and `README.md` |
## agent-workflow Context
When invoked inside an `agent-workflow`, call the `agent-workflow` skill's **continue-workflow** action immediately after each stage completes.
## Stage Dispatch
| Intent | Reference |
|--------|-----------|
| Start a new project | `references/create.md` |
| Clarify requirements | `references/refine.md` |
| Brainstorm ideas | `references/brainstorm.md` |
| Apply brainstorm to requirements | `references/apply-brainstorm.md` |
| Initialize new project repo | `references/initial.md` |
| Create a dev plan | `references/plan.md` |
| Implement from plan | `references/implement.md` |
| Review for defects | `references/review.md` |
| Test the implementation | `references/test.md` |
| Deploy the project | `references/deploy.md` |
| Apply `update.md` changes | `references/update.md` |
| Fix issues from `issues.md` | `references/fix-issues.md` |
If the intent matches multiple stages, ask before acting.
## Instructions
1. **Identify the project** — confirm `workspace/vibe-coding/{project-name}/`; if new, dispatch to `create`.
2. **Identify the stage** — map the request to one dispatch entry; announce role(s) and stage.
3. **Read the reference** — follow `references/{stage}.md`.
4. **Apply lifecycle rules** — archive intermediates, refresh living docs, never rewrite `initialized.md`.
5. **Report** — state what ran, which files changed, and what comes next.
## Key Principles
- **Single source of truth**: living docs always reflect current state.
- **Archive before overwrite**: never lose intermediate content.
- **Boundary discipline**: stay in the project folder.
- **One stage per turn**: run multiple stages in sequence if asked.
- **Refresh after change**: always update living docs before reporting done.
Files in this package (15)
- SKILL.md 5 KB
- references/agents-template.md 1 KB
- references/apply-brainstorm.md 1 KB
- references/brainstorm.md 1 KB
- references/create.md 1 KB
- references/deploy.md 5 KB
- references/fix-issues.md 1 KB
- references/implement.md 2 KB
- references/initial.md 1 KB
- references/plan.md 2 KB
- references/refine-reference-project.md 5 KB
- references/refine.md 2 KB
- references/review.md 3 KB
- references/test.md 2 KB
- references/update.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · x-school-academy/skill-pilot | 100 | MIT |
| TerminalSkills/skills | 100 | Apache-2.0 |
| jamditis/claude-skills-journalism | 100 | MIT |
| dtyq/magic | 100 | Apache-2.0 |
| realjaymes/marketingagentskills | 100 | MIT |
| LeadMagic/gtm-skills | 100 | MIT |
| sarvamai/skills | 100 | Apache-2.0 |
| shareai-lab/kode-cli | 95 | Apache-2.0 |
| andreibesleaga/gabbe | 90 | CC-BY-4.0 |
Database snapshot: 13.11.2026 · package version 4d0989b75d3a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100vibe
Use when working in a vibe-coded repository, where the user never reads the code and only runs the product and gives feedback, or when the user wants to start building a project that way. - 100vibe-delegate
Delegate a coding task to the Mistral Vibe CLI (`vibe`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Vibe — phrasings like "have Vibe implement X", "delegate this to Vibe", "run it through… - 100vibe-scaffold
Scaffolds a new vibe-coded project with guardrails - git, OpenSpec specs, an AGENTS.md wired for superpowers, ponytail, rtk and headroom. Use whenever the user says "let's start a new project", "start a new project", "new repo", "set up this repo", or asks to scaffold or initialize a project. - 90vibe-build
Full end-to-end "vibe code" workflow for building software from scratch — research, bootstrap, plan, build, verify, ship — so the user never has to explain the process. Use when starting any new software project (app, website, game, tool, script, extension — any field), when the… - 90vibe-audit
Runs a comprehensive 20-point code quality audit on a "vibe-coded" codebase that was shipped fast and now needs hardening. Use this skill whenever the user mentions vibe coding, vibe audit, code audit, code review, code cleanup, hardening a prototype, productionizing a codebase,… - 100vibe-skill-audit
Use when the user wants to create, update, review, or audit a repo-local Vibe skill under `skills/`, mentions "/vibe-skill-audit", "vibe-skill", "vibe skill", "创建 skill", "审查 skill", "skill 文案", or "自动匹配语义", or needs a Vibe-specific wrapper around `skill-creator` rather than a…