@openpresentation/opf 0.1.0

package/dist/spec/catalogs/narratives/venture-pitch.json

@@ -0,0 +1,109 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "venture-pitch",
+  "name": "Venture Pitch",
+  "summary": "Series A/B fundraising arc structured around the canonical investor questions.",
+  "audienceFit": [
+    "investors",
+    "venture-capitalists",
+    "series-a",
+    "series-b"
+  ],
+  "durationRange": {
+    "minMinutes": 10,
+    "maxMinutes": 30
+  },
+  "tags": [
+    "startup",
+    "fundraising",
+    "pitch",
+    "investor",
+    "series-a"
+  ],
+  "beats": [
+    {
+      "id": "opening",
+      "name": "Opening",
+      "instructions": "Establish identity",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "purpose",
+      "name": "Purpose",
+      "instructions": "State your mission",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "problem",
+      "name": "Problem",
+      "instructions": "Present the challenge",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "solution",
+      "name": "Solution",
+      "instructions": "Propose your idea",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "why-now",
+      "name": "Why Now",
+      "instructions": "Explain timing importance",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "market-size",
+      "name": "Market Size",
+      "instructions": "Demonstrate potential",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "competition",
+      "name": "Competition",
+      "instructions": "Analyze competitive landscape",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "product",
+      "name": "Product",
+      "instructions": "Showcase features/benefits",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "business-model",
+      "name": "Business Model",
+      "instructions": "Detail revenue streams",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "team",
+      "name": "Team",
+      "instructions": "Highlight key members",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "financials",
+      "name": "Financials",
+      "instructions": "Show projections/needs",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "closing",
+      "name": "Closing",
+      "instructions": "Reinforce brand",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/weekly-progress.json

@@ -0,0 +1,103 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "weekly-progress",
+  "name": "Weekly Progress",
+  "summary": "Tight rhythm-of-business arc for weekly progress reports: objectives, achievements, progress, challenges, opportunities, recognition, plan, discussion, conclusion. Designed for fifteen-to-thirty-minute team check-ins, not deep dives.",
+  "audienceFit": [
+    "managers",
+    "teams",
+    "cross-functional-partners"
+  ],
+  "durationRange": {
+    "minMinutes": 15,
+    "maxMinutes": 30
+  },
+  "tags": [
+    "rhythm-of-business",
+    "weekly",
+    "internal",
+    "operations"
+  ],
+  "beats": [
+    {
+      "id": "opening",
+      "name": "Opening",
+      "description": "Open with the initiative name, the date, and the one-line headline for the week. Frame the meeting in fifteen seconds so the rest of the time is content.",
+      "layoutHint": "title-left",
+      "instructions": "Initiative name & date",
+      "slideType": "text"
+    },
+    {
+      "id": "objectives",
+      "name": "Objectives",
+      "description": "State what the team set out to do this week. Specific, measurable. The audience should be able to read this slide alone and know what 'on track' would mean.",
+      "instructions": "Set the expectations",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "achievements",
+      "name": "Achievements",
+      "description": "Celebrate the week's wins. Concrete, attributable, dated. Brevity here — the meeting is for what's next, not a victory lap.",
+      "instructions": "Celebrate success",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "overall-progress",
+      "name": "Overall Progress",
+      "description": "Evaluate performance against the objectives. Use a simple status indicator (green/yellow/red) plus the leading metric. Help the audience scan the state in seconds.",
+      "instructions": "Evaluate performance",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "challenges",
+      "name": "Challenges",
+      "description": "Address what's hard right now: blockers, slipping items, surfaced risks. Tie each challenge to either an owner working it or a discussion you want this week.",
+      "instructions": "Address difficulties",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "opportunities-for-improvement",
+      "name": "Opportunities for Improvement",
+      "description": "Surface where the team can level up. Process tweaks, tooling needs, ways of working. Improvement opportunities should feel like seeds, not corrections.",
+      "instructions": "Seek growth",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "highlights-recognition",
+      "name": "Highlights & Recognition",
+      "description": "Recognize specific contributions by name. Recognition belongs in the deck, not just in the meeting — written acknowledgment travels further than verbal.",
+      "instructions": "Appreciate efforts",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "goals-next-week",
+      "name": "Goals Next Week",
+      "description": "Plan the week ahead with three to five specific goals. Each should be small enough to finish, large enough to matter, and clearly owned.",
+      "instructions": "Plan ahead",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "discussion-feedback",
+      "name": "Discussion & Feedback",
+      "description": "Open the floor with two or three prompts — decisions you need, opinions you want, blockers you'd like cleared. End the recap actively.",
+      "instructions": "Encourage input",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "conclusion",
+      "name": "Conclusion",
+      "description": "Close with one line that motivates the team into the next week. Echo the headline so the meeting feels closed.",
+      "layoutHint": "title-left",
+      "instructions": "Recap & motivate",
+      "slideType": "text"
+    }
+  ]
+}

package/dist/spec/catalogs/purposes/align.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-purpose/v1",
+  "id": "align",
+  "name": "Align",
+  "summary": "Create shared understanding and commitment across people who need to move together.",
+  "description": "Use when stakeholders need a common view of goals, constraints, priorities, or responsibilities. Emphasize shared language, explicit tradeoffs, and next steps.",
+  "outcome": "Stakeholders leave with the same priorities and operating assumptions.",
+  "successCriteria": [
+    "Teams agree on priorities",
+    "Open disagreements are surfaced",
+    "Owners and next steps are clear"
+  ],
+  "recommendedNarratives": ["strategic-narrative", "transformation-arc", "business-review"],
+  "recommendedTones": ["conversational", "authoritative"],
+  "tags": ["alignment", "strategy", "coordination"]
+}

package/dist/spec/catalogs/purposes/decide.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-purpose/v1",
+  "id": "decide",
+  "name": "Drive a Decision",
+  "summary": "Frame options, evidence, tradeoffs, and a recommendation so the audience can choose.",
+  "description": "Use when the deck exists to get a yes/no, select among options, approve a recommendation, or resolve ambiguity. Lead with the decision needed and make the ask explicit.",
+  "outcome": "The audience makes or authorizes a clear decision.",
+  "successCriteria": [
+    "Decision owner understands the options",
+    "Recommendation and tradeoffs are explicit",
+    "The final ask is concrete"
+  ],
+  "recommendedNarratives": ["scqa", "board-meeting", "project-proposal"],
+  "recommendedTones": ["formal", "authoritative", "persuasive"],
+  "tags": ["decision", "recommendation", "approval"]
+}

package/dist/spec/catalogs/purposes/educate.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-purpose/v1",
+  "id": "educate",
+  "name": "Educate",
+  "summary": "Teach a concept, process, product, or domain so the audience can use it correctly.",
+  "description": "Use when the primary job is learning. Structure around concepts, examples, practice, and checks for understanding rather than persuasion or reporting.",
+  "outcome": "The audience understands the material well enough to apply it.",
+  "successCriteria": [
+    "Definitions and examples are clear",
+    "Audience can apply the concept",
+    "Complexity builds progressively"
+  ],
+  "recommendedNarratives": ["educate", "focus", "company-intro"],
+  "recommendedTones": ["conversational", "technical"],
+  "tags": ["learning", "training", "enablement"]
+}

package/dist/spec/catalogs/purposes/index.json

@@ -0,0 +1,61 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-purpose-index/v1",
+  "version": "1",
+  "description": "Catalog of presentation purposes available in the openpresentation.org catalog. Each entry is a lightweight summary; full purpose records live in the per-id JSON files alongside this index. Purposes are referenced from OPF documents via purpose.",
+  "records": [
+    {
+      "id": "inform",
+      "name": "Inform",
+      "summary": "Give the audience clear context, facts, or status without asking for a decision.",
+      "file": "inform.json"
+    },
+    {
+      "id": "decide",
+      "name": "Drive a Decision",
+      "summary": "Frame options, evidence, tradeoffs, and a recommendation so the audience can choose.",
+      "file": "decide.json"
+    },
+    {
+      "id": "align",
+      "name": "Align",
+      "summary": "Create shared understanding and commitment across people who need to move together.",
+      "file": "align.json"
+    },
+    {
+      "id": "persuade",
+      "name": "Persuade",
+      "summary": "Change belief or win support for a specific argument, idea, or recommendation.",
+      "file": "persuade.json"
+    },
+    {
+      "id": "educate",
+      "name": "Educate",
+      "summary": "Teach a concept, process, product, or domain so the audience can use it correctly.",
+      "file": "educate.json"
+    },
+    {
+      "id": "report",
+      "name": "Report",
+      "summary": "Summarize performance, progress, or findings with enough context to interpret results.",
+      "file": "report.json"
+    },
+    {
+      "id": "pitch",
+      "name": "Pitch",
+      "summary": "Present an opportunity and ask for investment, approval, partnership, or sponsorship.",
+      "file": "pitch.json"
+    },
+    {
+      "id": "sell",
+      "name": "Sell",
+      "summary": "Move a buyer or evaluator toward purchase, adoption, renewal, or expansion.",
+      "file": "sell.json"
+    },
+    {
+      "id": "plan",
+      "name": "Plan",
+      "summary": "Establish a roadmap, operating plan, or sequence of actions with owners and next steps.",
+      "file": "plan.json"
+    }
+  ]
+}

package/dist/spec/catalogs/purposes/inform.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-purpose/v1",
+  "id": "inform",
+  "name": "Inform",
+  "summary": "Give the audience clear context, facts, or status without asking for a decision.",
+  "description": "Use when the deck needs to make the audience aware of current state, background, or findings. Prioritize clarity, completeness, and accurate framing over persuasion.",
+  "outcome": "The audience understands the situation and can repeat the important facts.",
+  "successCriteria": [
+    "Audience can summarize the key facts",
+    "No immediate decision is required",
+    "Follow-up questions are about implications, not basic context"
+  ],
+  "recommendedNarratives": ["status-update", "focus", "educate"],
+  "recommendedTones": ["formal", "conversational"],
+  "tags": ["awareness", "context", "status"]
+}

package/dist/spec/catalogs/purposes/persuade.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-purpose/v1",
+  "id": "persuade",
+  "name": "Persuade",
+  "summary": "Change belief or win support for a specific argument, idea, or recommendation.",
+  "description": "Use when the audience may be skeptical or undecided. Build a crisp thesis, support it with evidence, address objections, and end with a clear action.",
+  "outcome": "The audience accepts the argument or supports the recommendation.",
+  "successCriteria": [
+    "Main thesis is memorable",
+    "Evidence supports the argument",
+    "Likely objections are handled"
+  ],
+  "recommendedNarratives": ["problem-solution", "persuasive-sales", "golden-circle"],
+  "recommendedTones": ["persuasive", "authoritative"],
+  "tags": ["argument", "support", "belief-change"]
+}

package/dist/spec/catalogs/purposes/pitch.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-purpose/v1",
+  "id": "pitch",
+  "name": "Pitch",
+  "summary": "Present an opportunity and ask for investment, approval, partnership, or sponsorship.",
+  "description": "Use when the deck needs to create interest and move a high-stakes audience toward backing the opportunity. Lead with the opportunity, prove credibility, and make the ask concrete.",
+  "outcome": "The audience agrees to invest, sponsor, approve, or continue the conversation.",
+  "successCriteria": [
+    "Opportunity is clear",
+    "Evidence builds confidence",
+    "Ask and next step are explicit"
+  ],
+  "recommendedNarratives": ["pitch-deck", "venture-pitch", "golden-circle"],
+  "recommendedTones": ["persuasive", "authoritative", "inspirational"],
+  "tags": ["fundraising", "opportunity", "ask"]
+}

package/dist/spec/catalogs/purposes/plan.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-purpose/v1",
+  "id": "plan",
+  "name": "Plan",
+  "summary": "Establish a roadmap, operating plan, or sequence of actions with owners and next steps.",
+  "description": "Use when the deck should turn strategy into coordinated action. Make sequencing, ownership, dependencies, risks, and checkpoints visible.",
+  "outcome": "The audience understands the plan and accepts the next actions.",
+  "successCriteria": [
+    "Milestones and owners are clear",
+    "Dependencies and risks are visible",
+    "Next steps can be executed"
+  ],
+  "recommendedNarratives": ["project-proposal", "capacity-planning", "strategic-advisory"],
+  "recommendedTones": ["authoritative", "technical"],
+  "tags": ["roadmap", "execution", "planning"]
+}

package/dist/spec/catalogs/purposes/report.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-purpose/v1",
+  "id": "report",
+  "name": "Report",
+  "summary": "Summarize performance, progress, or findings with enough context to interpret results.",
+  "description": "Use for business reviews, project updates, research summaries, and recurring operating cadences. Prioritize the metric, the movement, the reason, and the implication.",
+  "outcome": "The audience understands what happened, why it happened, and what it means.",
+  "successCriteria": [
+    "Key metrics are easy to scan",
+    "Variance and drivers are explained",
+    "Implications are explicit"
+  ],
+  "recommendedNarratives": ["qbr", "business-review", "status-update", "survey-analysis"],
+  "recommendedTones": ["formal", "technical"],
+  "tags": ["performance", "progress", "findings"]
+}

package/dist/spec/catalogs/purposes/sell.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-purpose/v1",
+  "id": "sell",
+  "name": "Sell",
+  "summary": "Move a buyer or evaluator toward purchase, adoption, renewal, or expansion.",
+  "description": "Use for customer-facing decks where the goal is commercial movement. Focus on pain, value, proof, differentiation, and the next buying step.",
+  "outcome": "The buyer advances to the next step in the commercial process.",
+  "successCriteria": [
+    "Customer pain is named clearly",
+    "Value is tied to customer outcomes",
+    "Next commercial step is clear"
+  ],
+  "recommendedNarratives": ["persuasive-sales", "problem-solution", "challenge-resolution"],
+  "recommendedTones": ["persuasive", "conversational"],
+  "tags": ["sales", "customer", "commercial"]
+}

package/dist/spec/catalogs/social-platforms/bluesky.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-social-platform/v1",
+  "id": "bluesky",
+  "name": "Bluesky",
+  "summary": "Decentralized microblog network built on the AT Protocol.",
+  "description": "Bluesky handles are domain-style ('alice.bsky.social'). Profile URLs use the form 'https://bsky.app/profile/<handle>'. Renderers should pass the handle through unchanged.",
+  "baseUrl": "https://bsky.app",
+  "profileUrlPattern": "https://bsky.app/profile/{handle}",
+  "handlePrefix": "",
+  "handleExample": "alice.bsky.social",
+  "brandColor": "#1185FE",
+  "tags": ["microblog", "decentralized", "atproto"]
+}
+

package/dist/spec/catalogs/social-platforms/facebook.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-social-platform/v1",
+  "id": "facebook",
+  "name": "Facebook",
+  "summary": "General-purpose social network from Meta.",
+  "baseUrl": "https://facebook.com",
+  "profileUrlPattern": "https://facebook.com/{handle}",
+  "companyUrlPattern": "https://facebook.com/{handle}",
+  "handlePrefix": "",
+  "handleExample": "acme",
+  "brandColor": "#1877F2",
+  "tags": ["general", "brand"]
+}
+

package/dist/spec/catalogs/social-platforms/github.json

@@ -0,0 +1,15 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-social-platform/v1",
+  "id": "github",
+  "name": "GitHub",
+  "summary": "Code-hosting platform for developers and organizations.",
+  "description": "GitHub uses the same URL pattern for users and organizations ('/<handle>'). Use the companyUrlPattern for organization references for symmetry with platforms that distinguish.",
+  "baseUrl": "https://github.com",
+  "profileUrlPattern": "https://github.com/{handle}",
+  "companyUrlPattern": "https://github.com/{handle}",
+  "handlePrefix": "",
+  "handleExample": "alicechen",
+  "brandColor": "#181717",
+  "tags": ["developer", "code"]
+}
+

package/dist/spec/catalogs/social-platforms/index.json

@@ -0,0 +1,68 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-social-platform-index/v1",
+  "version": "1",
+  "description": "Catalog of social-media platforms available in the openpresentation.org catalog. Each entry is a lightweight summary; full platform records live in the per-id JSON files alongside this index. The property keys of any Socials object on Organization or Speaker resolve to ids in this catalog.",
+  "records": [
+    {
+      "id": "linkedin",
+      "name": "LinkedIn",
+      "summary": "Professional social network for individuals and companies.",
+      "file": "linkedin.json"
+    },
+    {
+      "id": "x",
+      "name": "X",
+      "summary": "Real-time microblog for news, opinions, and discussion. Formerly Twitter.",
+      "file": "x.json"
+    },
+    {
+      "id": "github",
+      "name": "GitHub",
+      "summary": "Code-hosting platform for developers and organizations.",
+      "file": "github.json"
+    },
+    {
+      "id": "youtube",
+      "name": "YouTube",
+      "summary": "Video-sharing platform with creator and brand channels.",
+      "file": "youtube.json"
+    },
+    {
+      "id": "instagram",
+      "name": "Instagram",
+      "summary": "Photo and short-form video network from Meta.",
+      "file": "instagram.json"
+    },
+    {
+      "id": "facebook",
+      "name": "Facebook",
+      "summary": "General-purpose social network from Meta.",
+      "file": "facebook.json"
+    },
+    {
+      "id": "tiktok",
+      "name": "TikTok",
+      "summary": "Short-form video network with strong recommendation feed.",
+      "file": "tiktok.json"
+    },
+    {
+      "id": "threads",
+      "name": "Threads",
+      "summary": "Text-first social network from Meta, integrated with Instagram identity.",
+      "file": "threads.json"
+    },
+    {
+      "id": "mastodon",
+      "name": "Mastodon",
+      "summary": "Decentralized microblog network across federated instances.",
+      "file": "mastodon.json"
+    },
+    {
+      "id": "bluesky",
+      "name": "Bluesky",
+      "summary": "Decentralized microblog network built on the AT Protocol.",
+      "file": "bluesky.json"
+    }
+  ]
+}
+

package/dist/spec/catalogs/social-platforms/instagram.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-social-platform/v1",
+  "id": "instagram",
+  "name": "Instagram",
+  "summary": "Photo and short-form video network from Meta.",
+  "baseUrl": "https://instagram.com",
+  "profileUrlPattern": "https://instagram.com/{handle}",
+  "handlePrefix": "@",
+  "handleExample": "@acme",
+  "brandColor": "#E4405F",
+  "tags": ["photo", "video", "lifestyle"]
+}
+

package/dist/spec/catalogs/social-platforms/linkedin.json

@@ -0,0 +1,15 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-social-platform/v1",
+  "id": "linkedin",
+  "name": "LinkedIn",
+  "summary": "Professional social network for individuals and companies.",
+  "description": "LinkedIn distinguishes between member profiles ('/in/<handle>') and company pages ('/company/<handle>'). Renderers should pick the appropriate URL pattern based on whether the parent is an Organization or a Speaker.",
+  "baseUrl": "https://linkedin.com",
+  "profileUrlPattern": "https://linkedin.com/in/{handle}",
+  "companyUrlPattern": "https://linkedin.com/company/{handle}",
+  "handlePrefix": "",
+  "handleExample": "alice-chen",
+  "brandColor": "#0A66C2",
+  "tags": ["professional", "default"]
+}
+

package/dist/spec/catalogs/social-platforms/mastodon.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-social-platform/v1",
+  "id": "mastodon",
+  "name": "Mastodon",
+  "summary": "Decentralized microblog network across federated instances.",
+  "description": "Mastodon profiles are instance-scoped: the canonical URL form is '<instance>/@<handle>' (e.g. https://hachyderm.io/@acme). The catalog cannot fix a single base URL — store full URLs as values, or '@<handle>@<instance>' as the rendered handle. The profileUrlPattern below is illustrative and assumes mastodon.social as a fallback.",
+  "baseUrl": "https://mastodon.social",
+  "profileUrlPattern": "https://mastodon.social/@{handle}",
+  "handlePrefix": "@",
+  "handleExample": "@alice@hachyderm.io",
+  "brandColor": "#6364FF",
+  "tags": ["microblog", "decentralized", "fediverse"]
+}
+

package/dist/spec/catalogs/social-platforms/threads.json

@@ -0,0 +1,13 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-social-platform/v1",
+  "id": "threads",
+  "name": "Threads",
+  "summary": "Text-first social network from Meta, integrated with Instagram identity.",
+  "baseUrl": "https://threads.net",
+  "profileUrlPattern": "https://threads.net/@{handle}",
+  "handlePrefix": "@",
+  "handleExample": "@alicechen",
+  "brandColor": "#000000",
+  "tags": ["microblog", "text"]
+}
+

package/dist/spec/catalogs/social-platforms/tiktok.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-social-platform/v1",
+  "id": "tiktok",
+  "name": "TikTok",
+  "summary": "Short-form video network with strong recommendation feed.",
+  "description": "TikTok profiles are addressable as '@<handle>'. The handlePrefix is '@' and is included in the URL.",
+  "baseUrl": "https://tiktok.com",
+  "profileUrlPattern": "https://tiktok.com/@{handle}",
+  "handlePrefix": "@",
+  "handleExample": "@acme",
+  "brandColor": "#010101",
+  "tags": ["video", "short-form"]
+}
+

package/dist/spec/catalogs/social-platforms/x.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-social-platform/v1",
+  "id": "x",
+  "name": "X",
+  "summary": "Real-time microblog for news, opinions, and discussion. Formerly Twitter.",
+  "description": "X uses a single profile URL pattern for both individuals and organizations. Handles are conventionally rendered with an '@' prefix.",
+  "baseUrl": "https://x.com",
+  "profileUrlPattern": "https://x.com/{handle}",
+  "handlePrefix": "@",
+  "handleExample": "@alicechen",
+  "brandColor": "#000000",
+  "tags": ["microblog", "news", "default"]
+}
+