How to Use AI for a Social Media Content Calendar

Your calendar has holes in it, and it's already Monday.

How to use AI for a social media content calendar comes down to one move. Start from a piece you already made, have a model list every separate idea in it, give each idea to the platform it suits, lay the month out in four weeks, and write the first drafts one week at a time. You edit.

Ask a model for thirty post ideas instead and you get thirty hooks that open the same way. By Thursday you've made the same point four times.

A content calendar is a slicing problem, not an ideas problem.

This walkthrough runs the job start to finish for a sample brand. Every prompt is shown as typed and every reply is quoted from running it, so the places it went wrong are in here too. At the end, a scheduled task writes next week's drafts before you sit down on Monday.

Pick one pillar piece that can feed a month

A pillar piece is the one thing you made with real effort that the rest of the month can be cut from. It doesn't have to be long. It has to be dense.

Here's the test. Can you say five separate things about it without repeating yourself? A product announcement usually can't. A how-to article with a story, a distinction, three fixes and an objection can.

These make good pillars:

1. A guide or long article you published
2. A webinar or podcast episode, with the transcript
3. A survey or report you ran yourself
4. A founder's long email or a newsletter issue
5. A case study with a before and after

A press release doesn't qualify, and neither does a feature list or anything you didn't write and can't defend. A model slices what is on the page. It can't add substance the page lacks.

The sample brand is Lantern Hill Coffee, a small roaster made up for this walkthrough so no real customer's data is in it. It sells whole bean coffee to home brewers, and to office managers who stock a break room. Its pillar piece is a 374 word article called "Why Your Pour-Over Tastes Sour, and the Three Minute Fix."

The article opens with a customer email saying her Ethiopian "tastes like lemon candy." It separates bright from sour and gives three fixes: grind one notch finer, use hotter water, let the bloom run longer.

Then it describes a two cup side by side test, answers the objection that light roast is supposed to taste sour, and mentions the brew guide card that ships in every bag.

Here's where the method stops working. A pillar piece with only two or three ideas in it feeds a week, not a month, and no model can stretch it without repeating itself. Pick the piece your audience asked about most this quarter. That's the one with ideas in it.

If you want the wider habit of getting more posts out of one source, the step by step guide to AI content repurposing goes through it. This post stays on the calendar.

Put the pillar piece and your rules in one thread

Open a new chat in Magai and paste the pillar piece first, then your brand rules under it, in the same message. The rules are the part people skip, and skipping them is why a month of posts sounds like five different companies.

Lantern Hill's rules, as typed:

Brand: Lantern Hill Coffee, a small roaster that sells whole bean coffee online.
Voice: friendly, plain, a little dry. We sound like the person who runs the roastery, not an ad.
Audience: home brewers with a kettle and a hand grinder. Second audience: office managers who stock a break room.
Never: hashtags, exclamation marks, "elevate your morning", emoji on LinkedIn.
Always: one specific detail per post that a reader could try tomorrow.
Platforms: LinkedIn, Instagram, Facebook, X.

If you want the model to match a voice, add two of your best past posts under the rules and say "Match this voice." Two is enough. Paste twenty and the model gets twenty topics to repeat along with the voice.

Add one more line under the rules, so the model proves it read the piece before you build on it:

Read the pillar piece above. Reply with only "Read it" and one sentence on who it is for.

The reply: "Read it. It’s for home brewers who want to fix sour pour-over coffee, and secondarily for office managers stocking a break room."

That's the right read, with both audiences in it. If it had said "coffee lovers," stop and correct it, because everything after this builds on that sentence.

Everything from here is typed into this same thread. That's the reason to do the job in Magai and not in a fresh chat for each step. The pillar piece and the rules stay in front of every model you ask, and when you switch models in one workflow the thread's memory doesn't reset. A switch is a slash pill in your message: /Claude to draft, /GPT or /Gemini when you want a second reader on the same material. Nothing gets pasted twice.

Every prompt in this walkthrough, with the blanks marked, sits in one pack, so you can paste them in order.

Pull out the ideas before you plan anything

Don't ask for a calendar yet. Ask for an inventory of what the pillar piece contains:

