docs(documentation): require official service terminology

- Require current vendor product names and capitalization
- Add correct Amazon VPC and AWS Lambda examples
- Prevent mechanical naming-prefix substitutions

Author: d-padmanabhan

skills/documentation-standards/SKILL.md

@@ -23,6 +23,7 @@ description: >-
 - **No AI slop** - remove filler, keep docs concrete and task-oriented
 - **No em dashes/en dashes** - use hyphens (`-`) instead
 - **Clickable navigation** - if readers may want to open a repo file, directory, section, ADR, rule, skill, script, workflow, or config, make it a Markdown link. Use backticks only when the path is a literal value, not a navigation target.
+- **Official terminology** - use each vendor's current official product and service names, capitalization, and branding. Verify uncertain names against current vendor documentation. For example, write **Amazon VPC**, not **AWS VPC**; write **AWS Lambda**, not **Amazon Lambda**. Do not apply one naming prefix mechanically across a provider's services.
 
 ## Voice