# Vibe To Agentic Framework

The conceptual framework behind the presentation, what "Vibe Coding to Agentic...

- Repository: https://github.com/shanraisshan/claude-code-best-practice (68426 stars)
- Category: Documents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add shanraisshan/claude-code-best-practice --skill vibe-to-agentic-framework -g -a claude-code -y`
Codex: `npx skills add shanraisshan/claude-code-best-practice --skill vibe-to-agentic-framework -g -a codex -y`
Cursor: `npx skills add shanraisshan/claude-code-best-practice --skill vibe-to-agentic-framework -g -a cursor -y`
Gemini CLI: `npx skills add shanraisshan/claude-code-best-practice --skill vibe-to-agentic-framework -g -a gemini-cli -y`

## Description

The conceptual framework behind the presentation, what "Vibe Coding to Agentic Engineering" means, why the journey is structured the way it is, and how every slide fits the narrative arc

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# The "Vibe Coding to Agentic Engineering" Framework

This skill teaches the **conceptual model** behind the presentation. Every slide and section exists to tell a single story: how a developer incrementally moves from unstructured "vibe coding" (Low level) to high-level agentic engineering (High level).

## Core Concept

**Vibe Coding (Low level)** is when a developer uses Claude Code with no structure, no project context, no conventions, no reusable knowledge. Every prompt is a coin flip. Claude might create random endpoints, ignore existing patterns, skip tests, and produce inconsistent code. The codebase drifts toward entropy with every interaction.

**Agentic Engineering (High level)** is when Claude Code operates as a fully configured engineering system. It knows the project architecture (CLAUDE.md), follows scoped conventions (Rules), loads domain expertise on demand (Skills), delegates to specialized workers (Agents), orchestrates multi-step workflows (Commands), automates lifecycle events (Hooks), and connects to external tools (MCP Servers). Every prompt produces consistent, tested, production-quality code.

The journey between these two extremes is **incremental and cumulative**. Each best practice builds on the previous ones, and the presentation teaches them in the order a developer should adopt them.

## The 4-Level Journey System

The presentation uses a 4-level scoring system instead of a percentage bar:

| Level | Order | Color | Journey Bar Height | Description |
|-------|-------|-------|--------------------|-------------|
| Low | 1 | Red/orange (`hsl(0, 70%, 45%)`) | 25% | Vibe coding territory, no structure |
| Medium | 2 | Yellow (`hsl(40, 70%, 45%)`) | 50% | Structured workflows, some automation |
| High | 3 | Light green (`hsl(80, 70%, 45%)`) | 75% | Domain knowledge, skills, custom agents |
| Pro | 4 | Deep green (`hsl(120, 70%, 45%)`) | 100% | Full agentic engineering, multi-agent teams |

The rest: https://github.com/shanraisshan/claude-code-best-practice/blob/HEAD/.claude/skills/presentation/vibe-to-agentic-framework/SKILL.md