Cookbook / Social media

Cookbook

Social media

Run a brand's social media from one Wiele workspace, with brand docs, a post per file, raw exports, a work log, and an agent that keeps them up to date.

Goal: everything about a brand's social media in one place that people and agents both work in. The brand voice, audience and campaign briefs, every post with its status and results, the exports and call notes they came from, and a log of what was done. Each week adds to it, and anyone can get all of it back with one wiele fetch.

The example brand is Acme Coffee, a roaster with an Instagram account and a LinkedIn page. Use one workspace per brand, or per client if you're an agency, so you can share each one separately.

Setup

With the Wiele skills installed, start your agent in any folder and say:

"Set up a Wiele workspace for Acme Coffee's social media. Anna writes the posts and Piotr approves anything with prices. We post on Instagram four times a week and on LinkedIn once a week."

The wiele-setup skill asks what comes in and what goes out, shows you the folder layout below and waits for your yes. Then it creates the workspace, writes the starter files filled in with what you told it, and pushes them. It saves your answers in raw/ so the docs have a source.

To do it by hand:

wiele workspace create "Acme Coffee social"
wiele fetch acme-coffee-social:/ ~/Wiele/acme-coffee-social

Create the files below in ~/Wiele/acme-coffee-social, then:

cd ~/Wiele/acme-coffee-social
wiele status
wiele push -m "Set up the workspace"

Folder layout

acme-coffee-social:/
  README.md                what goes where, rules, common requests
  AGENTS.md                rules for agents
  CLAUDE.md                @AGENTS.md
  docs/
    README.md              what each file holds, campaign template
    overview.md            goals, KPIs, team, who approves what
    brand-voice.md         how we sound, words we use and avoid
    audience.md
    pillars.md             content pillars and their share of posts
    platforms.md           accounts, formats, cadence
    learnings.md           what works, newest first, with evidence
    campaigns/
      2026-11-black-friday.md
  content/
    README.md              naming, statuses, post template
    2026-11/
      2026-11-24-instagram-grind-size.md
  raw/
    README.md
    2026-11/
      2026-11-05-kickoff-notes.md
      2026-11-30-instagram-insights.csv
  log/
    README.md
    2026-11.md
  assets/
    brand/
    2026-11/

Each folder has one job:

  • docs/ holds what is true now. Agents rewrite these files when something changes.
  • content/ holds one file per post per platform, in the month it goes out.
  • raw/ holds exports, call notes and client emails exactly as they arrived. Nothing here is edited, so every statement in docs/ can point to its source.
  • log/ holds one file per month, with a ## 2026-11-05 section per day: what was done, decided, published or learned.
  • assets/ holds images and video, named like the post they belong to.

Month folders keep listings short after years of posting. Campaign, pillar and platform live in each post's front matter rather than in folders, so a post has one place and an agent can still list every Black Friday post.

The README

The README tells people and agents where things go. Agents read it before they do anything.

# Acme Coffee social media

Everything about running Acme Coffee's social media: what we know, what we post,
what came in and what we did. People and agents follow this file.

## Folders

| Folder     | What goes in                                                 | Named                                             |
| ---------- | ------------------------------------------------------------ | ------------------------------------------------- |
| `docs/`    | Goals, brand voice, audience, pillars, platforms, campaigns  | `docs/TOPIC.md`, `docs/campaigns/YYYY-MM-NAME.md` |
| `content/` | One file per post: status, caption, assets and results       | `content/YYYY-MM/YYYY-MM-DD-PLATFORM-NAME.md`     |
| `raw/`     | Exports, meeting notes, feedback, research. Never edited.    | `raw/YYYY-MM/YYYY-MM-DD-SOURCE-NAME.EXT`          |
| `log/`     | A `## YYYY-MM-DD` section per day. New entries at the end.   | `log/YYYY-MM.md`                                  |
| `assets/`  | Images, video, design files. Brand files in `assets/brand/`. | `assets/YYYY-MM/` named like the post             |

## Rules

1. Read `docs/` before planning or writing anything. `raw/` is the evidence behind it.
2. New material goes into `raw/` first, unchanged. Then update the `docs/` files it
   changes and note it in the log with a link to the raw file.
3. A post's `status` is `idea`, `draft`, `review`, `approved`, `scheduled`,
   `published` or `dropped`. Don't delete posts; drop them.
4. Dates are YYYY-MM-DD. Names are lowercase with hyphens.
5. Text is Markdown, tables are CSV. One topic per file.
6. Every change ends with a log line and a push.

