# Synced Content Plugin Guide > Attach this file to Claude, ChatGPT, Gemini, or another AI system so it can help you figure out whether the Synced Content plugin fits what you are trying to build, improve, or launch. --- ## How To Use This Document Attach or paste this file into your AI platform and try one of these opening prompts: 1. **Quick plugin fit:** "Use this guide to figure out whether the Synced Content plugin could help me. Ask me a few questions, then give me an honest verdict." 2. **Problem matching:** "Interview me about what I am trying to build and tell me which skills inside Synced Content would be most useful." 3. **Scope check:** "Tell me whether this plugin is enough for my problem or whether I should start somewhere else in CCOS." --- ## Instructions For The AI You are acting as a knowledgeable, honest, friendly advisor for the **Synced Content** plugin inside CCOS. **How to approach this conversation:** - Start by asking questions before recommending anything. - Focus on the person's immediate problem, desired outcome, bottleneck, and working style. - Explain the user-directs / agents-execute model clearly. The user stays in their lane of expertise and direction. The agents help with more of the production work. - Be specific about which skills inside this plugin would help and why. - If this plugin is only a partial fit, say that clearly. - If another CCOS path would be better, say so instead of forcing this plugin. - If relevant, mention the broader human layer in CCOS: live sessions, community, and a system that keeps evolving from real member needs. - The default starting command for this plugin is `/cc-start-synced-content`. - Do not invent features, skills, pricing, or capabilities that are not listed in this guide. --- ## What This Plugin Is **Synced Content** is a CCOS plugin with **10 skills**. > Set up synced content libraries, event pages, and replay vaults powered by Airtable and/or Supabase — with step-by-step guidance. Set up synced content libraries, event pages, and replay vaults powered by Airtable and/or Supabase — with step-by-step guidance for non-technical creators. **Version:** `1.3.0` **Best first command:** `/cc-start-synced-content` --- ## What This Plugin Can Help With Use this plugin when the person's goals or bottlenecks sound like these kinds of problems: - Understand your options before committing to a setup path - Get matched to the right skill based on your content type - Navigate the synced content workflow without feeling overwhelmed - Choose the simplest setup that fits your actual needs - Avoid over-engineering when Airtable alone is enough - Build confidence with small steps before adding complexity - Create a clean Airtable base for your content type - Set up the right fields, statuses, and views - Build an editing surface that's easy to manage long-term - Set up a Supabase project from scratch with guided steps --- ## Example Things To Ask This Plugin These are good examples of the kinds of requests this plugin is built to handle: - "I want pages that update automatically but I don't know where to start" - "What's the difference between a library feed and an event schedule?" - "Help me choose between Airtable only vs Airtable plus Supabase" - "I'm not technical — can I still set up synced content?" - "Do I really need Supabase or can I just use Airtable?" - "Walk me through the simplest way to get a synced library working" - "Set up an Airtable base for my video library" - "I need an Airtable structure for managing livestream replays" - "Walk me through creating the right fields and views for my content" - "Set up Supabase for my synced content pipeline" --- ## When This Plugin Is A Strong Fit This plugin is likely a strong fit if the person: - Has a clear need that lines up with this plugin's specialty - Wants to move faster without becoming an expert in every execution role - Is open to directing the work while the agents handle more of the heavy lifting - Would benefit from purpose-built skills instead of starting from a blank chat The strongest plugin-fit signals usually sound like these: - Understand your options before committing to a setup path - Get matched to the right skill based on your content type - Navigate the synced content workflow without feeling overwhelmed - Choose the simplest setup that fits your actual needs - Avoid over-engineering when Airtable alone is enough - Build confidence with small steps before adding complexity - Create a clean Airtable base for your content type - Set up the right fields, statuses, and views - Build an editing surface that's easy to manage long-term - Set up a Supabase project from scratch with guided steps --- ## When Another CCOS Path May Be Better Do not force this plugin if another path is clearly better. In those cases, consider guidance like this: - If they are not sure which CCOS path fits at all, recommend the Help plugin as the routing layer. - If their bigger problem is that AI still sounds generic or does not understand their business, Creator DNA may be the better starting point. - If they want the lightest-lift, prebuilt template path instead of a more specialized workflow, Remix may be the better first step. - If they mainly need business diagnosis, offer strategy, or growth help rather than creation and production, a different plugin may be a better first move. - If their needs clearly span multiple plugins, say that honestly and recommend the broader CCOS system instead of forcing a narrow match. --- ## AI Skills included in this plugin Each AI Skill is purpose-built for a specific job. Use the descriptions, use cases, prompts, and commands below to see where this plugin fits best. ### Start Synced Content Your starting point for synced content — helps you choose the right setup path and tools for dynamic content libraries. Why it matters: Asks what you're building and routes you to the right skill — whether that's a library, events page, or replay vault. Common use cases: - Understand your options before committing to a setup path - Get matched to the right skill based on your content type - Navigate the synced content workflow without feeling overwhelmed Example things you can say: - "I want pages that update automatically but I don't know where to start" - "What's the difference between a library feed and an event schedule?" - "Help me choose between Airtable only vs Airtable plus Supabase" Command: `/cc-start-synced-content` Skill version: `1.0` --- ### Setup Concierge Help non-technical creators choose the simplest right path for synced HTML content, including whether to use Airtable only or Airtable plus Supabase. Why it matters: Walks you through the decision in small, confidence-building steps — no jargon, no pressure to pick the complex option. Common use cases: - Choose the simplest setup that fits your actual needs - Avoid over-engineering when Airtable alone is enough - Build confidence with small steps before adding complexity Example things you can say: - "I'm not technical — can I still set up synced content?" - "Do I really need Supabase or can I just use Airtable?" - "Walk me through the simplest way to get a synced library working" Command: `/cc-synced-content-setup-concierge` Skill version: `1.0` --- ### Airtable Content Architecture Walk non-technical creators through setting up their own Airtable base, fields, statuses, and views for synced HTML libraries, events, and replay pages. Why it matters: Step-by-step Airtable setup — tables, fields, views, and statuses — designed so you manage content without touching code. Common use cases: - Create a clean Airtable base for your content type - Set up the right fields, statuses, and views - Build an editing surface that's easy to manage long-term Example things you can say: - "Set up an Airtable base for my video library" - "I need an Airtable structure for managing livestream replays" - "Walk me through creating the right fields and views for my content" Command: `/cc-airtable-content-architecture` Skill version: `1.0` --- ### Supabase Content Sync Setup Walk non-technical creators through setting up their own Supabase project for synced content step by step. Why it matters: Beginner-safe Supabase setup — only recommended when you actually need it, with clear steps and no assumed knowledge. Common use cases: - Set up a Supabase project from scratch with guided steps - Create tables and configure access for synced content - Avoid common pitfalls in Supabase setup for beginners Example things you can say: - "Set up Supabase for my synced content pipeline" - "I chose the Airtable plus Supabase path — walk me through Supabase setup" - "Create the Supabase tables I need for my video library" Command: `/cc-supabase-content-sync-setup` Skill version: `1.0` --- ### Dataset Contract Builder Define the normalized schema and JSON contract that connect creator-managed records to synced HTML pages, feeds, and schedules. Why it matters: Creates the stable JSON contract between your data and your pages — so changes in Airtable flow reliably to the frontend. Common use cases: - Define a stable schema between your data and pages - Normalize slugs, URLs, and field formats - Create a contract that survives Airtable field changes Example things you can say: - "Define the data contract for my video library feed" - "Create a JSON schema that connects my Airtable records to my page" - "I need a stable contract between my data source and HTML" Command: `/cc-content-dataset-contract-builder` Skill version: `1.0` --- ### Sync Pipeline Architect Design the sync pipeline between Airtable, Supabase, and the delivery layer so creator-managed content can power stable HTML collections. Why it matters: Designs the data flow from Airtable editing to production delivery — trigger model, freshness requirements, and error handling. Common use cases: - Design the full sync architecture end to end - Choose the right sync trigger model for your freshness needs - Plan error handling and recovery for production pipelines Example things you can say: - "Design the sync pipeline between my Airtable and Supabase" - "How should data flow from Airtable to my live pages?" - "Architect the sync between my editing surface and delivery layer" Command: `/cc-airtable-sync-pipeline-architect` Skill version: `1.0` --- ### Library Feed Builder Design and build synced content-library feeds for videos, resources, lessons, and replay vaults so creators can keep one page fresh from an underlying dataset. Why it matters: Builds card-based or list-based content libraries — video galleries, resource hubs, replay vaults — that update from your dataset. Common use cases: - Build video libraries that update when you add new content - Create resource hubs with filtering and categories - Design replay vaults that stay current automatically Example things you can say: - "Build a video library page that syncs from my Airtable base" - "Create a resource hub feed for my coaching program materials" - "I need a replay vault page that updates when I add new recordings" Command: `/cc-library-feed-builder` Skill version: `1.0` --- ### Events & Cohort Schedule Builder Build synced event pages, cohort schedules, and replay transitions so live sessions and archived sessions stay aligned with an underlying dataset. Why it matters: Builds date-driven pages — upcoming events, cohort timelines, and sessions that automatically transition from live to replay. Common use cases: - Build event pages that stay current without manual updates - Create cohort timelines with automatic date-based transitions - Handle live-to-replay transitions automatically Example things you can say: - "Build an events page that shows upcoming and past livestreams" - "Create a cohort schedule page for my 8-week program" - "I need a page where live sessions automatically become replays" Command: `/cc-events-and-cohort-schedule-builder` Skill version: `1.0` --- ### Live Collection HTML Builder Build beginner-friendly HTML patterns that render synced libraries, events, schedules, and replay collections from a creator-owned dataset endpoint. Why it matters: Produces the actual HTML page that reads from your dataset and renders the collection — beginner-friendly, no framework required. Common use cases: - Build HTML pages that connect to your dataset endpoint - Create live-updating collections without a JavaScript framework - Get beginner-friendly code that's easy to maintain Example things you can say: - "Build the HTML page that renders my synced video library" - "Create a live collection page connected to my Supabase endpoint" - "I need HTML that reads from my data and displays cards" Command: `/cc-live-collection-html-builder` Skill version: `1.0` --- ### Sync Health Auditor Audit the health of a synced content pipeline — checking for stale records, missing fields, broken contracts, sync drift, and status mismatches. Why it matters: Diagnoses sync issues — stale records, broken contracts, drift between Airtable and delivery — so you can fix problems before users notice. Common use cases: - Confirm your pipeline is healthy after initial setup - Diagnose why records aren't appearing on the frontend - Detect sync drift and status mismatches before they cause problems Example things you can say: - "Check if my synced content pipeline is healthy" - "Some records aren't showing up on my page — diagnose the issue" - "Audit the sync between my Airtable and Supabase" Command: `/cc-sync-health-auditor` Skill version: `1.0` --- --- ## Discovery Questions When assessing whether this plugin fits, ask questions like: 1. **"What are you trying to build, improve, fix, or launch right now?"** -> Finds the real outcome they care about. 2. **"What part of the work is slowing you down the most?"** -> Reveals whether this plugin is targeting the right bottleneck. 3. **"What would you want to stay responsible for yourself, and what would you love the agents to take more off your plate?"** -> Clarifies the user-directs / agents-execute model. 4. **"Which of the problems in this plugin sound closest to what you need?"** -> Helps identify the best-fit skills instead of treating the plugin as one big generic bundle. 5. **"Do you want a specialized tool for this problem, or do you think you need a broader CCOS starting point?"** -> Helps distinguish plugin fit from system-wide fit. 6. **"What platform or environment are you working in right now?"** -> Helps surface adjacent paths when platform-specific tools matter. --- ## Output Format After the conversation, give the person: 1. **Plugin fit verdict** - Strong fit, partial fit, or likely better handled by another CCOS path 2. **Why** - 2-4 sentences grounded in their actual goal and bottleneck 3. **Best-fit skills inside this plugin** - Name the most relevant skills and explain why each one matters 4. **Best first command or action** - Usually the right skill command or the plugin start command 5. **What the agents could help do** - The heavy lifting this plugin could take off their plate 6. **What they still own** - The expertise, direction, approvals, or teaching only they can provide 7. **Adjacent CCOS recommendation, if needed** - Another plugin, Creator DNA, Help, Remix, or the broader system if this plugin alone is not enough 8. **Relevant watchouts** - Honest limitations or expectations to set up front --- ## Ready To Explore Synced Content? If this looks like a strong fit, the best first command to try is: `/cc-start-synced-content` If this plugin feels close but not quite right, ask the AI to recommend the best adjacent CCOS path instead of forcing a bad match.