CLAUDE.md as a product spec — the GHZ Code workflow
Most people write their CLAUDE.md like a README. At GHZ Creative, we don’t write it at all — we let Claude build its own context by asking us the right questions. Here’s why that works better.
Stop writing your own CLAUDE.md
The conventional advice is: write a detailed CLAUDE.md so the AI understands your project. Define the architecture, the conventions, the rules.
We tried that. It’s tedious, it goes stale fast, and half the time you forget to include the things that actually matter.
The GHZ Creative approach is different: let Claude write its own CLAUDE.md. We explain what we’re building, and Claude asks the questions it needs answered to work effectively. The context file becomes a conversation artifact — not a document we maintain.
How the workflow actually looks
At the start of a new project, we open Claude Code and describe the idea. Not in detail — just the vision, the target user, the core problem it solves.
Then we ask Claude: what do you need to know to build this? What framework fits? What architecture makes sense? Claude proposes options, explains trade-offs, and we make the final call. Claude then structures the CLAUDE.md with everything it learned from that conversation.
The result is a context file that actually reflects how the AI thinks about the project — not how a human thinks it should be documented.
When to update it
We don’t update CLAUDE.md on every commit. We update it when the structure changes, when the direction shifts, when a major decision invalidates the existing context. Maybe once a week, maybe once a month. When it’s necessary, not on a schedule.
The same applies to AGENTS.md. At GHZ Creative we use specialized agents — one for finding security vulnerabilities, one for SEO optimization, another for frontend design. Each gets its own context. But most of the time, we keep it simple. A vanilla setup does 90% of the work.
CLAUDE.md vs AGENTS.md
CLAUDE.md is the project brain. It holds the architecture decisions, the tech stack, the conventions — the things any agent working on the codebase needs to know.
AGENTS.md is for specialization. When we need an agent that only cares about security audits, or one that only handles CSS and component design, AGENTS.md scopes that agent’s context so it doesn’t try to do everything.
The combination is what powers the GHZ Code workflow: a general context for the project, and specific contexts for specialized tasks. But we always start simple and only add complexity when the project demands it.
The principle behind it
The best context file is one the AI built for itself. It knows what it needs better than we do. Our job is to answer its questions honestly and make the judgment calls on architecture and direction.
This is the workflow behind every product at GHZ Creative — FundingView, LiquidView, CrossDesk, ILY Padel, and now GHZ Code and GHZ Voice themselves. The AI builds its own map. We just tell it where we’re going.