# Content Method

## Table of Contents

- 1. Angle check
- 2. Human and AI boundary
- 3. Long-form archetypes
- 4. Progression devices
- 5. Default article flow

## 1. Angle Check

Before expanding a topic into a full piece, check whether it has at least two of these three forces:

- curiosity: does it make the reader want to know what happened next
- information: does the reader learn something concrete
- resonance: does it hit a feeling, dilemma, or lived problem

If the topic only has one weak force, improve the angle before drafting.

To improve the angle, look for:

- one specific scene
- one concrete tension
- one real question the writer actually cares about
- one visible case, person, or decision

## 2. Human and AI Boundary

Use AI for:

- structure suggestions
- counterpoints and supporting context
- analogy candidates
- background knowledge phrasing
- expansion after the angle is already clear

Keep on the human side:

- firsthand observation
- real emotional memory
- decisive judgment
- real lived detail
- verifiable facts tied to the writer’s biography

If the source lacks a real scene or real detail, do not fake one. Say less, or admit the uncertainty.

## 3. Long-Form Archetypes

### 3.1 Firsthand Experiment

Use when the article comes from the writer actually trying something, testing something, or stepping into a situation.

Push on:

- what triggered the attempt
- what happened step by step
- where expectation broke
- what changed in the writer’s understanding

### 3.2 Product Experience

Use when the writer is taking the reader through a tool, product, workflow, or new practice.

Push on:

- the concrete use scene
- the real feeling during use
- what worked, what did not
- how this compares to the old way

### 3.3 Phenomenon Breakdown

Use when the article starts from an observed pattern, cultural moment, or strange fact.

Push on:

- the observed phenomenon
- the first obvious explanation
- the deeper question beneath it
- the larger insight that naturally follows

### 3.4 Method Note

Use when the writer is sharing lessons, process, or advice.

Push on:

- humble opening instead of expert posture
- one concrete action per section when possible
- real cost, friction, and failure curve
- what the writer still has not solved

## 4. Progression Devices

### 4.1 Open From Something Happening

Prefer an opening that begins from:

- a moment
- a scene
- a fact that feels slightly off
- a question that is already alive

Avoid opening from a doctrine, slogan, or macro thesis unless the user explicitly asks for that tone.

### 4.2 Keep the Mainline Visible

When the article temporarily moves into history, theory, or example, bring it back with a short tether line.

Useful jobs:

- remind the reader what problem the article is solving
- show why the digression matters
- return the focus without sounding mechanical

Useful shapes:

- 说回前面那个问题。
- 这也是我前面为什么一直提这件事。
- 回到这篇文章真正想聊的点。

### 4.3 Unpack in Layers

Instead of stating the final insight immediately, use:

1. observation
2. surface explanation
3. deeper question
4. sharper insight

This keeps the reader inside the thinking process.

### 4.4 Reveal Cases One by One

When comparing several tools, examples, or cases:

- do not dump the full conclusion first
- reveal them one by one
- let the order escalate from ordinary to strongest
- add a short reaction or judgment when it helps

Use this only when the sequence improves curiosity and momentum.

### 4.5 Respect the Other Side

Before pushing a strong judgment, show that you understand:

- why someone would disagree
- why a reader might hesitate
- what a different life situation would make reasonable

This makes the argument sound lived and fair instead of preachy.

### 4.6 Close With a Return

For longer pieces, prefer an ending that returns to:

- the opening image
- the opening question
- a repeated phrase with new meaning
- a more grounded version of the initial feeling

Do not force a callback if the piece has not earned it.

## 5. Default Article Flow

Use this as the default long-form flow unless the source clearly wants something else:

1. open from a concrete scene, fact, or tension
2. give only enough background for the reader to stay with you
3. move through the core argument with visible cases and personal ownership
4. use tether lines whenever the article briefly expands outward
5. broaden only when the larger reference feels natural
6. close with a return, a decision, or a real lingering question

Formatting defaults for personal long-form pieces:

- prefer prose over bullet lists
- prefer spoken transitions over heavy subheads
- use headings only when the structure truly needs them