// Update documentation after a source-tree move without breaking repo-root command guidance
{what this skill teaches agents}
Structure public Rust crate docs so docs.rs reads as both a quick-start guide and an API reference
Refactor Rust crates toward httprunner-style bounded-context directories with thin mod.rs facades.
Validate internal Rust module splits without accidentally treating them like feature work.
Automated workflow patterns for publishing Rust crates to crates.io from GitHub Actions, including version injection, token auth, and multi-crate dependency ordering.
Audit repo-wide source-tree relocations while preserving root entrypoints and catching hidden path-bearing surfaces.
| name | source-layout-doc-sweep |
| description | Update documentation after a source-tree move without breaking repo-root command guidance |
| domain | documentation |
| confidence | high |
| source | manual |
Use this when a repository reorganizes implementation code under new source folders but intentionally keeps root-invoked commands stable. It applies best to mixed-language repos where user docs, contributor docs, and agent instructions all describe paths differently.
src\rust, src\dotnet, src\VSCode) instead of relying on scattered path mentions.cargo, dotnet, or packaging commands moved too.target\debug / target\release if the root Cargo workspace still owns build output.Repository layout section to the root README.md.github\copilot-instructions.md to describe both moved source roots and unchanged repo-root commandssrc\dotnet\HttpGenerator\README.md → ../../../README.mddocs\index.html and docs\Marketplace.md with the same path vocabulary used in README.md