executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
rust-bindingsGuides Rust ltp crate and ltp-cffi workflows for legacy CWS/POS/NER model loading, features, builds, and diagnostics.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill for native Rust or C workflows around LTP's legacy CWS/POS/NER implementation.
ltp, CWSModel, POSModel, NERModel, ModelSerde, Cargo features, or Rust examples.ltp-cffi, static/dynamic C library builds, C headers/symbols, or linking a C program to LTP.For Python ltp_extension wrappers, use ../legacy-extension/SKILL.md. For neural Python inference/training, use the Python sub-skills.
Run the static checker against a checkout or staged source tree:
python scripts/check_rust_layout.py --repo-root /path/to/ltp-checkout
It checks manifests, toolchain presence, feature hints, and optional legacy model files. It does not build by default.
For Rust model loading, enable required features:
[dependencies]
ltp = { version = "0.1", features = ["serialization", "parallel"] }
itertools = "0.14"
apache-avro = "0.18"
Use model files explicitly:
use std::fs::File;
use ltp::{CWSModel, POSModel, NERModel, ModelSerde, Format, Codec};
let cws: CWSModel = ModelSerde::load(File::open("cws_model.bin")?, Format::AVRO(Codec::Deflate))?;
Build ltp-cffi only after Rust and a C toolchain are intentionally available.
cargo/rustc and model files; the production environment that created this skill did not verify local Rust builds.