菜单
Activate when packaging a Logos module or UI app for distribution as an LGX package. Covers lgx create, adding platform variants, verification, portable builds, and installation via lgpm.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Create a Logos full app — a combined module + UI app project in a single root directory
Activate when creating a new Logos module with the universal C++ interface. Covers scaffolding, metadata.json, flake.nix with code generator, CMakeLists.txt, and the pure C++ impl header.
Activate when configuring Nix flake.nix for a Logos module. Covers flake inputs, follows declarations, preConfigure for code generation, mkLogosModule, overrides for local development, and workspace integration.
Activate when writing tests for Logos modules. Covers the logos-test-framework (LOGOS_TEST macros, LogosTestContext, module mocking, C library mocking, event testing), logos_test() CMake integration, logoscore integration tests, and Nix check configuration.
Activate when wrapping an external C or C++ library as a Logos universal module. Covers external_libraries in metadata.json, flake input configuration, extern C includes, and the Go library special case.
Activate when registering a new module in the logos-workspace. Covers adding git submodules, flake.nix inputs with follows declarations, scripts/ws REPOS array, repo groups, and dep-graph.nix regeneration.
基于 SOC 职业分类
| name | package-lgx |
| description | Activate when packaging a Logos module or UI app for distribution as an LGX package. Covers lgx create, adding platform variants, verification, portable builds, and installation via lgpm. |
Use this skill when:
nix build
The built plugin is at ./result/lib/<name>_plugin.so (Linux) or ./result/lib/<name>_plugin.dylib (macOS).
lgx create <name>
This creates an empty <name>.lgx archive.
lgx add <name>.lgx -v linux-x86_64 -f ./result/lib/<name>_plugin.so
lgx add <name>.lgx -v darwin-arm64 -f ./result/lib/<name>_plugin.dylib
For directory variants (e.g., UI apps with multiple files):
lgx add <name>.lgx -v linux-x86_64 -f ./result/lib/ --main <name>_plugin.so -y
lgx verify <name>.lgx
Validates the package against the LGX specification.
# Install a single package
lgpm --modules-dir ./test-modules install --file <name>.lgx
# Install all packages in a directory
lgpm --modules-dir ./test-modules install --dir ./packages/
# List installed packages
lgpm --modules-dir ./test-modules list
# Get package info
lgpm --modules-dir ./test-modules info <name>
logoscore -D -m ./test-modules &
logoscore load-module <name>
logoscore call <name> someMethod test
logoscore stop
For distribution, ensure the shared library has no Nix store references:
# Build portable (self-contained)
nix build .#portable
# Or use nix-bundle-lgx for automated bundling
nix build .#bin-bundle-lgx
Verify no store references leaked:
rg /nix/store result/ && echo "FAIL: store refs found" || echo "OK: portable"
If the module's flake.nix includes nix-bundle-lgx as an input, it may provide automated packaging outputs:
nix build .#lgx-package
This produces a ready-to-distribute .lgx file with the correct platform variant.
lgpd search <query>
lgpd list --category <category>
lgpd download <name> -o ./packages/
lgpm --modules-dir ./modules install --dir ./packages/