List every distinct idea in the pillar piece that could stand alone as a post. For each one, give a short label, the type (story, claim, distinction, how-to, objection or offer), and the single sentence from the piece that carries it.

The reply was a table of 36 rows. Look at the first three: "The lemon-candy complaint," "The customer's concern," and "Was the coffee bad?" Each is a different sentence of the same email. The model had split the article into sentences and called every sentence an idea. A calendar built on 36 of those would post the same email for a week.

The fix is a second prompt that says what an idea is:

That is too granular. Merge any ideas that make the same point, and keep only ideas that could carry a post of their own. Keep the best sentence for each.

Nine rows came back, and these are the ideas the rest of the month is built on:

1. The "lemon candy" cup (story)
2. Sour coffee is under-extracted coffee (claim)
3. Bright is different from sour (distinction)
4. Grind one notch finer (how-to)
5. Use hotter water for light roasts (how-to)
6. Give the bloom more time (how-to)
7. Test one change at a time with two cups (how-to)
8. Light roast isn't supposed to taste sour (objection)
9. The brew guide card in every bag (offer)

Read that list the way your audience would. Could each line carry a post by itself? Cut any that couldn't. Then look at the types, because they decide the order. Each type has a job, and the job has a place in the month:

Nine ideas is enough for a month if each one shows up in a different form on each platform. The next step decides which form goes where.

Decide what each platform is for

An idea has no platform. A post does. Before you build the grid, tell the thread what each platform does for the brand this month:

Decide what each platform is for with this pillar piece. For LinkedIn, Instagram, Facebook and X, give me its job, the formats we'll use, and how many posts a week. Put it in a table.

The first table gave Instagram three posts a week, which made eleven in all. One person can review ten without skimming, so the thread was told to give Instagram two, and this came back (trimmed):

The same idea does a different job on each row. "Sour coffee is under-extracted coffee" is a break room point on LinkedIn, a before and after on Instagram, a question on Facebook, and one line on X.

Give each platform its job before you give any post its wording. Skip that step and you get one post written four times in four tones.

If you also post to TikTok or YouTube Shorts, add them as rows and name a format the model can write, such as a spoken script. A platform with no format in the table gets no posts in the grid.

Look at what the table leaves out: posting times. Don't ask a model when to post. It can't see your audience, so it hands you the same Tuesday morning advice every account gets. Meta Business Suite shows Active times, based on when your followers were most active on Facebook and Instagram over the past 7 days, so pick the slot from that (Meta Business Suite help).

Two platform facts shape the grid. A LinkedIn Page admin can schedule a post anywhere between an hour and three months ahead, so a four week plan fits with room to spare (LinkedIn Help). And Meta Business Suite limits an Instagram photo post to 10 photos, so tell the model to plan carousels at ten slides or fewer (Meta Business Suite help).

How to use AI for a social media content calendar: an arc, not a pile

A pile of posts is how a calendar runs dry in week three. An arc gives each week a job. Week one names the problem, week two gives the fixes, week three answers the doubts, and week four makes the offer.

Build a four week calendar from the nine ideas and the platform table. Week one names the problem, week two gives the fixes, week three handles doubts and proof, week four makes the offer. Give me a table with these columns: week, day, platform, format, idea number, angle in one line. No idea is the main point of more than two posts in a week. Never two posts on the same platform on the same day.

The first grid came back with forty rows and three problems. Idea 7, the two cup test, was the main point of eight posts across the month. The objection and the test, ideas that belong in week three, were already showing up in week one. And all ten posts in week four leaned on the brew guide card, so the month ended as one long ad.

The obvious fix is to hand the model stricter rules. That's where it pushed back:

Two problems. Idea 7 is the main point of eight posts across the month, and the brew guide card shows up in every post in week four. Rebuild the calendar with these rules: week one uses only ideas 1, 2 and 3. Week two uses only 4, 5 and 6. Week three uses 7 and 8, plus one callback to idea 1. Week four uses idea 9 in no more than three posts and recaps 4, 5 and 6 in the rest. Same table, same columns.

It refused, and it was right: "I can’t make a calendar that satisfies all the rules and the platform schedule: it calls for 10 posts a week, but the idea limits allow at most 6 posts in weeks one through three and 9 in week four." Three ideas, two posts each, is six posts. The old rule about two posts per idea and the new rule about three ideas a week could not both be true.

