Content Studio

For your AI

Share this page with Claude. It reads the definition below, creates the folders, instructions, tags, and starter notes in your account.

---
name: Content Studio
description: 'A content creation pipeline with a tone of voice guide, idea backlog,
  drafts folder, published archive, and channel playbooks. Everything your AI needs
  to write in your voice and publish to the right place.

  '
tags:
- blog
- thread
- newsletter
- draft
- published
containers:
- name: Content Studio
  description: Content creation pipeline from idea to publication
  llm_instructions: |
    This container is a content creation system with a clear pipeline: Ideas → Drafts → Published.
    - Before creating content, search within Content Studio for the note titled "Voice & Tone" and follow it.
    - Before creating content for a specific platform, read the matching note in Content Studio > Channels. If no matching channel note exists, use the Voice & Tone note and ask whether the user wants a reusable channel playbook created.
    - Search within this template before creating a new note. If an idea, draft, or published piece for the same topic and format already exists, update or move the existing note instead of creating a duplicate.
    - Use short, specific note titles that describe the piece clearly. Prefer formats like "Why SQLite Still Wins for SaaS" or "Thread: Why SQLite Still Wins for SaaS".
    - Tag every content note with exactly one format tag: blog, thread, or newsletter.
    - Tag drafts with "draft". Remove the "draft" tag and add "published" when a piece is published.
    - When the user shares a vague idea, capture it in Ideas with whatever context they give. Do not flesh it out into a full draft unless asked.
    - When the user asks to write or draft something, move or create it in Drafts and write a first version following the Voice & Tone note.
    - When repurposing content across channels, create a separate note per format (e.g., one blog post and one thread) rather than cramming everything into one note.
    - If the target channel or format is unclear, ask one concise question before writing.
  children:
  - name: Ideas
    description: Content ideas and topics to explore
    llm_instructions: |
      Use this folder as a backlog of content ideas.
      - Create a note here when the user mentions a topic, angle, or content idea.
      - Keep idea notes short: a title, the core angle or hook, the target audience, and why it matters. Do not write full drafts here.
      - Tag with the intended format (blog, thread, or newsletter) when known.
      - Tag with "draft" only when moved to Drafts. Ideas stay untagged with "draft".
      - If the user shares a link as inspiration, save it in source_url and note what caught their attention.
  - name: Drafts
    description: Content currently being written
    llm_instructions: |
      Use this folder for content being actively written or edited.
      - Move notes here from Ideas when the user starts writing.
      - When writing a first draft, follow the Voice & Tone note in the parent Content Studio folder.
      - Structure blog posts with: a hook or opening line, the core argument in short sections, and a clear ending or CTA.
      - Structure threads with: numbered tweets, one idea per tweet, a hook in tweet 1, a CTA in the last tweet.
      - Tag every draft with "draft" and the format tag.
      - When the user asks for edits, revise in place. Do not create a new note for each revision.
      - If the user pastes raw text or bullet points, reshape it into the right format rather than just storing the raw input.
  - name: Published
    description: Archive of published content with links
    llm_instructions: |
      Use this folder as an archive of published content.
      - Move notes here from Drafts when the user confirms a piece is published.
      - Add the published URL in source_url.
      - Remove the "draft" tag and add the "published" tag.
      - Do not edit published content unless the user explicitly asks.
      - If the user wants a revised version after publishing, create a new draft or clearly mark the note as an updated version instead of silently overwriting the archive.
  - name: Channels
    description: One note per publishing platform with format rules
    llm_instructions: |
      Use this folder to store one note per publishing channel.
      - Each channel note should cover: platform name, audience, format and length guidelines, posting cadence, and any platform-specific rules.
      - Before writing content for a channel, read that channel's note for format guidance.
      - When the user adds a new platform, create a new note rather than appending to an existing one.
  notes:
  - title: Voice & Tone
    body: |
      This note defines how all content from this studio should sound. Your AI reads this before writing anything.

      **Voice:** Direct. Opinionated. Short sentences. Say less, mean more.

      **Rules:**
      - Short sentences. If a sentence has a comma, try splitting it into two.
      - No jargon. If it needs a glossary, rewrite it.
      - Talk to one person. "You", not "users" or "teams".
      - Be opinionated. Say what you are not. Saying no is a feature.
      - Delete half of it. Then see if it still works. It usually does.
      - Show, don't tell. Use examples and screenshots over explanations.

      **Avoid:** "revolutionary", "game-changing", "powered by AI", "leverage", "unlock", "supercharge", startup jargon.

      **Structure:**
      - Lead with the hook. If someone reads only the first line, they should want to keep reading.
      - One idea per paragraph. One idea per tweet. One idea per section.
      - End with a clear next step, not a summary.

      Edit this note to match your own voice. These are starting defaults, not rules.
    tags:
    - blog
    container_path: Content Studio
  - title: Blog
    body: |
      **Platform:** Blog (your own site)
      **Audience:** People interested in your product or topic area.
      **Format:** 500-1500 words. Short paragraphs. Subheadings every 2-3 paragraphs.
      **Cadence:** Whatever you can sustain. One good post beats three mediocre ones.
      **Rules:**
      - Write the headline last. It should make someone click, not summarize the article.
      - Open with a story, a problem, or a bold statement. Not "In this post, I will..."
      - End with a CTA: try the product, read another post, or follow you somewhere.

      Edit this note to match your blog's specifics.
    tags:
    - blog
    container_path: Content Studio > Channels
  - title: X / Twitter
    body: |
      **Platform:** X (Twitter)
      **Audience:** Your niche community.
      **Format:** Single tweets (< 280 chars) or threads (5-10 tweets).
      **Cadence:** A few times per week. Threads perform better than single tweets.
      **Rules:**
      - Tweet 1 is the hook. If it doesn't stop the scroll, the thread is dead.
      - One idea per tweet. No walls of text.
      - End threads with a CTA: follow, try the product, read the blog post.
      - Be a person, not a brand. Share what you actually think.

      Edit this note to match your account and audience.
    tags:
    - thread
    container_path: Content Studio > Channels