Agent skill · writing content · angular
adev-writing-guide
Comprehensive writing guide for Angular documentation (adev). Covers Google Technical Writing standards, Angular-specific markdown extensions, code blocks, and components. You MUST use this skill any time you plan to create, edit, or review documentation files in `adev/` or `adev/src/content`.
Why this skill is useful
Provides specific guidelines and standards for writing Angular documentation that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-04. 100,955 stars on the source repository.
What this skill does
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"). Language and Grammar Use second person ("you"): Address the reader directly. Prefer active voice: Clearly state who or what is performing the action (e.g., "The system generates a token" vs "A token is generated"). Standard American English: Use standard American spelling and punctuation. Conditional clauses first: Place "if" or "when" clauses before the instruction (e.g., "If you encounter an error, check the logs"). Define terms: Introduce new or unfamiliar terms/acronyms upon first use. Consistent terminology: Use the same term for the same concept throughout the document. Conciseness: Aim for one idea per sentence. Keep sentences short. Formatting and Organization Sentence case for headings: Capitalize only the first word and proper nouns in titles and headings. Lists: Numbered lists: Use for sequential steps or prioritized items. Bulleted lists: Use for unordered collections of items. Description lists: Use for term-definition pairs. Serial commas: Use the Oxford comma (comma before the last item in a list of three or more). Code formatting: Use code font for code-related text (filenames, variables, commands). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills angular/adev-writing-guide