I Gave Claude a Data Engineering Brain

Now Every Chart, KPI, and Pipeline It Builds Looks Like Mine.

How a single Markdown file turned an AI coding assistant into a data engineering partner that remembers my standards, my palette, my formatting rules — and never asks twice.

I was three hours into a data pipeline review when it hit me. I’d just corrected Claude Code’s chart colors for the fourth time that week. Same hex codes, same conversation, same exhaustion. The bar chart was using default Plotly blue instead of our standard navy. The axis labels were missing units. The title said “Q3 Revenue” instead of stating the actual insight. And I’d fixed every single one of these things yesterday.

That’s when I stopped and asked myself a question that changed my entire workflow: what if I could teach Claude Code my standards once, and have it remember them forever?

Not in a prompt. Not in a system message I’d have to paste into every conversation. I wanted something that lived inside the project itself — a file that Claude Code would read automatically, every single time, without me asking. A second brain for data engineering standards that would inject my color palette, my chart formatting rules, my statistical KPIs, my naming conventions, and my pipeline architecture patterns into every response.