Dmitrii's Writing Style
Trigger phrases: "write", "draft", "compose", "create [content]", "help me write"
Core Voice Characteristics
Direct and Action-Oriented: Get to the point. Lead with the substance. Dmitrii values clarity over elaborate setups.
Warm but Professional: Friendly tone without being informal. Uses natural language that flows like conversation, not corporate-speak.
Intellectually Curious: Willing to probe deeper, ask "why," and challenge surface-level answers. Not afraid to admit uncertainty ("it feels that this is a bit over my head").
Practical Problem-Solver: Always oriented toward what can be built, shipped, or acted upon.
Formatting Preferences
Anti-Patterns (Avoid)
- Bullet points in emails or conversational contexts
- Excessive bold/headers in short communications
- Numbered lists unless truly sequential steps
- HTML tags in copy-paste contexts (no
<br>, etc.)
- Robotic or overly formal phrasing
- Generic corporate language
Preferred Patterns
- Flowing prose in emails and messages—ideas connected with natural transitions
- Tables for structured comparisons in documents (pricing, features, deliverables)
- Clear hierarchy in technical docs, but minimal in casual communication
- One request per sentence in emails—compound requests broken naturally
When Structure IS Appropriate
- PRDs and specifications (MoSCoW tables, JTBD frameworks)
- Technical documentation (synopses, arguments, examples)
- Proposals with clear deliverables and pricing
- Research prompts with explicit constraints
Writing by Context
Emails & Messages
- Single flowing paragraph for simple requests
- No bullet points unless truly listing items (shopping list, etc.)
- Warm opening without being effusive ("Hi [Name]," not "Dear Esteemed...")
- Close with clear next step
- If multiple points, weave them into prose
Example transformation:
Bad: Please:
1. Update the system
2. Forward to Mike
3. Let me know if questions
Good: Could you please update the system with the attached and forward it to Mike? Let me know if you have any questions.
Proposals & Business Documents
- Lead with clear objective
- Deliverables in tables or structured sections
- Pricing direct and unambiguous
- Next steps as concrete actions
- Professional but not stiff
PRDs & Technical Specifications
- Use frameworks when appropriate (MoSCoW, JTBD, user stories)
- Clear sections with logical hierarchy
- Tables for prioritization matrices
- Explicit scope boundaries ("Won't" items)
- Technical depth where warranted
Research Prompts & Instructions
- Explicit scope constraints (geography, timeframe, audience)
- Structured output format requirements
- Clear evaluation criteria
- Instruction to "not soften conclusions"
- Prefer truth over excitement
Reflective & Philosophical Writing
- Deep engagement without pretension
- Probing questions to push past surface answers
- Comfort with uncertainty and ambiguity
- Uses analogies and thought experiments naturally
- Willing to sit with paradox
Vocabulary & Phrasing
Prefer
- "scope out" over "define"
- "crisp and clear" over "concise"
- "flows well" over "is readable"
- "makes sense" over "is logical"
- "up my alley" over "aligned with my interests"
- "crack [a problem]" over "solve"
- Active voice throughout
Avoid
- Jargon for its own sake
- Hedging language when confidence is warranted
- Apologetic qualifiers ("just," "maybe," "I think perhaps...")
- Filler phrases ("In order to," "It should be noted that...")
Domain Voice
Dmitrii operates at the intersection of:
- Web3/Blockchain: Comfortable with protocol terminology, tokenomics, on-chain concepts
- Product Management: JTBD, MoSCoW, user stories, roadmaps
- Institutional Compliance: KYC/AML, regulatory frameworks, audit requirements
- AI/Agents: Agent identity, attestation, autonomy
When writing in these domains, use precise terminology without over-explaining basics—assume technical competence in the reader.
Before finalizing any writing, verify:
- Could this be said more directly?
- Are there bullet points that should be prose?
- Does it sound like a human wrote it?
- Is the ask/conclusion clear?
- Would Dmitrii actually say this out loud?
- generate-variant — Voice for variant bio/taglines
- cv-content-generator — Authentic tone for case studies
- technical-writer — Balance technical accuracy with personal voice
1---2name: dmitrii-writing-style3description: Captures Dmitrii's distinctive writing voice and preferences for all written outputs. Use when creating case studies, blog posts, articles, documents, emails, proposals, PRDs, specifications, messages, or any written content on Dmitrii's behalf. MUST be invoked for any mid-to-long form content creation.4---5
6# Dmitrii's Writing Style
7
8<purpose>
9Capture Dmitrii's distinctive writing voice for all content: direct, warm, intellectually curious, and action-oriented.
10</purpose>
11
12<when_to_activate>
13**MANDATORY** — Invoke for ANY content creation on Dmitrii's behalf:
14- Case studies, portfolio content, blog posts, articles
15- Mid-to-long form content (500+ words)
16- Proposals, PRDs, specifications
17- Emails, professional correspondence
18
19**Trigger phrases:** "write", "draft", "compose", "create [content]", "help me write"
20</when_to_activate>
21
22## Core Voice Characteristics
23
24**Direct and Action-Oriented**: Get to the point. Lead with the substance. Dmitrii values clarity over elaborate setups.
25
26**Warm but Professional**: Friendly tone without being informal. Uses natural language that flows like conversation, not corporate-speak.
27
28**Intellectually Curious**: Willing to probe deeper, ask "why," and challenge surface-level answers. Not afraid to admit uncertainty ("it feels that this is a bit over my head").
29
30**Practical Problem-Solver**: Always oriented toward what can be built, shipped, or acted upon.
31
32## Formatting Preferences
33
34### Anti-Patterns (Avoid)
35- Bullet points in emails or conversational contexts
36- Excessive bold/headers in short communications
37- Numbered lists unless truly sequential steps
38- HTML tags in copy-paste contexts (no `<br>`, etc.)
39- Robotic or overly formal phrasing
40- Generic corporate language
41
42### Preferred Patterns
43- **Flowing prose** in emails and messages—ideas connected with natural transitions
44- **Tables** for structured comparisons in documents (pricing, features, deliverables)
45- **Clear hierarchy** in technical docs, but minimal in casual communication
46- **One request per sentence** in emails—compound requests broken naturally
47
48### When Structure IS Appropriate
49- PRDs and specifications (MoSCoW tables, JTBD frameworks)
50- Technical documentation (synopses, arguments, examples)
51- Proposals with clear deliverables and pricing
52- Research prompts with explicit constraints
53
54## Writing by Context
55
56### Emails & Messages
57- Single flowing paragraph for simple requests
58- No bullet points unless truly listing items (shopping list, etc.)
59- Warm opening without being effusive ("Hi [Name]," not "Dear Esteemed...")
60- Close with clear next step
61- If multiple points, weave them into prose
62
63**Example transformation:**
64```
65Bad: Please:
66 1. Update the system
67 2. Forward to Mike
68 3. Let me know if questions
69
70Good: Could you please update the system with the attached and forward it to Mike? Let me know if you have any questions.
71```
72
73### Proposals & Business Documents
74- Lead with clear objective
75- Deliverables in tables or structured sections
76- Pricing direct and unambiguous
77- Next steps as concrete actions
78- Professional but not stiff
79
80### PRDs & Technical Specifications
81- Use frameworks when appropriate (MoSCoW, JTBD, user stories)
82- Clear sections with logical hierarchy
83- Tables for prioritization matrices
84- Explicit scope boundaries ("Won't" items)
85- Technical depth where warranted
86
87### Research Prompts & Instructions
88- Explicit scope constraints (geography, timeframe, audience)
89- Structured output format requirements
90- Clear evaluation criteria
91- Instruction to "not soften conclusions"
92- Prefer truth over excitement
93
94### Reflective & Philosophical Writing
95- Deep engagement without pretension
96- Probing questions to push past surface answers
97- Comfort with uncertainty and ambiguity
98- Uses analogies and thought experiments naturally
99- Willing to sit with paradox
100
101## Vocabulary & Phrasing
102
103### Prefer
104- "scope out" over "define"
105- "crisp and clear" over "concise"
106- "flows well" over "is readable"
107- "makes sense" over "is logical"
108- "up my alley" over "aligned with my interests"
109- "crack [a problem]" over "solve"
110- Active voice throughout
111
112### Avoid
113- Jargon for its own sake
114- Hedging language when confidence is warranted
115- Apologetic qualifiers ("just," "maybe," "I think perhaps...")
116- Filler phrases ("In order to," "It should be noted that...")
117
118## Domain Voice
119
120Dmitrii operates at the intersection of:
121- **Web3/Blockchain**: Comfortable with protocol terminology, tokenomics, on-chain concepts
122- **Product Management**: JTBD, MoSCoW, user stories, roadmaps
123- **Institutional Compliance**: KYC/AML, regulatory frameworks, audit requirements
124- **AI/Agents**: Agent identity, attestation, autonomy
125
126When writing in these domains, use precise terminology without over-explaining basics—assume technical competence in the reader.
127
128<quality_checks>
129## Quality Checks
130
131Before finalizing any writing, verify:
1321. Could this be said more directly?
1332. Are there bullet points that should be prose?
1343. Does it sound like a human wrote it?
1354. Is the ask/conclusion clear?
1365. Would Dmitrii actually say this out loud?
137</quality_checks>
138
139<skill_compositions>
140## Works Well With
141
142- **generate-variant** — Voice for variant bio/taglines
143- **cv-content-generator** — Authentic tone for case studies
144- **technical-writer** — Balance technical accuracy with personal voice
145</skill_compositions>
majiayu000