Skip to content
Engines of
Creation
Create
Back to the marketplace

THE CREATOR GUIDE

Make something
someone can build on.

A good pack solves one clear problem. A movement mechanic, a set of UI assets, a repeatable skill. Give it a useful name, include the source, and show someone how to use it.

Start with a working example

Download an EoC pack and use its structure as a reference. The launch collection is curated by the EoC team; community uploads and paid listings are not open yet. This guide helps you prepare a portable pack you can share yourself.

Explore the RPG interface kit

Keep the package simple

my-pack/
  README.md       What it does and how to use it
  LICENSE         Your license and any required credits
  manifest.json   Name, version, type, compatibility
  src/            Editable source or original assets
  example/        A small working demonstration

For a skill, include a SKILL.md with a name, description, clear steps, and a way to check the result. For assets, specify formats, dimensions or scale, and usage rights.

Before you share

  • Explain exactly what is included and what someone still needs to set up.
  • List the engine or runtime, required dependencies, and versions you tested.
  • Use original work or files you have permission to redistribute. Include attribution and license notices.
  • Keep credentials and private project data out of every file.
  • Try the pack in a clean project. Include a small example and a short verification checklist.
  • State any network requests, account requirements, or ongoing costs.

Design for the handoff

Write a short request a creator can give their AI builder: what to add, which files to read, what to preserve, and how to verify it. Let the creator review the proposed changes before applying them.

For a current project, the EoC documentation covers editing, previewing, and checking your work.