General Rust advice is wrong here in specific, checkable ways, and an agent working from memory applies it anyway. The `rust-skills` corpus is 265 rules written against edition 2024; this workspace is edition 2021, and its unwrap, unsafe, profile and dependency rules are each superseded by a repo gate that says something different. `rust-coding` is the overlay that selects the rules a diff actually touches and reconciles each one against those gates before anything changes — it is not a second copy of the corpus. Wired end to end rather than dropped in: the role map in `check-project-skills-core.mjs`, `skills/manifest.json`, the routing table in `drive-meridian-maturity`, the README index, and symlinks from all three runtime trees back to the canonical `skills/` directory. `just check-skills` asserts every one of those, so a skill that is present but unrouted fails. `skills-lock.json` records the corpus's upstream source and content hash, so the rules being reconciled against are identifiable rather than whatever was last fetched. Signed-off-by: Joshua Belke <joshua@innovationhub-act.org>
11 lines
258 B
JSON
11 lines
258 B
JSON
{
|
|
"version": 1,
|
|
"skills": {
|
|
"rust-skills": {
|
|
"source": "leonardomso/rust-skills",
|
|
"sourceType": "github",
|
|
"skillPath": "SKILL.md",
|
|
"computedHash": "9719e9ebd94783d3436ed26156bf9bf2e4c7f63b3220d9d17ff90cba55c92bb8"
|
|
}
|
|
}
|
|
}
|