Relaxing that rule to once per platform got a second refusal, because X needs four posts a week and three ideas can't fill four X slots without repeating one.

The third rule fixed it: one idea may appear twice on X in a week, once as a single post and once as a thread or question. Then the grid built. Here are six of the ten week one rows, trimmed:

Across the month, week one used ideas 1, 2 and 3. Week two used 4, 5 and 6. Week three used 1, 7 and 8. Week four recapped 4, 5 and 6 and used idea 9 in three posts. No platform had two posts on the same day.

You might think forty posts from a 374 word article has to be repetitive. It is, if every post makes the same point in the same form. Nine ideas, four platforms and several formats is not the same post forty times, but it can drift there, which is why the check two steps down exists.

Before you accept any grid, read one platform top to bottom. Scroll only the Instagram rows. If four weeks of them read as a sequence, the arc holds. If they read as a pile, send it back.

Write the first drafts one week at a time

Don't draft the month in one go. Draft week one, read it, then ask for week two. Over forty posts the openings start to rhyme, and what you fix in week one goes into the rules before week two begins.

Write the first drafts for week one, post by post, following the grid. Rules:
- LinkedIn: 100 to 150 words, no emoji, end with a question an office manager could answer.
- Instagram carousel: ten slides at most. Give the headline for each slide, then one caption of two short paragraphs. For a Reel, give a spoken script of 60 words or fewer and one caption of two short paragraphs.
- Facebook: under 60 words, end with a question.
- X: under 280 characters each. Count them. A thread is three posts.
Label each draft with its day and platform. Do not repeat an opening line across posts.

Ten drafts came back. Here is Monday's LinkedIn post in full:

A sour cup is often a timing problem, not a bean problem. In a pour-over, water starts by pulling acids from the grounds, then moves on to the sugars. If the brew ends too soon, you get more sharpness and less sweetness. That’s what under-extraction means.

For a quick check, notice the finish after you swallow. Bright coffee can remind you of green apple and still finish sweet. Sour coffee tends to feel thin and puckery. That distinction matters in a break room too: people may call a light roast “bad” when the brew simply needs adjusting. What does your office coffee usually leave behind: a sweet finish or a puckery one?

It stays inside what the pillar piece says: acids first, then sugars, the finish as the clue. It brings in the break room from the brand rules, which is the right use of the second audience. It ends on a question an office manager could answer. At 112 words it sits inside the range.

Tuesday's X post was tighter:

Sour coffee often means under-extraction: the brew stopped before enough sweetness came through. A puckery finish is the clue.

The draft reported its own length as 123 characters. A script counted 126. That's a small miss on one post, and the next section shows how it played out across all six X posts.

Before you ask for week two, carry your edits forward. Tell the thread what you changed and why, and add any repeated fix to the rules. The next drafting prompt in the pack gains a line for exactly this reason: "Use only facts that are in the pillar piece. Do not add people, numbers, places, times or quotes that are not in it." The audit below is where that line came from.

Have a second model check every draft against the source

A model can write ten posts in a minute. You can't read ten posts in a minute and catch what's wrong with them. So give the drafts to a reader whose only job is to compare them with the pillar piece:

Audit the week one drafts against the pillar piece and the brand rules. List: 1) any fact, person, number, place or time that isn't in the pillar piece, 2) any two posts that share an opening line or a paragraph, 3) any post that breaks a rule, 4) any post that reads like an ad. Quote the line. If a post passes, say "Passes."

In this walkthrough the audit ran in the same model that wrote the drafts, which is the weaker setup. In your thread, start the message with a slash pill for a different family, /Gemini or /GPT, so the model checking the work isn't the one that wrote it. The thread carries the pillar piece, the rules and the drafts with it.

The reply found two real problems. Three lines used a "first sip" detail the pillar piece never mentions: "The pillar describes the cup’s finish, but doesn’t mention the first sip or call it lively." And the Tuesday Instagram carousel and the Thursday LinkedIn carousel both opened on the line "Bright isn’t sour."

It also reported on the X posts, and this is the part to take seriously. The audit said every X post was under 280 characters, which was true, and then listed corrected counts. Here are the counts, set against a script that measured each post:

