docs(skills): apply technical writing style

src/skills/style/build/SKILL.md

@@ -5,5 +5,5 @@ description: Use when creating, editing, or reviewing Bazel `BUILD` files or Rus
 
 # build-style
 
-Use this skill as the source of truth for Bazel `BUILD` files and Rust `Cargo.toml` package manifests.
+Use this skill for Bazel `BUILD` files and Rust `Cargo.toml` package manifests.
 Follow the shared style skill instructions in `src/skills/style/STYLE.md`.

src/skills/style/build/rules/dependencies.md

@@ -12,7 +12,7 @@ Add package-local dependency features only when the feature set is specific to t
 ### Rationale
 
 The repository has one Cargo workspace and one `Cargo.lock`.
-Centralized dependency versions keep package manifests consistent with the workspace lockfile.
+Centralized versions keep package manifests consistent with the workspace lockfile.
 
 ## Declare Rust dependencies in each build system
 
@@ -27,4 +27,4 @@ Apply this rule to `rust_library`, `rust_binary`, and `rust_test` targets.
 ### Rationale
 
 Cargo and Bazel resolve Rust dependencies independently.
-Complete declarations keep `cargo check`, Rust Analyzer, and Bazel builds consistent.
+Complete declarations keep Cargo, Rust Analyzer, and Bazel builds consistent.

src/skills/style/build/rules/tests.md

@@ -9,7 +9,7 @@ Do not add `[[test]]` entries to `Cargo.toml` unless the operator explicitly req
 
 ### Rationale
 
-Bazel is the source of truth for Rust test targets in this repository.
+This repository declares Rust test targets in Bazel.
 Keeping test declarations in Bazel avoids duplicate test target lists.
 
 ## Use one source input style per `rust_test`