Skip navigation
Pt. 3: What Goes Into /docs 🗂️ Agent-Ready Files (DRY Edition)
0:00

Pt. 3: What Goes Into /docs 🗂️ Agent-Ready Files (DRY Edition)

#aiagents #claudecode #vibecoding

Pt. 3: What Goes Into /docs 🗂️ Agent-Ready Files (DRY Edition) Keep it simple. Keep it reusable. Keep it Evergreen.🌲 Your /docs folder exists so agents don’t repeat work - DRY applies to context too. Typical files your CLAUDE.md should point to: – architecture.md System overview, components, data flow – decisions.md Why things were built this way (very important) – conventions.md Naming, formatting, repo rules – workflows.md How things are built, tested, deployed – integrations.md APIs, services, auth, rate limits – glossary.md Domain terms and meanings Why this works: – One source of truth – Less repetition in prompts – More consistent agent behavior Rule of thumb: If you explain it twice, document it once. Agents perform best when context is structured. Pt. 1: The Golden Folder 🥇 Link: Pt. 2: Why Your CLAUDE.md Needs a Table of Contents for /docs 🗂️ Link: Happy Vibe Coding! Michael #aiagents #claudecode #vibecoding #aiengineer

Comments

Comments from the original post on Instagram

No comments yet