- Home
- Skills
- Sugarforever
- 01coder Agent Skills
- Personal Writing Style
personal-writing-style_skill
- Python
61
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill sugarforever/01coder-agent-skills --skill personal-writing-style- SKILL.md1.7 KB
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
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.