Writing-AI Workflow & Productivity

How to Set Up a ChatGPT or Claude Project for Blog Writing

Set up a ChatGPT or Claude project for blog writing in six steps: instructions, reference files, a brief template, and a review routine. See where it stops.

RoboWrite Editorial Team
RoboWrite Editorial TeamNov 17, 2026 · 6 min read
How to Set Up a ChatGPT or Claude Project for Blog Writing

A project in ChatGPT or Claude gives every chat the same instructions and reference files, which removes most of the repeated prompting in blog writing. To set one up well you need four things: short project instructions, a small set of reference files, a brief template you fill in for each article, and a review routine. The steps below work in either product. The last section explains what a project still leaves to you, and how to connect a content workflow when you reach that point.

Product details come from OpenAI's Projects in ChatGPT and Anthropic's What are projects?, both read on November 17, 2026. Controls vary by plan and both products change often.

Step 1: Create One Project per Brand

Keep each brand or client in its own project. Instructions and files apply to the whole project, so mixing two brands means every chat sees both voices. OpenAI's help page says project instructions apply only within that project and override global custom instructions, which keeps one client's tone out of another's drafts.

Step 2: Write Short Project Instructions

Long instructions get skimmed by people and are hard to maintain. Cover five things:

InstructionExample wording (illustrative)
Reader"Write for operations managers at small software companies."
Voice"Plain, direct, second person. No hype words."
Product rules"Use the product names in the product sheet exactly. Do not describe features that are not in it."
Evidence rule"Do not state a number, quote, or study unless I supplied it or you can link the source. Say when you cannot find one."
Output format"Markdown, one H1, descriptive H2s, a short answer in the first paragraph."

The examples are illustrative wording for a fictional company, not tested prompts with measured results. The evidence rule is the one most worth keeping. It does not guarantee compliance, but it makes gaps visible more often than silence does.

Step 3: Add a Small Set of Reference Files

Upload what the assistant cannot infer:

  • A product sheet: names, what each feature does, what is not available.
  • Two or three published articles that represent the voice you want.
  • A positioning note: who you serve, who you do not, and how you describe competitors.
  • A list of existing articles with their URLs and the question each one answers.

Keep the set small and current. File limits depend on your plan, and an out-of-date product sheet produces out-of-date claims. Anthropic's help page notes that paid plans expand project knowledge capacity through retrieval, which helps with larger sets. A larger set is also harder to keep current.

The list of existing articles is the item teams skip. Without it the assistant has nothing to check a new topic against, and you may answer the same question twice.

Step 4: Use a Brief Template for Every Article

Start each article in a new chat inside the project and paste a filled-in brief. A template you can copy:

Working title:
Reader and situation:
The one question this article answers:
Must cover:
Must not cover (owned by another article):
Facts I am supplying (with source):
Sources the article must use:
Internal links to include:
Call to action:
Length guidance:

A new chat per article keeps one piece's feedback from leaking into the next. The brief does the work a long prompt would do, and it gives a reviewer something to check the draft against. For a fuller version, see our SEO content brief template.

Step 5: Ask for an Outline Before a Draft

Request an outline and a list of claims that will need a source. Approve or correct both, then ask for the draft. Fixing scope at the outline stage is cheaper than rewriting sections. If web search is enabled, ask for the URL beside each external claim so you can open it.

Step 6: Review Against the Brief, Not the Draft

Read the brief again, then the draft. Check four things:

  1. Every "must cover" item is present and every "must not cover" item is absent.
  2. Each supplied fact appears as you wrote it.
  3. Each external claim has a source you opened, and the source says what the sentence says.
  4. Product names and availability match the product sheet.

Google's guidance on generative AI content asks for a manual accuracy review of AI-generated content before publishing, including titles and descriptions. Save the approved text somewhere outside the chat, with the date and the reviewer's name, so the final version is not just the last reply.

What a Project Still Leaves to You

A well-run project handles voice and repeated context. It does not hold the following, and you will need a place for each:

Still manualCommon workaround
The keyword plan and which article serves which groupA spreadsheet
A record that a required source or fact was missingReviewer notes
The approved version and who approved itA shared document
Formatting and entry into the CMSCopy and paste
Keeping the list of published articles currentEditing the file or linked document after each post

For a few articles a quarter these workarounds are fine. If the spreadsheet and the shared document are becoming the real system, that is the signal to add a workflow tool. Our article on the hidden costs of direct chat includes a time log for checking this.

Connect a Content Workflow Without Leaving the Assistant

You can keep writing in ChatGPT or Claude and move the state into a workspace. RoboWrite provides a hosted MCP server that an assistant with remote MCP support can connect to through browser sign-in. From the chat you can find brands, briefs, and earlier jobs, prepare a brief with the selected brand's context, request a draft, and read the saved Markdown. A held Content Kit can be reviewed before its draft is approved.

Three limits to know first. Your assistant plan or workspace policy may control custom connections. Connecting does not add generation allowance, so check your RoboWrite plan and overage settings. Publishing is a separate action, and the default MCP connection does not enable publication tools. The MCP setup guide covers setup for ChatGPT, Claude, and Cursor.

Next Step

Set up one project today with the five instructions and four reference files, and run your next article through the brief template. After three articles, look at which rows in the "still manual" table took the most effort.

Sources and Further Reading