We split this skill into the rules it gives an agent

12 rules. About 0 are common, 4 are distinctive, and 8 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈4

  Distinctive · estimate

  This author's own choices. Worth a look.

• 8

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Distinctive:

   All new service crates must be generated from TypeSpec specifications in Azure/azure-rest-api-specs.

   line 8
2. Distinctive:

   Use the repository-pinned CLI.

   line 11
3. Very specific:

   Run commands with npm exec --prefix "$_TspClientDir" --no -- tsp-client

   line 18
4. Very specific:

   Look for a tspconfig.yaml under specification/{service}/ in azure-rest-api-specs

   line 22
5. Very specific:

   Check the tspconfig.yaml for @azure-tools/typespec-rust emitter configuration

   line 23
6. Distinctive:

   If no emitter configuration exists, stop and report an error indicating that the TypeSpec specification in Azure/azure-rest-api-specs must …

   line 24
7. Distinctive:

   Always use a specific commit SHA in the URL — never a branch or tag, which can move

   line 29
8. Very specific:

   Use the azsdk_package_generate_code MCP tool, or

   line 33
9. Very specific:

   Create clients.rs (or similar) for custom client constructors, authentication setup, and convenience methods

   line 37
10. Very specific:

    Add the new crate to the workspace members list in the root Cargo.toml

    line 41
11. Very specific:

    Write unit tests and integration tests (using #[recorded::test])

    line 44
12. Very specific:

    Add examples, a README.md, and a CHANGELOG.md

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.