playbooks

home / skills / sugarforever / 01coder-agent-skills / personal-writing-style

personal-writing-style skill

/skills/personal-writing-style

This skill ensures consistent personal writing style across content by applying punctuation, formatting, and tone guidelines during writing, translating, or

npx playbooks add skill sugarforever/01coder-agent-skills --skill personal-writing-style

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
1.7 KB
---
name: personal-writing-style
description: Personal writing style preferences. Reference this skill when writing, translating, or editing content to ensure consistent style, punctuation, and formatting.
---

# Personal Writing Style Guide

This skill defines personal writing style preferences, including punctuation, formatting, article structure, and tone conventions.

## Usage

Reference this skill when:
- Writing blog posts or articles
- Translating content
- Editing content for consistency
- Generating subtitles or captions

## Style Preferences

See `references/punctuation.md` for detailed punctuation rules.
See `references/article-structure.md` for article structure and heading conventions.

## Quick Reference

### Punctuation

| Element | Preferred | Avoid |
|---------|-----------|-------|
| Dash/破折号 | ` - ` (空格-连字符-空格) | `——` (中文破折号) |
| Ellipsis/省略号 | `......` (6个英文句点) | `……` (中文省略号) |
| **Quotes/引号** | `""` (中文弯引号) | `""` (英文直引号) |

⚠️ **Common Mistake**: Always use curved quotes `""` in Chinese body text. Straight quotes `""` are only for YAML/code.

### Article Structure

文章应该像自然对话一样流畅，而不是像教科书大纲那样机械。

- **结构隐于文中**：让内容本身传达层次，不靠编号、标签、"总结"等显式脚手架
- **用散文连接，不要硬切**：话题之间用过渡句桥接，写博客不是写论文

## Notes

- These preferences are personal style choices for consistent output
- Technical content (code, filenames) should use ASCII characters
- Markdown frontmatter should use straight quotes `"` for YAML syntax

Overview

This skill captures a personal writing-style guide to enforce consistent punctuation, formatting, and article structure across writing, translation, and editing tasks. It encodes preferences for punctuation symbols, quote behavior, and how to blend structure into natural prose. Use it as a reference to produce cohesive, reader-friendly content that follows these conventions.

How this skill works

When invoked, the skill inspects generated or edited text for adherence to the specified punctuation rules, quote styles, and formatting for technical elements. It flags and corrects common issues such as improper dash/ellipsis characters and ensures ASCII usage for code and filenames. It also guides article-level choices, favoring implicit structure and smooth transitions rather than explicit labeled scaffolding.

When to use it

  • Writing blog posts, articles, or long-form web copy
  • Translating content while preserving target-language typographic norms
  • Editing for consistent punctuation and formatting across a document
  • Generating subtitles, captions, or UI text that must match style rules
  • Preparing content that mixes prose with code or technical references

Best practices

  • Use spaced hyphen-minus for dashes (space - space) instead of language-specific em-dashes or double-character dash symbols
  • Represent ellipses as six ASCII periods (......) rather than single-language ellipsis glyphs
  • Use curved quotation marks in prose when the target language requires them; reserve straight quotes for YAML, code, and frontmatter
  • Keep technical elements (code, filenames, commands) in ASCII; avoid localized punctuation inside code blocks or filenames
  • Structure articles so hierarchy is implied by the prose and transitions; avoid explicit labels like 'summary' or numbered scaffolding

Example use cases

  • Translating a Chinese blog post while converting punctuation to preferred ASCII forms and curved quotes in body text
  • Editing a technical article to replace non-ASCII punctuation inside code blocks with ASCII equivalents
  • Generating captions that follow the ellipsis and dash conventions for consistent display across platforms
  • Writing an opinion piece where transitions and implied structure replace mechanical headings and lists

FAQ

Should straight quotes ever appear in prose?

No. Straight quotes are reserved for YAML, code, and frontmatter. Use curved quotes in body text when the language calls for them.

How to represent dashes and ellipses?

Use a spaced hyphen-minus for dashes (space - space) and six ASCII periods for ellipses (......). Avoid language-specific dash or ellipsis glyphs.