Claude AI Vibe Coding

What happens when Unix philosophy meets AI coding? My daily experiments with Claude, patterns I discovered, and why I stopped writing docs

My daily discoveries coding with Claude AI in Cursor IDE. Each article = one pattern discovered from terminal sessions. No fluff, no theory - just what works in vibe coding.

What You'll Find Here

Real coding sessions with Claude Code turned into patterns:

• Terminal-first development with bash (because GUIs hide the truth)

• Single file architectures in Cursor IDE (2000 lines > 20 files)

• Makefile over everything (Unix control > cloud convenience)

• Git as culture tracker (learned: commits = DNA)

The Approach

Problem hits -> Try solution -> Discover pattern -> Share if valuable

No made-up examples. No hypothetical scenarios. Every pattern comes from actual pain in terminal, actual code in Cursor, actual solutions with Claude AI.

Start With These

• Zero Documentation -> Living Code - Why documentation dies but code lives forever

• Makefile Over GitHub Actions - Total control vs cloud dependency

• Git as Evolution Engine - How git commits become cultural DNA

• Single Source Multi-Platform Publishing - Write once, publish everywhere

Tools Born From These Patterns

• @yemreak/culture - Discover patterns from any git repo

• @yemreak/vibe-coding - Tool collection following these patterns

Philosophy

Code is temporary. Patterns are eternal. Share the pattern, not the implementation.

Every learned: commit in our git history is a potential article. The ones that survive real usage make it here.