adev-writing-guide

Guide Angular documentation authoring with Google technical writing standards and markdown extensions.

Updated Apr 6, 2025

Search Tags:#documentation #angular #technical-writing #markdown-extensions #component-guidelines #google-writing-guidelines #adev

Ready to run

npx skills add https://github.com/Monosen/golink --skill adev-writing-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adev-writing-guide
Source: https://github.com/Monosen/golink/tree/main/.agents/skills/adev-writing-guide
Command: npx skills add https://github.com/Monosen/golink --skill adev-writing-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

Google Technical Writing Guidelines: tone, accessibility, audience-first language, and clear, actionable instructions.
Angular Documentation Specifics: Markdown extensions, component usage patterns, and consistent formatting for Angular content.
Collaboration & Review: templates and checklists to streamline authoring and peer review in the adev project.

Quick Start

Consult this guide whenever you author or review content in adev/src/content to ensure Google-style technical writing and Angular-specific documentation practices.

Frequently Asked Questions about adev-writing-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are the Google technical writing guidelines for Angular documentation?▼

Google technical writing guidelines for Angular documentation enforce a defined tone, audience-first language, and clear, actionable instructions to ensure content accessibility and consistency across the adev project.

How do I use Angular markdown extensions and components in adev?▼

To use Angular markdown extensions in adev, follow the centralized writing guide which provides specific component usage patterns and formatting rules for authoring content in adev/src/content.

What is the best way to review Angular technical writing for consistency?▼

The best way to review Angular technical writing for consistency is to use provided templates and checklists that streamline peer review and enforce Google-style technical writing standards in the adev project.

Can I use standard markdown for adev content without specific component guidelines?▼

Standard markdown alone is insufficient for adev content; the project requires specific Angular markdown extensions and component usage patterns to maintain proper documentation structure and consistency.

Does the adev writing guide support audience-first language formatting?▼

The adev writing guide supports audience-first language formatting by enforcing clear language style and formatting rules, ensuring technical documentation remains accessible and actionable for its intended readers.