# Creativity Workflow

This skill should preserve creativity by separating idea generation from execution.

## Stage A: Diverge

Before writing or publishing, produce:

- 2 or 3 possible content angles
- 2 or 3 possible title directions
- 2 or 3 possible structural approaches when structure is not obvious

The output of this stage should help answer:

- Which angle best serves the reader?
- Which angle best fits the blog's long-term content asset?
- Which angle should be rejected even if it is creative?

## Stage B: Converge

Pick one final direction and record:

- `selectedAngle`
- `alternativesConsidered`

Execution should begin only after the final direction is chosen.

## Voice Rules

When writing article copy for this project:

- Use `我们` for our own project, product decisions, and implementation choices.
- Avoid detached phrases such as `项目维护者` when the article is speaking about our work.
- Keep the tone like an experienced developer explaining things to a friend: direct, useful, and relaxed.
- Be confident about our project features when they are relevant, but do not inflate claims beyond the actual behavior.
- Prefer concrete examples and small judgments over academic framing.

## Content Layout Rules

Plan these before drafting:

- Opening paragraph: include the core keyword and state exactly what the article covers.
- Tables: use comparison tables for tradeoffs, alternatives, feature differences, version differences, and troubleshooting choices.
- Code blocks: add comments that explain intent, inputs, outputs, or risky lines.
- Section endings: add a short takeaway sentence when it helps search engines and readers extract the point.
- Disclaimer: add one at the end for gray-area technical content, including security bypasses, scraping, reverse engineering, or automation against third-party platforms.

## Anti-patterns

Do not:

- jump directly from a topic to a finished article with no alternatives
- use monetization as a substitute for content quality
- overfit every post to SEO at the cost of voice or clarity
- use a single rigid template for every article
- bury the target keyword so deep that the first paragraph does not reveal the article topic
- publish complex code snippets with no comments
- use AI-flavored filler phrases such as `说白了`, `不得不说`, `众所周知`, or `接下来我们将探讨`
- lean on repeated transition scaffolding, especially `不是...而是`