Don Corleone Writing Style

Security

Rewrite or draft text in a formal, measured, and decisive patriarchal style emphasizing respect, loyalty, clear terms, and reciprocal favors for authoritativ...

Install

openclaw skills install don-corleone-writing-style

Don Corleone (Godfather)-inspired writing style

Goal

Turn the user's text into a voice that sounds like a respected patriarch:

Calm authority (measured cadence, no frantic tone)
Respect and obligation (loyalty/favors as a framing device)
Decisive terms (clear requirements, deadlines, or next step)
Controlled pressure (firm boundaries, implied consequences without threats)

Online-informed style traits

Apply these traits consistently:

Soft-spoken command: short, deliberate lines that still control the room.
Formal respect markers: use "respect", "family", "loyalty", "trust", "honor" naturally and sparingly.
Favors as social contract: frame help as reciprocal obligation, not charity.
Measured restraint: avoid rage language; prefer poise, patience, and inevitability.
Traditional hierarchy cues: prioritize duty, order, and clear roles.

Non-negotiables (guardrails)

Do not copy dialogue or quotes from The Godfather.
No explicit violence. If pressure is requested, convert it into firm consequences (process, timelines, escalation).
No harassment, hate, or criminal instructions. Keep it professional.

Anti-AI-tells guardrails (from Wikipedia)

When rewriting/drafting, avoid patterns common in AI text (see Wikipedia:Signs of AI writing) such as:

Promotional puffery (prefer specific terms and requirements).
Vague attribution (avoid "experts say", "it is believed" unless the user provided sources).
Outline-like wrap-ups (avoid "in conclusion" / "overall" restating the thesis).
Template-y negation patterns like "Not X, but Y" or repetitive "not ... but ..." structures.
Excessive em-dashes and curly quote characters; prefer plain punctuation.
AI vocabulary stacking and "Additionally/Furthermore/Moreover/Notably" chains.

Workflow (use every time)

Clarify the objective: grant a favor, refuse a request, negotiate terms, or set expectations.
Pick the stance:
- Grant: "I will do this. Here is the condition."
- Refuse: "No. Here is the real constraint."
- Negotiate: "Here are the terms. Choose the path."
- Correct: "Explaining is not fixing. Do this instead."
Keep it tight:
- 1 to 3 short paragraphs, or about 6 to 12 lines total.
- Use short sentences. Cut filler.
Add obligation framing:
- Name what is owed (time, effort, cooperation, honesty).
- Name what you require to proceed (deadline, approval path, deliverable).
- Where suitable, frame it as a favor with reciprocal duty.
Add one authority device:
- A clear rhetorical question, or
- A clean pivot line ("Then you handle the rest."), or
- A short rule-of-the-house statement ("We do it in writing.").
Land the ending:
- A single next step with a deadline or decision request.

Language rules

Do

Use formal, direct language: "I need", "You will", "Send", "Decide".
Use boundaries: "That does not work", "I am not available for this".
Use terms: "by Friday", "in writing", "single owner", "one approval path".
Use respectful tone even when denying.

Avoid

Hedging: "maybe", "kind of", "I think", "just", "hopefully".
Rambling context dumps. Frame the request instead.
Over-the-top swagger. One strong line is enough.

Output formats

1) Rewrite (same meaning, new voice)

Return:

Don Corleone-style rewrite (just the rewritten text)
One-line rationale (max 1 sentence) describing the main change (tone, structure, terms)

2) Draft from scratch (user gives scenario)