Brand context is the product
The model is the same for everyone. What makes the output yours is the twelve section brand document every skill reads first.
People ask which model WriterDean uses. It is a fair question and the answer is in the docs. It is also the least interesting part of the system. Everyone has access to the same models. What they do not have is your brand context.
The document
Each brand in WriterDean has one context document with twelve sections: product overview, target audience, personas, problems and pain points, competitive landscape, differentiation, objections and anti personas, switching dynamics, customer language, brand voice, proof points, and goals. It has a version number and a changelog.
The structure comes from the product marketing skill in the open library we build on. We did not change it, and that is deliberate. If you export the document, it works with the same skills in your own repo.
How it gets written
The onboarding wizard offers two paths.
Paste your site URL and WriterDean crawls the homepage, about page, pricing page, blog, and meta tags. It drafts all twelve sections and asks you what to correct. Most teams get a usable first version in about ten minutes of edits.
Or walk through it one section at a time in a conversation. This takes longer and produces a better document, because you end up saying things about your customers that are not on your website.
What it changes
Every skill in every pipeline reads the document before it writes anything. The effect shows up in small places.
The copywriting skill uses your customer language section, so the draft uses the words your buyers use instead of the words your competitors use.
The proof points section is the only source of claims the draft can make. If a number is not in there, it does not appear in the draft. This is how we keep invented statistics out.
The brand voice section carries banned words and paired examples. A gate checks the draft against them and sends it back if it slips.
Keeping it current
Every substantive save bumps the version and adds a line to the changelog. Content records which version it was written against, so when you change your positioning, the refresh view can show you which published pieces were written under the old one.
Treat the document as a living thing. Ten minutes a month keeps it honest, and the drafts get better every time you do.