Working with Claude Code doesn't feel like programming. It feels like sketching. Fluid. Creative. Playful. I'm molding clay, not writing code. 📡 Project Ansible (AI summaries for Readwise) is my most ambitious build yet, and it felt like painting.
After more than a year of experimenting with AI assisted coding 💪 the interesting part for me is no longer “can the model do this?” but “what’s the structure and process that actually makes this work?” This project template is where I have ended up, and that now kick starts my projects.
Seven or eight real apps built with Claude Code, zero “actual” coding from me. A new white paper just described my workflow so precisely it felt like reading my own brain - so here’s how I actually do it.
Just grokked: CLAUDE.md files are sent with EVERY request. My rich 700+ line memory for 'do this task' seemed suddenly wasteful. Refactored to act as library index. 📉 Result: 730 → 442 lines (67% reduction). 30 min discussion, 2 min execution.
What if the best way to get great code from AI is to make it politely argue with itself? I tried the "antagonist agent" approach from a Claude Code event — and it genuinely feels like having a team. 🤖⚔️🤖