Template Studio

Template Studio

Purpose

Create one excellent editable template system, then compile channel-native packages without duplicating the design source or commercial truth.

When it fires

• A workflow, document, design system, website, application starter or deployment pattern should become a reusable template.
• A canonical template needs Notion, Canva, Figma, Framer, Webflow, Next.js, Vercel, Railway, Gumroad, Etsy or Creative Market packaging.
• A listed template needs compatibility, preview, documentation or clean-install maintenance.

Inputs

• Product manifest, exact source revision and canonical reference or specification.
• Template Studio task envelope with buyer job, customization boundary, token ceiling, target platforms, acceptance and stop conditions.
• Pinned design pack, dependency/license inventory, rights record and previous channel receipts.

Workflow

1. Resolve the product, repository, Template Studio pack, design authority and requested channel adapters from reviewed Registry state.
2. Bind one task envelope and one canonical editable source. Reject marketplace-first forks and private/customer data in template sources.
3. Define the buyer's starting state, completed result, installation or duplication path, editable zones, protected invariants and upgrade policy.
4. Assign product design, platform build, design-system review, channel compilation and independent verification to distinct owners.
5. Build the canonical source with examples, documentation, license, dependency policy, version metadata and a zero-secret configuration path.
6. Verify clean clone, install, duplicate, remix or import from a fresh environment. Test responsive, keyboard, screen-reader, contrast, reduced-motion, empty/error/recovery and export paths when applicable.
7. Compile each channel package using its adapter. Platform variants may alter packaging, metadata, preview dimensions and instructions, never core product identity, promise, price, license or rights.
8. Inspect every preview and deliverable, bind evidence to exact revisions, and issue a release receipt with compatibility and maintenance dates.

Output contract

Return canonical editable source, customization and installation documentation, clean-environment evidence, dependency/license inventory, channel packages, preview assets, maintenance policy, exact-revision release receipt and release decision.

Tools and MCP

Use GitHub for source and versioning; Figma for governed component and design-library authority; Canva for approved derivative templates; Notion for native workspace templates; Vercel and Railway for deployable starter evidence; browser verification for rendered platforms. Preserve native editable formats and export paths.

Quality bar

• A capable buyer can reach the promised result from a clean environment without hidden intervention.
• The source is editable, organized, documented, accessible and free of secrets or customer data.
• Previews truthfully represent the delivered version.
• Compatibility and maintenance ownership are explicit.
• Publication and pricing remain separate human-authorized gates.

Built on SIP — Starlight Intelligence Protocol Vertical: federated-product-studios · portable capability layer