This is Part 2 of our series, The System Behind Better Content, co-authored by Content Design Hub. You can read Part 1 here.
A content spec is a structured, testable document that defines how content should look, sound, and behave across a product, built from real user research so your team (and your AI tools) have a shared set of rules to work from. In Part 1, we showed you how you can create a content spec and what it might look like, but having the spec is only half the work. A document sitting in a folder doesn't change anything on its own, it has to be operationalized to earn its place in your workflow.
What’s inside
- 7 places to add your spec so the whole team actually uses it
- What AI gets wrong without a spec, and a full example prompt to fix it
- The full spec cycle from research to AI guardrails to closing the loop
Embedding a content spec into existing workflows
A content spec only delivers value if the whole team uses it. The spec makes that possible. If it’s in the spec, anyone can check against it. That includes product managers writing acceptance criteria, engineers writing automated test cases, and QA testers checking final screens.
7 places you could add your spec to
A spec needs to be embedded in the places where decisions happen. This could be your team’s:
- Design system: make the spec into a component on Figma so content rules live where design happens.
- Product management tool: include spec compliance in your definition of done so that no ticket closes without a content spec check.
- Code repository: store the spec as Markdown (.md) in the repository so developers can reference it without leaving their workflow.
- AI project files: upload the spec to Claude project files or in a new chat of your preferred AI tool as a Markdown (.md) with your brand and tone guidelines and keywords list. Structure your instructions to read and strictly adhere to the guidelines so the AI tool applies the approved language every time they generate content (more on this in section 4).
- Sprint kickoffs: reference the spec when writing user stories and defining acceptance criteria.
- Definitions of done: add "content checked against spec" as a required condition before any feature ships.
- QA checklists: include spec compliance as a structured check alongside usability tests and live site tests
The key is to keep the spec visible to your teammates and easy to reference wherever your team works, including the AI tools your team uses.
Add AI guardrails: writing for your users, not someone else's defaults
When AI tools generate content, they use their training data, but much of the publicly available digital content used to develop AI systems is disproportionately produced in Western and North American contexts. These perspectives differ from the lived experiences, cultural contexts, and perspectives of the users you are designing for.
What AI gets wrong without a spec
Without a spec grounded in user research, AI writing tools can produce content that is grammatically correct and seemingly polished, but culturally misaligned.
For an Australian student finance app, that might look like:
- ‘Your 401(k) contributions’. In Australia, it’s called superannuation or super.
- ‘Apply for social security benefits’. In Australia, this is Centrelink. The term, ‘social security’ means something entirely different.
- ‘File your federal income tax’. In Australia, you lodge a tax return with the ATO (Australian Taxation Office).
These are not AI trivial errors. Nor are they hallucinations. AI got these terms correct, but for a different audience.
When content is not localized, you may not only alienate your users, but also create anxiety and erode trust. In a regulated industry like financial services, it can also create compliance risk.
What the content spec does for AI
A content spec is one of the most effective prompt engineering assets your team can have. Prompt engineering is the practice of writing precise and reusable instructions that guide AI tools to produce consistent and predictable outputs.
When you feed your spec rules into an AI prompt, you give the model the guardrails so it doesn’t fill in the blanks and default to its training data.
Example prompt using a content spec
Role
You’re a content designer writing for a money management app aimed at Australian young people aged 18 to 24.
Context
Users may be managing money independently for the first time. They are familiar with informal language but need to learn formal financial terminology as part of using the app. Australian financial, tax, and welfare systems have specific terms that differ from other English-speaking countries.
Task
Write content for the app onboarding flow. Users will experience this flow when they sign up for the first time. The flow includes the welcome screen and account setup steps. It’s the first time a user will encounter key financial concepts like superannuation, HECS-HELP, and Centrelink payments. Each screen should introduce one concept at a time, explain it in plain English, and tell the user what action to take next.
Output
Screen-by-screen onboarding content, including headings, body copy, and button labels. Keep all sentences under 20 words. Each screen should have one heading, no more than 3 sentences of body copy, and one call-to-action.
Constraints
Use the content spec to guide your content decisions.
Use the acceptance criteria and user story to guide your deliverables.
Key rules include:
- Use 'superannuation' on first mention, then 'super'
- Use 'Centrelink payment,' not 'government benefit' or 'welfare'
- Use 'lodge a tax return,' not 'file taxes'
- Use 'transaction account,' not 'checking account'
- Address users as 'you', never 'the user' or 'our customers'
- Do not use North American financial terms (401k, social security, federal income tax)
- Legal disclosures must use terminology required by ASIC guidelines and cannot be rewritten for style.
Validation
Before finalising any content, check it against the content spec. If a term does not appear in the approved list, flag it for review rather than substituting a synonym.
Confirmation
Before you draft the content, confirm you can:
- Access and read the spec.
- The screens you will create.
- The user you are writing for.
- User story and acceptance criteria.
With these prompt rules, your AI tool has a strong starting point and will give you a better first draft.
The spec also helps teams evaluate AI output consistently. Instead of asking, “Does this sound right?’, you may question, “Does this align with our rules?”
Courses like AI Prompt Engineering for Content Creators can be a useful way to learn how to write effective AI prompts grounded in content design principles.
View content as a system, not a document
A content spec is a living system that connects user research to design decisions, team workflows, and AI tools. It's like a muscle; the more you use it, the stronger it gets. The more you add to it, the more accurate, reliable, and valuable it becomes.
Here's the full spec cycle:
- Research: discover how your users think, talk, and group information.
- Spec creation: turn those findings into explicit, testable rules.
- Spec storage: add your spec to systems and places where it can be used and updated.
- Team alignment: embed the spec in design reviews, sprint kickoffs, and definitions of done.
- AI guardrails: feed the spec into AI prompts to get consistent, culturally appropriate and accurate outputs.
- Close the loop: when research reveals a gap between user language and spec language, update the spec. The updated spec flows through everywhere content decisions are made (design guidelines, AI prompts, QA checklists, and developer documentation).
The content spec keeps your product human. It's rooted in research and reflects the context of your users; how they think, speak, and make sense of the world.
AI is now a standard part of content workflows. This means that the spec is no longer optional and is no longer just an engineering tool. Without a content spec, AI tools default to someone else's language, someone else's culture, and someone else's assumptions.
Product teams that invest in a content spec now are building a system that scales, learns, and most importantly, keeps the user at the centre of every decision.
Start with research. Build the spec. Keep your users in every decision.
Meet with us to learn how teams are using Optimal to transform interviews into insights and create content that truly connects.
