Loment-Lang
@Loment-Lang Organization
Public Skills
loment
by Loment-Lang
Read this before writing a program in Loment - FujoOS's own systems language (Rust-flavoured surface syntax plus capability domains; six more surface grammars - C, C++, Java, C#, Go, Python - share its semantics, see docs/188). With the toolchain installed you can write, check and compile native executables with no Python runtime. Use it for: writing a Loment program or a .lomt file; writing a Loment library (a library is a directory, dependencies are the use lines in the source, exports are pub, optional pkg.lomp manifest, see section 9); managing or debugging dependencies; compiling or running with the loment command; reading the E001-E036 error codes; looking up a builtin or a piece of syntax (loment builtins / loment syntax / loment cheat); expressing a piece of logic in the project's own language; how to write struct / enum / match / capability / guard; giving a project its own source extension (source_ext in loment.conf, section 7.1); registering a custom loment subcommand (loment foo runs loment-foo from PATH, section 7.2); and what differs when migrating from another language. For anything about libraries and dependencies read the lompi guide first (~/.claude/skills/lompi/SKILL.md, or <prefix>/share/lompi/skill/SKILL.md when you only have the package) - installing a library, resolving dependencies, which libraries exist on this machine, and what a use <name> resolves to all live there. Also use this whenever the task is to author, read or debug Loment source (.lomt / .lom / .lomp) or a Loment library with the toolchain installed.
lompi
by Loment-Lang
Use when managing Loment libraries with lompi, the package manager that ships with the Loment toolchain (a library is a directory; identity is a content hash; dependencies are the use lines in source). Triggers: installing, listing, or verifying a third-party Loment library / building or maintaining a package store / finding out which Loment libraries exist on this machine, or what a store contains / locating a library's source to read its pub fn surface / finding out what a library depends on / producing or checking a lockfile / debugging "missing dependency", "dependency cycle", or "lock does not match store" / questions about how packages are installed in Loment, which version gets picked, or whether two versions can coexist / mapping concepts over from pip, npm, or cargo. Also use for anything involving a Loment package store, lompi.lock, deps/, instance identity, or resolving .lomt library dependencies.