Feedback build generalist tools

When suggesting or scaffolding tools and skills, do NOT embed brand-specific logic, templates, or assumptions about Justin's business workflows.

Every tool should take generic inputs (asset paths, JSON config, template name) and produce generic outputs. Brand data is passed in at call time as config, never hardcoded into the tool itself.

Why: Justin corrected this explicitly after recommendations included brand-specific Reel templates, Nova Design product cards, JWVR-specific content formats, and brand-database integrations baked in. His words: "you are over estimating what you know about my businesses."

How to apply: Before proposing a skill or tool, ask "could someone with a completely different business use this?" If the answer is no, extract the brand logic into a data layer (JSON config, template file, CLAUDE.md brief) and keep the tool generic. The atomic/orchestrator pattern already supports this: atomics are generalist; brand context lives in orchestrator config or caller-supplied JSON, not inside the atomic itself. Never pre-wire a tool to a specific brand DB, brand color palette, or content format without Justin explicitly requesting it.

[auto-memory session 49459f9c-7146-4376-aecc-c233b8f538c1, confidence 0.88, mode direct]