Claude for Design Work: How to Stop Repeating the Same Taste Arguments Every Session

Running a web agency on Claude (Cursor, Claude Code, custom skills) produces solid code fast, but design taste degrades across sessions. The root cause: Claude has no persistent memory of rejected variants, accepted tokens, or design judgments. Brand facts are preserved; taste history is not.

The Core Problem

• A Stripe-inspired hero brief (brand docs, screenshots, 6K-token system prompt) generated gradient mesh, glassmorphic cards, feature pills, glow CTAs — generic 2023 SaaS #4 output. It took 18 iterations to fix, and spacing tweaks in prompt 13 reintroduced the glassmorphic card killed in prompt 5.
• A premium law firm brand kit produced fintech-style rounded cards and soft blue because Claude's training distribution averages “professional + clean” to that look.
• Two sections from the same kit (hero vs testimonials) in fresh sessions produced mismatched type pairings and button styling — as if designed by different studios.

Why Prompts and Projects Don't Fix It

Prompts forget. CLAUDE.md stores facts, not judgments. Projects pin documents, not taste history. The accumulated decisions (“8px radius forever,” “no glassmorphism on this account”) vanish each session.

The Workaround (Custom Memory Layer)

The author wired a separate layer that holds:

• Rejected variants
• Accepted tokens
• Voice rules with examples of what the client actually shipped

This subset is injected into every Claude call as live context. Same model, but now reading taste history instead of guessing.

Open Questions

The author asks the community:

• How do you keep taste consistent across sessions in AI-driven design work?
• Has anyone gotten Projects + CLAUDE.md to persist judgments (not just facts)?
• Anyone using a memory layer (custom or off the shelf) specifically for design work?