skills.rest
humblemuzzu
humblemuzzuCOMMUNITY
Explore all skills by this author →
Website𝕏@devmuzzammilGitHub

amp-voice

Enforce Amp voice guidelines across technical writing tasks.

5|Updated Mar 10, 2026
Search Tags:#documentation#writing#consistency#tone#voice#style-guide#amp
One-click install
npx skills add https://github.com/humblemuzzu/ghosttyyy --skill amp-voice
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amp-voice
Source: https://github.com/humblemuzzu/ghosttyyy/tree/main/pi-setup/config-skills/amp-voice
Command: npx skills add https://github.com/humblemuzzu/ghosttyyy --skill amp-voice

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Amp voice guidelines help writers produce authoritative, direct, and consistent technical content about Amp, without marketing fluff or emoji.

Core Features & Use Cases

  • Guides consistent tone and terminology for amp-related documentation, threads, and discussions.
  • Helps with naming skills, tools, commands, or features in amp projects.
  • Enables quick compliance reviews to ensure text aligns with amp voice guidelines.
  • References a central terminology guide for extended examples.

Quick Start

Draft a short paragraph about Amp features using direct, technical, and honest voice.

Frequently Asked Questions about amp-voice

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

FAQPage Schema
How do I maintain a consistent technical tone across Amp documentation?▼

Maintain a consistent technical tone by enforcing direct, casual, and honest voice guidelines that eliminate marketing fluff and emojis across all Amp documentation, threads, and discussions, ensuring authoritative and uniform content.

What writing style should I use for Amp feature naming and threads?▼

Use a direct, technical, and honest writing style for Amp feature naming and threads, specifying lowercase usage and avoiding emojis. This casual yet authoritative approach aligns project communications with the Amp voice terminology guide.

Does the Amp voice style guide allow emojis in technical writing?▼

No, the Amp voice style guide does not allow emojis in technical writing. It specifies a direct, technical, and honest tone using lowercase text to ensure consistent, authoritative communication across all Amp-related content.

How do I review my technical writing for Amp voice compliance?▼

Review your technical writing for Amp voice compliance by checking for direct, casual, and technical tone, lowercase usage, and the absence of emojis. Reference the central Amp terminology guide to validate terminology and consistency.

What is the best way to draft technical content about Amp features?▼

The best way to draft technical content about Amp features is to use direct, technical, and honest language with lowercase text and no emojis. Following the Amp voice guidelines ensures your documentation avoids marketing fluff and remains authoritative.

Related Skills

Explore More Content & Communication Skills→
GroundMountCompanyGroundMountCompany

brand-voice

Extract or build a brand voice profile with tone, vocabulary, and rhythm rules.

Community
Intermediate
taracodlabstaracodlabs
779

file_operations

Create and validate Windows files with absolute paths and standardized naming.

Official
Intermediate
MercurykzMercurykz

docs-writer

Write and refine Markdown documentation to align with project style guides.

Community
Intermediate
ThejanaJayalathThejanaJayalath

brand-voice

Extract writing style patterns from source material into a reusable voice profile.

Community
Intermediate