القائمة
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 ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 implementing inter-module communication in Logos. Covers LogosAPI::callModule(), LogosResult handling, dependency declaration in metadata.json, generated client stubs, and the QML bridge.
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 unit testing universal modules (direct impl class testing), logoscore integration tests, TEST_GROUPS, mock transport, 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.
| 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 -m ./test-modules -l <name> -c "<name>.someMethod(test)"
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/