unicloud-common-module

To share common modules across uniCloud cloud functions, package reusable cloud function logic into a central, version-controlled repository under cloudfunctions/common. This enforces modular design, standardizes interfaces, and reduces code duplication across projects.

The best way to manage shared dependencies for uniCloud cloud functions is to upload and attach version-controlled common modules. This approach standardizes APIs and simplifies maintenance by centralizing shared utility code.

The common module structure in uniCloud requires a front-matter driven SKILL.md, an entry point script in each module, and optional directories for scripts, references, and assets to enforce standardized interfaces.

You need to create a public module for uniCloud when building multiple cloud functions that require shared utilities, dependency management, and consistent APIs across projects to reduce code duplication and simplify maintenance.

Yes, you can use common modules to standardize APIs across different uniCloud projects. By packaging shared utilities into a central repository, you encourage modular design and ensure consistent interfaces wherever the modules are attached.

A limitation of using common modules in uniCloud is that each module must strictly contain a front-matter driven SKILL.md and an entry point script. Without these required structural elements, the module cannot be properly published or attached.