Skip to content
Back to skills

Specify Preferred Writing Style

ASecurity

Define writing tone, information density, and sentence style with concrete examples.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 22, 2026
ai-agentsgo

Works with

  • cursor
  • cli

Security analysis

A100/100

Scanned October 22, 2026

npx -y skills add alivirgo/Major-AI-Skills --skill specify-preferred-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Specify Preferred Writing Style?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Specify Preferred Writing Style
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/alivirgo-specify-preferred-writing-style/badge)](https://www.skillsdirectory.com/skills/alivirgo-specify-preferred-writing-style)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: specify-preferred-writing-style
description: "Define writing tone, information density, and sentence style with concrete examples."
category: common-sense
risk: safe
source: self
source_type: self
date_added: "2026-08-26"
tags: ["writing-style", "tone-matching", "copywriting", "style-presets", "communication", "prompt-engineering"]
tools: ["claude", "cursor", "gemini", "codex", "chatgpt"]
---

# Specify Preferred Writing Style (The 3D Style Matrix) (AI Skill)

## Overview
Asking an AI to *"write in a professional style"* almost always produces robotic, passive corporate jargon filled with meaningless phrases (*"In order to optimize synergistic alignment..."*). 

The **3D Style Matrix Protocol** decomposes style into **3 Concrete Levers**: **Tone** (warmth/authority), **Information Density** (words per insight), and **Sentence Cadence** (sentence length variety).

---

## The 3-Dimensional Style Framework

```
┌─────────────────────────────────────────────────────────────┐
│                 The 3D Style Control Levers                 │
│                                                             │
│  LEVER 1: TONE            ──► Casual Peer vs. Formal Senior │
│  LEVER 2: DENSITY         ──► High (Facts/words) vs. Sparse │
│  LEVER 3: CADENCE         ──► Short punchy vs. Flowing prose│
└─────────────────────────────────────────────────────────────┘
```

---

## The 5 Standard Professional Style Presets

Select one of these presets to instantly lock in the desired voice:

### Preset 1: The Pragmatic Practitioner (Engineering & Tech)
```markdown
Style Directive:
- Tone: Candid, direct, pragmatic - like a senior engineer writing notes for a peer.
- Density: High. Use exact CLI commands, code snippets, and error logs.
- Cadence: Active verbs, short sentences. Ban all corporate fluff and marketing adjectives.
```

---

### Preset 2: The Executive Decision Brief (Leadership)
```markdown
Style Directive:
- Tone: Authoritative, objective, decision-focused.
- Density: Extreme. Bottom Line Up Front (BLUF) followed by 3 bold supporting metrics.
- Cadence: Bulleted structures and comparative tables over long paragraphs.
```

---

### Preset 3: The Conversational Peer (Team & Slack)
```markdown
Style Directive:
- Tone: Warm, approachable, human, slightly humorous.
- Density: Moderate.
- Cadence: Conversational rhythms. Mix short 3-word sentences with natural spoken phrasing.
```

---

### Preset 4: The Direct-Response Copywriter (Sales & Landing Pages)
```markdown
Style Directive:
- Tone: Empathetic, urgent, benefits-focused.
- Density: High focus on customer pain and quantified relief.
- Cadence: Punchy, rhythmic, single-sentence paragraphs with frictionless CTAs.
```

---

### Preset 5: The Socratic Educator (Tutorials & Onboarding)
```markdown
Style Directive:
- Tone: Encouraging, patient, structured.
- Density: Gradual. Start with a real-world physical analogy before introducing technical syntax.
- Cadence: Step-by-step numbered breakdown with 1 check-for-understanding question.
```

---

## Real-World Comparison

### Scenario: Explaining Why We Delayed a Software Deployment

#### Vague Prompt ("Make it professional")
> *"Please be advised that due to unforeseen operational technicalities encountered during our comprehensive quality assurance staging pipeline, the leadership team has decided to strategically postpone the deployment..."*
> ❌ *(Stiff, impersonal, reads like a legal disclaimer).*

#### Using Preset 1: Pragmatic Practitioner
> *"We postponed today's billing release because our staging load tests showed payment webhooks failing on 4% of orders. Deploying broken billing on a Friday is an unforced error. The queue bug is isolated, and we will deploy Tuesday morning at 9 AM after verification."*
> ✅ *(Clear, accountable, direct).*

---

## Summary Best Practices
- **Never use "Professional" alone**: Replace it with *"Executive Brief"* or *"Pragmatic Practitioner"*.
- **Specify the Banned Clichés**: Always add *"Ban 'delve', 'tapestry', 'crucial', and 'game-changer'"*.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.