A workflow guide for taking a project from an initial idea through planning, coding, review, testing, deployment, and later fixes. It stores project requirements, plans, implementation notes, and deployment records in a defined workspace layout.

Use it to start projects from prompts, refine requirements, plan and implement features, review and test code, deploy, and apply updates or bug fixes.

It gives an AI coding project a consistent lifecycle and keeps its changing decisions and records organised.

vibe-coding — Skill for Claude Code and Codex by X-School-Academy

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add X-School-Academy/skill-pilot --skill vibe-coding

Clone the repo

git clone --depth 1 https://github.com/X-School-Academy/skill-pilot

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/vibe-coding/github.svg)](https://agentmods.dev/skills/x-school-academy/skill-pilot/vibe-coding)

Your own site

<a href="https://agentmods.dev/skills/x-school-academy/skill-pilot/vibe-coding"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/vibe-coding/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/x-school-academy/skill-pilot/vibe-coding"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/vibe-coding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,225 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00079	$0.01225
Opus 5.5	$0.00032	$0.00490
Sonnet 5.5	$0.00016	$0.00245
Haiku 4.5	$0.00008	$0.00122

Measured 16d ago against content hash 23704ca02252, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vibe-coding scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 16d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

core/skills/system/vibe-coding/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

timestamp=$(date +"%Y-%m-%d-%H%M")
mkdir -p design-archive
mv plan.md "design-archive/plan.$timestamp.md"

Read the full file on GitHub · 116 lines

Files

What ships with it

14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

16d ago First seen · 116 lines · 79 tokens per session scan A 23704ca02252

Subscribe to this mod's changes

vibe-coding is a skill published in the GitHub repository X-School-Academy/skill-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 79 tokens to every session and 1,225 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.

Planning Project management

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios · 35 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens