Template Marketplace

The Template Marketplace is the Templates tab on the one StudioBrain Marketplace (/plugins/marketplace; /marketplace redirects there). Desktop, mobile, and cloud share that UI. Packs and individual templates install the same way.

Install and Activate write the template into the current project and ingest it as an entity type (ingest_template / ProjectStore.ingestTemplate). That is not a CORE 9-type inject, and it is not a “download only” marker. After ingest, schema.updated refreshes the sidebar on every surface without a manual reload.

Internal contract: plans/SBAI-8124-marketplace-object-install-contract.md and Marketplace Type Sync.

Template Marketplace Overview

What Can Be Shared

Any Template Pack that meets the eligibility criteria can be shared on the Marketplace:

Entity templates — YAML-based entity type definitions
Document templates — Rich-text document structures (scripts, chapters, etc.)
AI generation rules — YAML rule files included in the pack’s rules/ directory
Example entities — Sample markdown files in the pack’s examples/ directory

Eligibility Criteria

A Template Pack must meet these requirements before marketplace submission:

pack.json metadata file is complete (id, name, description, author, version, entity_types)
All referenced template files exist in the pack’s templates/ subdirectory
Templates use template_version: "2.0" or higher
No hardcoded absolute paths or machine-specific references
All category values are valid: entity, document, rule, or skill
At least one example entity file in examples/ (strongly recommended)

Available Plans

Feature	Free	Indie	Team	Enterprise
Install community packs	Yes	Yes	Yes	Yes
Publish packs	No	Yes	Yes	Yes
Private packs	No	No	Yes	Yes
Commercial licensing	No	No	No	Yes

Finding and Installing Templates

Browsing the Catalog

Open Settings → Plugins → Marketplace (or /plugins/marketplace) and use the Templates / Packs tabs. From there you can:

Browse official, community, and yours
Filter packs and individuals
Search by name, author, or entity type

Installing from Marketplace

Browse or search for a pack or individual template
Click Install on the card
After install, use Activate on types you want in the sidebar
Files land in the project store (_Templates/ on desktop; ProjectStore / R2 on cloud)
Other signed-in surfaces pick up the type via schema.updated (desktop pulls bytes; mobile refetches cloud)

Local Pack Installation

Until cloud marketplace browsing is available, packs can be installed locally by placing them in the correct directory:

_Templates/
  Packs/
    my-pack-name/
      pack.json
      templates/
        CHARACTER_TEMPLATE.md
        LOCATION_TEMPLATE.md
      examples/
        example_character.md
      rules/
        character_rules.yaml

StudioBrain discovers packs from _Templates/Packs/ automatically on startup. After placing a pack directory there, restart the backend service to pick up the new pack.

Activation Workflow

Activate on the Marketplace card is schema ingest for that template. It writes the type definition into the project and publishes schema.updated. The type appears in the sidebar after ingest — you do not need a separate Settings > Entity Types pass or a page refresh.

Rules, skills, layouts, canvas, and workflows install as their own kinds. They are not ingested as entity types. Workflows use workflow_definitions. Automation stays on /api/flows and is not a Marketplace tab.

Plan limits still apply to how many Standard types a project may activate.

Creating Marketplace-Ready Templates

Required Metadata Fields

Every template file in your pack must include these frontmatter fields:

---
template_version: "2.0"
id: "my_entity_type"
entity_type: "my_entity_type"
category: "entity"           # entity | document | rule | skill
description: "Short description of what this template is for"
created_date: "2025-01-01"
last_updated: "2025-01-01"
status: "active"
---

The pack.json metadata file must include:

{
  "id": "my-pack-unique-id",
  "name": "My Pack Name",
  "description": "What this pack provides and who it is for",
  "author": "Your Name or Organization",
  "version": "1.0.0",
  "entity_types": ["my_entity_type"],
  "categories": ["entity"],
  "tags": ["narrative", "rpg"],
  "icon": "icon.png"
}

Documentation Requirements

Before submitting, your pack should include:

A README.md in the pack root explaining the entity types and intended use
Inline comments in YAML frontmatter explaining non-obvious field choices
At least one complete example entity in examples/
A CHANGELOG.md for packs with multiple versions

Testing Guidelines

Before submitting your pack to the marketplace, verify:

The pack loads without errors (check backend logs on startup)
All entity types appear correctly in Settings > Templates
Creating a new entity with your template works end to end
Example entities import without validation errors
AI generation rules produce sensible output (if your pack includes rules)

To test locally, place your pack in _Templates/Packs/ and restart the backend. Use the Settings > Templates panel to verify the pack appears and its types can be activated.

Template Versioning

How Updates Work

Template Packs use semantic versioning (major.minor.patch). When an update is available on the marketplace:

Patch (1.0.0 → 1.0.1) — Bug fixes and minor improvements. Safe to auto-apply.
Minor (1.0.0 → 1.1.0) — New fields added. Existing entities are unaffected (new fields appear as empty). Review before applying.
Major (1.0.0 → 2.0.0) — Breaking changes. Fields renamed, removed, or retyped. Manual migration may be required.

Backward Compatibility

StudioBrain’s markdown-first architecture makes versioning safer than traditional database-driven apps:

Existing entity markdown files are not modified on template update
New fields appear as empty in the editor for existing entities
Removed fields disappear from the editor but remain in the markdown file (data is preserved)
Renamed fields require a migration step to copy values from the old field name to the new one

Update Distribution

When a pack update is released:

The marketplace notifies users with the pack installed
Review the changelog and migration notes
Click Update in Settings > Templates
For major updates, a migration wizard guides you through field mapping
After update, test with a sample entity before applying project-wide