labali-blog-writing-style
Use this skill when writing or revising blog articles for the user's personal blog in the user's established voice.
Runtime Inputs
- Target article path or article topic.
- User intent: new draft, rewrite, refine, shorten, or expand.
- Existing article text when revising.
- Optional constraints such as word count, article type, or sections to preserve.
Core Goal
Preserve the author's voice and judgment style while improving article quality.
The target result is:
- sounds like the author,
- keeps the original article's core meaning,
- has clearer structure than many older posts,
- reads like a finished article rather than scattered notes.
NEVER
- Never produce fragmented bullet piles as the primary structure — use paragraphs as the default form.
- Never stack sections without transitions (note-like accumulation of disconnected blocks).
- Never use weak hierarchy where all headings carry the same visual weight regardless of content importance.
- Never output AI-style abstraction drift: phrases like "it's important to note that", "in conclusion", or "overall, this demonstrates".
- Never switch the output language to English unless the user explicitly requests it.
Mode × Subtype Routing
Use this table to determine which file sections to load in Phase 2.
Mode → workflow section in references/workflow.md
| Mode |
Section to load |
| new draft |
## 1. New Article Workflow |
| rewrite |
## 2. Rewrite Existing Article Workflow |
| partial refinement |
## 3. Partial Refinement Workflow |
| shorten |
## 4. Structure Rules (no dedicated section — use structure rules as guide) |
| expand |
## 4. Structure Rules (no dedicated section — use structure rules as guide) |
Subtype → skeleton section in assets/article-structure.md
| Subtype |
Section to load |
| technical summary |
## Subtype: Technical Summary |
| troubleshooting / postmortem |
## Subtype: Troubleshooting / Postmortem |
| workplace reflection |
## Subtype: Workplace Reflection |
| reading note / idea note |
## Subtype: Reading Note / Idea Note |
Execution Contract
Phase 1 — Inversion (gather before generating)
DO NOT proceed to Phase 2 until all required inputs are known.
Ask the user for any missing required inputs:
- Mode (required): new draft, rewrite, partial refinement, shorten, or expand.
- Subtype (required): technical summary, troubleshooting/postmortem, workplace reflection, or reading/idea note.
- Article content or topic (required): existing article text, or topic + key points for a new draft.
- Constraints (optional): word count target, sections to preserve, language override.
If all inputs are present in the user's initial message, skip asking and proceed directly to Phase 2.
Phase 2 — Generator (load and produce)
Execute in fixed order:
- Load
references/style-profile.md — establish voice and stable trait rules.
- Load
references/workflow.md — apply the matching workflow for the current mode.
- Load
assets/article-structure.md — use the skeleton for the identified subtype as structural scaffolding.
- Load
examples/anti-pattern.md — cross-check the draft against known failure patterns before writing.
- Load
examples/good.md — use as voice calibration reference to align tone and structure.
- Apply the author's stable traits:
- pragmatic judgment,
- direct but reasoned tone,
- engineering tradeoff awareness,
- mild personal sharpness without empty emotional venting.
- Avoid copying weaknesses from older posts:
- no fragmented bullet piles,
- no weak hierarchy,
- no note-like stacking without transitions,
- no loose section boundaries.
- Prefer article-shaped prose; use lists only for inherently list-shaped content.
- Preserve core facts and intent unless the user asks for substantive changes.
- When revising: improve structure first, then wording.
- Keep final text in Chinese unless the user explicitly requests another language.
- Output the complete article.
Output Rules
- Start with a short lead-in or context when helpful.
- Use clear section hierarchy.
- Use paragraphs as the default form.
- Use lists only for inherently list-shaped content such as comparisons, steps, or categorized points.
- End with a grounded summary, not forced uplift.
Editing Priorities
Apply these priorities in order:
- Preserve meaning and viewpoint.
- Match the author's voice.
- Improve structure and hierarchy.
- Improve readability and transitions.
- Tighten wording and remove AI-style abstraction drift.
Resources
- Voice and style profile:
references/style-profile.md
- Writing and revision workflow:
references/workflow.md
- Good writing examples:
examples/good.md
- Anti-patterns to avoid:
examples/anti-pattern.md
1---2name: labali-blog-writing-style3description: Create, rewrite, or refine personal blog posts in Kingson Wu's established voice for Chinese technical essays, workplace reflections, and reading notes. Use when the task is to draft a new article, revise an existing post, or make AI-written content sound like the author's earlier blog voice while preserving core meaning and improving structure, hierarchy, and readability. Trigger phrases: "write a blog post", "blog writing", "rewrite article", "refine post", "写博客", "改文章", "写文章".4license: MIT5---67# labali-blog-writing-style89Use this skill when writing or revising blog articles for the user's personal blog in the user's established voice.1011## Runtime Inputs1213- Target article path or article topic.14- User intent: new draft, rewrite, refine, shorten, or expand.15- Existing article text when revising.16- Optional constraints such as word count, article type, or sections to preserve.1718## Core Goal1920Preserve the author's voice and judgment style while improving article quality.2122The target result is:2324- sounds like the author,25- keeps the original article's core meaning,26- has clearer structure than many older posts,27- reads like a finished article rather than scattered notes.2829## NEVER3031- Never produce fragmented bullet piles as the primary structure — use paragraphs as the default form.32- Never stack sections without transitions (note-like accumulation of disconnected blocks).33- Never use weak hierarchy where all headings carry the same visual weight regardless of content importance.34- Never output AI-style abstraction drift: phrases like "it's important to note that", "in conclusion", or "overall, this demonstrates".35- Never switch the output language to English unless the user explicitly requests it.3637## Mode × Subtype Routing3839Use this table to determine which file sections to load in Phase 2.4041### Mode → workflow section in `references/workflow.md`4243| Mode | Section to load |44|------|----------------|45| new draft | `## 1. New Article Workflow` |46| rewrite | `## 2. Rewrite Existing Article Workflow` |47| partial refinement | `## 3. Partial Refinement Workflow` |48| shorten | `## 4. Structure Rules` (no dedicated section — use structure rules as guide) |49| expand | `## 4. Structure Rules` (no dedicated section — use structure rules as guide) |5051### Subtype → skeleton section in `assets/article-structure.md`5253| Subtype | Section to load |54|---------|----------------|55| technical summary | `## Subtype: Technical Summary` |56| troubleshooting / postmortem | `## Subtype: Troubleshooting / Postmortem` |57| workplace reflection | `## Subtype: Workplace Reflection` |58| reading note / idea note | `## Subtype: Reading Note / Idea Note` |5960## Execution Contract6162### Phase 1 — Inversion (gather before generating)6364DO NOT proceed to Phase 2 until all required inputs are known.6566Ask the user for any missing required inputs:67681. **Mode** (required): new draft, rewrite, partial refinement, shorten, or expand.692. **Subtype** (required): technical summary, troubleshooting/postmortem, workplace reflection, or reading/idea note.703. **Article content or topic** (required): existing article text, or topic + key points for a new draft.714. **Constraints** (optional): word count target, sections to preserve, language override.7273If all inputs are present in the user's initial message, skip asking and proceed directly to Phase 2.7475### Phase 2 — Generator (load and produce)7677Execute in fixed order:78791. Load `references/style-profile.md` — establish voice and stable trait rules.802. Load `references/workflow.md` — apply the matching workflow for the current mode.813. Load `assets/article-structure.md` — use the skeleton for the identified subtype as structural scaffolding.824. Load `examples/anti-pattern.md` — cross-check the draft against known failure patterns before writing.835. Load `examples/good.md` — use as voice calibration reference to align tone and structure.846. Apply the author's stable traits:85 - pragmatic judgment,86 - direct but reasoned tone,87 - engineering tradeoff awareness,88 - mild personal sharpness without empty emotional venting.897. Avoid copying weaknesses from older posts:90 - no fragmented bullet piles,91 - no weak hierarchy,92 - no note-like stacking without transitions,93 - no loose section boundaries.948. Prefer article-shaped prose; use lists only for inherently list-shaped content.959. Preserve core facts and intent unless the user asks for substantive changes.9610. When revising: improve structure first, then wording.9711. Keep final text in Chinese unless the user explicitly requests another language.9812. Output the complete article.99100## Output Rules101102- Start with a short lead-in or context when helpful.103- Use clear section hierarchy.104- Use paragraphs as the default form.105- Use lists only for inherently list-shaped content such as comparisons, steps, or categorized points.106- End with a grounded summary, not forced uplift.107108## Editing Priorities109110Apply these priorities in order:1111121. Preserve meaning and viewpoint.1132. Match the author's voice.1143. Improve structure and hierarchy.1154. Improve readability and transitions.1165. Tighten wording and remove AI-style abstraction drift.117118## Resources119120- Voice and style profile: `references/style-profile.md`121- Writing and revision workflow: `references/workflow.md`122- Good writing examples: `examples/good.md`123- Anti-patterns to avoid: `examples/anti-pattern.md`