Six posts, and neither the draft nor the audit matched the real count once. Nothing broke, because every post sat far under the limit. Close to the limit it would. Never accept a model's count as the count. Paste any X post within about 30 characters of the limit into the composer and let X count it.

The fix is a short prompt that touches only what failed:

Fix the three flagged posts: the Tuesday Instagram carousel, the Thursday LinkedIn carousel, and drop the first sip detail everywhere. Don't change anything that passed. Show only the posts you changed.

The Tuesday carousel now opens "Bright or sour?" and the Thursday one opens "The finish is a useful clue." The first sip lines were gone. "Don't change anything that passed" is the sentence doing the work, because without it a model tends to improve the posts you already approved.

If any slot in your grid is paid, gifted or a partner post, the audit needs one more rule. The FTC says a disclosure belongs with the endorsement itself, and is likely to be missed on a profile page, at the end of a post, behind a "more" click, or mixed into a group of hashtags. Plain words like "ad" or "sponsored" work (FTC, Disclosures 101 for Social Media Influencers). Add a line to the rules, such as "Any partner post opens with Ad:", and let the audit check for it.

The audit compares drafts to the pillar piece. It can't tell you the pillar piece is right. Any claim in the article that could embarrass you gets checked by a person.

Make Monday run itself

Everything so far is a good afternoon. This step makes it a system, so each Monday the week's drafts are already waiting.

First, make an agent: custom instructions that run on any model, which you can build without code (how to build an AI agent walks through it). Give it the rules, the platform rules, the nine ideas and the approved four week grid:

You draft social posts for Lantern Hill Coffee.

Brand rules:
[paste the brand rules block]

Platform rules:
[paste the platform rules from the drafting prompt]

Use only facts that are in the pillar piece. Do not add people, numbers, places, times or quotes that are not in it.

Pillar piece:
[paste the pillar piece]

The nine ideas:
[paste the numbered list]

The approved calendar:
[paste the four week table]

Second, create a scheduled task that uses that agent. A scheduled task is an agent that runs on its own on a day and time you set. Set this one to Monday at 7:00 a.m. with this prompt:

Find this week's rows in the calendar. Write a first draft for every post in those rows, following the platform rules. Then audit your own drafts for facts that are not in the pillar piece, shared opening lines, and rule breaks, and fix what you find. End with a short list of anything you could not check against the pillar piece.

Here is the whole setup in one place:

Delivery is a one line addition. With Gmail or Slack connected to the agent, end the task prompt with "Email me the drafts" or "Post the drafts to #social," and the agent acts in your own tools. The MCP route to social automation goes further, if you want the agent scheduling posts as well as drafting them.

A weekly task runs four or five times a month. The Standard plan includes 100 scheduled task runs a month, so one task per brand barely registers (Magai pricing).

The task works from what you pasted. It doesn't know which post flopped last week. When something does, add one line to the task prompt, such as "Question posts on Facebook got no replies last week, so write fewer of them," and keep each note to a line.

Your Monday is a review, not a writing session. Read the drafts against the pillar piece, and read the task's list of anything it couldn't check first, because that list is where the risk sits. Fix what it flagged, then schedule.

When a draft is wrong, change the agent and not just the draft. A wrong draft you only patch comes back wrong next Monday. A rule you add to the agent stays fixed.

Read the first Monday's drafts hard. That run is the real test of everything above.

Close the month, then slice the next one

At the end of week four, feed the results back. Paste the month's top three and bottom three posts with the numbers from your own analytics, and ask:

What do the top three posts share that the bottom three don't? Describe the pattern only. Don't claim a cause.

A model can describe a pattern across six posts. It can't prove why the pattern happened. Treat the answer as a hypothesis for next month's grid, and test it.

Keep a one line log for each month: the pillar piece, what the audit caught, and the rule you added because of it. After three months that log is the best brief you have for the next agent.

Then pick the next pillar piece and start a new thread for it, because a thread holding two pillar pieces blends them. Keep the agent and the task. Swap in the new ideas and the new grid, and the first Monday of the month is already covered.

If social is your whole job, Magai for social media managers covers the rest of the week.

What did you publish this month that could feed the next one?

Pick it. Open the thread. Slice it.