# ✅ Vibe Coding – AI-Assisted Code Sanity Checklist
*Use this before shipping AI-assisted code.*

## 🔍 Layer 1: Clarity & Comprehension
- [ ] I can explain what every function does
- [ ] I know why each line exists — or I’ve removed it
- [ ] No “black-box” code left in just because it worked

## 🧩 Layer 2: Fit & Alignment
- [ ] Matches project architecture or breaks it with purpose
- [ ] Uses the right abstraction (not over- or under-engineered)
- [ ] Accounts for performance, security, and error handling

## ✍️ Layer 3: Style & Structure
- [ ] Clear, intentional naming
- [ ] Readable layout—no magic numbers or deep nesting
- [ ] Formatting and conventions are consistent

## 🔁 Layer 4: Behavior & Boundaries
- [ ] Happy path is confirmed
- [ ] Unexpected inputs are handled
- [ ] At least one test proves it works

## 💬 Layer 5: Communication & Context
- [ ] PR or commit message explains **why**, not just what
- [ ] Comments clarify **intent**, not restate code
- [ ] Uncertainty or tradeoffs are called out

## 🌱 Self-Check
- [ ] Did I learn anything from this code?
> If not, you might be vibe-coding too hard. Pause and investigate.

[keysandquills.com](https://keysandquills.com)