If you're contributing to Angular's documentation, this is the rulebook you need loaded. It combines Google's technical writing standards with Angular's specific markdown extensions, so you'll know when to use `angular-ts` versus `ts`, how to add line highlighting and headers to code blocks, and which alert keywords (`NOTE:`, `TIP:`, `CRITICAL:`) render which styled blocks. The guide also covers custom components like `<docs-code>`, `<docs-card>`, and `<docs-workflow>` that are specific to the adev platform. Essentially, it keeps you from guessing or digging through existing docs to figure out the conventions. Load it before touching anything in `adev/src/content` and you'll write docs that match the rest of the Angular site.
npx skills add https://github.com/angular/angular --skill adev-writing-guide