agentleFS
Sign inStart free
Starlight-IntelligenceStarlight-Intelligence/starlight-agent-skills/skills/studios/template-studio/SKILL.md

template-studio

Skill1 starsChanged 4 months agoMITView on GitHub

Build editable, installable and commercially licensable Notion, Canva, Figma, Framer, Webflow, Next.js, Vercel, Railway and workflow templates from one canonical source. Use when a reusable template or marketplace-ready derivative needs clean-install proof, design review and platform-specific packaging.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 11
  2. Very specific:

    Verify clean clone, install, duplicate, remix or import from a fresh environment.

    line 32
  3. Distinctive:

    Use GitHub for source and versioning.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free