Adev Writing Guide

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.

skills.sh installs: 914
GitHub stars: 101.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add angular/angular --skill adev-writing-guide --agent claude-code

Installs into .claude/skills of the current project.

Files

Angular Documentation (adev) Writing Guide

This skill provides comprehensive guidelines for authoring content in adev/src/content. It combines Google's technical writing standards with Angular-specific markdown conventions, components, and best practices.

I. Google Technical Writing Guidelines

Tone and Content

Be conversational and friendly: Maintain a helpful yet professional tone. Avoid being overly casual.
Write accessibly: Ensure documentation is understandable to a diverse global audience, including non-native English speakers.
Audience-first: Focus on what the user needs to do, not just what the system does.
Avoid pre-announcing: Do not mention unreleased features or make unsupported claims.
Use descriptive link text: Link text should clearly indicate the destination (e.g., avoid "click here").