CREATOR GUIDE

How to turn an idea into a reusable Asset

Building with MOOR means starting from a blank file or foundation, creating useful local work, testing it, packaging it as an Asset, and publishing only when you choose.

The MOOR creator workflow

1. Choose the capability.
   Define whether the idea should become an app, skill, script, template, dataset, or integration.
2. Start from a foundation.
   Use a reusable starting point when it saves work, or begin blank when the idea needs full control.
3. Create locally.
   Edit creator files immediately. Signing in should not be required merely to begin making something.
4. Test the result.
   Confirm the capability works, its dependencies are explicit, and its normal user experience hides unnecessary technical machinery.
5. Package the Asset.
   Give it identity, a version, compatibility information, requirements, exports, and extension points.
6. Publish intentionally.
   Connect an account when you want to release the Asset to the Marketplace. Published releases are treated as immutable records.

What makes a strong MOOR Asset?

A strong Asset solves one understandable problem, has one obvious primary action, uses explicit contracts, avoids unnecessary dependencies, and remains useful outside the context in which it was created.

Can Assets be remixed?

Yes. MOOR is designed around reusable foundations and creator work that can become something else. Ownership, installation, placement, and modification are separate concepts so each action stays understandable.

Can I build without publishing?

Yes. Local creation comes first. Publishing is an optional network capability, not the condition for making useful work.