## Common requests

- "Plan next month": read docs/ and last month's results, add `idea` posts.
- "Write next week's posts": turn `idea` posts into `draft`s in the brand voice.
- "Here is the Instagram export": save it in raw/, fill in results, update learnings.
- "What worked on LinkedIn this quarter?": answer from learnings and results.
- "Start the Black Friday campaign": write the brief from the template, then its posts.

AGENTS.md adds the commands:

# Agent instructions

This folder is a Wiele workspace checkout. Read `README.md` first and follow its rules.

- Before you start, run `wiele pull` to get teammates' changes.
- Never edit files in `raw/`. Add new ones.
- After a change, add a line to this month's file in `log/`, then run `wiele status`
  and `wiele push -m "MESSAGE"`. Report the revision the push prints.
- On `PUSH_CONFLICT`, run `wiele pull --keep-local`, merge the other person's edits
  into your copy, and push again.

CLAUDE.md holds the line @AGENTS.md, so Claude Code reads the same rules. Codex, Cursor and most other agents read AGENTS.md directly.

A post

content/2026-11/2026-11-24-instagram-grind-size.md:

---
date: 2026-11-24
platform: instagram
format: carousel
status: draft
pillar: education
campaign: 2026-11-black-friday
assets: [assets/2026-11/2026-11-24-instagram-grind-size-1.png]
url:
---

# Grind size in three photos

## Caption

Too sour? Grind finer. Too bitter? Grind coarser. Three photos, one rule
for every brewer. #coffee #homebrewing #krakow

## Notes

Photos: espresso, V60 and French press grounds next to a coin for scale.

## Results

A post used on Instagram and LinkedIn gets two files, because the captions and results differ. Results go in about a week after publishing, with a link to the export they came from.

Working with the agent

Start Claude Code, Codex or Cursor in ~/Wiele/acme-coffee-social.

"Here are my notes from today's call with Piotr: Black Friday is 25% off beans and free shipping over 100 zł, no equipment discounts. Start the campaign."

The agent saves the notes as raw/2026-11/2026-11-18-call-with-piotr.md, writes docs/campaigns/2026-11-black-friday.md from the template in docs/README.md, adds idea posts for the campaign dates in content/2026-11/, and logs it:

wiele pull
wiele status
wiele push -m "Start the Black Friday campaign"

"Here's the Instagram export for November." (attach the CSV, or put it in raw/2026-11/)

The agent files it as raw/2026-11/2026-11-30-instagram-insights.csv, fills in Results in each post it covers, adds what it found to docs/learnings.md with the date and a link to the CSV, and pushes.

"Plan December. Four Instagram posts a week, one on LinkedIn."

The agent reads docs/, especially pillars.md and learnings.md, and November's posts, then writes December's idea posts with dates, pillars and a one-line brief each.

"Which posts are waiting for Piotr?"

grep -l "status: review" content/*/*.md

"What have we learned about reels this year?"

The agent answers from docs/learnings.md and the Results sections, citing files. On a large workspace it can use memory instead of reading everything.

Teammates and clients

Invite a teammate to the organization, then share the workspace:

wiele org invite anna@acme.example
wiele access invite anna@acme.example --path acme-coffee-social:/ --role write

Each person fetches the workspace and keeps it current:

wiele fetch acme-coffee-social:/ ~/Wiele/acme-coffee-social
wiele sync enable --directory ~/Wiele/acme-coffee-social

If an agency runs the account, the client can see the docs and posts without editing them:

wiele access invite owner@acme.example --path acme-coffee-social:/docs --path acme-coffee-social:/content --role read

Keep storage in check

Every saved version of a video counts toward storage. An owner or admin keeps fewer versions of assets/:

wiele workspace retention set /assets --workspace acme-coffee-social --keep-versions 5

See Versions, history and retention.

Optional: memory

The layout works without memory. If you turn it on, Wiele indexes the workspace and answers questions with citations, which helps once there are hundreds of posts and exports:

wiele memory enable --workspace acme-coffee-social
wiele memory answer "what is the Black Friday offer?" --workspace acme-coffee-social

The dates in file names, front matter and log headings let memory tell the newest value from older ones, so an offer that changed after a call comes back with the current value first. Memory costs credits; see Memory.

Use the layout for other projects

The same split works for most projects that collect knowledge and produce work: docs/ for what is true now, raw/ for what came in, log/ for what happened, and one folder for what the project produces, such as deliverables/, reports/ or specs/. The wiele-setup skill proposes that layout when you describe a different goal.